Code and BIOS in Flash, Run in RAM - gone?

I received my RCM4200 board and read several manuals.

In several places, they refer to the “Code and BIOS in Flash, Run in RAM” option.

The Dynamic C IDE shipped with my product doesn’t even have this option, even though the help still referred to it.

After downloading ver 10.46, the option is still missing but at least the help has been updated.

My only choices are RAM and FLASH for the “Store Program In” option.

With all the advice to choose “Code and BIOS in Flash, Run in RAM”, why can I no longer do this?

Why is the memory usage documentation so vague and useless? I am still trying to figure out if my code is in flash, sram, fsram, or serial flash. I have seen mention that code can be stored in any one of these, but no explanation as to how or when.

In one manual, it says that code can be run in battery backed sram - I’ve never seen the option to do this and assume it is for boards without fsram.

I can’t be the only one who is fighting this battle - any comrades in arms?

I use 10.21, an earlier version, and I have the following options:

Compile to target > Compile to Flash.
Compile to RAM.
Compile to Flash, Run in RAM.

I also set my project options ‘compiler tab’ window accordingly.

All the info you require is in the manuals albeit I agree finding your way around them takes some getting used to. A decent search facility would help and save time!

I generally use the ‘Compile to RAM’ option, which then runs the program in RAM, when I am doing some new software and fair bit of debugging and subsequent fixes.

I generally use the ‘Compile to Flash, Run in RAM’, which stores the program in FLASH but runs it in RAM, when debugging is complete and I want to run in standalone mode.

This may not directly answer your question but at least you will know what my earlier version does…and seems to me should should have these options or more.

Regards.

…at least when the RCM4200 is selected.

After much digging, I have decided that since the mfr only recommends running from RAM for the high speed RCM4200 that they forced the issue: the option to run from flash actually stores in flash but runs from ram while the option to run from ram runs from ram without the extra step of saving to flash (in order to save wear on the flash during debugging).