video playing using h/w accelerator

Panda board is not supported in this forum.

Could you try Ducati binary like indicate in next post?

http://e2e.ti.com/support/omap/f/849/p/217986/768060.aspx#768060

In this post it is indicated for 4AJ.1.1 and Blaze.

What release are you using? 4AJ1.1?, if it is 4AJ.2.1 follow same instructions.

I tried with 4Aj1.1 and 4AJ.2.1.

if I use the above binaries I'm getting below error.

[    8.020599] omap-rproc omap-rproc.1: Loaded BIOS image ducati-m3.bin, size 7664364
[    8.030517] omap-rproc omap-rproc.1: BIOS image version is 2
[    8.037414] rproc_check_poolmem: section size does not fit within carveout memory
[    8.045593] omap-rproc omap-rproc.1: static memory for IPU_MEM_IPC_VRING doesn't belong to poolmem
[    8.055328] omap-rproc omap-rproc.1: Failed to process the image: -28.

so I'm using the binary form the working ICS file system, which was using the H/w accelerator on Panda board ES(omap 4460). But I'm getting the above error(mentioned in previous post).

Hi Vnai,

That error is because the memory needed by ducati have change, try enabling HIGHMEM in your kernel. That should allow you to start ducai properly.

Hi,

I was tried by enabling CONFIG_HIGHMEM in my kernel (3.0.31)

but i am getting the build errors

drivers/media/video/tiler/tiler-iface.c: In function 'tiler_virt2phys':
drivers/media/video/tiler/tiler-iface.c:160: error: implicit declaration of function 'kmap_atomic'
make[4]: *** [drivers/media/video/tiler/tiler-iface.o] Error 1
make[3]: *** [drivers/media/video/tiler] Error 2
make[2]: *** [drivers/media/video] Error 2
make[1]: *** [drivers/media] Error 2

With Regards

V

Are you changing something else in the kernel?, because I don't see any kmap_atomic in that file line 160.

Please check the changes you are doing and try again.

Hi Israel,

Thank you for the answer.

We have the same issue.

HIGHMEM is enabled in the .config, but still the same issue:

The kernel is based on the Blaze - 4AJ.2.1 with some modifications.

As you know, we are using the RFBI, so HDMI, DPI and other DSS modules are disabled.

[ 5.491699] omap-rproc omap-rproc.1: Loaded BIOS image ducati-m3.bin, size 7664364
[ 5.501495] omap-rproc omap-rproc.1: BIOS image version is 2
[ 5.508331] rproc_check_poolmem: section size does not fit within carveout memory
[ 5.516754] omap-rproc omap-rproc.1: static memory for IPU_MEM_IPC_VRING doesn't belong to poolmem
[ 5.526855] omap-rproc omap-rproc.1: Failed to process the image: -28

I have few ducati-m3.bin - what are differences:

-rwxr-xr-x 1 gil gil 1388356 2012-10-31 11:14 ./hardware/ti/omap4xxx/domx/Ducati_binary/etc/firmware/ducati-m3.bin
-rwxr-xr-x 1 gil gil 1388356 2012-10-31 11:14 ./hardware/ti/domx/Ducati_binary/etc/firmware/ducati-m3.bin
-rw-r--r-- 1 gil gil 6803232 2012-10-31 17:55 ./out/target/product/blaze/system/vendor/firmware/ducati-m3.bin
-rw-r--r-- 1 gil gil 7664364 2012-11-08 11:46 /home/gil/Downloads/4AJ.2.1_Blaze_ducati-m3.bin

I am using the blaze system.img - by just downloading it, but I think I will use my compiled system.img.

Any ideas?

Thank you

Hi Gil,

The default ducati-m3.bin that comes in the mydroid is an old version, what you have to do is to replace that with the prebuild version that match with that release as pointed in the Relese Notes.

Building Ducati

Appropriate Ducati binary can be found on Android: Working with pre-built binaries page.

Just download the binary and place it in out/target/product/<blaze or blaze tablet>/system/vendor/firmware/ducate-m3.bin before create the system.img. Or if you aready flash the system.img try pushing the file using adb.

After that it should work.

Hi Israel,

As you see, the file I have downloaded from Omappedia 4AJ.2.1 is 7664364 bytes.

Which is what the log says it is loading too.

So I have the new ducati-m3.bin in the system:

root@android:/system/vendor/firmware # ls -l
-rw-r--r-- root root 7664364 2012-10-19 09:08 ducati-m3.bin
lrw-r--r-- root root 2012-10-18 15:19 hdcp.keys -> /factory/hdcp.keys
-rw-r--r-- root root 199068 2012-10-18 15:59 tesla-dsp.bin

Do I need to do anything else in the kernel to expect this big binary file?

Thank you

Gil

Hi,

No, I have only changed the CONFIG_HIGHMEM in the configeration. If I disable this the Build didn't facing any errors.

Error 0x8000101a from ducati Corresponds to ErrorUnsupportedIndex.

Log shows Setparam call for Enhanced port reconfig is resulting in this.

This could happen due to index mismatch between ducati and domx (mostly due to version mismatch in two)...

Is There any ducati binary available for panda board ES using 3.0.31 kernel and jelly bean FS .

Is It possible to increase the carveout memory.

Check this: http://www.omappedia.com/wiki/4AI.1.7_OMAP4_Icecream_Sandwich_Panda_Notes

It is not JB, but is is a kernel 3.0.31 and ducati is working, so you can use that kernel, change the FS to one from JB and use it's ducati-m3.bin if that meets your expectations.

carvout memory is increased by using HIGHMEM, seems like that patch fix that in the release from that link.

Hi,

I already used that ducati binary.

I'm getting carveout memory issue.

I try to solve that by enabling HIGHMEM in the kernel configeration. But if enable that i am getting build errors.

Hi Gil,

It is a big file because it has the OS for the M3 cores, video codecs, etc. You don't need to do anything else, are you still having issues?

Hi Israel,

Nope, I wasn't able to resolve this issue.

I tried many configurations.  But in the end - I tried the kernel you attached with the 9 patches patched and still the same issue.

I run the kernel on my board (change the Panda mach-id to mine to be able to boot) and still the same issue.

I have attached the log.8814.logcat_4AJ.1.7_panda_mem4g.txt

Thank you

Gil

Gil,

Are you trying with the kernel from AI.1.7 release?, if that is the case you should use the ducati binary from that release to, it should be this size:

-rw-rw-r-- 1 israel israel   6727928 Oct 25 21:10 4AI.1.7_Blaze_ducati-m3.bin

I tried this now, Still the same issue.

<6>[ 10.809051] omap-rproc omap-rproc.1: Loaded BIOS image ducati-m3.bin, size 6727928
<6>[ 10.818786] omap-rproc omap-rproc.1: BIOS image version is 2
<4>[ 10.826293] rproc_check_poolmem: section does not fit in carveout memory, pa=0xb2a00000 size=0x100000 st_base=0xef200000 st_size=0xd300000
<3>[ 10.843353] omap-rproc omap-rproc.1: static memory for IPU_MEM_IPC_VRING doesn't belong to poolmem

if (pa < pool->st_base || pa + size > pool->st_base + pool->st_size) 

So, pa=0xb2a00000 < st_base=ef200000 - which causes the failure.

It is not the size, only the start address.

Which is defined here: omap4_ducati_heap_addr = 0xef200000

I am not sure where 0xb2a00000 is coming from...

Gil

HI Israel,

One more thing to add to my previous post.

My board is a bit different then Panda board by having one a different memory:

static __initdata struct emif_device_details emif_devices = {
.cs0_device = &lpddr2_micron_4G_S4_dev
};

micron is the same as elpida, but we use 4G instead of 2G and CS0 instead of CS0 and CS1.

Thank you

Can you share the boot args you are passing to the kernel?

bootargs=console=ttyO2,115200n8 mem=456M@0x80000000 mem=512M@0xA0000000 init=/init vram=10M omapfb.vram=0:4M androidboot.console=ttyO2

Thank you

Gil,

Try passing "mem=1G vmalloc=768M" instead of "mem=456M@0x80000000 mem=512M@0xA0000000"

Gil,

Try what Grigory mention, but since you are using a 4G memory I am not sure about the fist parameter, it might be changed. Please try also changing it to 4G. But you need the vmalloc.

Hi Israel,

Nope, that didn't work, still the same issue:

Here is my the full bootargs:

#define CONFIG_BOOTARGS "console=ttyO2,115200n8 mem=4G vmalloc=768M init=/init vram=48M omapfb.vram=0:2M,1:2M androidboot.console=ttyO2 omapdss.debug=y omapfb.debug=y consoleblank=0 omapfb.mode=kopin_a230_panel:428x240"

What else can I do?

Thank you