Is it possible to get the complete Vivado 2018.2 project with SDK files to restore the Cmod A7 devices back to OOB? The provided OOB project does not include the AXI Quad SPI component so it doesn't seem to me that the provided OOB project files are what were originally used to generate the image. Maybe they are and some other method was used to preload the memorytest (knowing that procedure would be useful too).
I have used the "How To Store Your SDK Project in SPI Flash" guide to program the flash when using a Microblaze design but it would seem that it wouldn't work for the OOB program because the guide has the program loaded from QSPI to the external memory which in theory would get corrupt once the memory test is started. I could be wrong about that but it seems the most logical outcome of a memory test. So I'm guessing the memorytest was really loaded to BRAMs instead of external memory and getting an example of that would be useful.
The reason I ask is that I have been having a lot of issues flashing the QSPI with Microblaze designs. I get a lot of failures while flashing and when it does flash correctly it suffers from not starting until the reset button is pushed. I have seen some suggest that changing the FPGA configuration to SPI x1 fixes the issue I don't see how changing the initial load to SPI x1 mode affects the QSPI reads after the FPGA is already configured and should be executing code from the Microblaze.
I have a complete step by step procedure to my build, if that helps. I haven't ruled anything out but something isn't right.
Question
LucAce
Is it possible to get the complete Vivado 2018.2 project with SDK files to restore the Cmod A7 devices back to OOB? The provided OOB project does not include the AXI Quad SPI component so it doesn't seem to me that the provided OOB project files are what were originally used to generate the image. Maybe they are and some other method was used to preload the memorytest (knowing that procedure would be useful too).
I have used the "How To Store Your SDK Project in SPI Flash" guide to program the flash when using a Microblaze design but it would seem that it wouldn't work for the OOB program because the guide has the program loaded from QSPI to the external memory which in theory would get corrupt once the memory test is started. I could be wrong about that but it seems the most logical outcome of a memory test. So I'm guessing the memorytest was really loaded to BRAMs instead of external memory and getting an example of that would be useful.
The reason I ask is that I have been having a lot of issues flashing the QSPI with Microblaze designs. I get a lot of failures while flashing and when it does flash correctly it suffers from not starting until the reset button is pushed. I have seen some suggest that changing the FPGA configuration to SPI x1 fixes the issue I don't see how changing the initial load to SPI x1 mode affects the QSPI reads after the FPGA is already configured and should be executing code from the Microblaze.
I have a complete step by step procedure to my build, if that helps. I haven't ruled anything out but something isn't right.
Cmod-A7-35T.xdc
Steps.txt
user_35t_bd.tcl
Link to comment
Share on other sites
2 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.