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.

OMAP3515 with 512MB of SDRAM support

Other Parts Discussed in Thread: OMAP3515

Hi !

 

I am using a OMAP3515 with the 256MB SDRAM. It is working fine. However, for future support, we have to double the size of the SDRAM. We changed the x-loader and uboot. After the changes, we can access the memory location over the 256MB but we cannot use the memory after boot up. Here is the complain.

 

Memory policy: ECC disabled, Data cache writeback Truncating RAM at 80000000-9fffffff to -8fffffff (vmalloc region overlap).
OMAP3515 ES3.1 (full speed SGX, no IVA2)
SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000 Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024 Kernel command line: mem=512M console=ttyS2,115200n8 root=/dev/mtdblock4 rw rootfstype=yaffs2 stdin=serial Clocking rate (Crystal/DPLL/ARM core): 19.2/332/600 MHz Reprogramming SDRC GPMC revision 5.0
IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts Total of 96 interrupts on 1 active controller OMAP34xx GPIO hardware version 2.5 PID hash table entries: 1024 (order: 10, 4096 bytes) OMAP clockevent source: GPTIMER1 at 32768 Hz
Console: colour dummy device 80x30
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total

Is there any idea about this?

 

Philip