With the Cyclone III starter board my USB-JTAG pod fails to configure the board. The error in the Quartus message window is: Error (209014): CONF_DONE pin failed to go high in device 1 The on board usb blaster works fine (just remove jumper JP8 to select the onboard mode). The strange thing is it worked briefly (when I showed a colleague of course). While it worked I moved the pod around to see if the cable was the issue, but it kept working. Once I power cycled the board it stopped working in jtag mode (but the onboard circuit always works). My brand new boards have the same problem - but only jtag mode, so I can not use any onboard blaster. With both boards the pod always detects the device ok, and gives reasonable sounding errors if I power off the board etc. The debug Pod I have is a "USB blaster" rev B, with a ribbon cable that ends in a 10 pin header. I am using JTAG mode so the MSEL pins are over-ridden, and I can not think of any other reasons why it should fail. Thank you for your time and any advice you can give on this. Steve

--- Quote Start --- Thank you for your time and any advice you can give on this. --- Quote End --- Probe the JTAG pins with a scope. Make sure you use a short ground lead, eg., I'll often solder a loop of wire to a nearby capacitor ground and then loop that around the scope tip. Look at the signal integrity of the TCK pin first; look for ringing and a dip in its rising-edge (which can be caused by a transmission line reflection on that trace). Check the voltage high and low values of the signals. Compare those to the limits stated in the device handbook. Cheers, Dave

Thank you Dave. I looked at the signals: The JTAG pins look pretty good - overshoot / undershoot is about 200mV. On the starter kit the JTAG signals are buffered with an octal bus switch that is near to the header. The bus switch should be able to cleanup the small bit of ringing. Running the JTAG chain debugger reports that the connection is good and consistent after 1000 IDCODE tests. I could load the software on a different PC (use XP instead of Win7). Is there a reasonable chance that could be an issue? Thank you, Steve

--- Quote Start --- I could load the software on a different PC (use XP instead of Win7). Is there a reasonable chance that could be an issue? --- Quote End --- Loaded the software on XP - everything behaves the same as it did on Win7-32bit. Possibly its the pod? But it passed the jtag IDCODE tests...

--- Quote Start --- Possibly its the pod? But it passed the jtag IDCODE tests... --- Quote End --- Depending on how they generate the IDCODE, you might have a problem with TMS or TDI. The IDCODE is loaded into the shift-DR register on TAP reset, i.e., TMS high and 6 TCK clocks. In that case, TMS does not get toggled. When the IDCODE is read out, TDI is a don't care, so that is also not tested. How about trying to read the USERCODE? Or put the device into BYPASS mode, and then just shift a bit pattern through the JTAG chain. Cheers, Dave

At a different location someone got the system working with a revC pod. I have ordered one from Amazon ($25!). Hopefully it will start working for me with the new usb blaster. Thank you, Steve

CONF_DONE in failed to go high jtag | Altera Community

14 Replies

Altera_Forum
Honored Contributor
14 years ago
The pod is surprisingly easy to open - has a little slot right on the lid. No warranty stickers.

Its the cypress micro inside, cy7c68013a.
After that there is a 74244, which is nice of them since it might keep the pod alive if I plug it in wrong. Or at least make it easier to fix :) (actually the 74244 is probably needed to set the the IO voltage levels)

With the pcb out of the case it seems the micro is the one that warms up the entire pod.

As soon as Chinese new year is over I am getting the Terasic pod. They are closed until the 30th.

Thank you,
Steve
Altera_Forum
Honored Contributor
14 years ago
--- Quote Start ---
The pod is surprisingly easy to open - has a little slot right on the lid. No warranty stickers.

Its the cypress micro inside, cy7c68013a.
After that there is a 74244, which is nice of them since it might keep the pod alive if I plug it in wrong. Or at least make it easier to fix :) (actually the 74244 is probably needed to set the the IO voltage levels)

--- Quote End ---

Ok, this is a Cypress FX2. The USB-Blaster protocol was reverse engineered by Kolja Waschk and he wrote the original version of this code. Its subsequently been reused to implement these clones.

--- Quote Start ---

With the pcb out of the case it seems the micro is the one that warms up the entire pod.

--- Quote End ---

It shouldn't. The FX2 only draws a few milliamps. I wonder if they have an error in their firmware.

--- Quote Start ---

As soon as Chinese new year is over I am getting the Terasic pod. They are closed until the 30th.

--- Quote End ---

If you want to 're-task' your Cypress pod as a microcontroller development kit, let me know, and I'll post links to the Cypress FX2 download tool, and the open-source SDCC compiler.

Cheers,
Dave
Altera_Forum
Honored Contributor
14 years ago
Good news -
I took the ribon cable from the clone board and used it with the rev B usb blaster. Now everything works fine.
It could be that I have a bad cable, but the posts at http://www.alteraforum.com/forum/showthread.php?t=21949 seemed like the cable is an issue.

Could you provide the like to the cypress dev kit and compiler? I have a couple projects that could use something in this form factor (and price range)!

Thank you,
Steve
Altera_Forum
Honored Contributor
14 years ago
--- Quote Start ---

Could you provide the like to the cypress dev kit and compiler? I have a couple projects that could use something in this form factor (and price range)!

--- Quote End ---

I installed EZ-USB_devtools_version_261700.zip which is available from here:

http://www.cypress.com/?rid=14319

It installs an old version of Keil uVision (version 2).

The installation has example code.

You can also use the open-source SDCC compiler to generate 8051 code. Send me an email and I'll send you a couple of blinky LED examples (I've only just started tinkering with an FX2 board).

You'll need to know which pins/ports on the micro are connected to your USB-Blaster interface. Once you figure that out, you'll have yourself a GPIO board.

Cheers,
Dave

Forum Discussion

CONF_DONE in failed to go high jtag

14 Replies

Recent Discussions

Access to System MAX design for Agilex 5 kit

Arrow AXE5 Eagle Board JTAG issue

Cyclone 10 LP Evaluation Kit - Documentation

AGILEX 5 cvp mode

PDN file and PCB decoupling