Hi Martin,
Thank you very much. I followed your guidance to build it again
and got result uImage at var/run/tz_vmm_mx6. But I was not success
to boot it with either run/tz_vmm_mx6 or run/printf.
Below are log messages for trying with run/printf
Hit any key to stop autoboot: 0
MX6Q SABRESD U-Boot > fatload mmc 2:1 0x40000000
uImage_sabrelite_tz
reading uImage_sabrelite_tz
366675 bytes read
MX6Q SABRESD U-Boot > bootm 40000000
## Booting kernel from Legacy Image at 40000000 ...
Image Name:
Image Type: ARM Linux Kernel Image (gzip compressed)
Data Size: 366611 Bytes = 358 kB
Load Address: 10001000
Entry Point: 10001000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting kernel ...
Is that my board MX6Q SABRESD differs from SABRELITE causing this?
Please help me what I should do.
On 4/21/2015 5:48 PM, Martin Stein wrote:
Hit any key to stop autoboot: 0
MX6Q SABRESD U-Boot > fatload mmc 2:1 0x10001000 sabrelite.bin
reading sabrelite.bin
According to [3], the text address of your image is 0x10001000. Thus, it
isn't a good idea to fatload the image to this address too. You should
use an address that is outside of any image-segment range (see [4]) and
outside the boot loader image. According to the Sabrelite RAM-config in
[5], 0x40000000 might be a good idea in your case.
Just notice you that 'sabrelite.bin' is binary format not u-boot
image which I got from:
/usr/local/genode-gcc/bin/genode-arm-objcopy -O binary
var/run/tz_vmm_mx6/image.elf var/run/tz_vmm_mx6/sabrelite.bin
So I think I should fatload 'sabrelite.bin' into 0x10001000 which
is text address of the image then I can directly execute it at
that address with 'go' command. Is that my understanding wrong?
Thank you,
--Thong Nguyen.
On 4/21/2015 5:48 PM, Martin Stein wrote:
Hi Thong,
On 21.04.2015 09:24, thong wrote:
Hi Chirag garg,
Thanks for your help. I tried to build your hw_sabrelite_tz_support
branch as follow:
RUN_OPT="--target uboot" make run/tz_vmm_mx6
The "--target uboot" option is a deprecated way of configuring the run
tool. Thus, I assume that you either have an old Genode state with the
IIT-Madras imx6-support (a pretty recent feature) rebased onto it, or
you have a Genode state that is up-to-date and applying the deprecated
run options mistakenly.
If you're on the iitmadras/hw_sabrelite_tz_support branch, the latter is
the case. Make sure that you've deleted your old build directory and
created a new one by doing:
$GENODE_DIR/tool/create_builddir hw_sabrelite_tz
Then, you should not set RUN_OPT by hand when calling 'make' but adapt
it in [1] to the following value:
RUN_OPT = --include boot_dir/hw --include image/uboot
For more details on the new run options, see chapter "Modular tool kit
for automated testing" in [2].
Hit any key to stop autoboot: 0
MX6Q SABRESD U-Boot > fatload mmc 2:1 0x10001000 sabrelite.bin
reading sabrelite.bin
According to [3], the text address of your image is 0x10001000. Thus, it
isn't a good idea to fatload the image to this address too. You should
use an address that is outside of any image-segment range (see [4]) and
outside the boot loader image. According to the Sabrelite RAM-config in
[5], 0x40000000 might be a good idea in your case.
Cheers,
Martin
[1] $BUILD_DIR/etc/build.conf
[2] http://genode.org/documentation/release-notes/15.02
[3] $GENODE_DIR/base-hw/mk/spec-hw_sabrelite.mk
[4] genode-arm-objdump -ph $BUILD_DIR/var/run/$TARGET/image.elf
[5] $GENODE_DIR/base/include/platform/sabrelite/drivers/board_base.h
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main