Øyvind Harboe wrote:
> Note that these are LENGTHY discussions and since there are several
> capable people involved, I'm kinda waiting for the dust to settle.

Where do you see the dust? At least regarding OMAP3 we now know how do 
initialize ICEPICK [1] [2] (see below). For me, the dust is now how to 
do it correctly in OpenOCD. And as it seems you are the expert for 
this, it would be nice if you won't wait and help us now ;)

> It would probably get more people on board if you could, once the
> dust settles on these discussions, write up a summary of the
> problems and possible solutions.

It's easy ;) We just have to do what is described in [1] and done for 
urjtag in [2] properly in OpenOCD (== problem)

Short summary (more details in [1] & [2]):

OMAP3 reset config: Only ICEPICK is in scan chain. Additional TAPs 
(e.g. 'ARM') have to be enabled before being accessible. For this 
(ARM), it has to be done:

1) Apply a minimum of 10 TCK pulses to the OMAP3 device after nTRST is 
pulled high

2) Switch to DR 0x7, write 0x89 to DR 0x7, 8 bit length (note 1)

3) Switch to DR 0x2, write 0xa3002108 to DR 0x2, 32 bit length (note 1)

4) Switch IR to 'all-ones' (note 1)

5) Clock at least 10 TCK in run test idle

Note 1: All state switches have to be done 'shortest transition'. I.e. 
don't go over reset or run-test idle. From update DR / IR go directly 
to select DR.

Note 2: After 1 - 5 are done, never ever do any reset.

After 5, extend IR from 6 to 10 (6 + 4), put ICEPICK into bypass and 
then deal with ARM tap.

Additional info:

- ICEPICK IR length is 6

- ARM IR length is 4

- ICEPICK ID code is at DR 0x4 32bit length: 0x0B7AE02F

- ARM ID code is at DR 0xE 32bit length: 0x0B6D602F

Hopefully, for the "how to do this properly in OpenOCD" (== solutions) 
you can help us?

> There may in fact be a solution for your problems already

Hopefully! Would be nice if you could show them to us :)

Many thanks

Dirk

[1] http://elinux.org/OMAP3530_ICEPICK (Adding TAPs to the Scan Chain )

[2] 
https://lists.berlios.de/pipermail/openocd-development/2009-February/004745.html

_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to