cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Observer
Observer
145 Views
Registered: ‎10-07-2016

is SpiFlashProgrammer support 512Mb flash N25Q512

Hi,     I have some problems in my application.   

1   The "spiFlashProgrammer.vhd " module works normally at " A7-100t + N25Q256A13 ".   

     The size of update_image.bin is  4MB, and the module works correctly,  FPGA will work correctly after reboot.

     constant cAddrWidth : integer := 24;

     cAddrUpdateStart : std_logic_vector(31 downto 0) := X"00400000";

     cAddrUpdateEnd : std_logic_vector(31 downto 0) := X"00800000";

     cIdcode24N25Q : std_logic_vector(23 downto 0) := X"20BA19";

2    The "spiFlashProgrammer.vhd " module dose not work at " K7-325T  + N25Q512A13 .  ".   

     The size of update_image.bin is  8MB, set as below :

     constant cAddrWidth : integer := 24;  or  constant cAddrWidth : integer := 32; 

     cAddrUpdateStart : std_logic_vector(31 downto 0) := X"00800000";

     cAddrUpdateEnd : std_logic_vector(31 downto 0) := X"01000000";

     cIdcode24N25Q : std_logic_vector(23 downto 0) := X"20BA20";

     when I send erase command to the module,  I find the FSM works differently to" A7-100t + N25Q256A13 "  ,as show below:

As to 256Mb , the chipscope got FF from inSSDData8Receive . 

As to 512Mb , the chipscope got 00 from inSSDData8Receive , so the next state is right.

My question: 
1
  is this module support 512Mb flash  ?  how to fix this problem?

2  Should I adjust cSizeSector to fix this issue?

 4.png5.png6.png7.png

 

0 Kudos
1 Reply
Highlighted
Observer
Observer
132 Views
Registered: ‎10-07-2016

In N25Q512 situation, the erase state is wrong , I can get regEraseOK = 1 very quickly , less than 1 second . But in N25Q256 situation, I can get regEraseOK = 1 after at least 10 ~20 seconds , this is right.
0 Kudos