JTAG wiring diagram question « LeafLabs Garden

LeafLabs Garden » Support » Maple Hardware Support

JTAG wiring diagram question

(63 posts) (9 voices)

Started 5 years ago by Adam
Latest reply from gbulmer

12…5 Next »

Adam
Member

I need to do some debugging via OpenOCD, and for that I need to make a JTAG cable. I want to be sure I understand the diagram listed here:

http://leaflabs.com/docs/maple/jtag/#wiring

What pins connect to what pins? The diagram doesn't show connections from the 8 pin Maple JTAG connector to the 20 pin ARM connector. Or do I connect the first 8 pins of the Maple connector to the ARM connector? That doesn't make sense to me, since 9 pins on the ARM JTAG go to ground.

I searched the forums but can't find a pin-mapping.

Does anyone have a pin-mapping I can use? If not I will reverse-engineer it from the schematic, but I wanted to check here first.

Posted 5 years ago #
Adam
Member
Ok, I checked out the 20-pin ARM JTAG pinout here:

http://www.jtagtest.com/pinouts/arm20

I also checked the Maple R2 and R5 schematics here:

https://github.com/leaflabs/maple

I have a Maple R3, but couldn't find the schematic for that, but since the JTAG connectors are the same on R2 and R5 I am assuming they are the same for R3.

Here's my proposed pin mapping:
```
Maple JTAG pin       ARM JTAG pin
==================================
TRST  1 . . . . . . . . .  3 nTRST
GND   2 . . . . . . . . .  4 GND
TCK   3 . . . . . . . . .  9 TCK
TDO   4 . . . . . . . . . 13 TDO
TDI   5 . . . . . . . . .  5 TDI
TMS   6 . . . . . . . . .  7 TMS
VCC   7 . . . . . . . . .  2 VSUPPLY
TRST  8 . . . . . . . . .  3 nTRST
```
Is this correct?
Posted 5 years ago #
larryang
Member

Here's a previous thread http://forums.leaflabs.com/topic.php?id=200, which confirms that the diagram doesn't show anything.

Anyway, my question was about pullup resistors, since the chip has internal pull-up and pull-down resistors.

Posted 5 years ago #
gbulmer
Moderator

LeafLabs - a related JTAG header question.

Why did you decide to do the Maples 8-pin header, instead of using one of the ARM 10-pin headers?

Posted 5 years ago #

Adam
Member

Ok, I made the cable. I am using an Olimex ARM USB TINY:

http://www.olimex.com/dev/arm-usb-tiny.html

I'm on Ubuntu Linux 10.04. I got the OpenOCD software working - had to install version 0.4.0 from source, and use the Open Source libftdi. My configure line for OpenOCD looks like this:

./configure --enable-ft2232_libftdi --enable-usbprog

After installing a udev rules file like this:

SYSFS{idProduct}=="0004", SYSFS{idVendor}=="15ba", MODE="666", GROUP="plugdev", SYMLINK+="ft2232"

I am able to see the device via lsusb:

Bus 002 Device 033: ID 1eaf:0004
Bus 002 Device 023: ID 15ba:0004 Olimex Ltd. OpenOCD JTAG TINY

OpenOCD recognizes the board, but when I run make jtag debug using the main.cpp copied from the examples/blinky.cpp, I get the following error:

adamf@clay:~/src/libmaple$ make jtag debug
================================================================================

  Build info:
     BOARD:           maple
     MCU:             STM32F103RB
     MEMORY_TARGET:   jtag

  See 'make help' for all possible targets

================================================================================

