interesting
/
riscv-openocd
mirror of https://github.com/riscv/riscv-openocd.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
riscv-openocd/tcl/interface/ftdi/olimex-arm-usb-ocd-h.cfg

15 lines
314 B
INI
Raw Normal View History

cfg: Add config file variants using the ftdi driver instead of ft2232 part 1 - files that were tested an verified as working fine Change-Id: If5986853a1cf118a9eb3b4c13b036d0f71c39624 Signed-off-by: Andreas Fritiofson <andreas.fritiofson@gmail.com> Signed-off-by: Freddie Chopin <freddie.chopin@gmail.com> Reviewed-on: http://openocd.zylin.com/534 Tested-by: jenkins
2012-07-19 02:30:27 -05:00
#
# Olimex ARM-USB-OCD-H
#
# http://www.olimex.com/dev/arm-usb-ocd-h.html
#
interface ftdi
ftdi_device_desc "Olimex OpenOCD JTAG ARM-USB-OCD-H"
ftdi_vid_pid 0x15ba 0x002b
interface/ftdi/olimex-arm-usb-ocd-h: fix nTRST control definition According to my inspection of an Olimex ARM-USB-OCD-H adapter ACBUS0 is connected directly to an SN74LVC2T45 buffer input B2, and the corresponding output A2 is connected directly to the JTAG connector. It seems the information in the Olimex flyer is incorrect for the -H version and TRST can't be tri-stated, ACBUS2 is unused. The older ARM-USB-OCD device has SN74AC244 for an output buffer and ACBUS2 controls its !2OE, ACBUS0 connected to 2A1 (2Y1 is nTRST), in accordance with the information flyer. Change-Id: I22828b7b959b6f62c3f51367feb8fab9705641e5 Reported-by: Tim Sander <tim@krieglstein.org> Signed-off-by: Paul Fertser <fercerpav@gmail.com> Reviewed-on: http://openocd.zylin.com/2286 Tested-by: jenkins Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk> Reviewed-by: Tim Sander <tim@krieglstein.org>
2014-09-10 03:29:23 -05:00
ftdi_layout_init 0x0908 0x0b1b
cfg: Add config file variants using the ftdi driver instead of ft2232 part 1 - files that were tested an verified as working fine Change-Id: If5986853a1cf118a9eb3b4c13b036d0f71c39624 Signed-off-by: Andreas Fritiofson <andreas.fritiofson@gmail.com> Signed-off-by: Freddie Chopin <freddie.chopin@gmail.com> Reviewed-on: http://openocd.zylin.com/534 Tested-by: jenkins
2012-07-19 02:30:27 -05:00
ftdi_layout_signal nSRST -oe 0x0200
interface/ftdi/olimex-arm-usb-ocd-h: fix nTRST control definition According to my inspection of an Olimex ARM-USB-OCD-H adapter ACBUS0 is connected directly to an SN74LVC2T45 buffer input B2, and the corresponding output A2 is connected directly to the JTAG connector. It seems the information in the Olimex flyer is incorrect for the -H version and TRST can't be tri-stated, ACBUS2 is unused. The older ARM-USB-OCD device has SN74AC244 for an output buffer and ACBUS2 controls its !2OE, ACBUS0 connected to 2A1 (2Y1 is nTRST), in accordance with the information flyer. Change-Id: I22828b7b959b6f62c3f51367feb8fab9705641e5 Reported-by: Tim Sander <tim@krieglstein.org> Signed-off-by: Paul Fertser <fercerpav@gmail.com> Reviewed-on: http://openocd.zylin.com/2286 Tested-by: jenkins Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk> Reviewed-by: Tim Sander <tim@krieglstein.org>
2014-09-10 03:29:23 -05:00
ftdi_layout_signal nTRST -data 0x0100
cfg: Add config file variants using the ftdi driver instead of ft2232 part 1 - files that were tested an verified as working fine Change-Id: If5986853a1cf118a9eb3b4c13b036d0f71c39624 Signed-off-by: Andreas Fritiofson <andreas.fritiofson@gmail.com> Signed-off-by: Freddie Chopin <freddie.chopin@gmail.com> Reviewed-on: http://openocd.zylin.com/534 Tested-by: jenkins
2012-07-19 02:30:27 -05:00
ftdi_layout_signal LED -data 0x0800