Re: Raspberry Pi test report

On Wed, Jan 22, 2020 at 2:18 AM Christian Mauderer wrote: > I think the not yet merged patch from Niteesh is a good reference: > > https://lists.rtems.org/pipermail/devel/2020-January/056860.htm > l The above instructions are not

Re: Raspberry Pi test report

I think the not yet merged patch from Niteesh is a good reference: https://lists.rtems.org/pipermail/devel/2020-January/056860.html On 21/01/2020 21:31, Alan Cudmore wrote: > I can try QEMU. Is there a quick pointer to the QEMU parameters needed > to run a Pi2 image? > Alan > > On Tue, Jan 21, 2

Re: Raspberry Pi test report

I can try QEMU. Is there a quick pointer to the QEMU parameters needed to run a Pi2 image? Alan On Tue, Jan 21, 2020 at 3:22 PM Christian Mauderer wrote: > > Does the same error occur on the Pi2 Qemu? In that case you could use it > for proper debugging. > > On 21/01/2020 03:35, Alan Cudmore wrot

Re: Raspberry Pi test report

Does the same error occur on the Pi2 Qemu? In that case you could use it for proper debugging. On 21/01/2020 03:35, Alan Cudmore wrote: > I don't really have a debug setup.. I'm just using printk for now. But > I have a pretty efficient setup where I can add a few printk > statements, rebuild and

Re: Raspberry Pi test report

On 21/01/2020 00:30, Chris Johns wrote: > On 21/1/20 10:20 am, Alan Cudmore wrote: >> As it turns out the latest RTEMS master may need some of the dtb >> and/or overlay files in the raspberry pi SD card. But the updated >> instructions that Niteesh submitted for the raspberrypi BSP should >> still

Re: Raspberry Pi test report

I don't really have a debug setup.. I'm just using printk for now. But I have a pretty efficient setup where I can add a few printk statements, rebuild and copy the smp01.exe sample over to the SD card. I use this board: https://www.adafruit.com/product/3589 It lets me connect the serial port using

Re: Raspberry Pi test report

What is your debugging setup? It would be really helpful for my future works on Rpi3. Thanks, Niteesh On Tue, 21 Jan, 2020, 7:23 AM Alan Cudmore, wrote: > A little more information on my Raspberry Pi 2 SMP tests: > > The BSP startup is getting to this loop: > https://git.rtems.org/rtems/tree/cp

Re: Raspberry Pi test report

A little more information on my Raspberry Pi 2 SMP tests: The BSP startup is getting to this loop: https://git.rtems.org/rtems/tree/cpukit/score/src/percpustatewait.c#n49 (In the function _Per_CPU_State_wait_for_non_initial_state) In the while loop on line 49, the CPU state is PER_CPU_STATE_INITIA

Re: Raspberry Pi test report

On 21/1/20 10:20 am, Alan Cudmore wrote: > As it turns out the latest RTEMS master may need some of the dtb > and/or overlay files in the raspberry pi SD card. But the updated > instructions that Niteesh submitted for the raspberrypi BSP should > still be valid. Great. > Either way, we should be

Re: Raspberry Pi test report

As it turns out the latest RTEMS master may need some of the dtb and/or overlay files in the raspberry pi SD card. But the updated instructions that Niteesh submitted for the raspberrypi BSP should still be valid. Either way, we should be able to automate it. A firmware release on Github is ~180 m

Re: Raspberry Pi test report

On 6/1/20 9:42 am, Alan Cudmore wrote: > I finally found the time to try the latest RTEMS head on my collection of > Raspberry Pi models. > The last time I tried to run RTEMS on a Pi, I had trouble with the current > version of the Raspberry Pi Firmware, so I had to go back to a specific tag on > t

Re: Raspberry Pi test report

On 20/1/20 6:42 am, Alan Cudmore wrote: > I tried the latest RTEMS master on my collection of single core RPis and they > all worked. I used the kernel_address=0x20 option in the config.txt file. > The BSP did not identify the RPi Model B (26 pin GPIO header) or the RPi Model > A+ (1.1) since t

