Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add FRAM attribute to Energia #31

Closed
rei-vilo opened this issue Dec 9, 2016 · 10 comments
Closed

Add FRAM attribute to Energia #31

rei-vilo opened this issue Dec 9, 2016 · 10 comments

Comments

@rei-vilo
Copy link
Member

rei-vilo commented Dec 9, 2016

FRAM is an exclusive technology, but how to leverage it for large arrays?

Please document how to use FRAM as RAM with Energia.

@spirilis
Copy link

spirilis commented Dec 9, 2016

I had a thread on 43oh for Wolverine FRAM tips & tricks that might still apply...

@rei-vilo
Copy link
Member Author

rei-vilo commented Dec 9, 2016

@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;

@spirilis
Copy link

spirilis commented Dec 9, 2016

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)

@rei-vilo
Copy link
Member Author

rei-vilo commented Dec 9, 2016

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;

@rei-vilo rei-vilo changed the title How to use FRAM as RAM with Energia? Add FRAM attribute to Energia Jan 8, 2017
@rei-vilo
Copy link
Member Author

rei-vilo commented Jan 8, 2017

Add FRAM attribute to Energia in the pins_energia.h related to FRAM-based LaunchPads.

#define FRAM __attribute__((section(".text")))

@rei-vilo
Copy link
Member Author

rei-vilo commented Jan 8, 2017

See pull-request #32

@StefanSch
Copy link
Contributor

StefanSch commented Jan 26, 2017

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
...

@rei-vilo
Copy link
Member Author

PLACE_IN_FRAMseems fine, unless @robertinant has a better suggestion.

@rei-vilo rei-vilo mentioned this issue Jan 26, 2017
@rei-vilo
Copy link
Member Author

See #32 (comment)

@rei-vilo
Copy link
Member Author

The FRAM is write protected on the MSP430FR2433. See #47.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants