Thank you very much for the quick response, Stefan :)
I built a simple log Genode scenario for wand_quad for testing purposes, and I am previously used to receiving iso images for x86_32/x86_64.
However, there is no iso image! I am left with a log.core file in the var/run directory and I don't know how to construct a bootable microSD card image from these files.
Forgive my ignorance, and many thanks for the help!! Joel Desermeau
Hello,
On 02.01.2018 19:42, Baconicsynergy via genode-main wrote:
I built a simple log Genode scenario for wand_quad for testing purposes, and I am previously used to receiving iso images for x86_32/x86_64.
However, there is no iso image! I am left with a log.core file in the var/run directory and I don't know how to construct a bootable microSD card image from these files.
by default you will find a file build/wand_quad/var/run/<run-name>/image.elf, which could be used by your u-boot with the 'bootelf' command (if supported by the bootloader on your sd-card).
You may also build an Genode image to be used with 'bootm' command of your u-boot. Add to the RUN_OPT in your build/wand_quad/etc/build.conf
RUN_OPT += --include image/uboot
After you invoked the re-run the run script you will find the image under build/wand_quad/var/run/<run-name>/uImage
The u-boot (and SD-card) you have to setup yourself. Either you have one already shipped with your board or you may try to create a u-boot using our tool in "tool/create_uboot".
Hope it helps,
Alex.
Hi,
On 04.01.2018 16:51, Alexander Boettcher wrote:
Hello,
On 02.01.2018 19:42, Baconicsynergy via genode-main wrote:
I built a simple log Genode scenario for wand_quad for testing purposes, and I am previously used to receiving iso images for x86_32/x86_64.
However, there is no iso image! I am left with a log.core file in the var/run directory and I don't know how to construct a bootable microSD card image from these files.
by default you will find a file build/wand_quad/var/run/<run-name>/image.elf, which could be used by your u-boot with the 'bootelf' command (if supported by the bootloader on your sd-card).
You may also build an Genode image to be used with 'bootm' command of your u-boot. Add to the RUN_OPT in your build/wand_quad/etc/build.conf
RUN_OPT += --include image/uboot
After you invoked the re-run the run script you will find the image under build/wand_quad/var/run/<run-name>/uImage
The u-boot (and SD-card) you have to setup yourself. Either you have one already shipped with your board or you may try to create a u-boot using our tool in "tool/create_uboot".
When using the create_uboot tool, an image file for your MMC is created containing a freshly built u-boot and all what u-boot needs to run on WandBoard. The image has a size of 8 Mb and, at the end, the tool tells you the command line to copy the image to your MMC with a seek of 1 byte. So you can create a filesystem afterwards that starts, lets say, at 10 Mb offset for your Genode images.
Unfortunately, the create_uboot tool doesn't work with the newest Genode toolchain. But there's an easy way to circumvent this problem:
! # download older toolchain (change x86_64 to x86_32 in the URL if needed) ! wget https://sourceforge.net/projects/genode/files/genode-toolchain/16.05/genode-... ! ! # rename your current toolchain so we're not going to overwrite it ! mv /usr/local/genode-gcc /usr/local/genode-gcc-latest ! ! # extract older toolchain (again you might adapt x86_64) ! sudo tar xPf genode-toolchain-16.05-x86_64.tar.bz2 ! ! # rename older toolchain ! mv /usr/local/genode-gcc /usr/local/genode-gcc-16.05 ! ! # make sure Genode uses the older toolchain ! ln -sf -T /usr/local/genode-gcc-16.05 /usr/local/genode-gcc ! ! # create MMC image ! tool/create_uboot wand_board ! ! # switch back to your current toolchain ! ln -sf -T /usr/local/genode-gcc-latest /usr/local/genode-gcc
I hope this helped?
Cheers, Martin
-
Alexander Boettcher -
Baconicsynergy -
Martin Stein