[email protected] wrote on 2009-08-18 15:37:14:
> It's not all I want it to be, but it's more than what I started with.
> I hope it helps someone else.
>
> Best!
>
> Brian Findlay
> [attachment "mini2440.cfg" deleted by Jonas Horberg/Alm/Sauer]
======From mini2440.cfg=====
[snip]
# JTAG ADAPTER SPECIFIC
# IMPORTANT! Any JTAG device that uses ADAPTIVE CLOCKING will likely
# FAIL as the pin RTCK on the mini2440 10 pin JTAG Conn doesn't exist.
# This is Pin 11 (RTCK) on 20 pin JTAG connector. Therefore it is
# necessary to FORCE setting the clock. Normally this should be
configured
# in the openocd.cfg file, but was placed here as it can be a tough
# problem to figure out. THIS MAY NOT FIX YOUR PROBLEM.. I modified
# the openOCD driver jlink.c and posted it here. It may eventually end
# up changed in openOCD, but its a hack in the driver and really
should
# be in the jtag layer (core.c me thinks), but haven't done it yet. My
# hack for jlink.c may be found here.
[snip]
#-------------------------------------------------------------------------
# JTAG ADAPTER SPECIFIC
# IMPORTANT! See README at top of this file.
#-------------------------------------------------------------------------
jtag_khz 12000
jtag_rclk 3000
jtag interface
[snip]
=========end===========
I believe that the JTAG speed setting belongs to the board configuration
file
(the placement is correct), but the jtag_rclk speed request command shall
not be used for boards without RTCK. It do not make sense to use both the
jtag_khz and jtag_rclk command in the configuration state. The one that is
used latst in the script will be used when the interface is initialized.
The Mini2440 lacks RTCK support so jtag_rclk should be removed and
jtag_khz kept. There is a mismatch in the 12MHz and 3MHz parameters
so it is unclear which of them is valid.
Best regards
Jonas Hörberg_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
