Design Con 2015
Breaking News
Break Points

Extending Debugging Resources

NO RATINGS
View Comments: Newest First | Oldest First | Threaded View
przem
User Rank
Manager
standards
przem   3/31/2014 1:25:56 PM
NO RATINGS
As a not very sophisticated user of native debugging features of ARM chips I am confused at the plethora of facilities in different chip generations. I know that there begin to be standard debugging cells, but it still is tricky to know what's there. FWIW, to preserve my sanity I try to stick to standard toolchain GCC/GDB for Cortex chips from M0 to A8, and as far as I know there is no way to 'introspect' into exactly which capacities are on the platform I am working with at the moment.

This is a problem with ARM in general, for instance for the system peripherals. On Intel, the PCI resources self-identify but on ARM you just have to read the SRM and write down the memory addresses.As a result, the abstraction has to be handled by software, e.g. device trees on Linux, and the result is quite cryptic. The same goes for debugging, but AFAIK there is no standard to describe it in the way device trees describe the I/O peripherals.

More Blogs from Break Points
Delivering high quality doesn't mean leaning on QA to find your errors. Quality assurance is not supposed to find bugs.
Software is inherently fragile. A memory management unit can prop it up.
Reading, writing, and arithmetic: all are important in engineering education.
Storing files in the cloud may be the solution du jour, but here are one engineer's concerns on the risks.
The trillion-sensor world is not going to happen anytime soon. Just do the math.
Radio
LATEST ARCHIVED BROADCAST
EE Times Senior Technical Editor Martin Rowe will interview EMC engineer Kenneth Wyatt.
Top Comments of the Week
Like Us on Facebook

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
EE Times on Twitter
EE Times Twitter Feed
Flash Poll