Category: Configuration/Programming
tool:-
device:-

If you are using the USB-Blaster™ II or the On-Board USB-Blaster II development kit, try lowering the JTAG Clock (TCK) frequency to see if the symptoms improve.

$ jtagconfig --setparam "USB-BlasterII [USB-0]" JtagClock 16M

If the following message appears, there may be a problem with the JTAG chain on the board, so please check the hardware, such as whether the DIP switch settings on the development kit are correct.

<Message>
Unable to read device chain - JTAG chain broken

If the following error occurs, the cable name may be incorrect. Enter just jtagconfig to check the cable name, then try again with the correct cable name.

<Message>
Error when scanning hardware - No devices

example:
In this example, the cable name will be "Helio [USB-1]".

$ jtagconfig
1) Helio [USB-1]
Unable to read device chain - JTAG chain broken