AnsweredAssumed Answered

Hiding BF527 upper memory from vdk

Question asked by MartyC on May 8, 2012
Latest reply on May 9, 2012 by MartyC

I have 32 megabytes of SDRAM on my system (with a BF527) and use the following
in the LDF file:

MEM_SDRAM0_BANK0 { TYPE(RAM) START(0x00000004) END(0x003FFFFF)  WIDTH(8) }
MEM_SDRAM0_BANK1 { TYPE(RAM) START(0x00400000) END(0x007FFFFF)  WIDTH(8) }
MEM_SDRAM0_BANK2 { TYPE(RAM) START(0x00800000) END(0x00BFFFFF)  WIDTH(8) }
MEM_SDRAM0_BANK3 { TYPE(RAM) START(0x00C00000) END(0x00EFFFFF)  WIDTH(8) }

Can I safely use my own memory management for the upper 16 megabytes of

memory? For example, is the following safe?

/// Key - This must not overwrite anything that the VDK or libraries use
u8 *pHighMem = (u8 *) (16UL * 1024UL * 1024UL);
memset( pHighMem, 0xA5, (16UL * 1024UL * 1024UL));  

If not, is there a way for me to self-manage the upper 16 megabytes of memory?
I do not want them to be visible to the VDK or underlying libraries.

Outcomes