Difference between revisions of "BeagleBoardJTAG"

From eLinux.org
Jump to: navigation, search
m (Add ARM RealView ICE)
Line 239: Line 239:
<br />
<br />
The PEEDI package includes also an PEEDI to TI14 adapter and an TI20 to TI14 adapter.
The PEEDI package includes also an PEEDI to TI14 adapter and an TI20 to TI14 adapter.
==ARM RealView ICE==
The new release of software (3.3) for the [http://www.bluewatersys.com/blog/?p=71 ARM RealView ICE] supports Texas Instruments’ range of OMAP3 processors.

Revision as of 19:18, 12 December 2008

The page is about JTAG on OMAP3530 used at BeagleBoard.

Beagle JTAG connection

The BeagleBoard comes with a 14 pin TI JTAG connector. For JTAG pin out see section 8.16 of BeagleBoard HW Reference Manual (rev. B5). This is the same header interface as used in other TI products and is NOT the standard 14 pin ARM layout. Depending on your JTAG tool, you'd need a 20-pin to 14-pin TI adapter.

Note: JTAG on BeagleBoard uses 1.8V!

The 14-pin TI JTAG connector that is used on BeagleBoard is supported by a large number of JTAG emulation products and has been tested using Lauterbach, Spectrum Digital XDS510USB+ and TI XDS560 emulation pods. Note that it will not work with the Spectrum Digital XDS510USB (non-plus) as it does not support a target with 1.8V JTAG.

The following picture is from a TI OMAP JTAG presentation:

Ti arm jtag.jpg

Beagle uses the 14-pin TI header.

Note: TI uses some different pin names. Translation:

  • TVD => VREF at Beagle
  • TCLKO == TCK
  • #### == Key (empty))
  • TDI => GND at Beagle

Beagle adapter

The Flyswatter we plan to use has a 14 pin ARM layout, so we need to create a converter. From JTAG pin assignments document:

     ARM-14-JTAG                               TI-14-JTAG

VREF        1 - - 2  GND           JTAG_TMS    1 -  - 2  JTAG_nTRST
JTAG_nTRST  3 - - 4  GND           JTAG_TDI    3 -  - 4  GND
JTAG_TDI    5 - - 6  GND           VREF        5 -  x 6  KEY (empty)
JTAG_TMS    7 - - 8  GND           JTAG_TDO    7 -  - 8  GND
JTAG_TCK    9 - - 10 GND           JTAG_RTCK   9 -  - 10 GND
JTAG_TDO   11 - - 12 JTAG_SRST_N   JTAG_TCK   11 -  - 12 GND
VREF       13 - - 14 GND           JTAG_EMU0  13 -  - 14 JTAG_EMU1
   FlySwatter                TOP               Beagle

See 14 pin ARM to TI adapter for a verified JTAG adapter from TinCanTools.

Open source JTAG software

It would be very interesting to get the JTAG working with open source tools. The main open source JTAG software is OpenOCD.

OpenOCD JTAG bring up

On IRC it was discussed what will be necessary to get OpenOCD working with OMAP3 on BeagleBoard:

  • OpenOCD compatible JTAG hardware interface with FTDI's FT2232 chip, e.g. Flyswatter.
  • Create an adapter to convert the Flyswatter 14-pins JTAG into 14-pins TI JTAG
  • Get latest OpenOCD source
  • Add Cortex-A8 CPU ID. Currently only Cortex-M3 is supported. Take this as example. Once you connect to target you should get error message expect cpuid of xxxxxx but got yyyyyy which should contain Cortex-A8 CPU ID.
  • Take CPU scan lengths from OMAP3530 CCS config.
  • Regarding EMU0/EMU1 pins on BeagleBoard, pulling both pins down does currently not make Cortex-A8 CPU accessible. Only one TAP is visible (ICEPick). Therefore OpenOCD will not be able to validate the scan chain. The documentation for the control of EMU0/EMU1 is very misleading:
0 0 ICEPick + default TAP(s)
0 1 ICEPick Reserved
1 0 ICEPick Wait-in-reset
1 1 ICEPick Default condition
NOTES: ICEPick is always in the scan chain
Default TAPs are the ARM and the ETB

This table is identical to the Davinci documentation, with one BIG difference:

  • The OMAP3xx has NO default TAP (ARM or ETB taps) which means that the configuration of EMU0-L/EMU1-L doesn't add ARM to scan chain (above table is wrong, though).

The OMAP3xx uses a TAP router, it needs to be programmed with the information about available TAPS first, before ARM is accessible. Once the DAP has been added to the TAP router, via a programming sequence, the ARM core can be accessed.

TI has a good presentation describing the functionality of the ICEPick TAP Router (or generically refered to as JTAG Route Controller or JRC). The ICEPick jtag device ID is 0x0b73b02f (Manufacturer: 0x017, Part: 0xb73b, Version: 0x0) and is the same as the Davinci series.

It may still be possible to use the EMU0-L/EMU1-L configuration, but with consideration that the TAP router will already configured for with the arm core interface. Yet to be tested.

If above basics work, additionally MMU, cache support and some include files for A8 might be added to OpenOCD.

Note: If you made some progress regarding BeagleBoard OpenOCD support, please send a short note to BeagleBoard ML and OpenOCD ML.

Status end of October 2008:

  • Kees and Nishanth have some status info
  • There is some discussion how to extend OpenOCD to support JRC configuration (see thread JTAG emulator with openocd for beagleboard).

Build OpenOCD

OpenOCD build instructions describe how to build OpenOCD. For questions you can use OpenOCD Mailing list.

Get OpenOCD code via svn:

> svn checkout svn://svn.berlios.de/openocd/trunk

For Flyswatter you additionally need libftd2xx or libFTDI. While libFTDI is available in source, libftd2xx is supposed to be 50% faster than libFTDI, but only available as (binary) shared library.

If you have both, unpack libftd2xx and build OpenOCD:

> tar xvfz libftd2xx0.4.15.tar.gz
> cd trunk
> ./bootstrap
> ./configure --enable-ft2232_ftd2xx --with-ftd2xx=<path_to>/libftd2xx0.4.15 --prefix=/home/user/bin/openOCD
or (depending which FTDI library you use, see above)
> ./configure --enable-ft2232_libftdi -with-ftd2xx=<path_to>/include --prefix=/home/user/bin/openOCD
> make

JTAG hardware

For BeagleBoard JTAG debugging, there are some HW interfaces available. Several can be found on the TI tools directory.

TinCanTools Flyswatter

TinCanTools is currently working at Flyswatter support for OpenOCD for OMAP3530. They also have a BeagleBoard Adapter Kit.


In case you like to order Flyswatter and Adapter Kit international, here an example for Europe (Germany):

  • Flyswatter: US-$ 49.95
  • BeagleBoard Adapter Kit: US-$ 18.00
  • International shipping: US-$ 27.00 (select USPS, it's the cheapest!)

Sum: US-$ 94.95 => EUR 65.28 + EUR 8.76 VAT (Germany) = EUR 74.04

Flyswatter will use OpenOCD (Beagle (OMAP3xx) support under development),

BDI 2000


Chuck Fleming reports:

The BDI2000 appears to work with the omap35xx.cfg and regOMAP3500.def files that come with the BDI hardware. I had to modify the 10-pin cable so that the BeagleBoard JTAG header matched the BDI target A connector:

- TARGET: processing reset request
- TARGET: BDI executes scan chain init string
- TARGET: Bypass check 0x00000001 => 0x00000002
- TARGET: JTAG exists check passed
- Core#0: ID code is 0x0B6D602F
- Core#0: DP-CSW  is 0xF0000000
- Core#0: DBG-AP  at 0xD4011000
- Core#0: DIDR    is 0x15141012
- TARGET: BDI waits for RESET inactive
- TARGET: Reset sequence passed
- TARGET: resetting target passed
- TARGET: processing target startup ....
- TARGET: processing target startup passed
     Core number       : 0
     Core state        : debug mode (ARM)
     Debug entry cause : Debug Request
     Current PC        : 0x40200000
     Current CPSR      : 0x000001d3 (Supervisor)
          User     FIQ     Superv   Abort     IRQ      Undef
GPR00: 480029fc 480029fc 480029fc 480029fc 480029fc 480029fc
GPR01: 00000000 00000000 00000000 00000000 00000000 00000000
GPR02: 00000001 00000001 00000001 00000001 00000001 00000001
GPR03: 00000060 00000060 00000060 00000060 00000060 00000060
GPR04: 00000000 00000000 00000000 00000000 00000000 00000000
GPR05: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4
GPR06: 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4 80f2f2f4
GPR07: 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88 80e9ee88
GPR08: 80e3ffdc 34484608 80e3ffdc 80e3ffdc 80e3ffdc 80e3ffdc
GPR09: 80e3fec8 26a1c132 80e3fec8 80e3fec8 80e3fec8 80e3fec8
GPR10: 00000018 08040f16 00000018 00000018 00000018 00000018
GPR11: 80e3fecc 3c278260 80e3fecc 80e3fecc 80e3fecc 80e3fecc
GPR12: 0000006e 24200625 0000006e 0000006e 0000006e 0000006e
GPR13: 00000000 00000000 80e3feb0 00000000 00000000 d1868045
GPR14: 00000000 00000000 80e84f44 00000000 00000000 d55a4cc8
PC   : 40200000
CPSR : 000001d3
SPSR :          00000000 00000000 00000000 00000000 00000000
beagle>md 0x40200000
40200000 : e320f000 e320f000 e320f000 e320f000  .. ... ... ... .
40200010 : e320f000 e320f000 e320f000 eafffffc  .. ... ... .....
40200020 : b6273502 e7aa052b 047694c8 91ca77d8  .5'.+.....v..w..
40200030 : 12b9579e ef2eef1b 00543892 494f9bc1  .W.......8T...OI
40200040 : 3f63013d 82eee656 b7adfe8d 993f1368  =.c?V.......h.?.
40200050 : 51f1cf9b 0464a23e bea76e3c 3d275f5c  ...Q>.d.<n..\_'=
40200060 : 76554290 6776c892 a6cd088f 6dd4529a  .BUv..vg.....R.m
40200070 : 067261b8 e5f80e9e cb4ea075 25a9dd95  .ar.....u.N....%
40200080 : 779db8c6 0496597b 7d5f8d5a 24f44cd6  ...w{Y..Z._}.L.$
40200090 : 99ab46f9 9ddc06d9 fd34567a 2035bab8  .F......zV4...5
402000a0 : a16b6760 fe863cf7 29046202 39fb0d49  `gk..<...b.)I..9
402000b0 : dc9fd18c e50f536c 09ae66dd cad9ff91  ....lS...f......
402000c0 : c46bdbdb be791808 89ff83fa 2d3bc71e  ..k...y.......;-
402000d0 : 43f5a3b6 0aed1747 ba3c4752 6af0573a  ...CG...RG<.:W.j
402000e0 : 3570da77 9a1dc961 324b876c 5d592060  w.p5a...l.K2` Y]
402000f0 : b870f487 1277c035 4609dcf4 53b534c4  ..p.5.w....F.4.S
     Core number       : 0
     Core state        : debug mode (ARM)
     Debug entry cause : Single Step
     Current PC        : 0x40200004
     Current CPSR      : 0x000001d3 (Supervisor)
     Core number       : 0
     Core state        : debug mode (ARM)
     Debug entry cause : Single Step
     Current PC        : 0x40200008
     Current CPSR      : 0x000001d3 (Supervisor)

BDI config

The BDI config files might help getting OpenOCD to work with BeagleBoard.

This configuration assumes the "default" EMU 0 and 1 configuration (both not connected/high state). In this EM setup at first only one TAP is exported. A set of commands must be run on the first tap (embedded ICE) to enable access to the core:

SCANINIT    t1:w1000:t0:w1000:  ;toggle TRST,
SCANINIT    ch10:w1000:         ;clock TCK with TMS high and wait
SCANINIT    i6=07:d8=89:i6=02:  ;connect and select router
SCANINIT    d32=81000080:       ;IP control: KeepPowered
SCANINIT    d32=a3002048:       ;TAP3: DebugConnect, ForcePower, ForceActive
SCANINIT    d32=81000081:       ;IP control: KeepPowered, SysReset
SCANINIT    d32=a3002148:       ;enable TAP3
SCANINIT    cl10:i10=ffff       ;clock 10 times in RTI, scan bypass


Lauterbach Debugger supports OMAP3503/15/25/30.

XDS510 and CCS

XDS510 and CCS (code composer studio) can be used to debug OMAP3503/15/25/30. Configuration screen shot. For CCS setup see TI OMAP JTAG presentation, too (start page: 16).


PEEDI JTAG/BDM Emulator and Flash Programmer of Ronetix supports OMAP3.
A configuration file for the Beagleboard can be found here: omap3530.cfg
PEEDI has a built-in support for GNU gbd based debuggers and a built-in Flash Programmer.
The Flash Programmer is capable to program:
- NOR Flash devices (over 900)
- NAND and OneNAND Flash devices (small page, larger page, 8/16 bit), various methods of ECC calculation, bad block management.
- DataFlash devices
- SPI DataFlash devices
- images located on a TFTP/FTP/HTTP server or a MMC/SD card (which allows standalone mode).

The PEEDI package includes also an PEEDI to TI14 adapter and an TI20 to TI14 adapter.

ARM RealView ICE

The new release of software (3.3) for the ARM RealView ICE supports Texas Instruments’ range of OMAP3 processors.