CCS/MSP430F5659: How to unlock and write to iformation memory segment A ?

Hi Mat,

I had read this information before the open this case, I still think that I have any problem with the silicone of this device or somethink that I does not exactly understand.

I had solve this problem through the following way, in my origin code I copy the image of the segment to RAM, then update it's image in the RAM according to the requered data, then erase the segment in information memory, then write the updated image from the RAM to information memory:

unsigned long address = 0x1900;//segment A

char data = 0x55;

FCTL4 = FWPW;

if(FCTL3 & LOCKA)

FCTL3 = FWPW + LOCKA;

//clear segment

FCTL3 = FWKEY;

FCTL1 = FKEY + ERASE;

*address = 0;

FCTL1 = FWKEY;

FCTL3 = FWKEY + LOCK;

//write data

if(FCTL3 & LOCKA)

FCTL3 = FWPW + LOCKA;

FCTL4 = FWPW + LOCKINFO;

while(FCTL3 & BUSY){};

FCTL4 = FWPW;

if(FCTL3 & LOCKA)

FCTL3 = FWPW + LOCKA;

FCTL1 = FWKEY;

FCTL3 = FWKEY + WRITE;

*(char*)(address) = data;

FCTL1 = FWKEY;

FCTL3 = FWKEY + LOCK;

if(FCTL3 & LOCKA)

FCTL3 = FWPW + LOCKA;

FCTL4 = FWPW + LOCKINFO;

I dont know why, but only this a very stranger method is working, everytime I need to check the LOCKA bit to access to the segment A (to erase or to write) ?

I think that I wrote in the code above unnecessary rows, but I don't understand it exactly, in my previous projects for another microcontrollers from this family it was more simple to implement.

Hi All,

I have error problem when using the TI download app, MSP430 USB Firmware Upgrade Example with data need to put in the information memory, infoD.

My chips is MSP430F5659, and my data in TI-TEXT file are:

@1800

FF AA

@8000

4F 14 F1 03 C1 43 00 00 E2 B2 3E 09 7A 24 B1 13

F6 6C C1 4C 00 00 E2 C2 3E 09 73 3C 03 43 C2 3C

03 43 C0 3C 03 43 BE 3C 92 B3 2C 53 BB 24 B1 13

24 84 C1 4C 00 00 B6 3C B1 13 38 65 A2 B3 2C 53

…

I don’t have error without the two line (@1800, FF AA). My code is:

case UPDATE_CODE_CMD:

       // set starting BSL process

       __disable_interrupt();

       if (FCTL3 & LOCKA) {

              FCTL3 = FWKEY | LOCKA;

       }

       else {

              FCTL3 = FWKEY;

       }

USBKEYPID = 0x9628;                                  

USBCNF &= ~PUR_EN;              

USBPWRCTL &= ~VBOFFIE;                               

USBKEYPID = 0x9600;                                  

__delay_cycles(500000);

       ((void(*)())0x1000)();           // Call BSL

       break;

Any idea to fix this problem?

Thanks,

Jack

Hi Mat,

This is my problem, I had write a simple code to write two symbols  'A' then 'B' to the information memory segment A to address 0x1980, in the first case it works properly but in the second case I have a problem, the program counter jumps to any statement outside of the current function, when I change the code at the first write 'B' then 'A' in the same manner the problem appears always in the case 'B':

#define u8 unsigned char

void main(void)

{

    u32 addr = 0;

    FCTL4 = FWPW;

    if(FCTL3 & LOCKA)

           FCTL3 = FWPW + LOCKA;

    //clear segment

    while(FCTL3 & BUSY){};

    FCTL3 = FWPW;

    FCTL1 = FWPW + ERASE;

    *(u8*)(0x1980) = 0;

    while(FCTL3 & BUSY){};

    FCTL3 = FWPW + LOCK;

    if(!(FCTL3 & LOCKA))

           FCTL3 = FWPW + LOCKA;

    FCTL4 = FWPW;

    //write 'A'

    FCTL4 = FWPW;

    if(FCTL3 & LOCKA)

           FCTL3 = FWPW + LOCKA;

    FCTL3 = FWKEY;

    FCTL1 = FWKEY+WRT;

    *(u8*)(0x1980) = 'A';

    //write 'B'

    FCTL1 = FWKEY+WRT;

    addr = 0x1980;//I had try it with the address 0x1981 and get the same result

    *(u8*)(addr) = 'B';

    FCTL1 = FWKEY;

    FCTL3 = FWKEY+LOCK;

    if(FCTL3 & LOCKA)

           FCTL3 = FWPW + LOCKA;

    FCTL4 = FWPW;

    FCTL1 = FWKEY;

    FCTL3 = FWKEY+LOCK;

}

This problem appears because the following compiler's interpretation, I work with MSP430F5659 MCU, I suppose that is a silicon problem because I haven't the same problem with the other segments of information memory, I can write to the segment A using constant addresses under debug session, sometimes depend of the current code compilation (the sentence assignment in the code memory) it works properly (case 'B') under free running condition (no debug session) :

If I am in your situation, for clearing this issue (flash writing) I will use UART logging (during free running), and not breakpoint debugging. I will also try to write (after segment erase) at two different location inside Info segment A, for example 01980h and 01990h. I don't code in C for MSP430, so don't know about staff related to pointers / addresses, but produced code in assembler is OK.

EDIT: I just tried my flasher for writing data to Info A segment of MSP430F5659. Block write executed from RAM is used.

File test_infoa_5...

org 01980h
dw 00123h, 04567h, 089ABh, 0CDEFh, 01122h, 03344h, 05566h, 07788h
...
end

@1980
23 01 67 45 AB 89 EF CD 22 11 44 33 66 55 88 77
...
q

Flashing...

d:\msp430>flash -f test_infoa_5.txt -uinfoa -einfo -w -v

File: "test_infoa_5.txt"
@1980 128 bytes
Total Size: 128 bytes

Found SBW+ at COM7

Get Device
# JTID Fuse Device Core Hard Soft LotWafer DieX DieY
1  91   OK   3081  2106  10   10  B7A50951 0A00 1100

Unlock InfoA

Erase Info
Time: 135 ms

Write
Time: 132 ms  Speed: 0,9 KB/s

Verify
Time: 52 ms  Speed: 2,4 KB/s

Release Device

Total Time: 422 ms

d:\msp430>flash -rq 1980

Found SBW+ at COM7

Get Device
# JTID Fuse Device Core Hard Soft LotWafer DieX DieY
1  91   OK   3081  2106  10   10  B7A50951 0A00 1100

Read Quick
#1
1980: 0123 4567 89AB CDEF 1122 3344 5566 7788
Time: 39 ms

Release Device

Total Time: 125 ms

d:\msp430>