From: "Barbier, Renaud" <renaud.barbier@abaco.com> To: Ahmad Fatoum <a.fatoum@pengutronix.de>, Barebox List <barebox@lists.infradead.org> Subject: RE: NXP Layerscape Date: Mon, 14 Jun 2021 15:16:27 +0000 [thread overview] Message-ID: <MN2PR16MB3135E10CC5F4B532EDA547D291319@MN2PR16MB3135.namprd16.prod.outlook.com> (raw) In-Reply-To: <ad0091c0-2919-de80-01d5-41cea68d5550@pengutronix.de> I am a bit confused on how the QSPI image is built. >From images/Makefile.layerscape $(obj)/barebox-ls1046ardb-qspi.image: $(obj)/start_ls1046ardb.pblb \ $(board)/ls1046ardb/ls1046ardb_rcw_qspi.cfg \ $(board)/ls1046ardb/ls1046ardb_pbi.cfg It makes use of the file ls1046ardb/ls1046ardb_pbi.cfg not ls1046ardb/ls1046ardb_qspi_pbi.cfg. ls1046a_qspi_pbi.cfg contains an endian swap that I can see in the U-boot rcw+pbi data. When I take an hex dump of the barebox-ls1046ardb-qspi.image, I see that the scratchpad register 2 (BOOTLOCPTR) in the PBI section points to 0x10000000 (as in the PBI file), not the PBL address start address. How can this work? Renaud -----Original Message----- From: Ahmad Fatoum <a.fatoum@pengutronix.de> Sent: 10 June 2021 15:09 To: Barbier, Renaud <renaud.barbier@abaco.com>; Barebox List <barebox@lists.infradead.org> 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%7C01%7Crenaud.barbier%40abaco.com%7Cdf668f5e5f2d497d54cb08d92c194c3e%7Ce6f27451899d4d0db8fa88baafa551a7%7C0%7C0%7C637589309423979193%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=SnXT0WYjQMJL%2FwK1LaOK1h7OMUcLiL37cojY2hzP89s%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@lists.infradead.org > https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists > .infradead.org%2Fmailman%2Flistinfo%2Fbarebox&data=04%7C01%7Crenau > d.barbier%40abaco.com%7Cdf668f5e5f2d497d54cb08d92c194c3e%7Ce6f27451899 > d4d0db8fa88baafa551a7%7C0%7C0%7C637589309423989184%7CUnknown%7CTWFpbGZ > 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%7Cdf668f5e5f2d497d54cb08d92c194c3e%7Ce6f27451899d4d0db8fa88baafa551a7%7C0%7C0%7C637589309423989184%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hB2sfEPHomEzn0ICOo9o%2BfRwu3kpXuSvyGZ%2FP%2FnRmpc%3D&reserved=0 | 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:[~2021-06-14 15:18 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-10 13:49 Barbier, Renaud 2021-06-10 14:09 ` Ahmad Fatoum 2021-06-10 17:08 ` Barbier, Renaud [not found] ` <MN2PR16MB31359FACA75C0F54E7672C5691359@MN2PR16MB3135.namprd16.prod.outlook.com> [not found] ` <33d59215-cd45-71cc-5f0b-e26d0a43e9d1@pengutronix.de> [not found] ` <MN2PR16MB31352F2590A920BB39ACC17F91359@MN2PR16MB3135.namprd16.prod.outlook.com> 2021-06-10 16:35 ` Ahmad Fatoum [not found] ` <MN2PR16MB3135880DC913705C5BE493BB91359@MN2PR16MB3135.namprd16.prod.outlook.com> 2021-06-10 16:50 ` Ahmad Fatoum [not found] ` <MN2PR16MB3135787D6B3FCF98CAA0F53591359@MN2PR16MB3135.namprd16.prod.outlook.com> 2021-06-11 8:29 ` Ahmad Fatoum 2021-06-14 15:16 ` Barbier, Renaud [this message] 2021-06-15 8:49 ` Sascha Hauer 2021-06-15 19:02 ` Barbier, Renaud
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=MN2PR16MB3135E10CC5F4B532EDA547D291319@MN2PR16MB3135.namprd16.prod.outlook.com \ --to=renaud.barbier@abaco.com \ --cc=a.fatoum@pengutronix.de \ --cc=barebox@lists.infradead.org \ --subject='RE: NXP Layerscape' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox