Re: [yocto] #yocto bootchooser: Cannot get state 'state' - Hans-Ulrich Schlieben

From: "Hans-Ulrich Schlieben" <hu.schlieben@codewrights.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
	"Robert Berger@yocto.user" <robert.berger.yocto.user@gmail.com>,
	Enrico Joerns <ejo@pengutronix.de>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
	"barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [yocto] #yocto bootchooser: Cannot get state 'state'
Date: Thu, 23 Jan 2020 16:31:31 +0000	[thread overview]
Message-ID: <DB8PR03MB5498E0319EA232F097C0FB9CFE0F0@DB8PR03MB5498.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <288b08bb-8248-fa5f-d62f-011215bdbeb2@pengutronix.de>

Hi,

both dd copies of barebox (with and without offset) reproduced a system which no longer shows anything on the console.
Probably I setup something wrong when building barebox.

Regards

hu

> Hi Ahmad,
> 
>>
>> Hello,
>>
>> On 1/23/20 4:30 PM, Hans-Ulrich Schlieben wrote:
>>> Hi Robert,
>>>
>>> there where no SDK, bison and flex missing. Now it compiled. Thanx.
>>> There are
>>>
>>> Copying it onto the system and running it from the console just returned error code 132 and: 
>>> Illegal instruction
>>
>> Running what?
> The barebox executable in the barebox folder, not some image. The executable starts with ELF so it should run, shouldn't it?
> In the barebox README states:  The barebox image is a normal Linux 
> executable, so it can be started  just like every other program

Few lines earlier, it says that the scenario in the document uses ARCH=sandbox, which indeed is an ELF executable for your host system. When building for ARCH=arm though, the resulting ELF isn't meant for running under an OS, even an ARM. Instead the necessary sections are copied out of the ELF according to a SoC-specific layout.

>>> I copied the .config file from yocto into the barebox directory. Do I have still the wrong architecture?
>>>
>>> Perhaps I have to copy  ./images/barebox-phytec-phycard-imx6q-1gib.img onto the destination system starting at offset 0x1000 using dd.
>>> How to copy barebox onto the sdcard? There is no setupmbr executable in ./scripts/setupmbr, just a c file and no working Makefile.
>>
>> barebox already has the dcd offset in, just dd the correct image to the start of your SD-Card and it should work.
> Wait, just running dd if= bareboximagefile of=/dev/mmcblk0 would just kill my Partitiontable in sector 0. 

For testing, you can just kill your partition table, but yes eventually, you will want to copy barebox later in the image.

> When I look into the bareboximagefile I see two sections starting with something like barebox.......UUUUUUUUUUUUUUUUUUUUUUUUUU at offset 0 and offset 0x1000.
> The part at 0x1000 resembles more what I see on my sdcard on offset 
> 0x1000 so my approach would be to dd if= bareboximagefile of=/dev/mmcblk0 bs=512 offset=8 skip=8.
> What do you think?

yes, this should work.

> 
>>
>> Cheers
>> Ahmad
>>
>>
> Thank you and Best Regards
> 
> hu
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pengutronix.de%2F&amp;data=01%7C01%7Chu.schlieben%40codewrights.de%7C94d4466fb4154885110908d7a01fb7b0%7C0974af9b352b437cb606e9f242c0c227%7C0&amp;sdata=pv5a4oMQQIrYqN%2FHq3zoJxONm0QuuJkXOa9UqFPu38Q%3D&amp;reserved=0 |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |