Closed rei-vilo closed 6 years ago
I had a thread on 43oh for Wolverine FRAM tips & tricks that might still apply...
@spirilis Thank you for the pointer.
I've already saw and used the trick but I want it included and fully supported in Energia.
#define PERSIST __attribute__((section(".text")))
uint8_t DisplayBuffer[LCD_MAXIMUM_Y][LCD_MAXIMUM_X] PERSIST;
Gotcha... Guess that would just mean Energia including the #define in its Energia.h file? (or something like it, like #define FRAM or #define FRAM_MEMORY as that attribute)
Yes, plus some doc!
...and a more catchy name, like FRAM
or FRAM_MEMORY
.
#define FRAM __attribute__((section(".text")))
and to use it
uint8_t DisplayBuffer[LCD_MAXIMUM_Y][LCD_MAXIMUM_X] FRAM;
Add FRAM
attribute to Energia in the pins_energia.h
related to FRAM-based LaunchPads.
#define FRAM __attribute__((section(".text")))
See pull-request #32
I am a little bit burned child with short names esp. in defines and that they got reused.
May we can find a better / unique name, e.g.
STORE_IN_FRAM
PLACE_IN_FRAM
ALLOCATE_IN_FRAM
IN_FRAM
...
PLACE_IN_FRAM
seems fine, unless @robertinant has a better suggestion.
The FRAM is write protected on the MSP430FR2433. See #47.
FRAM is an exclusive technology, but how to leverage it for large arrays?
Please document how to use FRAM as RAM with Energia.