c0881ba2d5
Similar to the Sheevaplug fix inf95f8b70fbd0f7e9c91a2d9006b1abb2dd07ebf2 the OpenRD device has its JTAG interface on the first channel of the ft2232, which is 0 for the new driver but was 1 for the old one. Correct the config file appropriately. Also the device description was missing the trailing " B" and thus not picking up the device correctly. Finally add an adapter_khz setting in the OpenRD board configuration file - set to 2MHz to match the Sheeva variant. Confirmed as working thanks to Phil Hands providing me access to his hardware to test on. See also Debian Bug#793214; https://bugs.debian.org/793214 Change-Id: Ifacf53124eaa330bbbdf36dfa79e3256bf2a5201 Signed-off-by: Jonathan McDowell <noodles@earth.li> Reviewed-on: http://openocd.zylin.com/4254 Tested-by: jenkins Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk>
15 lines
316 B
INI
15 lines
316 B
INI
#
|
|
# Marvell OpenRD
|
|
#
|
|
# http://www.marvell.com/products/embedded_processors/developer/kirkwood/openrd.jsp
|
|
#
|
|
|
|
interface ftdi
|
|
ftdi_device_desc "OpenRD JTAGKey FT2232D B"
|
|
ftdi_vid_pid 0x0403 0x9e90
|
|
ftdi_channel 0
|
|
|
|
ftdi_layout_init 0x0608 0x0f1b
|
|
ftdi_layout_signal nTRST -data 0x0200
|
|
ftdi_layout_signal nSRST -noe 0x0400
|