Embedded Systems Conference
Breaking News
Break Points

Extending Debugging Resources

NO RATINGS
View Comments: Threaded | Newest First | Oldest First
przem
User Rank
Author
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
Congress needs an engineering mindset.
IT people live in a different world from firmware developers.
A talent agent for the power programmers and superstar engineers makes sense.
Jack talks to HCC Embedded about very high-reliability firmware design.
Freescale gets “typ” and “max” right for their Kinetis family.
Flash Poll
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
Top Comments of the Week
March 2015 Cartoon Caption Contest: Mountain Climbing
March 2015 Cartoon Caption Contest: Mountain Climbing
The mountain had formed millions of years before when two tektronix plates collided.
208 comments