Success! Subscription added.
Success! Subscription removed.
Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your profile.
Hello,
I've been working on this problem for 3 days but still can't find a solution.
The background:
How the problem occured :
So far what i'm sure about:
What makes me confused:
Hope my question is clear enough.
Tell me if you need more information
Thanks !
Link Copied
Hi CLi19,
Can you check if the MSEL pins are correctly/properly set to AS mode? Also check the power supply to the EPCS64 to ensure the EPCS64 is power up. Use multi-meter or oscilloscope to check the voltage level on the MSEL pins and the EPCS64 power supply pin.
Regards,
Nooraini
Hi Nyosof,
Thanks for your answer.
I should add one more context : the epcs flash used is Cypress Spansion FL064PIF with SPI interface.
I did a few more investigation into the problem, here is what I got:
1.1 I tried msel(3 downto 0) = "1011" and "1101" and "1001" and "1010", nothing changed, still can't program the .jic, but .sof could be programmed.
1.2 I tried mesuring VCC, SCLK , CSn, SI and SO of the EPCS chip, it seems at board powering up, the fpga tried to send command to the Flash via SPI, I haven't yet investigated into the detail of those commands.
2. I changed to another "good" board. and I find the reason of BUG.
2.1 I re-programmed several times the new "good" board with old "good" .sof and .jic, all good.
2.2 I then found that I forgot to add the .sdc file in my "bug" project. So I add it and re-compile the project, re-programmed with the .sof and .jic, all good.
2.3 I then re-programmed this board with the "BUG" .jic, and like the first board, this board can't access to the Flash any more, but this time I can re-program the Flash, but when I power down and up the board, the fpga can't be configured by the Flash..
Due to my stupid tests, I now have two valuable boards non functionnal...
I wonder if my .jic wothout .sdc has destroyed the FPGA? but I can still program the .sof to fpga... i think i'm running into a situation super complicated...
Hope you can give me some advices.
Thanks very much.
Nooraini ,
We are having the same issue, and cannot use the method you suggested to erase the flash, as it still complains about the device ID. Also when we generated the JIC we tell it to disable ID checking!
Hi CLi19,
I assume that you are aware that currently we don't support Cypress Spansion for FPGA AS configuration scheme. JFYI, our Quartus programmer is validated and guarantee to correctly program only EPCQ-A and MT25Q devices. The current direction for low density EPCS and EPCQ EOL is to switch EPCQA device. You can refer to the PDN1708 and AN822 for the details in the following link:
https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/pcn/pdn1708.pdf
https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/an/an822.pdf
For high density EPCQ/EPCQL(=>256Mb), the plan is moving to support 3rd party flash devices starting from Quartus v18.1. However we have identify MT25Q flash family devices from Micron can be use as replacement for EPCQ/EPCQL(=>256Mb). You can refer to the following link for details:
Anyway, going back to this issue, have you try to perform full erase on the SPI flash device? Try to instantiate the SFL IP into the Cyclone IV design? You can refer to chapter 1.4.1 Instantiating the Intel FPGA Serial Flash Loader IP Core from the AN370 in the following link:
https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/an/an370.pdf
Create a custom design with just the SFL IP instantiated in the Cyclone IV proejct design. Set the unused pin option to reserve as input tristate. Please refer to the attached screen shot. Then recompile the design to get a new sof file.
Regards,
Nooraini
Community support is provided Monday to Friday. Other contact methods are available here.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
For more complete information about compiler optimizations, see our Optimization Notice.