From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 15 Nov 2022 12:00:16 +0100 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1outfs-008BpW-Gu for lore@lore.pengutronix.de; Tue, 15 Nov 2022 12:00:16 +0100 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1outfr-0003Tm-AQ; Tue, 15 Nov 2022 12:00:15 +0100 Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1outfl-0003Sv-1P; Tue, 15 Nov 2022 12:00:09 +0100 Received: from mfe by ptx.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1outfk-0001Q2-MB; Tue, 15 Nov 2022 12:00:08 +0100 Date: Tue, 15 Nov 2022 12:00:08 +0100 From: Marco Felsch To: "Joshi, Pranay" Message-ID: <20221115110008.swrhxebrbdveo7zh@pengutronix.de> References: <50eb7f21-9075-abf8-27f4-6064bb3f1194@pengutronix.de> <20221114105803.6gmyv3fcwz4skzfw@pengutronix.de> <20221115094115.rxiaepnmabnkmeav@pengutronix.de> <20221115101626.t3tofvn56vrupw7t@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20180716 Subject: Re: [DistroKit] [ptxdist] Prepare Image for Raspberry Pi 4 X-BeenThere: distrokit@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: DistroKit Mailinglist List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "ptxdist@pengutronix.de distrokit@pengutronix.de" , Ahmad Fatoum , Roland Hieber Sender: "DistroKit" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: distrokit-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false On 22-11-15, Joshi, Pranay wrote: > > And you're using the arm-v7a version? > We have used platform-rpi and platform-v7a, both. You need to use the platform-v7a platform, everything else will not work. I mean by "And you're using the arm-v7a version", you use the oselas-toolchain for ARMv7-A. > > Which platform did you select and which image did you flashed to the SD card? > Used "hd.img" from both platform and also used "rpi.hdimg" from platform-v7a. Also the only image you should use is the rpi.hdimg which comes from the platform-v7a/images/ dir. Since you switched from origin/master to origin/next, there could be a problem with dependency tracking. Can you please run 'ptxdist clean' and say 'y' while you getting asked to clean all. After this step you can rebuild your whole project. Please ensure before that you selected the platform-v7a platformconfig and the IMAGE_RPI2. Regards, Marco > > Pranay Joshi > Lead Engineer-Firmware Engineering > Drilling Services > Baker Hughes > > > -----Original Message----- > From: Roland Hieber > Sent: Tuesday, November 15, 2022 3:46 PM > To: Joshi, Pranay > Cc: ptxdist@pengutronix.de distrokit@pengutronix.de ; Ahmad Fatoum ; Marco Felsch > Subject: Re: [DistroKit] [ptxdist] Prepare Image for Raspberry Pi 4 > > [You don't often get email from rhi@pengutronix.de. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] > > EXTERNAL EMAIL: This email originated outside of our organization. Do not click on any links or open attachments from unexpected or unknown senders unless you can verify the content is safe. > > > On Tue, Nov 15, 2022 at 10:41:15AM +0100, Marco Felsch wrote: > > Hi, > > > > On 22-11-15, Joshi, Pranay wrote: > > > Hi Marco, > > > > > > Thanks for response. > > > > > > Please find attached error logs for more detail. > > > > Thanks for the error log. > > > > > Read start_cd.elf bytes 685540 hnd 0x00000000 > > > Read fixup_cd.dat bytes 2657 hnd 0x00000000 > > > Firmware: 679ebca20dc08ca3f5392e02d772fed727debdae Sep 9 2019 > > > 18:51:29 > > > 0x00d03114 0x00000000 0x00000000 > > > start_cd.elf: is not compatible > > > This board requires newer software > > > Get the latest software from > > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww > > > w.raspberrypi.com%2Fsoftware%2F&data=05%7C01%7Cpranay.joshi%40ba > > > kerhughes.com%7Cf65894b84494477078fa08dac6f275e6%7Cd584a4b7b1f24714a > > > 578fd4d43c146a6%7C0%7C0%7C638041041910681676%7CUnknown%7CTWFpbGZsb3d > > > 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D% > > > 7C3000%7C%7C%7C&sdata=0Krk8ee8ZLDh9ev0puV61aVmuN3srVLlLbK%2Fd9Qa > > > ZbE%3D&reserved=0 > > > > The version of the start_cd.elf seems a bit old since Ahmad updated it > > to v1.20220331 and the loader says it is from 2019. > > > > To sum up a few things since I just stepped in into this conversation: > > Let me just step into this conversation too… 🙂 I'm not very experienced with RPi 4 either, but you can try using the newer firmware files from > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fraspberrypi%2Ffirmware%2Ftree%2Fmaster%2Fboot&data=05%7C01%7Cpranay.joshi%40bakerhughes.com%7Cf65894b84494477078fa08dac6f275e6%7Cd584a4b7b1f24714a578fd4d43c146a6%7C0%7C0%7C638041041910681676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NnQIczuz1XiA6xORUuHcOjy5inYFWVFCQs0LT5nPpLM%3D&reserved=0 and put them into /rpi-firmware in your DistroKit tree. I'm not sure if barebox will work, but it's worth a try. > > - Roland > > -- > Roland Hieber, Pengutronix e.K. | r.hieber@pengutronix.de | > Steuerwalder Str. 21 | https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pengutronix.de%2F&data=05%7C01%7Cpranay.joshi%40bakerhughes.com%7Cf65894b84494477078fa08dac6f275e6%7Cd584a4b7b1f24714a578fd4d43c146a6%7C0%7C0%7C638041041910681676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5OLgrwdAWtBihl2GUmwvWRdN4HGBEx2ESSFO3X6FK0M%3D&reserved=0 | > 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |