Often overlooked, the map file can provide a wealth of information to the intrepid developer. Map files can help:
- optimizing for RAM usage and/or code space
- updating firmware (with or without a bootloader)
- debugging difficult crash bugs
- statistical profiling
With so much information, how can you use it? Where do you look? How do you turn the wall of text and numbers into a true map of the code?
Elecia will demonstrate how to use map files. She will focus on an ARM Cortex-M but it will be relevant to other processors.
To post reply to a comment, click on the 'reply' button attached to each comment. To post a new comment (not a reply to a comment) check out the 'Write a Comment' tab.
Please login (on the right) if you already have an account on this platform.
Otherwise, please use this form to register (free) an join one of the largest online community for Electrical/Embedded/DSP/FPGA/ML engineers: