Forum Discussion
Examine CFI device and save data by command line
Hello,
I'd like to examine a CFI device and save data (POF or HEX) by command line like for chain device.
c:\intelFPGA_pro\18.1\qprogrammer\bin64\quartus_pgm -c "USB-BlasterII [USB-1]" -m JTAG -o e;CPLD_U25_dump.pof;EPM2210
or through CDF file.
How it can be done?
17 Replies
- leonidK
New Contributor
Hello,
I tried to work with Quartus 19.1 and now have a following problem.
Please look attached image.
The system has not recognized a CFI device S29GL256P.
What right name of the device?
- leonidK
New Contributor
A bit of help, please...
- FakhrulA_altera
Regular Contributor
Please be advised that due to the absence of a response from you regarding the previous notification we provided, we will be transitioning this thread to community support. If you have any new questions or concerns, we kindly suggest opening a new thread to receive assistance from Intel experts. However, if you do not have any further inquiries, the community users will be available to assist you on this thread. Thank you for your understanding.
- FakhrulA_altera
Regular Contributor
Hi leonidK,
I noticed that you are using Quartus 18.1. Based on the information I received internally, there is an issue in the CFI flash examination using the command line in 18.1.
In 18.1, the programmer is able to execute the examine operation but it didn't save the examined data into a POF file.
In 19.1, we fixed the issue where the programmer will automatically save the examined data into a POF file with default name of flash_examine.pof after the examine operation is completed. Hence, I would advise you to use Quartus 19.1.
Regards,
Fakhrul
- leonidK
New Contributor
Thank you.
I'll try it.
- FakhrulA_altera
Regular Contributor
Hi leonidK,
We still have not received any feedback from the software .eng team on this issue. It seems currently they are busy with higher critical/priority issues on their hand. I have filed an escalation regarding this issue and will be waiting for the feedback.
Sorry for the inconvenience caused.
Regards,
Fakhrul
- leonidK
New Contributor
Thank you.
- FakhrulA_altera
Regular Contributor
Hi leonidK,
My apologies for the delay in response. We had trouble accessing the platform to reply to the community forum on our end earlier this week. I just received feedback from one of the SMEs on this issue. Apparently, he said that this is a legacy device that needs some time for them to check it and escalation might be required for this as well to speed up the process. The earliest answer would be around next week, I will try to update with you again if there's any response from them. Sorry for the inconvenience caused.
Regards,
Fakhrul
- leonidK
New Contributor
Hello Fakhrul,
Please check the issue a.s.a.p.
I need to know is it possible or no.
- FakhrulA_altera
Regular Contributor
Hi leonidK,
My apologies. I'm still waiting for a response from the internal expert.
Let me follow up with them and get back to you.
Regards,
Fakhrul
- leonidK
New Contributor
I tried. It works for device in JTAG chain, but doesn't work for CFI device.
- FakhrulA_altera
Regular Contributor
Hi leonidK,
Sorry for the delay. It should be similar to this > -o e;file.pof;device_name -o ei;file.jic;device_name
Have you tried this one? You can refer in Quartus II Scripting Reference Manual - Intel
Let me know if this works.
Regards,
Fakhrul
- leonidK
New Contributor
I'm looking forward for your answer.