[Gen9 Android Development] Quallenauge:
Okay, so maybe the ducati framework is the bad guy!

Using the 1Gbyte model is the same as the file doesn't exists. Have a look at the logfile:

I/cat ( 488): <6>[ 8.482421] omap-rproc omap-rproc.1: Loaded BIOS image ducati-m3.bin, size 5841740
I/cat ( 488): <4>[ 8.482635] rproc_check_poolmem: section size does not fit within carveout memory
I/cat ( 488): <3>[ 8.482696] omap-rproc omap-rproc.1: static memory for IPU_MEM_IPC_VRING doesn't belong to poolmem
I/cat ( 488): <3>[ 8.482971] omap-rproc omap-rproc.1: Failed to process the image: -28

The ducati subsystem isn't initialized. So camera and HW video shouldn't work.

So the graphics subsystem is working: good!

For the ducati I have made some modifications, because TI has made some changes in this area. It's work for me and the delivered archos ducati, but not for you. So my bet is the memory definition. Maybe I made some mistake there. Can please someone have look on this (I modified my kernel to print out some values) and the according files?:

I/cat ( 619): <6>[ 0.000000] android_display: ion carveouts: 77594624 tiler2d, 0 nonsecure
I/cat ( 619): <6>[ 0.000000] omap4_total_ram_size = 0x20000000
I/cat ( 619): <6>[ 0.000000] omap4_smc_size = 0x300000
I/cat ( 619): <6>[ 0.000000] omap4_ion_heap_secure_input_size = 0x0
I/cat ( 619): <6>[ 0.000000] omap4_ion_heap_secure_output_wfdhdcp_size = 0x0
I/cat ( 619): <6>[ 0.000000] omap4_ducati_heap_size = 0x1900000
I/cat ( 619): <6>[ 0.000000] omap4_ion_heap_tiler_mem_size = 0x80000
I/cat ( 619): <6>[ 0.000000] omap4_ion_heap_nonsec_tiler_mem_size = 0x80000
I/cat ( 619): <6>[ 0.000000] omap4_smc_addr = 0x9fd00000
I/cat ( 619): <6>[ 0.000000] omap4_ion_heap_secure_input_addr = 0x9fd00000
I/cat ( 619): <6>[ 0.000000] omap4_ion_heap_secure_output_wfdhdcp_addr = 0x9fd00000
I/cat ( 619): <6>[ 0.000000] omap4_ducati_heap_addr = 0x9e700000
I/cat ( 619): <6>[ 0.000000] omap4_ion_heap_tiler_mem_addr = 0x9e680000
I/cat ( 619): <6>[ 0.000000] omap4_ion_heap_nonsec_tiler_mem_addr = 0x9e600000
I/cat ( 619): <6>[ 0.000000] Archos reference values: ARCHOS_PHYS_ADDR_DUCATI_SIZE = 0xc06f7025
I/cat ( 619): <6>[ 0.000000] ARCHOS_OMAP4_ION_HEAP_TILER_SIZE = 0x1900000
I/cat ( 619): <6>[ 0.000000] ARCHOS_OMAP4_ION_HEAP_SECURE_SIZE = 0x80000
I/cat ( 619): <6>[ 0.000000] ARCHOS_PHYS_ADDR_DUCATI_MEM = 0x80000
I/cat ( 619): <6>[ 0.000000] ARCHOS_PHYS_ADDR_HEAP_TILER = 0x9e700000
I/cat ( 619): <6>[ 0.000000] ARCHOS_PHYS_ADDR_HEAP_SECURE = 0x9e680000
I/cat ( 619): <6>[ 0.000000] ARCHOS_PHYS_ADDR_OMAP_RAM_CONSOLE = 0x9e600000
I/cat ( 619): <6>[ 0.000000] omap_ion_init: secure_input id=2 [9fd00000-9fd00000] size=0
I/cat ( 619): <6>[ 0.000000] omap_ion_init: secure_output_wfdhdcp id=5 [9fd00000-9fd00000] size=0
I/cat ( 619): <6>[ 0.000000] omap_ion_init: tiler id=1 [9e680000-9e700000] size=80000
I/cat ( 619): <6>[ 0.000000] omap_ion_init: nonsecure_tiler id=3 [9e600000-9e680000] size=80000
I/cat ( 619): <6>[ 0.000000] omap_ion_init: system id=0 [0-0] size=0
I/cat ( 619): <6>[ 0.000000] omap_ion_init: tiler_reservation id=4 [0-0] size=0
I/cat ( 619): <3>[ 0.000000] Archos Console values OMAP_RAM_CONSOLE_START_DEFAULT: 0xa0000000 OMAP_RAM_CONSOLE_SIZE_DEFAULT: 0x200000!
I/cat ( 619): <3>[ 0.000000] Archos Console values ARCHOS_PHYS_ADDR_OMAP_RAM_CONSOLE: 0x9fc00000 ARCHOS_OMAP_RAM_CONSOLE_SIZE: 0x100000!

The omap console has another value, but could this be the cause?

I don't get it, but if someone else had a look he find's my mistake for sure.

Stock memory definition: https://github.com/Quallenauge/kernel-archos/blob/master/arch/arm/mach-omap2/archos-memory.c

New memory initialisation routines:

https://github.com/Quallenauge/kernel-archos/blob/linux-ics-3.0.21/arch/arm/mach-omap2/omap4_ion.c

The CONFIG_ION_OMAP_DYNAMIC config option is turned ON, so this would be used for the memory definition sections.

Also an idea to get more logoutput: Add an wait statement, so the statement is printed out on adb logcat:

/ArchosKernel-3.0.21/drivers/media/video/tiler/tiler-main.c in function: tiler_alloc_block_area

if (IS_ERR_OR_NULL(mi)){
pr_err("tiler_alloc_block_area: Can't alloc block area!");
msleep(5);
goto done;
}

---------- Post added at 12:29 PM ---------- Previous post was at 12:23 PM ----------

I'm using the omaplfb from TI reference kernel, which is included since last summer.

The watchdog daemon seems to talk to the kernel module. Lets have a look at the driver file: omap_wdt.c.

I think, mostly the base TI watchdog is used at this area.

All modules where compiled everytime CM10.1 is build. This is done automatically by the scripts. Additional modules are also build. Take a look inside the BoardConfig.mk file inside the archos device folder.

Thanks for the hint!

After the kernel works for the 512MByte models, I plan to integrate your changes.

---------- Post added at 01:04 PM ---------- Previous post was at 12:29 PM ----------

I added an debug kernel, which has implemented the suggested changes:

http://www.4shared.com/file/g3DhVBvh/zImage.html

I also changed the omap console memory options.

Does this kernel gives some more output?