openocd -f support/openocd/run.cfg
Open On-Chip Debugger 0.4.0 (2010-11-28-20:19)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.berlios.de/doc/doxygen/bugs.html
1000 kHz
jtag_nsrst_delay: 100
jtag_ntrst_delay: 100
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
Info : clock speed 1000 kHz
Info : JTAG tap: stm32.cpu tap/device found: 0x01b00037 (mfg: 0x01b, part: 0x1b00, ver: 0x0)
Warn : JTAG tap: stm32.cpu       UNEXPECTED: 0x01b00037 (mfg: 0x01b, part: 0x1b00, ver: 0x0)
Error: JTAG tap: stm32.cpu  expected 1 of 1: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3)
Info : TAP stm32.bs does not have IDCODE
Warn : JTAG tap: stm32.bs       UNEXPECTED: 0x00000000 (mfg: 0x000, part: 0x0000, ver: 0x0)
Error: JTAG tap: stm32.bs  expected 1 of 5: 0x06412041 (mfg: 0x020, part: 0x6412, ver: 0x0)
Error: JTAG tap: stm32.bs  expected 2 of 5: 0x06410041 (mfg: 0x020, part: 0x6410, ver: 0x0)
Error: JTAG tap: stm32.bs  expected 3 of 5: 0x16410041 (mfg: 0x020, part: 0x6410, ver: 0x1)
Error: JTAG tap: stm32.bs  expected 4 of 5: 0x06414041 (mfg: 0x020, part: 0x6414, ver: 0x0)
Error: JTAG tap: stm32.bs  expected 5 of 5: 0x06418041 (mfg: 0x020, part: 0x6418, ver: 0x0)
Warn : Unexpected idcode after end of chain: 33 0x0ff08000
Warn : Unexpected idcode after end of chain: 65 0xfc000000
Warn : Unexpected idcode after end of chain: 97 0xc0000001
Warn : Unexpected idcode after end of chain: 129 0xc000001f
Warn : Unexpected idcode after end of chain: 161 0xc000001f
Warn : Unexpected idcode after end of chain: 193 0xc000001f
Warn : Unexpected idcode after end of chain: 225 0xc000001f
Warn : Unexpected idcode after end of chain: 257 0xc000001f
Warn : Unexpected idcode after end of chain: 289 0xc000001f
Warn : Unexpected idcode after end of chain: 321 0xc000001f
Warn : Unexpected idcode after end of chain: 353 0xc000001f
Warn : Unexpected idcode after end of chain: 385 0xc000001f
Warn : Unexpected idcode after end of chain: 417 0xc000001f
Warn : Unexpected idcode after end of chain: 449 0xc000001f
Warn : Unexpected idcode after end of chain: 481 0xc000001f
Warn : Unexpected idcode after end of chain: 513 0xc000001f
Warn : Unexpected idcode after end of chain: 545 0xc000001f
Warn : Unexpected idcode after end of chain: 577 0xc000001f
Error: double-check your JTAG setup (interface, speed, missing TAPs, ...)
Info : JTAG tap: stm32.cpu tap/device found: 0x01b00037 (mfg: 0x01b, part: 0x1b00, ver: 0x0)
Warn : JTAG tap: stm32.cpu       UNEXPECTED: 0x01b00037 (mfg: 0x01b, part: 0x1b00, ver: 0x0)
Error: JTAG tap: stm32.cpu  expected 1 of 1: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3)
Info : TAP stm32.bs does not have IDCODE
Warn : JTAG tap: stm32.bs       UNEXPECTED: 0x00000000 (mfg: 0x000, part: 0x0000, ver: 0x0)
Error: JTAG tap: stm32.bs  expected 1 of 5: 0x06412041 (mfg: 0x020, part: 0x6412, ver: 0x0)
Error: JTAG tap: stm32.bs  expected 2 of 5: 0x06410041 (mfg: 0x020, part: 0x6410, ver: 0x0)
Error: JTAG tap: stm32.bs  expected 3 of 5: 0x16410041 (mfg: 0x020, part: 0x6410, ver: 0x1)
Error: JTAG tap: stm32.bs  expected 4 of 5: 0x06414041 (mfg: 0x020, part: 0x6414, ver: 0x0)
Error: JTAG tap: stm32.bs  expected 5 of 5: 0x06418041 (mfg: 0x020, part: 0x6418, ver: 0x0)
Warn : Unexpected idcode after end of chain: 33 0x0ff08000
Warn : Unexpected idcode after end of chain: 65 0xfc000000
Warn : Unexpected idcode after end of chain: 97 0xc0000001
Warn : Unexpected idcode after end of chain: 129 0xc000001f
Warn : Unexpected idcode after end of chain: 161 0xc000001f
Warn : Unexpected idcode after end of chain: 193 0xc000001f
Warn : Unexpected idcode after end of chain: 225 0xc000001f
Warn : Unexpected idcode after end of chain: 257 0xc000001f
Warn : Unexpected idcode after end of chain: 289 0xc000001f
Warn : Unexpected idcode after end of chain: 321 0xc000001f
Warn : Unexpected idcode after end of chain: 353 0xc000001f
Warn : Unexpected idcode after end of chain: 385 0xc000001f
Warn : Unexpected idcode after end of chain: 417 0xc000001f
Warn : Unexpected idcode after end of chain: 449 0xc000001f
Warn : Unexpected idcode after end of chain: 481 0xc000001f
Warn : Unexpected idcode after end of chain: 513 0xc000001f
Warn : Unexpected idcode after end of chain: 545 0xc000001f
Warn : Unexpected idcode after end of chain: 577 0xc000001f
Error: double-check your JTAG setup (interface, speed, missing TAPs, ...)
Command handler execution failed
Warn : jtag initialization failed; try 'jtag init' again.
Info : JTAG tap: stm32.cpu tap/device found: 0x01b00037 (mfg: 0x01b, part: 0x1b00, ver: 0x0)
Warn : JTAG tap: stm32.cpu       UNEXPECTED: 0x01b00037 (mfg: 0x01b, part: 0x1b00, ver: 0x0)
Error: JTAG tap: stm32.cpu  expected 1 of 1: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3)
Info : TAP stm32.bs does not have IDCODE
Warn : JTAG tap: stm32.bs       UNEXPECTED: 0x00000000 (mfg: 0x000, part: 0x0000, ver: 0x0)
Error: JTAG tap: stm32.bs  expected 1 of 5: 0x06412041 (mfg: 0x020, part: 0x6412, ver: 0x0)
Error: JTAG tap: stm32.bs  expected 2 of 5: 0x06410041 (mfg: 0x020, part: 0x6410, ver: 0x0)
Error: JTAG tap: stm32.bs  expected 3 of 5: 0x16410041 (mfg: 0x020, part: 0x6410, ver: 0x1)
Error: JTAG tap: stm32.bs  expected 4 of 5: 0x06414041 (mfg: 0x020, part: 0x6414, ver: 0x0)
Error: JTAG tap: stm32.bs  expected 5 of 5: 0x06418041 (mfg: 0x020, part: 0x6418, ver: 0x0)
Warn : Unexpected idcode after end of chain: 33 0x0ff08000
Warn : Unexpected idcode after end of chain: 65 0xfc000000
Warn : Unexpected idcode after end of chain: 97 0xc0000001
Warn : Unexpected idcode after end of chain: 129 0xc000001f
Warn : Unexpected idcode after end of chain: 161 0xc000001f
Warn : Unexpected idcode after end of chain: 193 0xc000001f
Warn : Unexpected idcode after end of chain: 225 0xc000001f
Warn : Unexpected idcode after end of chain: 257 0xc000001f
Warn : Unexpected idcode after end of chain: 289 0xc000001f
Warn : Unexpected idcode after end of chain: 321 0xc000001f
Warn : Unexpected idcode after end of chain: 353 0xc000001f
Warn : Unexpected idcode after end of chain: 385 0xc000001f
Warn : Unexpected idcode after end of chain: 417 0xc000001f
Warn : Unexpected idcode after end of chain: 449 0xc000001f
Warn : Unexpected idcode after end of chain: 481 0xc000001f
Warn : Unexpected idcode after end of chain: 513 0xc000001f
Warn : Unexpected idcode after end of chain: 545 0xc000001f
Warn : Unexpected idcode after end of chain: 577 0xc000001f
Error: double-check your JTAG setup (interface, speed, missing TAPs, ...)
error: -100
Command handler execution failed
make: *** [debug] Error 1

So it seems like there's something wrong with the JTAG communication. My run.cfg file looks like this:

# script for stm32

#interface ft2232
#ft2232_device_desc "Olimex OpenOCD JTAG"
#ft2232_layout olimex-jtag
#ft2232_vid_pid 0x15ba 0x0003

interface ft2232
ft2232_device_desc "Olimex OpenOCD JTAG TINY"
ft2232_layout olimex-jtag
ft2232_vid_pid 0x15ba 0x0004

if { [info exists CHIPNAME] } {
   set  _CHIPNAME $CHIPNAME
} else {
   set  _CHIPNAME stm32
}

if { [info exists ENDIAN] } {
   set  _ENDIAN $ENDIAN
} else {
   set  _ENDIAN little
}

# jtag speed speed should be <= F_CPU/6. F_CPU after reset is 8MHz, so ufse F_JTAG = 1MHz
jtag_khz 1000

jtag_nsrst_delay 100
jtag_ntrst_delay 100

#use combined on interfaces or targets that can't set TRST/SRST separately
reset_config trst_and_srst

#jtag scan chain
if { [info exists CPUTAPID ] } {
   set _CPUTAPID $CPUTAPID
} else {
  # See STM Document RM0008
  # Section 30.6.3
   set _CPUTAPID 0x3ba00477
}

jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID

if { [info exists BSTAPID ] } {
   # FIXME this never gets used to override defaults...
   set _BSTAPID $BSTAPID
} else {
  # See STM Document RM0008
  # Section 29.6.2
  # Low density devices, Rev A
  set _BSTAPID1 0x06412041
  # Medium density devices, Rev A
  set _BSTAPID2 0x06410041
  # Medium density devices, Rev B and Rev Z
  set _BSTAPID3 0x16410041
  # High density devices, Rev A
  set _BSTAPID4 0x06414041
  # Connectivity line devices, Rev A and Rev Z
  set _BSTAPID5 0x06418041
}
jtag newtap $_CHIPNAME bs -irlen 5 -expected-id $_BSTAPID1 \
           -expected-id $_BSTAPID2 -expected-id $_BSTAPID3 \
           -expected-id $_BSTAPID4 -expected-id $_BSTAPID5

set _TARGETNAME $_CHIPNAME.cpu
target create $_TARGETNAME cortex_m3 -endian $_ENDIAN -chain-position $_TARGETNAME

$_TARGETNAME configure -work-area-virt 0 -work-area-phys 0x20000000 -work-area-size 0x5000 -work-area-backup 0

#flash bank stm32x 0x08000000 0x00020000 0 0 $_TARGETNAME
set _FLASHNAME $_CHIPNAME.flash
flash bank $_FLASHNAME stm32x 0x08000000 0x00020000 0 0 $_TARGETNAME

proc nopforever {} {
    puts "Resetting the chip..."
    reset run
}

init
nopforever

(Similar to structuresound's cfg file from http://forums.leaflabs.com/topic.php?id=532)

Anybody have any ideas what's wrong? Why can't I communicate with the Maple via JTAG?

Posted 5 years ago #

Adam
Member

Just chatted on IRC with okie and mbolivar. okie suggested the following:

Maple JTAG pin       ARM JTAG pin
==================================
TRST  1 . . . . . . . . .  3 nTRST and 15 RST
GND   2 . . . . . . . . .  4 GND
TCK   3 . . . . . . . . .  9 TCK
TDO   4 . . . . . . . . . 13 TDO
TDI   5 . . . . . . . . .  5 TDI
TMS   6 . . . . . . . . .  7 TMS
VCC   7 . . . . . . . . .  2 VSUPPLY and 1 VREF
TRST  8 . . . . . . . . .  3 nTRST

As well as pulling down the following ARM JTAG pins to ground with a 10k resistor for each:

11 RTCK
17 DBGRQ
19 DBGACK

I haven't done this yet - I will report back when I try it.

Posted 5 years ago #

crenn
Moderator

IRC? I didn't realise they had an IRC channel, where is it?

EDIT: Found it! http://leaflabs.com/community/

Posted 5 years ago #
mbolivar
LeafLabs

okie's schematic is available here:
http://leaflabs.com/wp-content/uploads/2010/11/maple-jtagadapter.png

(will be integrated into the jtag docs)

Posted 5 years ago #
Adam
Member

okie, mbolivar,

Thank you for the work doing the schematic and posting it!

Will you also post the source file? I may want to make an adapter PCB.

Posted 5 years ago #
mbolivar
LeafLabs

okie's put it up in the maple hardware design repo:
https://github.com/leaflabs/maple/tree/master/jtagadapter/

Posted 5 years ago #
gbulmer
Moderator

Sorry to bump, but ...

Why did LeafLabs decide to do the Maples 8-pin header, instead of using one of the ARM 10-pin headers? If it were an ARM socket, wouldn't connectors be available "off the shelf".

Posted 5 years ago #
okie
Administrator

gbulmer, you are absolutely right. I am to blame for the 8-pin header. Frankly, I didn't know that the 10-pin header was an ARM standard, and when I made that made the decision or the 8-pin header over a year ago, I was unaware of any off-the-shelf under 14-pins. I had seen development boards with their own tiny-ish JTAG connectors with options to buy little adapter boards and cables. These would be cheap; I think we should do a run of barebones adapter boards for the Maple r1's, r3's and the in-stock r5's that will allow both the 8-pin adapter and the ARM-standard 10-pin header to connect to the 20-pin debuggers. Then, switch to the 10-pin header in Rev7.

Posted 5 years ago #
gbulmer
Moderator

I had seen development boards with their own tiny-ish JTAG connectors with options to buy little adapter boards and cables. These would be cheap;

I like cheap :-)

