Enabling 256 ram (for those that have it)

Jan 14, 2010 at 6:07 AM
Edited Jan 14, 2010 at 12:44 PM

At the request of Pavel, and with hopes of making this discussion more organized, I have started a new topic for this. I should mention that I began discussing this issue on 011309 in a different thread:


(Note: there are a few more posts in the other thread, but I'll continue discussing the issue here)


That being said, I will give a recap of the issue...On the Rev. C3 (and I assume newer) BB, the available ram was updated to 256 mb. In the BSP for the EVM, bsquared has included an environment variable (BSP_SDRAM_BANK1_ENABLE) to enable 256 mb ram, and it is used in config.bib, located in the TI_EVM_3530->Files directory. Adding this variable and doing a clean build created a successful build, but using MLO and EBOOTSD.nb0 to boot NK.bin off an SD card, the boot fails to continue past the jump into NK.bin. Is there another change I should have made? Advise on the issue is appreciated.


Woops, sorry guys, looks like i got it working! Aparently I was correct on all I needed to do. I mentioned in the other discussion that I was wondering about DMA. DV said that the bsp didn't support it, but I was wondering what the bsp catalog item under "DMA" was for. As well, does anyone know of a good tool that can be used to monitor the system's ram and clear out areas that were filled due to memory leaks or programs that did not clean up after they were closed?


Jan 19, 2010 at 4:59 AM

For application work I recommend this tool:



For OAL level work, your test cases should take care of this...