embedded

I am new to arm architecture, I work on embedded software and was trying to learn about the .axf file which is present in my project binary's debug folder. Discovered that it is an arm executable format file generated by linker while the build process and it is used in debugging the crashes. So it is obvious that it contains some debugging information but its not clear what kind of information that is? And also there exists one .map file in the debug folder, so what could be the difference between these two files? The AXF file is an object file format generated by ARM's RealView compiler (also

I'm using a microSD card in an embedded design. The card is connected to a microcontroller using the SPI interface. It worked fine for all cards I've used before, but now my new card will not initialize. The card is a Transcend 2 GB microSD card (TS2GUSD). After sending the initial clock train to switch to SPI mode, I do the following: CMD0 (Argument 0, CRC 0x95) -> Response 0x01 -> OK CMD8 (Argument 0x000001AA, CRC 0x87) -> Response 0x01 0x000001AA -> Means it's SDC V2+ card, the voltage range 2.7 V - 3.6 V is supported -> OK Then I should send the ACMD41 command, but when sending the CMD55

I'm debugging a piece of (embedded) software. I've set a breakpoint on a function, and for some reason, once I've reached that breakpoint and continue I always come back to the function (which is an initialisation function which should only be called once). When I remove the breakpoint, and continue , GDB tells me: Program received signal SIGTRAP, Trace/breakpoint trap. Since I was working with breakpoints, I'm assuming I fell in a "breakpoint trap". What is a breakpoint trap? Breakpoint trap just means the processor has hit a breakpoint. There are two possibilities for why this is happening.

I have an system running embedded linux and it is critical that it runs continuously. Basically it is a process for communicating to sensors and relaying that data to database and web client. If a crash occurs, how do I restart the application automatically? Also, there are several threads doing polling(eg sockets & uart communications). How do I ensure none of the threads get hung up or exit unexpectedly? Is there an easy to use watchdog that is threading friendly? The gist of it is: You need to detect if the program is still running and not hung. You need to (re)start the program if the

I write a project for a non POSIX embedded system so I cannot use gcc option --coverage (i don't have read or write). What else can I do to produce gcov like output. I do have an output function. It can be most easily done with by a processor with embedded trace, a board design that exposes the trace port, and a suitable hardware debugger and associate software. For example, many Cortex-M based devices include ARM's embedded trace macrocell (ETM), and this is supported by Keil's uVision IDE and ULINK-Pro debugger to provide code coverage and instruction/source level trace as well as real-time