Hi,
I want to use fastboot to run the Hello demo of Fiasco on Odroid-Q2 board[1]. However, I failed.
Firstly, I use make fastboot_rawimage E=hello MODULE_SEARCH_PATH=...
The UART output is:
Starting download of 935936 bytes
downloading of 935936 bytes finished Kernel size: 000e4000 Ramdisk size: 00000000 Booting raw image.. Boot with zImage Wrong Ramdisk Image Format [err] boot_get_ramdisk
Starting kernel ...
Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0060ad0-0xf0061550) Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl
KERNEL: Warning: No page-fault handler for 0xee202108, error 0x94000848, pc f004
It is said the format is wrong, so I change to make fastboot_uimage E=hello MODULE_SEARCH_PATH=...
The UART output:
downloading of 937984 bytes finished Kernel size: 000e4040 Ramdisk size: 00000000 Booting kernel.. ## Booting kernel from Legacy Image at 40008000 ... Image Name: L4 Image #4 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 933888 Bytes = 912 KiB Load Address: 41000000 Entry Point: 41000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK
And nothing happen. So what`s the problem?
Thanks, Best Regards, Zachary
[1] http://www.hardkernel.com/main/products/prdt_info.php?g_code=G135278861948&a...
Hi,
On Mon Dec 01, 2014 at 02:46:46 +0000, Zachary wrote:
I want to use fastboot to run the Hello demo of Fiasco on Odroid-Q2 board[1]. However, I failed.
Firstly, I use make fastboot_rawimage E=hello MODULE_SEARCH_PATH=...
This is the right variant.
The UART output is:
Starting download of 935936 bytes
downloading of 935936 bytes finished Kernel size: 000e4000 Ramdisk size: 00000000 Booting raw image.. Boot with zImage Wrong Ramdisk Image Format [err] boot_get_ramdisk
Starting kernel ...
Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0060ad0-0xf0061550) Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl
KERNEL: Warning: No page-fault handler for 0xee202108, error 0x94000848, pc f004
It is said the format is wrong, so I change to
It complains on the ramdisk image format but there is none. fastboot_rawimage is the right one to use. Looks like there's some issue here with a page-fault that should not happen. I'm wondering how we could debug this. Is the multi-processor option enabled in Fiasco?
Adam
Adam Lackorzynski <adam <at> os.inf.tu-dresden.de> writes:
Hi,
It complains on the ramdisk image format but there is none. fastboot_rawimage is the right one to use. Looks like there's some issue here with a page-fault that should not happen. I'm wondering how we could debug this. Is the multi-processor option enabled in Fiasco?
Thanks you for your response. I am sure the multi-processor option is enabled.
I changed the execute model to "TrusteZone normal side", and I get more output:
Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0060b50-0xf00615d0) Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl L2: ID=4100c4c8 Type=1a340340 Aux=7e470001 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 Watchdog initialized SERIAL ESC: allocated IRQ 85 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: unknown compiled with gcc 4.7.3 for Samsung Exynos [] Build: #19 Mon Dec 1 16:59:44 CST 2014 Per_cpu_data_alloc: (orig: 0xf0060b50-0xf00615d0)
KERNEL: Warning: Buddy::alloc: Size mismatch: a80 v 1000 Allocate 2688 bytes (3KB) for CPU[4] local storage (offset=11894b0, 0xf11ea000-) Timer for CPU0 is at IRQ 28 Number of CPUs: 4
KERNEL: Warning: No page-fault handler for 0xee620004, error 0x94000848, pc f008
KERNEL: Warning: CPU0: Pager of 5 is invalid (pfa=00000100, errorcode=94000005)) KERNEL: Warning: CPU0: Pager of 5 is invalid (pfa=00000100, errorcode=94000005)) KERNEL: Warning: CPU0: Pager of 5 is invalid (pfa=00000100, errorcode=94000005)) KERNEL: Warning: CPU0: Pager of 5 is invalid (pfa=00000100, errorcode=94000005)) KERNEL: Warning: CPU0: Pager of 5 is invalid (pfa=00000100, errorcode=94000005)) KERNEL: Warning: CPU0: Pager of 5 is invalid (pfa=00000100, errorcode=94000005)) KERNEL: Warning: CPU0: Pager of 5 is invalid (pfa=00000100, errorcode=94000005)) KERNEL: Warning: CPU0: Pager of 5 is invalid (pfa=00000100, errorcode=94000005)) KERNEL: Warning: CPU0: Pager of 5 is invalid (pfa=00000100, errorcode=94000005)) KERNEL: Warning: CPU0: Pager of 5 is invalid (pfa=00000100, errorcode=94000005)) KERNEL: Warning: CPU0: Pager of 5 is invalid (pfa=00000100, errorcode=94000005)) KERNEL: Warning: CPU0: Pager of 0 is invalid (pfa=00000100, errorcode=94000005))
Best, Zachary.
On Tue Dec 02, 2014 at 02:58:38 +0000, Zachary wrote:
Adam Lackorzynski <adam <at> os.inf.tu-dresden.de> writes:
Hi,
It complains on the ramdisk image format but there is none. fastboot_rawimage is the right one to use. Looks like there's some issue here with a page-fault that should not happen. I'm wondering how we could debug this. Is the multi-processor option enabled in Fiasco?
Thanks you for your response. I am sure the multi-processor option is enabled.
I changed the execute model to "TrusteZone normal side", and I get more output:
I do not think that makes a particular difference in this case, it's still the same issue. It's some tricky one. I'll cross check with one of my 4412-based boards, however, no promises.
Adam
l4-hackers@os.inf.tu-dresden.de