Hello Renaud, On 10.06.21 18:44, Barbier, Renaud wrote: > It partially starts: > > => go 0xa0020000 > ## Starting application at 0xA0020000 ... > > > barebox 2021.03.0-00096-gb6358ef010-dirty #14 Thu Jun 10 16:26:59 BST 2021 > > > Board: LS1046A RDB Board > FIT: Opened FIT image: PPA Firmware > FIT: No match found. Trying default. > FIT: configuration 'config@1': PPA Secure firmware > FIT: image 'firmware@1': 'PPA Firmware: Version LSDK-20170625' Huh, apparently U-Boot is running at EL3 and loads barebox at EL3 as well. EL3 barebox tries to load PPA (secure monitor) and that fails. This shouldn't happen with normal boots though, because: - if barebox runs at EL3, nothing besides BootROM has run before it, so it can load the PPA normally, which returns to barebox in EL2 - if barebox runs at EL2, it will automatically skip installation of the PPA Cheers, Ahmad > > -----Original Message----- > From: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx> > Sent: 10 June 2021 17:36 > To: Barbier, Renaud <renaud.barbier@xxxxxxxxx> > Cc: barebox@xxxxxxxxxxxxxxxxxxx > Subject: Re: NXP Layerscape > > > > [**EXTERNAL SOURCE**]:Please verify the source before clicking link or opening attachment. > > On 10.06.21 18:23, Barbier, Renaud wrote: >> Could the barebox image be started from memory with a "go" command? >> What would be the entry point? > > Here's the barebox code that implements booting other barebox images: > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.pengutronix.de%2Fcgit%2Fbarebox%2Ftree%2Farch%2Farm%2Fmach-layerscape%2Fpblimage.c&data=04%7C01%7Crenaud.barbier%40abaco.com%7Cffecae81cdee4a7b7eb608d92c2dce3d%7Ce6f27451899d4d0db8fa88baafa551a7%7C0%7C0%7C637589397510510674%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DLsQvcf5K4QVJtZ8UJSNE%2Fywd80%2FoT2ZUGS3T0NISps%3D&reserved=0 > > Apparently entry point is at offset 128K. Keep in mind that U-Boot go (at least on ARM32) does not do cache maintenance or turn off the MMU, so funny effects may be expected. > > Cheers, > Ahamd > >> >> -----Original Message----- >> From: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx> >> Sent: 10 June 2021 17:14 >> To: Barbier, Renaud <renaud.barbier@xxxxxxxxx> >> Subject: Re: NXP Layerscape >> >> >> >> [**EXTERNAL SOURCE**]:Please verify the source before clicking link or opening attachment. >> >> Hi Renaud, >> >> (please keep mailing list CC'd) >> >> On 10.06.21 16:53, Barbier, Renaud wrote: >>> I am not using a USB serial adapter. Currently I have a RJ-45 to RS232 to my laptop. >>> >>> Should not BOOTLOCPTR be set I the PBI. I see 0x40100000 for U-boot and 0x10000000 for barebox. Unless it does not apply for PPA boot flow. >> >> I don't know about the specifics of the first stage boot on the Layerscape, I just wanted to point you at the docs and ask if the steps I had documented there work for you or not. >> >> Cheers, >> Ahmad >> >>> >>> -----Original Message----- >>> From: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx> >>> Sent: 10 June 2021 15:09 >>> To: Barbier, Renaud <renaud.barbier@xxxxxxxxx>; Barebox List >>> <barebox@xxxxxxxxxxxxxxxxxxx> >>> Subject: Re: NXP Layerscape >>> >>> >>> >>> [**EXTERNAL SOURCE**]:Please verify the source before clicking link or opening attachment. >>> >>> Hello Barbier, >>> >>> On 10.06.21 15:49, Barbier, Renaud wrote: >>>> I received a NXP LS1046A-RDB >>> >>> It doesn't reboot cleanly with a USB serial adapter attached! >>> Jfyi, gave me a scare first time, when I thought I broke something ^^. >>> >>>> >>>> I built barebox for the LS1046A and got the image barebox-ls1046ardb-qspi.image. >>>> I programmed the image in the alternative SPI bank as per NXP instructions: >>>> => tftp $load_addr >>>> => sf erase 0 +$filesize && sf write $load_addr 0 $filesize >>>> >>>> Barebox does not boot. >>>> >>>> I did notice that u-boot is at address 0x40100000 while the RCW is at 0x40000000. >>>> My understanding is that barebox is one image and shall be >>>> programmed at offset 0 of the SPI (0x40000000) >>> >>> Can't comment on that. Sascha did the integration. >>> >>>> At present I cannot connect my I.C.E. due a pin stuck in my MIPI connector. >>>> >>>> Any return on experience is welcome. >>> >>> Can comment on that: Last time I did this, I wrote some documentation: >>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. >>> barebox.org%2Fdoc%2Flatest%2Fboards%2Flayerscape.html&data=04%7C0 >>> 1 >>> %7Crenaud.barbier%40abaco.com%7C0e00e06c3236419cae1108d92c2acefe%7Ce6 >>> f >>> 27451899d4d0db8fa88baafa551a7%7C0%7C0%7C637589384654589155%7CUnknown% >>> 7 >>> CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJX >>> V >>> CI6Mn0%3D%7C1000&sdata=OUk8SFTmrlH0U%2F8aiXZonQHxLplyEjlMtc7Y5JHx >>> % >>> 2BUk%3D&reserved=0 >>> >>> There I flashed barebox from another barebox booted from SD-Card. >>> I'd assume that should still work. I can't recall how the CPLD needed to be tickled, but it would be helpful to know whether doing it like described in the documentation doesn't work for you. >>> >>> Cheers, >>> Ahmad >>> >>>> >>>> Cheers, >>>> Renaud >>>> >>>> >>>> _______________________________________________ >>>> barebox mailing list >>>> barebox@xxxxxxxxxxxxxxxxxxx >>>> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flis >>>> t >>>> s >>>> .infradead.org%2Fmailman%2Flistinfo%2Fbarebox&data=04%7C01%7Cren >>>> a >>>> u >>>> d.barbier%40abaco.com%7Cdf668f5e5f2d497d54cb08d92c194c3e%7Ce6f274518 >>>> 9 >>>> 9 >>>> d4d0db8fa88baafa551a7%7C0%7C0%7C637589309423989184%7CUnknown%7CTWFpb >>>> G >>>> Z >>>> sb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0 >>>> % >>>> 3 >>>> D%7C1000&sdata=ORpVZlyPk2o7%2FyVYOkJPeAWNnq2%2FkxKauxep7gvDJ%2Bo >>>> % >>>> 3 >>>> D&reserved=0 >>>> >>> >>> -- >>> Pengutronix e.K. | | >>> Steuerwalder Str. 21 | https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pengutronix.de%2F&data=04%7C01%7Crenaud.barbier%40abaco.com%7Cffecae81cdee4a7b7eb608d92c2dce3d%7Ce6f27451899d4d0db8fa88baafa551a7%7C0%7C0%7C637589397510510674%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=almI5k4Eunio%2FSXlzJvPEjdbojWK9u%2B7%2BQ9jMYAEJbA%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 | https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pengutronix.de%2F&data=04%7C01%7Crenaud.barbier%40abaco.com%7Cffecae81cdee4a7b7eb608d92c2dce3d%7Ce6f27451899d4d0db8fa88baafa551a7%7C0%7C0%7C637589397510510674%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=almI5k4Eunio%2FSXlzJvPEjdbojWK9u%2B7%2BQ9jMYAEJbA%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 | https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pengutronix.de%2F&data=04%7C01%7Crenaud.barbier%40abaco.com%7Cffecae81cdee4a7b7eb608d92c2dce3d%7Ce6f27451899d4d0db8fa88baafa551a7%7C0%7C0%7C637589397510510674%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=almI5k4Eunio%2FSXlzJvPEjdbojWK9u%2B7%2BQ9jMYAEJbA%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@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
