Menu

#63 Peripheral RAM block mapping

closed-fixed
5
2012-03-22
2010-11-20
No

Please ensure that special purpose RAM blocks (such as the USB RAM in MSP430F55xx chips) are not used as general-purpose memory by the linker. Some means for returning these special purpose RAM blocks to the general RAM pool when their associated peripherals won't be used would also be a nice feature.

Discussion

  • Peter A. Bigot

    Peter A. Bigot - 2012-03-22

    The msp430mcu part of this.

    commit 36f03e85daf909091f718504c5511d72a2eda345
    Author: Peter A. Bigot <pabigot@users.sourceforge.net>
    Date: Thu Mar 22 01:50:40 2012 -0500

    SF 3113886 Peripheral RAM block mapping

    Create custom memory maps that treat the USB memory as normal RAM for cases
    where USB is not required.

     
  • Peter A. Bigot

    Peter A. Bigot - 2012-03-22

    Note: Current development msp430mcu does not have USB memory for the 55xx chips; I'm hoping this will be fixed in the next few days. The fix has been validated with a build for the 5630.

    commit c2c87dede340cea31724cb907c5017be01ca2500
    Author: Peter A. Bigot <pabigot@users.sourceforge.net>
    Date: Thu Mar 22 04:01:56 2012 -0500

    SF 3113886 Peripheral RAM block mapping

    Enhance the concept of an MCU identifier to accept a single suffix _foo, the
    presence of which causes an extra ldscript path to be added, and an extra
    CPP define to be present. E.g., given -mmcu=msp430f5529_nousb, the C
    preprocessor will define:

    __MSP430F5529__
    __MSP430F5529_NOUSB__

    and the script paths will prefer the memory.x found in
    .../ldscripts/msp430f5529/nousb/ over the one in .../ldscripts/msp430f5529/.

     
  • Peter A. Bigot

    Peter A. Bigot - 2012-03-22
    • status: open --> closed-fixed
     

Log in to post a comment.