Embedded Systems Conference
Breaking News
Break Points

Extending Debugging Resources

View Comments: Newest First | Oldest First | Threaded View
User Rank
przem   3/31/2014 1:25:56 PM
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
Unless we have a quantitative understanding of our profession it will be more art than science.
Bill Maher has his new rules. But there's an old rule: When in doubt, petition the Federal government for a solution.
Siglent’s new arbitrary waveform generator is a pro-level instrument for a (well-off) hobbyist price.
Ints have limited ranges. Floats can be slow and memory hogs. Are there any alternatives?
ST's ART accelerator gives near-zero wait state operation out of slow flash.
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