On 04.12.2010 07:12, Austin, Alex wrote:
I imagine the problem is voltage, actually. The OMAP3530 and other similar 
devices run their JTAG ports at 1.8V, and the ARM-USB-OCD doesn't like working 
below 3V.

Therefore the Flyswatter

http://www.tincantools.com/product.php?productid=16134&cat=0&page=1&featured

is popular for OMAP3 because it supports 1.8V.

Dirk

________________________________________
From: openocd-development-boun...@lists.berlios.de 
[openocd-development-boun...@lists.berlios.de] On Behalf Of Nick Pelling 
[nickpell...@nanodome.com]
Sent: Friday, December 03, 2010 12:52 PM
To: openocd-development@lists.berlios.de
Subject: [Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?

Hi everyone,

I've just plugged my trusty old Olimex ARM-USB-OCD (the Swiss Army
Knife of JTAG debuggers) into my shiny new S5PC100-based board and...
I'm struggling to see how to get it working even slightly.

Has anyone got anywhere with the s5pc100 or other CoreSight-based
Cortex A8s (apart from the OMAP3530 as per
http://elinux.org/BeagleBoardOpenOCD )? Firas Achkar mentioned trying
this on the urbetter board (which I think is actually the original
ODroid) a month ago, as did Matt Hsu in November 2009. But trying the
latest openocd's autoprobe (as David Brownell suggested then) didn't
seem to produce anything so revealing as an ID code.

Incidentally, I've read through the CoreSight chapter in the latest
Samsung datasheet but that had precisely nothing so useful as a TAP
ID code or a DAP ID code to get started. Stepping through every
occurrence of JTAG also revealed nothing useful.

Any suggestions? Has anyone tried the same thing for the S5PC110 (as
per the ODroid-T etc)? Might there be some hidden nest of Samsung SoC
OpenOCD developers in a far-flung corner of Korea?

Cheers, ....Nick Pelling....

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development


_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to