I think we should do a run of barebones adapter boards for the Maple r1's, r3's and the in-stock r5's that will allow both the 8-pin adapter and the ARM-standard 10-pin header to connect to the 20-pin debuggers.

I'm not sure if this is what you mean, but if you just make a batch of PCB's, no components, I'd be happy to populate my own, and posting a PCB may be 'letter post'.

Then, switch to the 10-pin header in Rev7

Yes, please do this.
I am changing to 10 (2x5) pin on my "robot" board.
Are you thinking 0.1" or 0.05" header?

At the moment, to keep the cost low, I am using ordinary 0.1" header pins.
Also, I am using 0.1" because I can make the IDC cables :-)
I can make an adapter for 0.1" IDC on veroboard too (ugly but workable).

The 'new' 10-pin ARM JTAG is 0.05"
http://www.samtec.com/productinformation/technicalspecifications/overview.aspx?series=FTSH
but I don't understand how easy it will be to use them.
Also, they are amazingly expensive, i.e. comparable to a low-end STM32F103!

Any thoughts?

Posted 5 years ago #
Adam
Member
okie,

If you do an adapter PCB, will you make two different 8 pin headers - one for top side connector, and one for bottom side? As I put my connector on the bottom side, I realized that the ribbon cable would have an odd pin order, something like this for the 8 pin header:

It's normal if you put the connector on top:
```
Maple JTAG top side:    1 2 3 4 5 6 7 8
Ribbon      cable:      1 2 3 4 5 6 7 8
```
But if you put the JTAG connector on the bottom, the cable pins look like this:
```
Maple JTAG bottom side: 7 8 5 6 3 4 1 2
Ribbon cable:           8 7 6 5 4 3 2 1
```
So ideally there would be two connectors, one if you soldered your JTAG connector sticking up from the top, and one for people who put their connector on the bottom.

Does this make sense?

I chose to put my JTAG connector on the bottom because I have a couple of shields to plug in on the top, and that would be hard if I put it on the top of the Maple board.

And a bare PCB or kit would be fine with me - I would be fine assembling it myself. But just having this all worked out will save the software-ish people like me a lot of trouble!

Whether it is 8 or 10 pin doesn't make that much difference to me, since the Olimex JTAG dongles all have the ARM 20 pin header, not the 10 pin one. Either way I'd still need an adapter.

Also if you decide not to make one - let me know, and I will do it via SFE's small run service.
Posted 5 years ago #
gbulmer
Moderator

adamfeuer - I imagine the PCB will be pretty small, i.e. 1.5" x 1"

I will do it via SFE's small run service.

for a board that small it might be worth looking at http://dorkbotpdx.org/wiki/pcb_order

who charge more than SFE's BatchPCB per square inch ($5/sq. inch), but have no setup charge (Batch PCB is $10). It appears that postage within the USA is included in that $5/sq. inch price.
Hence dorkbotpdx.org are lower-cost for anything under 4 square inches.

Further, I think dorkbotpdx.org make 3 boards for that $5/sq inch price, so they are always lower cost than BatchPCB if you need more than one copy of the same PCB.

WARNING: I have not tried them. I saw the link on a forum but can't find the thread again.

Posted 5 years ago #

RSS feed for this topic

12…5 Next »

Reply »

You must log in to post.