07-04-2007 10:42 AM
07-11-2007 01:42 PM
AnthonV,
Could you explain why you woud like to change the heap size? Also, I'm assuming you mean the heap set aside for the operating system, is that right?
07-24-2007 02:01 AM
Hi Allison, I want to increase the heap size as I am worried that I might run out of memory when loading many images into the heap. So I am referring to the heap allocated to the application's data. If this resizes automatically as required then this is not an issue and I do not have to set it at all.
I'm looking at the RT Get Memory Stats.vi output and noticed that the 'Heap Contiguous' is getting close to zero - assuming that IMAQ wants a contiguous block for every image's data this is soon going to be a problem for me. Have a look at the attached image - it shows the output from RT Get Memory Stats.vi. Currently it shows 7MB contiguous heap available, but another few 2megapixel images loaded will reduce this to zero.
It is also very possible that I misunderstand the memory allocation process in the RT targets so let me know if this is the case.
Thanks
Anthon
07-25-2007 11:44 AM
07-26-2007 01:01 AM
Unfortunately these aren't images that can be saved to disk. Some are created on-line from captured images and some are read from flash at startup - they are required for the image processing that is done on the device.
What I'm asking if one has control over the allocation of the RAM to code space and heap/stack space as on a normal system. In some case you might have a large vi that requires more code space, but in others there might be a need for more dynamically allocated heap.
I'm using the cheapest CVS at the moment.
07-26-2007 04:51 PM