JozefL

Yes, you shouldn't need to change any settings to be able to read and write from the main FRAM block. I'm able to observe a persistent variable being incremented with the following code on the FR5994 #include <stdio.h> #include <msp430.h> unsigned long __attribute__((section(".persistent"))) persist = 5; int main (void) { WDTCTL = WDTPW | WDTHOLD; while (1) { persist++; printf ("persist %ld\n", persist); for (int i = 0; i < 1000; i++); } return 0; } I don't know what setup Energia does by default, but you should check that at least the watchdo

Hi Stefan, Yeah TI changed some of the URLs around, so the following link still points to an old 8.x.x release even though it used to be used to download the latest: http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/latest/index_FDS.html But this link will always have the latest release https://www.ti.com/tool/download/MSP430-GCC-OPENSOURCE Thanks! Jozef

Hi, It seems there is a bug using the "persistent" attribute in C++. Internally, the compiler validates the attribute and emits that warning before the initializer has been parsed. The attribute works fine in a C program. As a work-around I would suggest explicitly putting the variable in the ".persistent" section, this has the same effect as the "persistent" attribute. unsigned long int __attribute__((section(".persistent"))) FRAM_count = 5; Apologies that this bug caused confusion! Regards, Jozef

Hi, It's good to see people using the new MSP430-GCC toolchain. I'm glad it's being made available within the Energia client. I'll note that you can use the "upper", "either", "lower" attributes to place code/data in a specific memory region, instead of having to manually specify a section. So you can do ADI_REG_TYPE __attribute__((upper)) Param_Data_IC_1[PARAM_SIZE_IC_1] ... instead of ADI_REG_TYPE __attribute__((section(".upper.rodata"))) Param_Data_IC_1[PARAM_SIZE_IC_1] ... I'd also like to point out that the MSP430-GCC version used by "package_msp430_elf_GC