Oh I see, I thought that aarch64/raspberry had the same issue too. Yes, the aarch64 BSP works fine with the latest firmware. I was able to boot from USB too. I wanted to setup rtems-tester for aarch64/raspberry BSP using TFTP/PXE boot, So I needed help with that.
On Sun, 25 Sept 2022 at 20:31, Alan Cudmore <[email protected]> wrote: > Hi Noor, > > The firmware issue that I am aware of is for the 32 bit arm/raspberrypi > BSPs. I would expect that your Aarch64 BSP would work with the latest > Raspberry Pi firmware. Are you talking about aarch64/raspberrypi or > arm/raspberrypi? > > Alan > > > > *From: *Noor Aman <[email protected]> > *Sent: *Sunday, September 25, 2022 3:53 AM > *To: *William Moore <[email protected]>; Alan Cudmore > <[email protected]>; Hesham Moustafa <[email protected]>; > [email protected] <[email protected]> > *Subject: *rtems-tester for raspberry pi 4B > > > > Hey, > > Now that I have built a BSP, I wanted to run the rtems-tester for > Raspberry Pi. But I'm confused on what to do now. The raspberry pi 2 bsp > required u-boot in order to run the test which is understandable as rpi2 > didnt had support for PXE boot, but the raspberry pi 4b has support for > tftp boot but I'm unable to use it. Any ideas about how to do that? I would > still like to know how u-boot was used for the earlier raspberry pi. > > > > One thing more, once you said > > Current Raspberry Pi BSPs have problem with the firmware that we have not > resolved. Once we are past a certain commit of the Raspberry Pi firmware, > RTEMS will not boot. This has prevented me from booting RTEMS on the > Raspberry Pi Zero 2 W (Quad core). I know your project is for the Pi 4, but > it would be great if we could finally figure that out. > > > > because of this I was using old firmwares (1.20200601), but after I > finished building BSP, I thought of booting from USB but newer firmware was > required. So I tried the firmware-1.20220830 (latest) and it just worked. I > tried some more releases and everything worked just fine. I'm just > wondering what caused things to change. > > > > Thanks, > > Noor > > >
_______________________________________________ devel mailing list [email protected] http://lists.rtems.org/mailman/listinfo/devel
