MSP430F5342: BSL code retention during power cycle

Jace,

I did use the default linker file and just added the following to the MEMORY section:

    ZAREA                   : origin = 0x1000, length = 0x0010
    BSL430_VERSION_VENDOR   : origin = 0x1010, length = 0x0001
    BSL430_VERSION_CI       : origin = 0x1011, length = 0x0001
    BSL430_VERSION_API      : origin = 0x1012, length = 0x0001
    BSL430_VERSION_PI       : origin = 0x1013, length = 0x0001
    ZAREA_CODE              : origin = 0x1014, length = 0x002E
    BSLSIG                  : origin = 0x17F0, length = 0x000C
    JTAGLOCK_KEY            : origin = 0x17FC, length = 0x0004

and the following to the SECTIONS section:

    .ZAREA      : {} > ZAREA
    .BSL430_VERSION_VENDOR : {} > BSL430_VERSION_VENDOR
    .BSL430_VERSION_CI     : {} > BSL430_VERSION_CI
    .BSL430_VERSION_API    : {} > BSL430_VERSION_API
    .BSL430_VERSION_PI     : {} > BSL430_VERSION_PI
    .ZAREA_CODE : {} > ZAREA_CODE
    .BSLSIG     : {} > BSLSIG
    .JTAGLOCK_KEY : {} > JTAGLOCK_KEY

I did this to make it look like the linker file that came with the template project for the msp430f5418a device (I checked the MSP430F5342 datasheet for the proper memory offsets.) Do I need to do something more? Regarding the lnk430FXXXX_BSL_AREA.cmd file, I did not find such a file anywhere in my installations (I also tried lnk430F5342_BSL_AREA.cmd to match my device.) Where can I find this file?

Thank you,

svl123

Hi Jace,

I think I understand what the problem is now. In the .map file, the main body of BSL code has the output section label .text which is placed in memory starting at 0x10000:

.text      0    00010000    0000081c     
                  00010000    00000244     BSL430_Command_Interpreter.obj (.text:main)
                  00010244    000001a8     BSL430_PI_TA.obj (.text:PI_receivePacket)
                  000103ec    000000d0     BSL430_API.obj (.text:BSL430_writeMemory)
                  000104bc    00000086     BSL430_Command_Interpreter.obj (.text:sendDataBlock)
                  00010542    00000074     BSL430_Command_Interpreter.obj (.text:receiveDataBlock)
                  000105b6    00000054     BSL430_API.obj (.text:BSL430_crcCheck)
                  0001060a    00000054     rts430x_lc_rd_eabi.lib : autoinit.c.obj (.text:__TI_auto_init_nobinit_nopinit_hold_wdt:__TI_auto_init_nobinit_nopinit_hold_wdt)
                  0001065e    0000004e     BSL430_PI_TA.obj (.text:sendByte)
                  000106ac    00000048     BSL430_PI_TA.obj (.text:PI_sendData)
                  000106f4    00000046     BSL430_API.obj (.text:BSL430_readMemory)
                  0001073a    00000042     BSL430_API.obj (.text:BSL430_unlock_BSL)
                  0001077c    0000003e     rts430x_lc_rd_eabi.lib : lsl32.asm.obj (.text:l_lsl_const)
                  000107ba    0000002a     BSL430_API.obj (.text:BSL430_massErase)
                  000107e4    00000024     rts430x_lc_rd_eabi.lib : copy_zero_init.c.obj (.text:decompress:ZI:__TI_zero_init_nomemset:__TI_zero_init_nomemset)
                  00010808    0000000c     BSL430_API.obj (.text:_system_pre_init)
                  00010814    00000006     rts430x_lc_rd_eabi.lib : exit.c.obj (.text:abort)
                  0001081a    00000002                            : startup.c.obj (.text:_system_post_cinit)

This code has length 0x81c which is too long for the 2kb allocated to the BSL area (as you mentioned in your last reply). Now, based on the .cmd file, the .text section wants to go into FLASH:

#ifndef __LARGE_DATA_MODEL__
    .text       : {} > FLASH                // Code
#else
    .text       : {} >> FLASH2 | FLASH      // Code
#endif

So I copied this line from the linker file that came with the template (in the MEMORY section of the .cmd):

FLASH					: origin = 0x1042, length = 0x7AE

But this gives me the memory overflow error, as before. To get rid of this error, how much freedom do I have to shuffle memory around? Can I move the BSLSIG & JTAGLOCK_KEY section to 0x1042, move the FLASH down (start at 0x1052) and then get rid of the .infoD section and allocate its space to FLASH as well? Then I would have one contiguous block of memory (from 0x1052 to 0x187F) which should give me enough space for my .text section.)

I looked at the .map file and there doesn't seem to be anything written to the .infoD section of memory. Is it safe to get rid of it? Also, is it safe to move the BSLSIG & JTAGLOCK_KEY sections to a different address?

Thank you,

svl123

multiple edits: fixed addresses of above memory sections

Ok, I understand. I'll leave the locations as they are.

One last question regarding this topic: how do I tell the linker to "overflow"? Is the following an example of "write to FLASH and if not enough space overflow to FLASH 2":

.text       : {} >> FLASH2 | FLASH

Thanks,

svl123