We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hello,
Here is an email I have just (re)sent to Keil support:
"Hello,
Could you please make sure the RAM drive uses a variable that is mapped to the start address provided in "File_Config.c" instead of a pointer to that address...? As it is now, the linker will not report collisions between the RAM drive and any other RAM region! This could really improve the quality of RL-ARM based products, I think."
Can't that only happen if you reveal the area for the RAM file system to the linker as RW area? That in fact would be... unwise.
RAM_DRIVE 0xA1200000 0x400000 { ; ***************************************************************** ; * DO NOT MAP ANYTHING INTO THIS REGION - RESERVED FOR RAM DRIVE * ; ***************************************************************** }
As you see, I did not map anything into the reserved region.
And while they're at it, they should maybe change malloc so it doesn't return some strange value from a run-time allocated pool.