On Thu, Mar 17, 2011 at 2:50 PM, Laurent Gauch <[email protected]> wrote: > Hi Mathias K., > > You have this command buffer > > 4b 02 01 39 02 00 00 c0 04 3b 06 80 6b 01 81 4b 02 03 > > 4b 02 01 / TMS shift no read > 39 02 00 00 c0 04 / IN OUT 3 bytes read > 3b 06 80 / IN OUT 1 byte read > 6b 01 81 / TMS shift 1 byte read > 4b 02 03 / TMS shift no read > > This command buffer should return 5 bytes data.
Thanks a lot Laurent for this dissecting. > > There are no reason here the Amontec JTAGkey-2 do not send back the 5 bytes, > except if you have RTCK return clock enabled !!! RTCK is not enabled, I double-checked. JTAG speed is : adapter_khz 1000. CPU freq should be around 12MHz, so this speed should be quite OK. SDRAM initialization sequence and smaller files writes works quite right at these speeds. Larger images writes have this error. > > But a bad previous command buffer could corrupt the JTAGkey-2 ft2232 mpsse > interface. > > Please send me the complet debug file . Hmm... I'll have to see how I can do this. The file is almost gigabyte in size. Maybe you can point me what to look for in the log, or which parts would be significant ? > > Also, could you please try the same with Amontec JTAGkey D22X WHQL certified > driver you found at > http://www.amontec.com/download/amontec-jtagkey-driver-d2xx-20091124.zip I'll try these and keep you informed. BR, Drasko _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
