RE: [yocto] #yocto bootchooser: Cannot get state 'state'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Ahmad,

i asked phytec about barebox2019 and was told that it supports imx6ul and not imx6q. I should continue to use barebox2017.
So I use Barebox2017, which works in zeus with bootchooser.

Thank you very much for your great help.

hu

-----Original Message-----
From: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx> 
Sent: Tuesday, 21 January 2020 21:21
To: Hans-Ulrich Schlieben <hu.schlieben@xxxxxxxxxxxxxx>; Enrico Joerns <ejo@xxxxxxxxxxxxxx>; yocto@xxxxxxxxxxxxxxxxxxxxxx
Cc: barebox@xxxxxxxxxxxxxxxxxxx
Subject: Re: [yocto] #yocto bootchooser: Cannot get state 'state'

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@xxxxxxxxxxxxxx>
>> Sent: Monday, 20 January 2020 16:23
>> To: Hans-Ulrich Schlieben <hu.schlieben@xxxxxxxxxxxxxx>; Enrico 
>> Joerns <ejo@xxxxxxxxxxxxxx>; yocto@xxxxxxxxxxxxxxxxxxxxxx
>> Cc: barebox@xxxxxxxxxxxxxxxxxxx
>> 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&amp;data=01%7C01%7Chu.schlieben%40codewr
>> ights.de%7Ce3ebad52e8684e97508408d79eaf7bdc%7C0974af9b352b437cb606e9f
>> 242c0c227%7C0&amp;sdata=DZxO9KqXifll8fJMkpncakmLGAzbR1uMXnSKziBVzLY%3
>> D&amp;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&amp;data=01%7C01%7Chu.schlieben%40codewrights.de%7Ce3ebad52e8684e97508408d79eaf7bdc%7C0974af9b352b437cb606e9f242c0c227%7C0&amp;sdata=82oH7MjlqIb3kDd0NRfhXyWz%2FFYQqD9I7P9YhcfKbKc%3D&amp;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                       | https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pengutronix.de%2F&amp;data=01%7C01%7Chu.schlieben%40codewrights.de%7Ce3ebad52e8684e97508408d79eaf7bdc%7C0974af9b352b437cb606e9f242c0c227%7C0&amp;sdata=82oH7MjlqIb3kDd0NRfhXyWz%2FFYQqD9I7P9YhcfKbKc%3D&amp;reserved=0  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox



[Index of Archives]     [Linux Embedded]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux