OMAP3530 ICEPICK - Revision history

Crayfranklin at 15:42, 17 December 2010

2010-12-17T15:42:41Z

Crayfranklin at 15:37, 17 December 2010

2010-12-17T15:37:35Z

Jcm at 02:21, 14 December 2010

2010-12-14T02:21:51Z

Jcm at 02:20, 14 December 2010

2010-12-14T02:20:52Z

Dirk: Add link to ICEPICK init

2009-03-12T18:57:08Z

Add link to ICEPICK init

Dirk: Format heading

2009-03-12T18:42:13Z

Format heading

Dirk: Add urjtag hack

2009-03-12T18:41:43Z

Add urjtag hack

Dirk: Update description

2009-03-12T18:28:50Z

Update description

Dirk: Update details

2009-03-12T18:25:25Z

Update details

Dirk: Add ICEPICK details

2009-03-12T18:23:34Z

Add ICEPICK details

@@ Line 18: / Line 18: @@
 * If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit] with [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]], make sure configure EMU0 & EMU1 the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way: In contrast to the picture EMU0 & EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2).
 * The OMAP3xx uses a TAP router, it needs to be [[OMAP3530_ICEPICK|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. '''NOTE''': Due to the presence of a TAP router (JRC) on e.g. the BeagleBoard-xM you want to set the EMU0 and EMU1 jumpers ON (pins 1-2, nearest to the JTAG ribbon cable) such that they are high and configure the default chain with only the ICEpick. OpenOCD will use ICEpick control commands to add the other devices (such as the processor DAP - Debug Access Port) once it has started. If you do not set the pins this way, the JTAG chain will be too long and OpenOCD will not be able to initialize it correctly.
-* TI has a [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf 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.  '''NOTE:'''  There is a newer revision of the ICEPick available with a different jtag device ID 0x1b89102f (mfg: 0x017, part: 0xb891, ver: 0x1).  Jon Masters' blog has a [http://www.jonmasters.org/blog/2010/12/13/using-openocd-with-beagleboard-xm/ very good description] about the needed changes to the OpenOCD configuration file to allow discovery of the 'proper' TAP... (until this change gets into OpenOCD)...
+* TI has a [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf 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.
 * ICEPICK IR length is 6
 * ARM IR length is 4

@@ Line 18: / Line 18: @@
 * If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit] with [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]], make sure configure EMU0 & EMU1 the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way: In contrast to the picture EMU0 & EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2).
 * The OMAP3xx uses a TAP router, it needs to be [[OMAP3530_ICEPICK|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. '''NOTE''': Due to the presence of a TAP router (JRC) on e.g. the BeagleBoard-xM you want to set the EMU0 and EMU1 jumpers ON (pins 1-2, nearest to the JTAG ribbon cable) such that they are high and configure the default chain with only the ICEpick. OpenOCD will use ICEpick control commands to add the other devices (such as the processor DAP - Debug Access Port) once it has started. If you do not set the pins this way, the JTAG chain will be too long and OpenOCD will not be able to initialize it correctly.
-* TI has a [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf 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.
+* TI has a [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf 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.  '''NOTE:'''  There is a newer revision of the ICEPick available with a different jtag device ID 0x1b89102f (mfg: 0x017, part: 0xb891, ver: 0x1).  Jon Masters' blog has a [http://www.jonmasters.org/blog/2010/12/13/using-openocd-with-beagleboard-xm/ very good description] about the needed changes to the OpenOCD configuration file to allow discovery of the 'proper' TAP... (until this change gets into OpenOCD)...
 * ICEPICK IR length is 6
 * ARM IR length is 4

@@ Line 17: / Line 17: @@
 * 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).
 * If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit] with [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]], make sure configure EMU0 & EMU1 the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way: In contrast to the picture EMU0 & EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2).
-* The OMAP3xx uses a TAP router, it needs to be [[OMAP3530_ICEPICK|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. NOTE: Due to the presence of a TAP router (JRC) on e.g. the BeagleBoard-xM you want to set the EMU0 and EMU1 jumpers ON (pins 1-2, nearest to the JTAG ribbon cable) such that they are high and configure the default chain with only the ICEpick. OpenOCD will use ICEpick control commands to add the other devices (such as the processor DAP - Debug Access Port) once it has started. If you do not set the pins this way, the JTAG chain will be too long and OpenOCD will not be able to initialize it correctly.
+* The OMAP3xx uses a TAP router, it needs to be [[OMAP3530_ICEPICK|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. '''NOTE''': Due to the presence of a TAP router (JRC) on e.g. the BeagleBoard-xM you want to set the EMU0 and EMU1 jumpers ON (pins 1-2, nearest to the JTAG ribbon cable) such that they are high and configure the default chain with only the ICEpick. OpenOCD will use ICEpick control commands to add the other devices (such as the processor DAP - Debug Access Port) once it has started. If you do not set the pins this way, the JTAG chain will be too long and OpenOCD will not be able to initialize it correctly.
 * TI has a [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf 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.
 * ICEPICK IR length is 6

@@ Line 16: / Line 16: @@
 This table is identical to the [http://wiki.davincidsp.com/index.php?title=Debugging_on_DaVinci_using_Olimex_dongle 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).
 * If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit] with [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]], make sure configure EMU0 & EMU1 the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way: In contrast to the picture EMU0 & EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2).
-* The OMAP3xx uses a TAP router, it needs to be [[OMAP3530_ICEPICK|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.
+* The OMAP3xx uses a TAP router, it needs to be [[OMAP3530_ICEPICK|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. NOTE: Due to the presence of a TAP router (JRC) on e.g. the BeagleBoard-xM you want to set the EMU0 and EMU1 jumpers ON (pins 1-2, nearest to the JTAG ribbon cable) such that they are high and configure the default chain with only the ICEpick. OpenOCD will use ICEpick control commands to add the other devices (such as the processor DAP - Debug Access Port) once it has started. If you do not set the pins this way, the JTAG chain will be too long and OpenOCD will not be able to initialize it correctly.
 * TI has a [http://focus.ti.com/lit/ml/sprp603/sprp603.pdf 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.
 * ICEPICK IR length is 6

@@ Line 179: / Line 179: @@
 ===Configuration===
-The following code snippet is part of a hackish 'omap3' command added to urjtag to verify basic ICEPICK initialization. See [http://sourceforge.net/mailarchive/message.php?msg_name=49A14373.5070006%40googlemail.com urjtag mailing list] for complete patch.
+The following code snippet is part of a hackish 'omap3' command added to urjtag to verify basic ICEPICK initialization. See [http://sourceforge.net/mailarchive/message.php?msg_name=49A14373.5070006%40googlemail.com urjtag mailing list] for complete patch. This is an urjtag implementation of above [[OMAP3530_ICEPICK#Adding_TAPs_to_the_Scan_Chain|scan chain configuration documentation]].
   printf( _("Starting OMAP3 ICEPICK initialization sequence ... ") );

@@ Line 3: / Line 3: @@
 The page is about [http://wiki.davincidsp.com/index.php?title=OMAP3_Overview OMAP3530] ICEPICK. See [[BeagleBoardJTAG|BeagleBoard JTAG page]] for more info about JTAG on OMAP3530 used at [[BeagleBoard|BeagleBoard]].
-=ICEPICK infos=
+==ICEPICK infos==
 * Regarding EMU0/EMU1 pins on BeagleBoard, pulling both pins down does not make Cortex-A8 CPU accessible.  Only one TAP is visible (ICEPick). Therefore OpenOCD is not able to access ARM TAP. The documentation for the control of EMU0/EMU1 is very misleading:

@@ Line 99: / Line 99: @@
 == ICEPICK instructions ==
-The following log shows a IR discovery scan of the icepick using [http://urjtag.org/ urjtag].
+===Discovery===
 Replace '<type>' of the cable command with the cable type you use. E.g.
@@ Line 174: / Line 176: @@
   tap/device found: 0x0b7ae02f (Manufacturer: 0x017, Part: 0xb7ae, Version: 0x0)

@@ Line 5: / Line 5: @@
 =ICEPICK infos=
-* 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:
+* Regarding EMU0/EMU1 pins on BeagleBoard, pulling both pins down does not make Cortex-A8 CPU accessible.  Only one TAP is visible (ICEPick). Therefore OpenOCD is not able to access ARM TAP. The documentation for the control of EMU0/EMU1 is very misleading:
 0 ICEPick + default TAP(s)

@@ Line 2: / Line 2: @@
 [[Category: OMAP]]
 The page is about [http://wiki.davincidsp.com/index.php?title=OMAP3_Overview OMAP3530] ICEPICK. See [[BeagleBoardJTAG|BeagleBoard JTAG page]] for more info about JTAG on OMAP3530 used at [[BeagleBoard|BeagleBoard]].
 == Adding TAPs to the Scan Chain ==