I work on the self-driving car project at Google, and we use the
TMS570LS3137 and OpenOCD for some of our development. For quite a while
we've used some hacks to OpenOCD to support big-endian mode with mixed
success, and I'm finally trying to push clean(er) support into OpenOCD head.
I have a pull request here: http://openocd.zylin.com/#/c/2064/1
This fixes the endianness issues when accessing memory (as best as I can
tell) and the bizarre byte/halfword access issues that Alex Züpke posted
about a few months ago:
Re: [OpenOCD-devel] [OpenOCD-user] TMS570: corrupted memory access
From: Alex Züpke <alexander.zuepke@hs...> - 2014-01-31 12:38:14
Hi,
I'm re-posting my question from the user's list regarding my corrupted
memory accesses on the devel list again:
I have a TI TMS570 / ARM Cortex R4 and troubles on byte and half-word
accesses on the flash and SRAM area from the debug interface.
The differences in behavior for reads vs writes of the processor's AHB-AP
memory access interface are truly bizarre, and I have no idea if it's a
TMS570 quirk or generic to Cortex-R4 or Cortex-A. However, I don't know of
any other big-endian Cortex-R/Cortex-A processors to test against and
big-endian handling seemed pretty broken before, so this should be a strict
improvement.
If anybody has a TMS570 or another big-endian Cortex-A/Cortex-R processor
(are there any?), please try this out and see how it works for you.
Seth
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
