Forum Discussion
Occasional ContributorError (209014): CONF_DONE pin failed to go high in device 1.
I want to flash a simple led blink code bitstream file in Cyclone V E Dev kit using USB blaster. When I am trying to flash using USB blaster I am getting below error:
Error (209014): CONF_DONE pin failed to go high in device 1. Make sure all communication cables are securely connected, select a different device, check the power on the target system, or make sure all nCE pins are connected to GND. The Intel FPGA Knowledge Database contains many articles with specific details on how to resolve this error. Visit the Knowledge Database at https://www.altera.com/support/support-resources/knowledge-base/search.html and search for this specific error message number.
I tried to configure the DPI switch below combination:
DPI SW1.1 =ON, 1.2 = ON, 1.3=ON, 1.4=ON
DPI SW2.1=OFF,2.2=ON,2.3=OFF,2.4=OFF
& same switch i tried
DPI SW2.1=ON,2.2=ON,2.3=OFF,2.4=OFF
DPI SW4.1=ON,4.2=OFF,4.3=OFF,4.4=OFF
When I am opening programmer and hardware setup USB Blaster is coming and then I am performing auto detect and it is showing 3 options:
5CEBA7
5CEFA7
5CEFA7ES
I choose 5CEFA7 and then change the files and choose configure and the start. But after 32% it is showing failed and i am getting the error message. Can anyone plese suggest do I set the DPI switch correctly or shall I miss anything.
14 Replies
FvMSuper Contributor
Hi,
Altera CVE board has als built-in USB Blaster II. Did you try to program via this interface? Sure the generated .sof is for the right FPGA type? You can also try *.sof example files shipped with the board. Installation package still available at altera.com for download. Cyclone® V E FPGA Development Kit | Altera
Regards
Frank
Sameer-sahuHi FvM ,
I have tried to use built-in USB Blaster then also I got the same error. When I tried to flash the .sof bitstream file at that time D11 led present in the board was glowing. When the failed message pop up then that led turn of. Below are my DPI switch setting:SW1 = keep factory/default MSEL setting
SW2-1 = OFF // MAX V CPLD 5M2210 System Controller in-chain
SW2-2 = ON // bypass HSMC port
SW2-3 = OFF // fan disabled
SW2-4 = OFF // reserved
SW4-1 = ON // select programmable oscillator clock
SW4-2 = OFF // enable on-board oscillator
SW4-3 = OFF // load factory design from flash at power-up
SW4-4 = OFF // embedded USB-Blaster II does not send FACTORY command at power-up. Can you please suggest do I miss any steps or share me some example code along with details procedure then it will fast the process instead of open forum. My mail id is [email protected].
FakhrulA_alteraRegular Contributor
Hi Sameer,
Thank you for the update.
From the screenshot, the device is detected in JTAG, so the USB-Blaster connection looks OK. The error at around 32% usually means the FPGA configuration did not complete, and CONF_DONE did not go high.
Please try the following next:
- Use the built-in USB-Blaster II on the Cyclone V E Development Kit.
- Confirm the .sof file is generated for the exact FPGA device on the board, for example 5CEFA7F31.
- Try programming one of the example .sof files from the Cyclone V E Development Kit design package.
- Keep the board DIP switch setting at the default/factory setting as listed in the development kit user guide.
If the example .sof file also fails with the same error, please share the Quartus version used and a clear photo of the board DIP switch settings.
Regards,
Fakhrul- Sameer-sahu
Hi FakhrulA_altera & FvM ,
Thanks for your valuable suggestion. I went through Cyclone V E dev kit user guide and set my DPI swichs to default mode. I am attaching the screenshot of my DPI switch setting as well as user guide suggested screenshot. Then I have tried to flash my led blink code as well
- Try programming one of the example .sof files from the Cyclone V E Development Kit design package.
from below websit:
https://docs.altera.com/v/u/resources/770950/cycloneve-5cefa7f31-fpga-v12.1.1.0.zip
Still I am getting the same error when I tried to use built in embedded usb blaster. For your reference I am attaching the screenshot. Could you please suggest do I miss anything it settings of DPI switches. I am using Quartus Prime 19.1 Lite edition.
Thanks & Regards,
Sameer
- FakhrulA_altera
Hi Sameer,
Thank you for checking with the default DIP switch settings and also trying the example .sof.
Since the same CONF_DONE error occurs with both your design and the official example .sof, this may not be related to your LED design. The next step is to isolate whether the issue is from the board setup or the configuration path.
Please help to check the following:
- Confirm the exact FPGA part number printed on the board/device matches 5CEFA7F31.
- In Quartus Programmer, try Auto Detect again and confirm the JTAG chain is detected correctly.
- Make sure only the correct .sof for 5CEFA7F31 is assigned to the FPGA device.
- Power cycle the board, then try programming again using the built-in USB-Blaster II.
- If possible, please share a clear screenshot of the Quartus Programmer setup, including the full JTAG chain and assigned .sof file.
As the example .sof also fails, the issue may be related to board configuration, power, or the CONF_DONE path rather than the design file itself.
Regards,
Fakhrul
- Try programming one of the example .sof files from the Cyclone V E Development Kit design package.
- Sameer-sahu
Hi FakhrulA_altera ,
Could you please suggest any feedback based on my previous replay. So that I can debug the Issue quickly.
- FakhrulA_altera
Hi Sameer,
Apologies for the delayed response.
Could you please refer to the following KDB articles for this specific CONF_DONE error?
- https://community.altera.com/kb/knowledge-base/why-do-i-receive-the-error-conf-done-pin-failed-to-go-high-in-device-x-when-i-tr/347292
- https://community.altera.com/kb/knowledge-base/error-conf-done-pin-failed-to-go-high-in-device-/340233
Please also try programming with the attached .sof file and confirm whether the same error is observed.
For the next step, could you please try the following?- Keep all DIP switches at the factory default setting.
- Remove any external connection or daughter card from the board.
- Power cycle the board.
- Program only the official example .sof file from the Cyclone V E Development Kit design package.
- If probing is available, please check the CONF_DONE, nSTATUS, and nCONFIG signal levels during programming.
Also, could you confirm how many Cyclone V E development kit boards show this same behavior out of the total boards tested?
Regards,
Fakhrul
- Sameer-sahu
Hi FakhrulA_altera ,
I will try this and let you know. - Sameer-sahu
Hi FakhrulA_altera ,
I have tried all the steps suggested by you. But still I am getting the same error. The DPI switchs are place by default attached in my previous message. How to check my JTAG is working or not?- FakhrulA_altera
Hi,
We would like to check if there are any updates regarding this issue.
As we have not received a response to our previous follow-up, this thread will be transitioned to community support. We hope your concerns have been addressed.
Should you require further assistance, please feel free to open a new thread. Otherwise, community users may continue to assist here.
Thank you.
- FakhrulA_altera
Hi Sameer,
Auto Detect showing the chain TDI > 5CEFA7 >5M2210Z > TDO confirms that the JTAG connection is working. Therefore, the USB-Blaster II and JTAG cable path are likely OK.
Since the same error occurs with the official example .sof file, default DIP switch settings, and no external cards connected, this is unlikely to be caused by your LED design or the .sof file.
Please check the following:- Confirm the FPGA marking on the board is 5CEFA7F31I7N.
- Use the supplied board power adapter and make sure the board power LEDs are normal.
- If available, measure nSTATUS and CONF_DONE during programming. nSTATUS should remain high after configuration starts, and CONF_DONE should go high when configuration completes.
- Try the board test software or factory design to check whether the board can run any known-good design.
If CONF_DONE remains low while using the official example .sof, the issue is most likely related to the board power or configuration circuitry, not the JTAG connection. In this case, please contact the board supplier or distributor for board-level support or replacement.
Regards,
Fakhrul
