
You should see a few toggles of CCLK, then CSO_B goes low, and the next 8 clocks deliver the Read command (see the attached image for VS = 111). If you are seeing CCLK and CSO_B, then PROG and INIT are in the correct states. I'd also double-check that nothing else is driving your VS pins into an unknown state.
Spi serial flash programmer schematic symbol serial#
If you have a serial Flash test you can run from the FPGA (MicroBlaze is great for this), that will verify the physical connections.

that the 1200E's dedicated MOSI pin is hooked up correctly and that nothing else is driving it during configuration. Double-check your schematic, FPGA symbol, PCB, etc. Since you're not getting anything on the MOSI pin, I'd start there. In my design, there is another 32-bit microprocessor on the board, there are some interfaces between the microprocess and the FPGA, canthese interfaces cause the problem? So I think I should be able to see commands coming out from MOSI, if it works well.Ĥ. While i was monitoring the MOSI pin, I repeatly hold PROG_B signal low and release it. But I cannot see the startup commands sent out from the MOSI pin of FPGA and the reply from the SPI. By using the scope, I could see the CCLK signal, and the CSO_B was logic '0'. In case that this problem related to the power up sequence of the FPGA and the SPI flash, I tried to hold the PROG_B signal to logic zero for sometime, then release it. Write FDRI issued before or after decrypt operation: 0ĭecryptor keys not used in proper sequence : 0Ģ. IDCODE not validated while trying to write FDRI : 0 Maximum TCK operating frequency for this device chain: 10000000.īoundary-scan chain validated successfully. *** BATCH CMD : ReadStatusRegister -p 1

But I cannot configure the FPGA through the SPI flash.ġ.The following is what I got from "read the status register" using JTAG, after I tried to start the FPGA from the SPI. Also I can program the SPI flash by "direct programming using iMPACT". In the board, I use master SPI mode to configure the FPGA, and the SPI device is AT45DB642D. I am dubugging a new board which uses xc3s1200e.
