Forum Discussion
in MAX 10 Dev kit
Hi Altera Community,
I am encountering a JTAG Server Error Code 35 when attempting to program my MAX 10 Development Kit using the USB-Blaster.
Below are the details of my setup and the issue:
Board: MAX 10 Development Kit
Programmer Cable: USB-Blaster
Problem Description:
When opening the Quartus Programmer and clicking Start (or running Auto Detect), the process fails with the following log:
Error (209053): Unexpected error in JTAG server -- error code 35 Error (209040): Can't access JTAG chain
6 Replies
- sstrell
Super Contributor
Which exact kit is this? Does it need a separate power supply or is it powered by the USB?
- Hetvi
New Contributor
ITS POWERD VIA USB ...ATTACHING THE DEV KIT LINK MAX® 10 FPGA 10M08 Evaluation Kit (POWER SOL'N 1) | Altera
- sstrell
Super Contributor
Stupid question: you're powering the board via USB power and using a separate 10-pin USB Blaster cable for configuration? This board does not appear to have an on-board USB Blaster so you need the standard 10-pin JTAG connection to the board. You can't program the device with just the USB connector.
https://docs.altera.com/r/docs/812857/current/max-10-fpga-10m08s-evaluation-kit-user-guide/supported-items-not-included-with-the-kit
- Hetvi
New Contributor
Yes, exactly. I am powering the board separately via USB and using a dedicated 10-pin USB-Blaster connected to the JTAG header for configuration.
- AqidAyman_Altera
Regular Contributor
Hi,
Error 209053 ("Unexpected error in JTAG server — error code 35") is a JTAG server communication fault, and it typically surfaces together with Error (209040): "Can't access JTAG chain," which can be caused by a download cable problem, TDO not connected properly, a noisy TCK signal, or TDI shorted to GND.
Refer here: Error: Cant access JTAG chain
I can give you the suggestion on the step-by-step troubleshooting as below:
- Check physical connectivity and board power first.
- Verify TCK signal integrity.
- Try a different USB-Blaster cable.
- Check for a JTAGServer service conflict.
- Check for the virtual JTAG device on the JTAG chain.
- Check for a JTAG Secure mode conflict (if applicable).
- Check cable driver installation.
- FvM
Super Contributor
Hi Hetvi,
to exclude one possible issue, what's the exact USB Blaster model you are using? Some cheap clones are not working with recent drivers, due to an intentional incompatibility built-in by chip vendor FTDI.
Regards Frank