Thank you.
I have to go, but what I can see is that the result with a
500khz-no-RTCK is the same as 30MHz-with-RTCK !
With this info, this should be not an trouble regarding a RTCK not
comming, and not an JTAGkey-2 trouble but an trouble coming from an
higher layer of the openocd code.
I will try to have a deeper view on Monday.
Regards,
Laurent
http://www.amontec.com
Koeller, T. wrote:
Hi Laurent,
After restarting both your Amontec JTAGkey-2 and your TI
davinci board,
does openocd stop ever at the same command line ? (OpenOCD is able to
detect the davinci correctly, then break)
Yes, if I do a clean start after unplugging the adapter and
powering off the board, it always starts successfully (well,
at least it did every time I tried so far).
If not we could reach an unstable JTAG signals, termination line...
If yes, the problem is really coming from the OpenOCD in
this case, we
need more detail :
- Could you please run 1. and 2. with debug level d3 ?
I did - see attached files good_start.log, bad_start.log and
nand_access.log.
- Could you please try to deactivate the RTCK ( RCLK -
adaptive clock )
and run at low frequency with adapter_khz 500 -> and let me know the
same debug level d3.
Did that too - see files good_start_500kHz.log and
bad_start_500kHz.log.
Thanks for the quick response!
Thomas
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
