DistroKit Mailinglist
 help / color / mirror / Atom feed
From: "Joshi, Pranay" <Pranay.Joshi@bakerhughes.com>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: "ptxdist@pengutronix.de distrokit@pengutronix.de"
	<distrokit@pengutronix.de>,
	Ahmad Fatoum <a.fatoum@pengutronix.de>,
	Roland Hieber <rhi@pengutronix.de>
Subject: Re: [DistroKit] [ptxdist] Prepare Image for Raspberry Pi 4
Date: Tue, 15 Nov 2022 11:27:50 +0000	[thread overview]
Message-ID: <PH0PR08MB80147C75464F0AFB26D8AF3782049@PH0PR08MB8014.namprd08.prod.outlook.com> (raw)
In-Reply-To: <20221115110008.swrhxebrbdveo7zh@pengutronix.de>

> 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.

Yes, we are using OSELAS Toolchain for ARMv7a.

> 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.

Ok, We will check.

Pranay Joshi
Lead Engineer-Firmware Engineering
Drilling Services
Baker Hughes


-----Original Message-----
From: Marco Felsch <m.felsch@pengutronix.de> 
Sent: Tuesday, November 15, 2022 4:30 PM
To: Joshi, Pranay <Pranay.Joshi@bakerhughes.com>
Cc: Roland Hieber <rhi@pengutronix.de>; ptxdist@pengutronix.de distrokit@pengutronix.de <distrokit@pengutronix.de>; Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [DistroKit] [ptxdist] Prepare Image for Raspberry Pi 4

  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 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 <rhi@pengutronix.de>
> Sent: Tuesday, November 15, 2022 3:46 PM
> To: Joshi, Pranay <Pranay.Joshi@bakerhughes.com>
> Cc: ptxdist@pengutronix.de distrokit@pengutronix.de 
> <distrokit@pengutronix.de>; Ahmad Fatoum <a.fatoum@pengutronix.de>; 
> Marco Felsch <m.felsch@pengutronix.de>
> 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%2F
> > > ww 
> > > w.raspberrypi.com%2Fsoftware%2F&amp;data=05%7C01%7Cpranay.joshi%40
> > > ba 
> > > kerhughes.com%7Cf65894b84494477078fa08dac6f275e6%7Cd584a4b7b1f2471
> > > 4a 
> > > 578fd4d43c146a6%7C0%7C0%7C638041041910681676%7CUnknown%7CTWFpbGZsb
> > > 3d 
> > > 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
> > > D% 
> > > 7C3000%7C%7C%7C&amp;sdata=0Krk8ee8ZLDh9ev0puV61aVmuN3srVLlLbK%2Fd9
> > > Qa
> > > ZbE%3D&amp;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&amp;data=05%7C01%7Cpranay.joshi%40bakerhughes.com%7C34f075792bea4a8e256008dac6f8904d%7Cd584a4b7b1f24714a578fd4d43c146a6%7C0%7C0%7C638041068130984689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=irAsz2Rgkhs4rsEcZalwc1LLGsw3bt8g%2FNaBMqT7Q8c%3D&amp;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&amp;data=05%7C01%7Cpranay.joshi%40bakerhughes.com%7C34f075792bea4a8e256008dac6f8904d%7Cd584a4b7b1f24714a578fd4d43c146a6%7C0%7C0%7C638041068130984689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=FJMKFVHcSyd6WUPH9fKvNMXwGzIRNuvl8W3X%2Fcx%2B7y0%3D&amp;reserved=0 |
> 31137 Hildesheim, Germany                | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686         | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2022-11-15 11:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PH0PR08MB801478F4321D6EC7F26475AB82329@PH0PR08MB8014.namprd08.prod.outlook.com>
2022-10-31  8:01 ` Ahmad Fatoum
     [not found]   ` <PH0PR08MB80142B5E46E08F7A38197224823C9@PH0PR08MB8014.namprd08.prod.outlook.com>
     [not found]     ` <SN4PR0801MB8017A9D758C4B6BB3D006FAD82059@SN4PR0801MB8017.namprd08.prod.outlook.com>
2022-11-14 10:58       ` Marco Felsch
2022-11-15  6:05         ` Joshi, Pranay
2022-11-15  9:41           ` Marco Felsch
2022-11-15  9:47             ` Joshi, Pranay
2022-11-15 10:04               ` Marco Felsch
2022-11-15 10:16             ` Roland Hieber
2022-11-15 10:30               ` Joshi, Pranay
2022-11-15 11:00                 ` Marco Felsch
2022-11-15 11:27                   ` Joshi, Pranay [this message]
2022-12-01 12:09                     ` Ahmad Fatoum
2022-12-02  5:39                       ` Joshi, Pranay
2022-12-02  6:14                         ` Ahmad Fatoum
2022-12-05  6:00                           ` Joshi, Pranay

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=PH0PR08MB80147C75464F0AFB26D8AF3782049@PH0PR08MB8014.namprd08.prod.outlook.com \
    --to=pranay.joshi@bakerhughes.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    --cc=m.felsch@pengutronix.de \
    --cc=rhi@pengutronix.de \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox