Re: foc_odroid_x2 with tftp boot via uboot on odroid u3
Hi, thanks for the answers. If you say you got the x2 to work at the odroid u3, I believe its clearly a uboot problem. I had to use bootm twice because the first use gave me the "unknown os" error. I think the first bootm call loads the uImage from the preload location 0x7000 to 0x4100 and the second one loads it from 0x4100. So the first bootm could possibly only be "bootm" without parameter, the second one needs to have the 0x4100 to work. I also tried bootelf with the image.elf and bootp, nothing worked so far. bootelf freezes quite similar to the bootm command. It says, that its starting the application. The script Alexy sent is working and I compiled an image.img in the meantime and deployed it at the tftp server. I also renamed it to zImage. Problem still exists. I tried your uboot code, but I fail to flash it to the sd card. Am I right that I have to use: apt-get install device-tree-compiler (for needed dts, was not necessary at the previous version) make odroid_config (make smdk4412_config is not present) make -j Is the odroid config for u3? There is no sd_fuse folder so I am somehow stuck here, because I have no idea on how to format the sd card correctly and where to put which files. Would appreciate if you can give some kind of instruction on how to prepare sd cards or emmc for such devices and flash all necessary files to it. I think that my formatting, which leaves the first 1GB of the sd untouched, is not the best way and I am an absolute beginner here. Thanks. Best regards, Bernhard. On 26.01.2017 21:17, rmillo wrote: Hi Bernhard It does not seem to be a network or usb problem. Clearly the uboot is loading the image from TFTP server. Why do you use two bootm calls, if you only load the uImage in address 0x7000? When uboot is usesd to boot some operating systems like android or other linux distributions bootm can be used as: bootm $(kernel_addr) $(ramdisk_addr) But this only can done if there are loaded on memory the kernel and the ramdisk. In this case GenodeOS don't use ramdisk, it uses only kernel image. I think that the problem with Genode can be the image format. As Alexy Gallardo explains we have tested the Odroid-U3 with the Odroid-X2 support, but we boot the image with the bootz (at address 0x4100) command because we use a zImage format created with the raw_image script that him attached to you. Your uboot seems to don't have this command (bootz), maybe it can be enable on uboot compilation. Now i'm not in work to see the source of Uboot that we are using, but take a look on this Uboot project with support to Odroid-X2 and Odroid-U3.: https://github.com/dsd/u-boot Have you tried boot the elf image with bootelf? Or have you tried to boot the same image from an storage device to test it first and then move it for the tftp? Best regards On 26/01/2017 02:50 PM, Bernhard Blieninger wrote: 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 0x4100 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 0x7000 odroid/uImage bootm 0x7000 bootm 0x4100 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-0-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 1258 and hcor 12580010 hc_length 16 usb: usb_refclk_enable is active
Re: foc_odroid_x2 with tftp boot via uboot on odroid u3
Hi Bernhard It does not seem to be a network or usb problem. Clearly the uboot is loading the image from TFTP server. Why do you use two bootm calls, if you only load the uImage in address 0x7000? When uboot is usesd to boot some operating systems like android or other linux distributions bootm can be used as: bootm $(kernel_addr) $(ramdisk_addr) But this only can done if there are loaded on memory the kernel and the ramdisk. In this case GenodeOS don't use ramdisk, it uses only kernel image. I think that the problem with Genode can be the image format. As Alexy Gallardo explains we have tested the Odroid-U3 with the Odroid-X2 support, but we boot the image with the bootz (at address 0x4100) command because we use a zImage format created with the raw_image script that him attached to you. Your uboot seems to don't have this command (bootz), maybe it can be enable on uboot compilation. Now i'm not in work to see the source of Uboot that we are using, but take a look on this Uboot project with support to Odroid-X2 and Odroid-U3.: https://github.com/dsd/u-boot Have you tried boot the elf image with bootelf? Or have you tried to boot the same image from an storage device to test it first and then move it for the tftp? Best regards On 26/01/2017 02:50 PM, Bernhard Blieninger wrote: > 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 0x4100 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 0x7000 odroid/uImage > bootm 0x7000 > bootm 0x4100 > > 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-0-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 1258 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
Re: foc_odroid_x2 with tftp boot via uboot on odroid u3
Hello,
Sorry for the previous email the two lines that I said put in "etc / build" of
the compilation directory of foc_odroid_x2 only works on the genodeOS version
that we have here. For it to work you must add the attached script in
"genodeDir / tool / run / image".
Set on ../genodeDir/build/foc_odroid_x2/etc/build.conf the fellowing lines
For generate a zImage and now if it should work
RUN_OPT = --include boot_dir / foc \
--include image / raw_image
Copy the image to the TFTP server
At the start of the uboot
If image format is zImage use:
Usb start
Tftp 0x40001000 odroid / uImage
Bootz 0x40001000
If this does not work try changing the uboot version. At the beginning of us
working with the odroid the uboot version did not allow support for the
network. I do not know if this is what may be happening to you. In github
there are several uboot projects that can be compiled for the odroid.
Regards
Alexy
On jueves, 26 de enero de 2017 1:57:19 P. M. CST Bernhard Blieninger wrote:
> Hi Alexy,
>
> thanks for the hint.
> If I just use your two lines as they are written below and put the uboot
> lines away compiling won't start with the error message:
> Aborting, could not load '../genode/tool/run/image/raw_image'
>
> There is not image/raw_image in this folder and i unfortunately didn't
> find anything about it with google.
>
> I do also not have any bootz command, it says unkown command bootz, the
> bootm command boots the zImages without complaining.
>
>
> Best regards,
>
> Bernhard.
>
> On 25.01.2017 20:58, Alexy Gallardo Segura wrote:
> > Hi,
> >
> >> |setenv ethact sms0|
> >> |setenv ethaddr 00:10:75:2A:AE:E0|
> >> |setenv gatewayip 192.168.4.1|
> >> |setenv netmask 255.255.255.0|
> >> |setenv serverip 192.168.4.2|
> >> |setenv usbethaddr 00:10:75:2A:AE:E0|
> >> |setenv ipaddr 192.168.4.43|
> >> |
> >> |usb start|
> >> |tftp 0x7000 odroid/uImage|
> >> |bootm|
> >
> > If image format is zImage use:
> > usb start
> > tftp 0x7000 odroid/uImage
> > bootz 0x7000
> >
> > set on ../genodeDir/build/foc_odroid_x2/etc/build.conf the fellowing
> > lines
> > for generate a zImage.
> >
> > RUN_OPT = --include boot_dir/foc \
> >
> > --include image/raw_image
> >
> > cheers,
> >
> > Alexy
> >
> >> |Where uImage is the uImage created from the foc_odroid build.
> >>
> >> Then I used
> >>
> >> ||mkimage -A arm -C none -T script -n 'Custom Boot Script' -d
> >>
> >> boot.txt boot.scr||
> >> ||
> >> ||to build the boot.scr and booted the odroid u3.||
> >
> > --
> > 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
--
Lic. Alexy Gallardo Segura\nCentro Territorial Villa Clara.\nEmpresa de
Tecnologías de la Información para la Defensa (XETID)-UCLV\nCarretera a
Camajuaní, km 5.5, Santa Clara, Villa Clara, CUBA\nE-mail: al...@uclv.cu,
al...@xetid.cu\nTeléf:042-226714\nwww.xetid.cu\n##
# Build specific binary raw image
#
# \param elf_img ELF binary to build raw image from
#
proc run_image {elf_img} {
# parse ELF entrypoint and load address
set raw_img "[run_dir]/image.img"
exec [cross_dev_prefix]objcopy -O binary $elf_img $raw_img
puts "Binary raw image created: ./$raw_img"
}--
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
Re: foc_odroid_x2 with tftp boot via uboot on odroid u3
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 '. 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 smime.p7s Description: S/MIME Cryptographic Signature -- 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
Re: foc_odroid_x2 with tftp boot via uboot on odroid u3
Hi Alexy, thanks for the hint. If I just use your two lines as they are written below and put the uboot lines away compiling won't start with the error message: Aborting, could not load '../genode/tool/run/image/raw_image' There is not image/raw_image in this folder and i unfortunately didn't find anything about it with google. I do also not have any bootz command, it says unkown command bootz, the bootm command boots the zImages without complaining. Best regards, Bernhard. On 25.01.2017 20:58, Alexy Gallardo Segura wrote: Hi, |setenv ethact sms0| |setenv ethaddr 00:10:75:2A:AE:E0| |setenv gatewayip 192.168.4.1| |setenv netmask 255.255.255.0| |setenv serverip 192.168.4.2| |setenv usbethaddr 00:10:75:2A:AE:E0| |setenv ipaddr 192.168.4.43| || |usb start| |tftp 0x7000 odroid/uImage| |bootm| If image format is zImage use: usb start tftp 0x7000 odroid/uImage bootz 0x7000 set on ../genodeDir/build/foc_odroid_x2/etc/build.conf the fellowing lines for generate a zImage. RUN_OPT = --include boot_dir/foc \ --include image/raw_image cheers, Alexy |Where uImage is the uImage created from the foc_odroid build. Then I used ||mkimage -A arm -C none -T script -n 'Custom Boot Script' -d boot.txt boot.scr|| ||to build the boot.scr and booted the odroid u3.|| -- 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 smime.p7s Description: S/MIME Cryptographic Signature -- 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
Re: foc_odroid_x2 with tftp boot via uboot on odroid u3
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 '. 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 -- Christian Helmuth Genode Labs https://www.genode-labs.com/ · https://genode.org/ https://twitter.com/GenodeLabs · /ˈdʒiː.nəʊd/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth -- 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
performance benchmark
Hello all, Is there any benchmark (performance) tool ready to run in Genode? I am trying to introduce some redundant execution scheme into the Nova kernel and I would like to have a hint of the performance impact (on Genode components). Since it is an unfinished work, the demo is the only scenario I can run now. I have read about the trace session in 13.08 release which may help but I failed to build the trace example scenario (to get some insight of the feature) *Here are the outputs* In the master branch: make run/trace ... cp: cannot stat ‘bin/rpc_name’: No such file or directory while executing "exec cp bin/$binary [run_dir]/genode" (procedure "copy_and_strip_genode_binaries_to_run_dir" line 4) invoked from within ... In the 13.08 release make run/trace Makefile:91: /mk/global.mk: No such file or directory make: *** No rule to make target `/mk/global.mk'. Stop. I also read about the* TCP/IP Automated benchmarking* in 13.05 release. In the master branch: make run/network_test_nic_raw Error: No run script for network_test_nic_raw In the 13.05 release Makefile:91: /mk/global.mk: No such file or directory make: *** No rule to make target `/mk/global.mk'. Stop. Any suggestion is welcom. -- Parfait T. -- 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