Re: Re: Raspberry Pi test report

...@rtems.org > *Subject: *Re: Raspberry Pi test report > > > > On 19/01/2020 20:42, Alan Cudmore wrote: > > > I tried the latest RTEMS master on my collection of single core RPis and > > > they all worked. I used the kernel_address=0x20 option in the > > > conf

RE: Re: Raspberry Pi test report

: Raspberry Pi test report On 19/01/2020 20:42, Alan Cudmore wrote:> I tried the latest RTEMS master on my collection of single core RPis and> they all worked. I used the kernel_address=0x20 option in the> config.txt file.> The BSP did not identify the RPi Model B (26 pin GPIO header) or th

RE: Re: Raspberry Pi test report

  From: Christian MaudererSent: Sunday, January 19, 2020 2:49 PMTo: Alan Cudmore; Christian Mauderer; gsnb...@gmail.comCc: rtems-de...@rtems.orgSubject: Re: Raspberry Pi test report On 19/01/2020 20:42, Alan Cudmore wrote:> I tried the latest RTEMS master on my collection of single core RPis

Re: Raspberry Pi test report

On 19/01/2020 20:42, Alan Cudmore wrote: > I tried the latest RTEMS master on my collection of single core RPis and > they all worked. I used the kernel_address=0x20 option in the > config.txt file. > The BSP did not identify the RPi Model B (26 pin GPIO header) or the RPi > Model A+ (1.1) sinc

Re: Raspberry Pi test report

I tried the latest RTEMS master on my collection of single core RPis and they all worked. I used the kernel_address=0x20 option in the config.txt file. The BSP did not identify the RPi Model B (26 pin GPIO header) or the RPi Model A+ (1.1) since they use the older device ID register format. It'

Re: Raspberry Pi test report

The Debian Linux variant for the Raspberry Pi (Raspbian) is still 32 bit for both the Pi 3 and 4, so I would think 32 bit ports would run on both. The Raspberry Pi 4 has a Quad Core A72, 1 to 4 Gigabytes of LPDDR4 SDRAM, Gigabit ethernet, USB 3, Wi-fi and bluetooth. I have not looked into it enough

Re: Raspberry Pi test report

On 08/01/2020 00:24, Joel Sherrill wrote: > > > On Tue, Jan 7, 2020 at 12:42 PM Christian Mauderer > wrote: > > Hello Alan, > > I pushed the patches mentioned further below. So the raspberry BSP > should now work again for all raspberry 1 and 2 on the off

Re: Raspberry Pi test report

On Tue, Jan 7, 2020 at 12:42 PM Christian Mauderer wrote: > Hello Alan, > > I pushed the patches mentioned further below. So the raspberry BSP > should now work again for all raspberry 1 and 2 on the official master > branch. Note that the > > kernel_address=0x20 > > is still necessary. >

Re: [EXTERNAL] Re: Raspberry Pi test report

Thank you for the updates, I will try out the latest on my collection of Raspberry Pis and report back. Alan On 1/7/20, 1:47 PM, "devel on behalf of Christian Mauderer" wrote: Hello Alan, I pushed the patches mentioned further below. So the raspberry BSP should now work again

Re: Raspberry Pi test report

Hello Alan, I pushed the patches mentioned further below. So the raspberry BSP should now work again for all raspberry 1 and 2 on the official master branch. Note that the kernel_address=0x20 is still necessary. Best regards Christian On 06/01/2020 11:10, Christian Mauderer wrote: > H

Re: Raspberry Pi test report

Hello Alan, thanks for your very detailed tests. On 05/01/2020 23:42, Alan Cudmore wrote: > I finally found the time to try the latest RTEMS head on my collection > of Raspberry Pi models. > The last time I tried to run RTEMS on a Pi, I had trouble with the > current version of the Raspberry Pi F

Raspberry Pi test report

I finally found the time to try the latest RTEMS head on my collection of Raspberry Pi models. The last time I tried to run RTEMS on a Pi, I had trouble with the current version of the Raspberry Pi Firmware, so I had to go back to a specific tag on the Rasberry Pi firmware repository to get RTEMS t