On Mon Jan 12, 2015 at 12:12:43 +0100, cem akpolat wrote:
Couple of months ago, I was trying to run l4 on the samsung nexus s, but then I decided to switch to Cubieboard2 due to the simple configurations and costs stemming from the JTAG/UART interfaces which are quite expensive(around 1000 Euro). What I did:
- the fiasco is compiled for All-sunxi and cubieboard
- l4re is compiled for cubieboard2.
- the uImage is generated through the following command make uimage -C ~/l4android/src/l4/ E=L4LinuxARM
O=~l4android/src/build/l4/
- boot.scr file for uboot is created in which the compiled kernel image is
given as kernel as belowe
setenv kernel_addr_r 0x46000000 # 8M setenv fdt_addr 0x49000000 # 2M setenv fdt_high 0xffffffff # Load fdt in place instead of relocating
fatload mmc 0 0x43000000 /script.bin
fatload mmc 0 ${kernel_addr_r} /uImage setenv bootargs "console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=EDID:1280x1024p60 rw root=/dev/mmcblk0p2 rootwait"
fatload mmc 0 ${fdt_addr} /sun7i-a20-cubieboard2.dtb
bootm ${kernel_addr_r} - ${fdt_addr}
#End of the setup
# What I am seeing on the console outputs
API Version: (87) experimental Sigma0 config ip:40090100 sp:00000000 Roottask config ip:40140260 sp:00000000 Starting kernel fiasco at 40001388 Non-HYP kernel detected but running in HYP mode, switching back.
What exactly Fiasco tries to tell me with this message "Non-HYP kernel detected but running in HYP mode, switching back.".
Bootstrap tries to tell us that it detected a non-HYP enabled Fiasco.OC that it shall load, but the system is currently running in HYP mode so it wants to switch it to non-HYP mode. And that somehow fails. Which type/version of u-boot are you using?
Adam