Here is a shot of my pinout, if it helps:
[image: image.png]
On Fri, 14 Jul 2023 at 09:55, Abe Lapped <abe19285...@gmail.com> wrote:
> Good morning,
>
> Thank you for this. I just checked the pin configuration and retried on
> another board. The board is definitely powered on (the status lights come
> on) and the cable orientation is correct, but I'm still getting the same
> error... could it be something to do with my configuration files?
>
> Interface:
> adapter driver ftdi
> ftdi device_desc "Olimex OpenOCD JTAG ARM-USB-OCD-H"
> ftdi vid_pid 0x15ba 0x002b
>
> ftdi layout_init 0x0908 0x0b1b
> ftdi layout_signal nSRST -oe 0x0200
> ftdi layout_signal nTRST -data 0x0100
> ftdi layout_signal LED -data 0x0800
>
> #jtag_nsrst_delay 200
> #jtag_ntrst_delay 200
> transport select jtag
>
> reset_config srst_only
>
> target:
> if { [info exists CHIPNAME] } {
> set _CHIPNAME $CHIPNAME
> } else {
> set _CHIPNAME ks869x
> }
>
> adapter speed 6000
>
> # jtag scan chain
> jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf
> -expected-id 0xe
>
> set _TARGETNAME $_CHIPNAME.cpu
>
> target create $_TARGETNAME arm920t -endian little -chain-position
> $_TARGETNAME
>
> $_TARGETNAME configure -work-area-phys 0x10000 -work-area-size 0x40000
> -work-area-backup 0
>
> Thank you,
>
>
> On Thu, 13 Jul 2023 at 17:49, Tommy Murphy <tommy_mur...@hotmail.com>
> wrote:
>
>> > I tried unplugging the cable from the target completely and running
>> again, and got the same error.
>>
>> That makes sense since TDO on the Olimex will most likely be pulled or
>> floating high by default so it'll be read as 1 when disconnected. The fact
>> that it's reading high when connected is the issue. As I mentioned before,
>> maybe the connector is not orientated properly (at both ends - Olimex and
>> board connector). If it is then the issue may be board related. Either
>> there's some jumper or other configuration needed for the debug connection
>> to work, the debug block is locked from access on some way, the board is
>> faulty, etc.
>>
>
