This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP3530 POP Memory Organization

Hello,

   I have a Embest DevKit8000 with a OMAP3530DCUS chip on it. The Win CE 6.0 R3 BSP supplied by the vendor (Embest) is a rather old and buggy  (Bsquare 6.09) and I can only get my builds to work with the memory configured with 128Meg of SDRAM. I have everything running on this unit in a release build but now need to bump this up to 256Meg in order to load a debug OS build. The BSP (based on the EVM3530) has a flag BSP_SDRAM_BANK1_ENABLE but setting this to 1 causes the OS boot to fail (I did update XLDR and EBOOT since they are the ones that map the memory configuration.

Q1:  The somewhat vague documentation that came with the board indicates the board has 256Meg on board -- Since the SDRAM is located on the POP module on the chip itself I was wondering if there is a way to identify and verify what the memory chip on this thing actually is?

Q2:  Assuming I do have a 256MB SDRAM - how would the OMAP see the memory   The TRM says there are 2 SDRC chip selects going to the POP and that each CS only handles 1Gb or 128MB -- so if I have a 256M on the chip I gather that I enable the bank 1 chip select (rather than try to enlarge the CS address range in th SDRC registers)

Q3: Since my build includes DSPLINK and is compiled and working I would like to add the "extra" memory onto the end by enlarging NK and moving the RAM section behind the CMEM_DSP section

    Current working config.bib  

NK                        84001000    01FFF000    RAMIMAGE ; 32MB - 4K  
RAM                     86000000    02800000    RAM   ; 40 MB  
DISPLAY              88800000    01000000    RESERVED ; 16MB  
CMEM_DSP         89800000    02800000    RESERVED ; 40 MB (+128MB later)

    Trying to do this:  

NK                          84001000    047FF000    RAMIMAGE ; 72MB - 4K  
DISPLAY                     88800000    01000000    RESERVED ; 16MB  
CMEM_DSP      89800000    02800000    RESERVED ; 40 MB  
RAM                         8C000000    02800000    RAM      ; 40 MB  
; or....  
;RAM                         8C000000    08000000    RAM      ; 128MB       

Looks like if I do this I need to set AUTOSIZE to off -- Do I need to keep NK and RAM sections contiguous?  I would like to avoid this if possible as it will for rebuilding of the DSPLINK code and moving the display addresses in image_cfg.h..

Q4:   I'd like to confirm the files I need to be messing with to make sure I'm not missing one:

      platform/<OS Name>/DevKit8000.bat (a.k.a EVM3530.bat) in the Platform root dir   turn on BSP_SDRAM_BANK1_ENABLE?

      platform/<OS Name>/SRC/Inc/addrtab_cfg.inc   physical to virtual memory mapping... 

      platform/<OS Name>/SRC/Boot/xldr/platform.c   Memory_Setup()

      platform/<OS Name>/Files/config.bib   Defines the locations of various components including NK, RAM, DISPLAY, CMEM   also sets AUTOSIZE 

      platform/<OS Name>/SRC/Inc/image_cfg.h

  •  Defines the size of the DEVICE_RAM_XXX   #define DEVICE_RAM_SIZE                 0x10000000

Thanks, Bill