>/ Hello David,
/>/ I am not so sure about this. Still smells like reset problem to me.
/>/
/>/ It should be noted that when I let small bootloader execute from the
/>/ SPI flash and do the reset (and some other config), I can attach  with
/>/ OpenOCD, i.e. chain is well scanned. I was able after attachment to
/>/ set-up SDRAM and launch eCos application (which would further
/>/ configure SoC). Now I erased the flash and tried without bootloader. I
/>/ do not exactly know what bootloader is doing (have not insight in the
/>/ code yet), but obviously nothing expect reset is needed for a proper
/>/ chain scanning.
/>/
/>/ It should be also noted that Lauterbach jtag attaches without any
/>/ problems. I do not think that it does anything special for this step.
/>/ All what is needed after is few lines of SDRAM set-up and application
/>/ can be uploaded and run. But that comes after attachment (as for
/>/ OpenOCD).
/>/
/>/ All this confirms that hardware is working properly. I am almost
/>/ convinced that bug is either on OpenOCD side (I tried with both ftd
/>/ libs) or I should configure reset in some special way...
/>/
/>/ Would anybody have some hints after these additional explanations ?
/>/
/>/ Best regards,
/>/ Drasko
/>/ /It is not coming from your JTAGkey-2 since you can scan and detect the chain after configuration of your system.

It is really somewhere in the OpenOCD .

But you could try to disable the use of RTCK feature from the Amontec JTAGkey-2 and run at a super low frequency before doing your scan chain detection.

Also, could you please try to disconnect the JTAGkey from USB port before doing this. OpenOCD is still not really clean regarding the finish using the Amontec JTAGey as other FT2232 USB JTAG dongle before closing its handle in mpsse mode.

The sequence before closing the JTAGkey as other FT2232 USB JTAG dongle should be :
- 1. place all pin as input
- 2. quit the mppse bitbang mode
- 3. close the handle

CLEAN AFTER COMING :-)

the 1. and 2. are NOT DONE in the actual OpenOCD and it can make trouble when you close and re-open the openocd.

Let us know the debug output in this case.

Regards,
Laurent

 http://www.amontec.com
Amontec USB JTAG cable suite : JTAGkey JTAGkey-2 JTAGkey-3 ( coming soon with SWD support )
Before starting openocd with Amontec JTAGkey-2,
- the two Green LEDs should be 'ON'
- the Red LED should be 'OFF'
- the Yellow LED should be 'OFF'

(this is not the case after closing openocd and restarting openocd, since the openocd do not implement the 1. 2. as explained before )

The internal greenn LED comes 'ON' when the host computer enumerated the Amontec JTAGkey-2. OFF if in suspend mode.

The external greenn LED comes 'ON' if the Voltage target VREF is present and between 1.3V to 5.5V. OFF if no VREF or SUSPEND mode.

The red LED of the JTAGkey-2 and JTAGkey-2P let see the signal status of the TMS between the FT2232 and the UHS buffer. (UHS buffer are 2x faster than LVTTL making the 30MHz possible on the JTAGkey-2 from 1.3V to 5.5V / tested on Xilinx spartan -3a )
'ON' if TMS from FT2232 driven to '0'

The yellow LED of the JTAGkey-2 and JTAGkey-2P let see if a output signal is active between the FT2232 the UHS buffer.
'ON' if any of TCK TMS TDI SRST TRST are driven by FT2232 to UHS buffer
'OFF' if all the TCK TMS TDI SRST TRST are not driven.
(The yellow is controled by all the output enable of each signal)

The LEDs on the Amontec JTAGkey-2 can serve to certify the state of the FT2232 before open the device in mode mpsse, and closing from the mpsse. This make the Amontec JTAGkey-2 and Amontec-2P unique !

Note: P of Amontec JTAGkey-2P is for voltage Pump on pin 19 of the 20-pin connect. On Amontec JTAGkey-2P, the voltage Pump, called sometimes VPUMP, provides 3.3V @ 500mA on pin 19 .

Best regards,
Laurent
http://www.amontec.com
Amontec USB JTAG cable suite : JTAGkey JTAGkey-2 JTAGkey-3 ( coming soon with SWD support )








_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to