From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Hans-Ulrich Schlieben <hu.schlieben@codewrights.de>,
Enrico Joerns <ejo@pengutronix.de>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [yocto] #yocto bootchooser: Cannot get state 'state'
Date: Tue, 21 Jan 2020 21:21:19 +0100 [thread overview]
Message-ID: <ec5a32e4-3317-9691-a286-0c7053f25f4c@pengutronix.de> (raw)
In-Reply-To: <DB8PR03MB5498C89CCD516C2AF1D457C7FE0D0@DB8PR03MB5498.eurprd03.prod.outlook.com>
Hi,
On 1/21/20 6:51 PM, Hans-Ulrich Schlieben wrote:
> Hi Ahmad,
>
> thank you for the great help. There's a lot to learn for me here.
>> Does it come from the phytec git directly? Upstream barebox has this:
> The zeus image I build here includes layer meta-phytec branch zeus and a custom layer from phytec called meta-ksp0663.
> On the custom layer I created a new branch zeus and just renamed the barebox and barebox-targettools bbappend files from 2017 to 2019.
>
> You are right about the missing state in barebox2019.01.
> for barebox 2019 drvinfo just contains:
> state
>
> drvinfo for barebox 2017 says:
> state
> imx6qdl_phytec_boot_state.19
> Does that mean that the driver is not loaded?
This means you have a state driver, but there was no device to bind to.
> At the barebox2019 version of_dump returns: Cannot find nodepath state
> At the barebox2017 version of_dump returns a full subtree for imx6qdl_phytec_boot_state and the eeprom entry for state.
>
> Looking into the 2017 barebox sources using find ./ -iname "imx6qdl-phytec*.dtsi" it finds imx6qdl-phytec-state.dtsi:
> This file does not exist in the 2019 barebox sources. There is only imx6ul-phytec-state.dtsi available.
Ha! That's it. The file is in upstream barebox, so no idea why Phytec dropped it.
That's probably a question for Phytec support.
Cheers
Ahmad
>
> Now I will try the upstream version.
>
> Thank you very much for your help.
>
> Best Regards
>
> hu
>
>> -----Original Message-----
>> From: Ahmad Fatoum <a.fatoum@pengutronix.de>
>> Sent: Monday, 20 January 2020 16:23
>> To: Hans-Ulrich Schlieben <hu.schlieben@codewrights.de>; Enrico Joerns <ejo@pengutronix.de>; yocto@lists.yoctoproject.org
>> Cc: barebox@lists.infradead.org
>> Subject: Re: [yocto] #yocto bootchooser: Cannot get state 'state'
>>
>> Hello,
>>
>> On 1/16/20 4:09 PM, Hans-Ulrich Schlieben wrote:
>>> Hi Ahmad,
>>>
>>> Thanks to your Mail I tested with barebox_2017.12.0-phy6.bb (thud used barebox_2017.12.0-phy4.bb) and this works in zeus too.
>>>
>>>> According to the state command output under thud, your state is stored on the EEPROM, not the NAND. Look for update-eeprom in your device tree.
>>>> There should also be an /dev/eeprom0.update-eeprom in barebox.
>>> That seems right, when working the eeprom is written to on each boot.
>>> But I could not find any references to *eep* inside barebox in any layer.
>>
>> Does it come from the phytec git directly? Upstream barebox has this:
>> https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.pengutronix.de%2Fcgit%2Fbarebox%2Ftree%2Farch%2Farm%2Fdts%2Fimx6qdl-phytec-state.dtsi%3Fh%3Dnext&data=01%7C01%7Chu.schlieben%40codewrights.de%7Cfd604ff2646c497fbb3508d79dbca678%7C0974af9b352b437cb606e9f242c0c227%7C0&sdata=fXOQB7awFhPhxJmDAyN5ipLxe3W8IbAw3vp03GL1Y10%3D&reserved=0
>>
>> I would imagine, yours does to. You can check in the yocto build directory.
>> (If you have rm_work enabled, you might need RM_WORK_EXCLUDE += "your-barebox-recipe"
>> in your local.conf)
>>
>> Also try of_dump /state inside of barebox to see the device tree node.
>>
>> The reason, you haven't found it in the deploy/ device tree is that barebox modifies the kernel device tree on loading and adds the state nodes to it.
>>
>>>> if not, try executing the drvinfo command and see if the driver has probed the EEPROM.
>>>>>> Looks like the state node is missing in your device tree.
>>
>> Do you have the state driver enabled? drvinfo should tell you that.
>>
>> Cheers
>> Ahmad
>>
>> --
>> Pengutronix e.K. | |
>> Steuerwalder Str. 21 | https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pengutronix.de%2F&data=01%7C01%7Chu.schlieben%40codewrights.de%7Cfd604ff2646c497fbb3508d79dbca678%7C0974af9b352b437cb606e9f242c0c227%7C0&sdata=Edh9RArsjllc2C5LSvixIndwBoKZfMY0dnbLT2NdE1w%3D&reserved=0 |
>> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
>> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-01-21 20:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <r276.1579090214262888471.6UJY@lists.yoctoproject.org>
2020-01-15 13:02 ` Enrico Joerns
2020-01-15 13:26 ` Hans-Ulrich Schlieben
2020-01-15 13:38 ` Ahmad Fatoum
2020-01-15 13:39 ` Ahmad Fatoum
2020-01-15 14:25 ` Hans-Ulrich Schlieben
2020-01-15 14:36 ` Ahmad Fatoum
2020-01-15 14:47 ` Enrico Joerns
2020-01-16 15:13 ` Hans-Ulrich Schlieben
2020-01-20 15:31 ` Ahmad Fatoum
2020-01-21 18:28 ` Hans-Ulrich Schlieben
2020-01-21 20:18 ` Ahmad Fatoum
2020-01-22 17:59 ` Robert Berger@yocto.user
2020-01-23 15:30 ` Hans-Ulrich Schlieben
2020-01-23 15:36 ` Ahmad Fatoum
2020-01-23 16:11 ` Hans-Ulrich Schlieben
2020-01-23 16:17 ` Ahmad Fatoum
2020-01-23 16:31 ` Hans-Ulrich Schlieben
2020-01-16 15:09 ` Hans-Ulrich Schlieben
2020-01-20 15:23 ` Ahmad Fatoum
2020-01-21 17:51 ` Hans-Ulrich Schlieben
2020-01-21 20:21 ` Ahmad Fatoum [this message]
2020-01-23 15:37 ` Hans-Ulrich Schlieben
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ec5a32e4-3317-9691-a286-0c7053f25f4c@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=ejo@pengutronix.de \
--cc=hu.schlieben@codewrights.de \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox