Rick Kimball
Rick Kimball
malloc isn't ever going to be perfect, You are only looking at a snapshot of the stack usage when you call malloc. In the next call, the stack might walk...
what do you plan to do when your malloc fails?
The alternative to the approach suggested is to move the STACK pointer to say 0x2000 0000+1024 at the start. Move the start of heap to 0x2000 0000+1024 and let it...
Thinking about it more you would also have to adjust the start of RAM to be above the stack .. so 0x2000 0000+1024 and heap to start at start of...
I personally feel you should suffer failure if you are using malloc()/new in an embedded application. Memory fragmentation will eventually cause your device to fail at the least opportune moment....
Is there any way to add an additional format specifier for binary? I'd love to be able to use: Serial.printf("bits=0b%08b\n", 0x33);
Thanks @justinschoeman! We learn something new everyday.
BTW: my configuration is the latest source code compiled Ubuntu 15.10 3.3V ft232rl ftdi dongle from sparkfun msp430fr5969 launchpad
Picture of the default bsl-entry-sequence as it looks to a logic analyzer 
I only backed up to the old one to see if it would work after the latest version failed. I only needed the flash-bsl feature to recover an FRAM chip...