Kernel Newbies archive on lore.kernel.org
 help / color / Atom feed
* Missing FDT description in DTB
@ 2019-12-06  9:03 Tomek Domek
  2019-12-06 11:16 ` Tomek Domek
  2019-12-06 11:26 ` Valdis Klētnieks
  0 siblings, 2 replies; 4+ messages in thread
From: Tomek Domek @ 2019-12-06  9:03 UTC (permalink / raw)
  To: kernelnewbies

[-- Attachment #1.1: Type: text/plain, Size: 939 bytes --]

Hi
I have FSBL and SSBL. SPL uboot starts successfully and u-boot.img is
loaded successfully but it hangs on 'boot_from_devices' function and
'fit_find_config_node':

fit_find_config_node: Missing FDT description in DTB
No matching DT out of these options:
Firmware image with one or more FDT blobs
boot_from_devices error
SPL: failed to boot from all boot devices

I have suspicion that I wrongly create u-boot.img. My system build do this
by executing:

./tools/mkimage -f auto -A arm -T firmware -C none -O u-boot -a 0x100000 -e
0 -n "someName" -E  -d u-boot-no-dtb.bin u-boot.img  >/dev/null
The same issue occurs when I use u-boot-dtb.bin version.
The value 0x100000 is the value stored in CONFIG_SYS_TEXT_BASE.

 And this uboot and spl is somekind of experimental software which is in
the middle of creation. Could anyone try to guide what might be possible
the reason of the issue as I am a bit new in u-boot development?

BR
Tomek

[-- Attachment #1.2: Type: text/html, Size: 1189 bytes --]

<div dir="ltr">Hi<div>I have FSBL and SSBL. SPL uboot starts successfully and u-boot.img is loaded successfully but it hangs on &#39;boot_from_devices&#39; function and &#39;fit_find_config_node&#39;:</div><div><br></div><div>fit_find_config_node: Missing FDT description in DTB<br>No matching DT out of these options:<br>Firmware image with one or more FDT blobs<br>boot_from_devices error<br>SPL: failed to boot from all boot devices<br></div><div><br></div><div>I have suspicion that I wrongly create u-boot.img. My system build do this by executing:</div><div><br></div><div>./tools/mkimage -f auto -A arm -T firmware -C none -O u-boot -a 0x100000 -e 0 -n &quot;someName&quot; -E  -d u-boot-no-dtb.bin u-boot.img  &gt;/dev/null<br></div><div>The same issue occurs when I use u-boot-dtb.bin version.</div><div>The value 0x100000 is the value stored in CONFIG_SYS_TEXT_BASE.</div><div><br></div><div> And this uboot and spl is somekind of experimental software which is in the middle of creation. Could anyone try to guide what might be possible the reason of the issue as I am a bit new in u-boot development?</div><div><br></div><div>BR</div><div>Tomek</div><div><br></div></div>

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Missing FDT description in DTB
  2019-12-06  9:03 Missing FDT description in DTB Tomek Domek
@ 2019-12-06 11:16 ` Tomek Domek
  2019-12-06 11:26 ` Valdis Klētnieks
  1 sibling, 0 replies; 4+ messages in thread
From: Tomek Domek @ 2019-12-06 11:16 UTC (permalink / raw)
  To: kernelnewbies

[-- Attachment #1.1: Type: text/plain, Size: 1292 bytes --]

OK I found on my own.
The proper mkimage command is:
./tools/mkimage -A arm -T firmware -C none -O u-boot -a 0x100000 -e 0 -n
"someName" -d u-boot-dtb.bin u-boot.img
without '-f auto and -E'

pt., 6 gru 2019 o 10:03 Tomek Domek <tomekdomek8585@gmail.com> napisał(a):

> Hi
> I have FSBL and SSBL. SPL uboot starts successfully and u-boot.img is
> loaded successfully but it hangs on 'boot_from_devices' function and
> 'fit_find_config_node':
>
> fit_find_config_node: Missing FDT description in DTB
> No matching DT out of these options:
> Firmware image with one or more FDT blobs
> boot_from_devices error
> SPL: failed to boot from all boot devices
>
> I have suspicion that I wrongly create u-boot.img. My system build do this
> by executing:
>
> ./tools/mkimage -f auto -A arm -T firmware -C none -O u-boot -a 0x100000
> -e 0 -n "someName" -E  -d u-boot-no-dtb.bin u-boot.img  >/dev/null
> The same issue occurs when I use u-boot-dtb.bin version.
> The value 0x100000 is the value stored in CONFIG_SYS_TEXT_BASE.
>
>  And this uboot and spl is somekind of experimental software which is in
> the middle of creation. Could anyone try to guide what might be possible
> the reason of the issue as I am a bit new in u-boot development?
>
> BR
> Tomek
>
>

[-- Attachment #1.2: Type: text/html, Size: 1795 bytes --]

<div dir="ltr">OK I found on my own.<div>The proper mkimage command is:</div><div>./tools/mkimage -A arm -T firmware -C none -O u-boot -a 0x100000 -e 0 -n &quot;someName&quot; -d u-boot-dtb.bin u-boot.img<br></div><div>without &#39;-f auto and -E&#39;</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">pt., 6 gru 2019 o 10:03 Tomek Domek &lt;<a href="mailto:tomekdomek8585@gmail.com">tomekdomek8585@gmail.com</a>&gt; napisał(a):<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi<div>I have FSBL and SSBL. SPL uboot starts successfully and u-boot.img is loaded successfully but it hangs on &#39;boot_from_devices&#39; function and &#39;fit_find_config_node&#39;:</div><div><br></div><div>fit_find_config_node: Missing FDT description in DTB<br>No matching DT out of these options:<br>Firmware image with one or more FDT blobs<br>boot_from_devices error<br>SPL: failed to boot from all boot devices<br></div><div><br></div><div>I have suspicion that I wrongly create u-boot.img. My system build do this by executing:</div><div><br></div><div>./tools/mkimage -f auto -A arm -T firmware -C none -O u-boot -a 0x100000 -e 0 -n &quot;someName&quot; -E  -d u-boot-no-dtb.bin u-boot.img  &gt;/dev/null<br></div><div>The same issue occurs when I use u-boot-dtb.bin version.</div><div>The value 0x100000 is the value stored in CONFIG_SYS_TEXT_BASE.</div><div><br></div><div> And this uboot and spl is somekind of experimental software which is in the middle of creation. Could anyone try to guide what might be possible the reason of the issue as I am a bit new in u-boot development?</div><div><br></div><div>BR</div><div>Tomek</div><div><br></div></div>
</blockquote></div>

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Missing FDT description in DTB
  2019-12-06  9:03 Missing FDT description in DTB Tomek Domek
  2019-12-06 11:16 ` Tomek Domek
@ 2019-12-06 11:26 ` Valdis Klētnieks
  2019-12-06 12:37   ` Tomek Domek
  1 sibling, 1 reply; 4+ messages in thread
From: Valdis Klētnieks @ 2019-12-06 11:26 UTC (permalink / raw)
  To: Tomek Domek; +Cc: kernelnewbies

[-- Attachment #1.1: Type: text/plain, Size: 651 bytes --]

On Fri, 06 Dec 2019 10:03:34 +0100, Tomek Domek said:

>  And this uboot and spl is somekind of experimental software which is in
> the middle of creation. Could anyone try to guide what might be possible
> the reason of the issue as I am a bit new in u-boot development?

Is there a reason why you're using an experimental uboot/spl rather than
a known-stable working version for whatever hardware this is?

(Of course, if this is bring-up of a new architecture that has never been
supported by uboot, so there's never been a  working uboot for the device, it's
time to quote the movie Animal House: "My advice to you is to start drinking
heavily")


[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Missing FDT description in DTB
  2019-12-06 11:26 ` Valdis Klētnieks
@ 2019-12-06 12:37   ` Tomek Domek
  0 siblings, 0 replies; 4+ messages in thread
From: Tomek Domek @ 2019-12-06 12:37 UTC (permalink / raw)
  To: Valdis Klētnieks; +Cc: kernelnewbies

[-- Attachment #1.1: Type: text/plain, Size: 1069 bytes --]

Yes, it is for bringup purpose. We have working uboot software and we split
the code in order to have FSBL and SSBL and I had such problem but it was a
matter of deleting "-f auto" and -E option from mkimage for building
u-boot.img. Now FSBL, SSBL and kernel starts successfully.

pt., 6 gru 2019 o 12:26 Valdis Klētnieks <valdis.kletnieks@vt.edu>
napisał(a):

> On Fri, 06 Dec 2019 10:03:34 +0100, Tomek Domek said:
>
> >  And this uboot and spl is somekind of experimental software which is in
> > the middle of creation. Could anyone try to guide what might be possible
> > the reason of the issue as I am a bit new in u-boot development?
>
> Is there a reason why you're using an experimental uboot/spl rather than
> a known-stable working version for whatever hardware this is?
>
> (Of course, if this is bring-up of a new architecture that has never been
> supported by uboot, so there's never been a  working uboot for the device,
> it's
> time to quote the movie Animal House: "My advice to you is to start
> drinking
> heavily")
>
>

[-- Attachment #1.2: Type: text/html, Size: 1411 bytes --]

<div dir="ltr">Yes, it is for bringup purpose. We have working uboot software and we split the code in order to have FSBL and SSBL and I had such problem but it was a matter of deleting &quot;-f auto&quot; and -E option from mkimage for building u-boot.img. Now FSBL, SSBL and kernel starts successfully.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">pt., 6 gru 2019 o 12:26 Valdis Klētnieks &lt;<a href="mailto:valdis.kletnieks@vt.edu">valdis.kletnieks@vt.edu</a>&gt; napisał(a):<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, 06 Dec 2019 10:03:34 +0100, Tomek Domek said:<br>
<br>
&gt;  And this uboot and spl is somekind of experimental software which is in<br>
&gt; the middle of creation. Could anyone try to guide what might be possible<br>
&gt; the reason of the issue as I am a bit new in u-boot development?<br>
<br>
Is there a reason why you&#39;re using an experimental uboot/spl rather than<br>
a known-stable working version for whatever hardware this is?<br>
<br>
(Of course, if this is bring-up of a new architecture that has never been<br>
supported by uboot, so there&#39;s never been a  working uboot for the device, it&#39;s<br>
time to quote the movie Animal House: &quot;My advice to you is to start drinking<br>
heavily&quot;)<br>
<br>
</blockquote></div>

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-12-06  9:03 Missing FDT description in DTB Tomek Domek
2019-12-06 11:16 ` Tomek Domek
2019-12-06 11:26 ` Valdis Klētnieks
2019-12-06 12:37   ` Tomek Domek

Kernel Newbies archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernelnewbies/0 kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ https://lore.kernel.org/kernelnewbies \
		kernelnewbies@kernelnewbies.org
	public-inbox-index kernelnewbies

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernelnewbies.kernelnewbies


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git