[U-Boot] mkimage for ls1021a-twr.dtb

[U-Boot] mkimage for ls1021a-twr.dtb

[zvivered]

Hello,

I'm compiling vanilla 4.1.13 for ls1021a with gcc created with crosstool-ng
Upon kernel build completion I got the file: ls1021a-twr.dtb

Then I ran:
mkimage -A arm -O Linux -C none -T kernel -n 3.14.4 -d ls1021a-twr.dtb
uImage.dtb

using tftp I downloaded:
uImage -> 0x83000000
uRamdisk -> 0x88000000
uImage.dtb -> 0x8F000000
bootm 83000000 88000000 8F000000

Upon booting uImage.dtb I got:
ERROR: uImage is not a fdt - must RESET the board to recover.
Could not find a valid device tree

What am I doing wrong ?

I have a uImage.dtb taken from NXP's Yocto project. 
With this file I'm getting:
## Flattened Device Tree blob at 8f000000
Booting using the fdt blob at 0x8f000000
Loading Kernel Image ... OK
Using Device Tree in place at 8f000000, end 8f008469

With my file I'm getting:
## Flattened Device Tree from Legacy Image at 8f000000
Image Name:
Iamge Type: ARM Linux ..
....
ERROR: uImage is not a fdt - must RESET the board to recover.
Could not find a valid device tree

Thank you in advance,
Z.V






--
View this message in context: http://u-boot.10912.n7.nabble.com/mkimage-for-ls1021a-twr-dtb-tp277542.html
Sent from the U-Boot mailing list archive at Nabble.com.

[U-Boot] mkimage for ls1021a-twr.dtb

[Alison Wang]

For dtb, you can use ls1021a-twr.dtb directly. No need to use mkimage.

To generate uImage, you can use mkimage for it.

mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n "Linux Kernel" -d arch/arm/boot/zImage uImage.ls1021a


Best Regards,
Alison Wang

> -----Original Message-----
> From: U-Boot [mailto:u-boot-bounces at lists.denx.de] On Behalf Of
> zvivered
> Sent: Monday, January 02, 2017 9:51 PM
> To: u-boot at lists.denx.de
> Subject: [U-Boot] mkimage for ls1021a-twr.dtb
> 
> Hello,
> 
> I'm compiling vanilla 4.1.13 for ls1021a with gcc created with
> crosstool-ng
> Upon kernel build completion I got the file: ls1021a-twr.dtb
> 
> Then I ran:
> mkimage -A arm -O Linux -C none -T kernel -n 3.14.4 -d ls1021a-twr.dtb
> uImage.dtb
> 
> using tftp I downloaded:
> uImage -> 0x83000000
> uRamdisk -> 0x88000000
> uImage.dtb -> 0x8F000000
> bootm 83000000 88000000 8F000000
> 
> Upon booting uImage.dtb I got:
> ERROR: uImage is not a fdt - must RESET the board to recover.
> Could not find a valid device tree
> 
> What am I doing wrong ?
> 
> I have a uImage.dtb taken from NXP's Yocto project.
> With this file I'm getting:
> ## Flattened Device Tree blob at 8f000000
> Booting using the fdt blob at 0x8f000000
> Loading Kernel Image ... OK
> Using Device Tree in place at 8f000000, end 8f008469
> 
> With my file I'm getting:
> ## Flattened Device Tree from Legacy Image at 8f000000
> Image Name:
> Iamge Type: ARM Linux ..
> ....
> ERROR: uImage is not a fdt - must RESET the board to recover.
> Could not find a valid device tree
> 
> Thank you in advance,
> Z.V
> 
> 
> 
> 
> 
> 
> --
> View this message in context: http://u-
> boot.10912.n7.nabble.com/mkimage-for-ls1021a-twr-dtb-tp277542.html
> Sent from the U-Boot mailing list archive at Nabble.com.
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] mkimage for ls1021a-twr.dtb

[Vered Zvi]

Hi Alison,

I created a busybox file system.
So I have a folder on the host that contains:
/bin /sbin /tmp /proc /usr /lib ...

Can you please explain how should I create a root file system with genext2fs (or with anotehr utility) ?

Thank you,
Z.V
________________________________________
From: Alison Wang [alison.wang at nxp.com]
Sent: Thursday, January 05, 2017 4:13 AM
To: Vered Zvi; u-boot at lists.denx.de
Subject: RE: [U-Boot] mkimage for ls1021a-twr.dtb

For dtb, you can use ls1021a-twr.dtb directly. No need to use mkimage.

To generate uImage, you can use mkimage for it.

mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n "Linux Kernel" -d arch/arm/boot/zImage uImage.ls1021a


Best Regards,
Alison Wang

> -----Original Message-----
> From: U-Boot [mailto:u-boot-bounces at lists.denx.de] On Behalf Of
> zvivered
> Sent: Monday, January 02, 2017 9:51 PM
> To: u-boot at lists.denx.de
> Subject: [U-Boot] mkimage for ls1021a-twr.dtb
>
> Hello,
>
> I'm compiling vanilla 4.1.13 for ls1021a with gcc created with
> crosstool-ng
> Upon kernel build completion I got the file: ls1021a-twr.dtb
>
> Then I ran:
> mkimage -A arm -O Linux -C none -T kernel -n 3.14.4 -d ls1021a-twr.dtb
> uImage.dtb
>
> using tftp I downloaded:
> uImage -> 0x83000000
> uRamdisk -> 0x88000000
> uImage.dtb -> 0x8F000000
> bootm 83000000 88000000 8F000000
>
> Upon booting uImage.dtb I got:
> ERROR: uImage is not a fdt - must RESET the board to recover.
> Could not find a valid device tree
>
> What am I doing wrong ?
>
> I have a uImage.dtb taken from NXP's Yocto project.
> With this file I'm getting:
> ## Flattened Device Tree blob at 8f000000
> Booting using the fdt blob at 0x8f000000
> Loading Kernel Image ... OK
> Using Device Tree in place at 8f000000, end 8f008469
>
> With my file I'm getting:
> ## Flattened Device Tree from Legacy Image at 8f000000
> Image Name:
> Iamge Type: ARM Linux ..
> ....
> ERROR: uImage is not a fdt - must RESET the board to recover.
> Could not find a valid device tree
>
> Thank you in advance,
> Z.V
>
>
>
>
>
>
> --
> View this message in context: http://u-
> boot.10912.n7.nabble.com/mkimage-for-ls1021a-twr-dtb-tp277542.html
> Sent from the U-Boot mailing list archive at Nabble.com.
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
The information contained in this communication is proprietary to Israel Aerospace Industries Ltd. and/or third parties, may contain confidential or privileged information, and is intended only for the use of the intended addressee thereof. If you are not the intended addressee, please be aware that any use, disclosure, distribution and/or copying of this communication is strictly prohibited. If you receive this communication in error, please notify the sender immediately and delete it from your computer.