Home/Support/Support Forum/RCM6600W: Increasing available memory when compiling to flash?
New and improved user forum site going live on 12/6 (All users will need to reset their password when the new forum is active)
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

RCM6600W: Increasing available memory when compiling to flash?

0 votes
I have some xmem buffers I'd like to make as large as possible. I was using xavail() to figure out how much memory could be allocated, and I ran into something that seemed off.

Regardless of whether I compile to flash or ram when debugging, xavail returns the same amount of free memory.

Is this an artifact of debugging, or is the amount of xmem used the same regardless of where I'm compiling to?

If it is possible to use more of the extended memory when compiling to flash, what needs to be done to allow it?
asked Nov 16, 2016 in Rabbit Software by casey New to the Community (18 points)
I've confirmed that it is not an artifact of debugging by running from flash and printing it out of serial port f.

Please log in or register to answer this question.

1 Answer

+1 vote
Best answer
Compiling to Flash does not mean executing from FLASH... The code is copied into RAM at startup as the execution speed from RAM is much faster. This is why there is no difference between the available XMEM in either mode.

Compiling to RAM when debugging is quicker to load and does not contribute to wear on the FLASH.

answered Nov 17, 2016 by petermcs Veteran of the Digi Community (1,132 points)
selected Nov 17, 2016 by casey
That's what I'd figured. Thank you for confirming. Just wish the wireless libraries didn't add in 400KB of code. Seems like it's all coming from the WPA implementation.