i.mx6q with 512MB VPU memory allocation always failed. but 1G works.

[wallyyeh]

Hi, I'm using SabreSD board with SDK-3.0.35_4.1.0 and try to downsize it's memory to 512MB, to see if it works fine for our cost down version product.

I re-compile u-boot with change the define "PHYS_SDRAM_1_SIZE    (1u * 512 * 1024 * 1024)" to make SabreSD boot with 512MB.

and use gplay to see if VPU works normally, but kernel continue output: "Physical memory allocation error!".

I change back uboot to use 1G memory and gplay works fine. I think I may need guides to setting my SabreSD board correctly with 512MB RAM.

below is my bootargs:

console=ttymxc0,115200 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 fbmem=64M video=mxcfb0:dev=hdmi,1024x768M@60,if=RGB24,bpp=32 quiet mem=512M ldo_active=on

and my GPU reserved 32M, VPU reserved 128M. any suggestion would be appreciated, thanks.

[jimmychan]

Test I.MX6dq in 512M memory , 512M should work fine.

weiping.Liu do you have any suggestion to this customer?

[wallyyeh]

Since performance tool "Antutu" is a android app, the test report seems on android?

our product is putting sabreSD board run in ubuntu 11.10

test case is following:

1. set resolution to 1920x1080

2. gplay test.mp4

I try the SDK-3.10.17 and "gplay test.mp4" works fine with 512MB.

SDK-3.0.35_4.1.0 failed, kernel just output "Physical memory allocation error!", then kernel panic.

SDK-3.0.101_4.1.1 also failed, kernel output "FIFO_RD_AUX_MSB read fails", "FIFO_RD_AUX_LSB read fails" and "Physical memory allocation error!", then kernel panic.

if I change the resolution to 1024x768(or lower, ex: 800x600), all SDKs will works fine.

seems kernel 3.0 will get memory allocation problem when call vpu_alloc_dma_buffer() (which in kernel/driver/mxc/vpu/mxc_vpu.c) with RAM 512MB and resolution higher than 1024x768.

Since our low cost product is based on our old product which use SDK-3.0.35, we hope any patches for fix this memory allocation issue.

btw, there's a quick way to test 512MB without build u-boot, just simply passing "mem=512m" to boot kernel cmdline.