Hi all,
tried something else instead. Deleted the whole sd card again and flashed it with a fat32 partition starting at 1GB to ensure I don't write some place, that is rewritten when sd_fusing script writes boot data to sd card. I feared that if i load 0x41000000 it could be the zImage kernel which is on the sd card already.
I also have to correct myself i have to use the usbnet uboot code from here: https://github.com/mkaczanowski/u-boot/tree/odroid-u3-usbnet Otherwhise it wont boot the usb parts(network card).
Now I used the uImage from Ubuntu from the tftp server and the uImage from the genode build. The boot.txt looks like this:
setenv ethact sms0 setenv ethaddr 00:10:75:2A:AE:E0 setenv gatewayip 192.168.0.254 setenv netmask 255.255.255.0 setenv serverip 131.159.12.22 setenv usbethaddr 00:10:75:2A:AE:E0 setenv ipaddr 192.168.0.23
usb start tftp 0x70000000 odroid/uImage bootm 0x70000000 bootm 0x41000000
Boot uImage now seem to work, Ubuntu runs to its kernel panic again but Genode now unfortunately hangs at Starting kernel.
Is it possible that now all is running as expected but x2 genode code can not be used at u3? I'd expected that i should at least be able to boot, even if some usb drivers or something will not work?
Best regards,
Bernhard.
Here is the full log dump:
U-Boot 2010.12-00000-gb93fb15-dirty (Jan 18 2017 - 20:24:29) for Exynox4412
CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9] APLL = 1000MHz, MPLL = 880MHz DRAM: 2 GiB
PMIC VERSION : 0x00, CHIP REV : 3 TrustZone Enabled BSP BL1 version: 20121128
Checking Boot Mode ... SDMMC MMC Device 0: 15343 MB *** Warning - using default environment
In: serial Out: serial Err: serial ModeKey Check... run normal_boot Net: usb_ether Hit any key to stop autoboot: 0
Load Boot Script from mmc 0:1 <<<
reading boot.scr 351 bytes read in 23 ms (14.6 KiB/s) ## Executing script at 40008000 (Re)start USB... USB0: Exynos4412-ehci: init hccr 12580000 and hcor 12580010 hc_length 16 usb: usb_refclk_enable is active low: YES ProTIP: If usb doesn't work - try playing with 'usb_invert_clken' environment USB EHCI 1.00 scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 1 Ethernet Device(s) found scanning usb for keyboard ... Waiting for Ethernet connection... done. Using sms0 device TFTP from server 192.168.0.1; our IP address is 192.168.0.23; sending through4 Filename 'odroid/uImage'. Load address: 0x70000000 Loading: ##################################################### 264.6 KiB/s done Bytes transferred = 773987 (bcf63 hex) ## Booting kernel from Legacy Image at 70000000 ... Image Name: Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 773923 Bytes = 755.8 KiB Load Address: 41000000 Entry Point: 41000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ERROR: booting os 'Unknown OS' (3) is not supported Boot with zImage
Starting kernel ...
On 26.01.2017 13:58, Bernhard Blieninger wrote:
Hi Christian,
thanks, this did not fix the problem either. I tested it with the uImage from ubuntu and the uImage from genode.
Best regards,
Bernhard.
On 26.01.2017 11:15, Christian Helmuth wrote:
Hi,
I've just a small hint regarding the following issue.
On Wed, Jan 25, 2017 at 07:30:11PM +0100, Bernhard Blieninger wrote:
mkimage -A arm -C none -T script -n 'Custom Boot Script' -d boot.txt boot.scr
Problem now is that is says something like:
*ERROR: booting os 'Unknown OS' (3) is not supported*When generating an uImage mkimage supports to set the operating system in the commandline via '-O <os>'. So, your mkimage command line should read
mkimage -A arm -O linux -C none -T script -n 'Custom Boot Script' -d boot.txt boot.scr
Hope it helps
Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main