Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
17117 Discussions

Sof file cannot be written.

Yamada1
Beginner
2,211 Views

As the title suggests, sof files cannot be written.

When the sof file is written, the following message appears and ends.

Error (209040): Can't access JTAG chain

Error (209015): Can't configure device. Expected JTAG ID code 0x02EE30DD for device 1, but found JTAG ID code 0x00000000. Make sure the location of the target device on the circuit board matches the device's location in the device chain in the Chain Description File (.cdf).

Error (209012): Operation failed

 

The device is recognized by "Auto Detect", and there is no particular abnormality in JTAG Chain Test.

Also, there was no difference between the device name detected by "Auto Detect" and the device specified in the design.

What are the possible factors?

 

It would be helpful if you could give me a hint to solve the problem.

Labels (1)
0 Kudos
1 Solution
WZ2
Employee
2,170 Views

Hi there,

There are some points I wanna make sure at first:

  1. What is the series of your FPGA?
  2. What is the failure rate for this issue (failed board/ total board)? 

The JTAG id 0x00000000 seems strange. Please try to change the line or port on your computer.

By the way, how you confirm “there is no particular abnormality in JTAG Chain Test”. It's also possible that the FPGA is damaged.

Best regards,

WZ


View solution in original post

0 Kudos
3 Replies
WZ2
Employee
2,171 Views

Hi there,

There are some points I wanna make sure at first:

  1. What is the series of your FPGA?
  2. What is the failure rate for this issue (failed board/ total board)? 

The JTAG id 0x00000000 seems strange. Please try to change the line or port on your computer.

By the way, how you confirm “there is no particular abnormality in JTAG Chain Test”. It's also possible that the FPGA is damaged.

Best regards,

WZ


0 Kudos
Yamada1
Beginner
2,163 Views
Thank you for your comment.
 
I'm sorry to trouble you, but I solved it by myself.
It turned out that the cause was that the response to the load of the core power supply was slow, so it was not able to respond to the current increase immediately after the end of sof writing, and the voltage was below the operating limit voltage.
 
Sorry for the trouble.
 
0 Kudos
WZ2
Employee
2,145 Views

Hi there,

I am glad to see that the problem solved.


I wanted to check if you have any further questions or concerns. If not, I will go ahead and mark this issue as resolved.

Additionally, we would greatly appreciate it if you could take a moment to fill out our survey. Your feedback is valuable to us and helps us improve our support quality.

Thank you for your time and cooperation.

Best regards,

WZ


0 Kudos
Reply