Static RAM BitBanding Macro

[tmall]

Posted on April 17, 2010 at 20:22

Static RAM BitBanding Macro

#stm32 #stm32 #bitbanding #bitbanding #bitbanding #bitbanding #stm32 #stm32

[tmall]

Posted on May 17, 2011 at 13:47 The original post was too long to process during our migration. Please click on the provided URL to read the original post. https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006I6Yt&d=%2Fa%2F0X0000000bql%2FxjkbDLA3EaAatPqc4_vrOyD8hb91yJjA57zHVZB9qPU&asPdf=false

[Tesla DeLorean]

Posted on May 17, 2011 at 13:47

I can't speak to GCC, but with my old RealView tool chains the linker could take a DEF file containing addresses of code/data in ROM that could be linked against the code going into FLASH/RAM. It could pretty much point to anything, anywhere.

Other than that, you should be able to control the link order, and the sections pieces of code/data are going. But as Andrew has pointed out, some of this fine grain control is mainly an embedded thing, where you do want to explicitly control where specific sections have to end up in the image, including initialized variables which are tacked at the end of the FLASH/ROM image and copied into RAM by the C runtime. If you can't do it with the linker, a post link stage which can fixup, patch or checksum, or otherwise package the firmware image is something I would consider. -Clive