Onlytronix

When working in embedded environments, you do not have an operating system and a graphical user interface telling you which memory is filled up. There is no friendly prompt telling you what to remove to free up space. The linker map is basically your local disk properties tab, except everything is in addresses and hexadecimal values. I ran into this while working with a Parallax Propeller 1 board, Propeller C, and SimpleIDE . My code looked small: a simple LED blink and an R2U2 runtime verification monitor. The microcontroller had 32 KB of Hub RAM, but the program was still getting too large. That did not make sense. The confusing part The monitor object itself was only about 60 bytes. A blinking LED program is tiny. So why was the whole program acting like it wanted the entire 32 KB chip?   Why I Opened the Assembly and Map Files Before opening the map file, I spent hours rewriting the code and removing things from the source code to reduce the size. The...