Raspberry Pi 4

I’m running Chris Hall’s test ROM image and have encountered what I believe to be a significant problem – I wonder whether anyone else can confirm this.

If I do a ‘find’ from the filer menu, the process hangs as soon as it finds a match. I presume that the issue is the same as that which prevents ObjAsm from running – as soon as it finds a matching ‘GET’, the process hangs. This is my real problem – I’m trying to reconstruct my lpr driver module.

It is NOT my test rom, it is Sprow’s. Please repeat the test using RC16 (which on the Pi 4 would require power to be supplied to the GPIO pins and a USB hub connected to the OTG socket (the power socket) for USB). The test rom has some modules which are older than RC16 and has a breakpoint (which would cause an AODT without a JTAG device). It is only intended for testing USB on the Pi 4. Be patient, a daily beta rom will soon be available.

It is NOT my test rom, it is Sprow’s.

Yes, sorry – my bad. I scrolled up the page and saw Sprow’s reference to you testing the ROM!

Please repeat the test using RC16 (which on the Pi 4 would require power to be supplied to the GPIO pins and a USB hub connected to the OTG socket (the power socket) for USB).

I’m not in a position to do that – I don’t have the necessary hub which is why I waited for the ROM with the new USB driver.

The test rom has some modules which are older than RC16 and has a breakpoint (which would cause an AODT without a JTAG device). It is only intended for testing USB on the Pi 4. Be patient, a daily beta rom will soon be available.

I suspect that the breakpoint is affecting dismounts in Sunfish, which report an AODT.

Director (provided in RC16) also does not work with the test rom,

I have updated my site to show changes from the Pi RISC OS 5.24 image to the Pi RC16 image here and the changes to the rom here with links to the source which explains the change – hope this helps.

Director (provided in RC16) also does not work with the test rom

Director looks to be OK here with my XHCI and USB3 aware ROM build which is based on a source code archive of 29Aug20, with only the HAL_BCM2835 and XHCIDriver updates, and no breakpoints. I have yet to see any issue.

Is the JTAG breakpoint a significant issue?

P.S. Just tried Director against sprow’s ROM and it seems OK, starts up, menus work …

I’m running Chris Hall’s test ROM image and have encountered what I believe to be a significant problem – I wonder whether anyone else can confirm this.

If I do a ‘find’ from the filer menu, the process hangs as soon as it finds a match.

I have tried sprow’s ROM here and Find worked as expected.

I suspect that the breakpoint is affecting dismounts in Sunfish, which report an AODT.

Sunfish’s frontend is renowned for AODTs.

I think I read somewhere that the USB Test ROM was only provided to test the functionality of the Pi 4 USB ports and that every thing else could be uncompleted development. Do we need to be careful what we are testing?

Just tried Director against sprow’s ROM and it seems OF, starts up, menues work …

Yes, here too – I haven’t been able to identify an issue with Director

Has anyone fixed the SDIO driver glitch? I have a photo but uploads can’t
Be done here, but it says init mod DisplayManager, then several more, then init mod SCSIFiler then init mod SDIODriver, then the cursor blinks permanently after the ‘r’ of Driver?

This is with RC16 and the custom USB test rom; using a RPi4 4GB which is an early model but updated firmware etc around June…

I don’t have this issue with my Pi 4 (4GB), using RC16 disc image plus test rom and updated firmware.

OK; I’ve just tried on my 4GB RPi. Using the RC16 unmodified, and using the ‘pi4xhci’ ROM, both result in the soft hang at mod init SDIODriver_

I updated the firmware via Raspbian32 a month or two ago. I bought the RPi4 4GB the moment it was released! So it may be that there is something ‘odd’ about the hardware that was quietly fixed. I’m going to go and check on this thread to see if the 8GB Pi boots normally. Then go and buy one! The 4GB Pi is fine for 64-bit Linux / AArch64 practice anyway! :) I will post a brief update if it works or fails (the 8GB Pi), then wait until the ‘official’ release. If it works, then my 4GB Pi might be of use to ensure support of even the first batch of Pi 4 4GBs.

What is the best option Pi for the portable PiTop?

What is the best option Pi for the portable PiTop?

Personally I’d go for a Pi 3B+ for the Pi-Top 2 but with a little extra cooling, even though it doesn’t strictly need it.

A Pi 4 can be made to fit in a Pi-Top v1, but it’s not a great keyboard or trackpad. In fact, quite a bit about the Pi-Top v1 isn’t great. Lots of RMAs, especially on batteries and hubs.

The Pi3B+ fits the PiTop and is the fastest of the Pi1-Pi3s. The new form factor of the Pi4B does not fit the PiTop2. Some people have fitted a Pi4B into old PiTop1. My information suggests that the next offering from PiTop will not be a traditional laptop but will work with all Pis and use a separate bluetooth keyboard.
https://www.kickstarter.com/projects/pi-top/pi-top-4-the-new-go-anywhere-do-anything-computer/posts/2815825

I have fitted the Pi4 into the PiTopV1. Also the RTC WFI Hat and use CJEs BattMan. The other PiTop stuff will not work. Looks like the SPI stuff is changed.
Internal speaker I have not try.
If anyone need more information… feel free to ask ;-)

I forget…
Passiv cooling under the hat, pimeroni header extender partial use, USB Surfstick via USB C Y-cable (stick will not work via host). All is wirking very well and it looks like the Pi4 need lees power than the Pi3B+. Accu lives longer.

the next offering from PiTop will not be a traditional laptop but will work with all Pis and use a separate bluetooth keyboard.

Which rules us out. Although this looks interesting: https://nexdock.com/touch/

A bit like the LapDock models of old.

I did sign up for the Kickstarter for the original NexDock, but at the last minute, they changed the spec from USB-connected keyboard to Bluetooth connected, rendering it useless for RISC OS.

I did sign up for the Kickstarter for the original NexDock, but at the last minute, they changed the spec from USB-connected keyboard to Bluetooth connected, rendering it useless for RISC OS.

Do the little USB to Bluetooth adapters not work in that way?

Would the Logitech K400+ not work via the USB?

Excuse me if I’m totally off-course here!

My information suggests that the next offering from PiTop will not be a traditional laptop but will work with all Pis and use a separate bluetooth keyboard.

I already have something similar to this, running PiOS on a Pi4, using a touchscreen from Waveshare. Will PiTop have RISC OS support? In fact, if I could get the touchscreen working in RO (as discussed above), I would be happy.

I have try a PI DSI screen and looks like it works with Thomas Touchscreen driver but I’m not sure if the driver works with other screens.
Looks like the link to his homepage is temporally broken.

Edit: The driver you find here

Looks like the XHCI changes have now been merged so that the 14 Sep 2020 rom should now ‘just work’ on the Pi 4 under the RC16 SD card image.

Have try this morning. Works on my Pi4 4GB PiTop.

Will try the new XHCI ROM; I am using RC16 from 2 days ago – works fine; I used the test ROM briefly to set up VNC.

I managed to get an 8GB filesystem image by using ‘RISC OS Direct’ SD image (8GB),installing it, copying over the RC16, booting on Pi3B+, setting up the RC16 beta HD4 !Boot directory, then adding the XHCI Rom using Mac + SD card, booting, configuring, then putting the ‘normal’ RC16 back.

The issue I had with ‘SDIO’ is that RO absolutely hates these Kingston 16 and 32GB SD cards I got; they work fine on previous PIs, and on Pi4 (4GB early and 8GB one!) using Linux, but with RISC OS they boot up to the activation of the SDIO driver – and it does a soft-hang (flashing cursor) there. I will check this weekend if it still happens with the latest release, because if not, I will need to help searching for bugs – the cards are proper ones bought a while ago. There is a chance this bug may appear when people start testing RISC OS on the RPi4 in a more widespread manner. Thank you for all the hard work getting the RPi4 this far! (and I hope to help one day) :)

RC16 (which is from 14 June 2020) plus the 13 Sep 2020 daily rom now works on the Pi4.

There are still some issues though. If you unplug a USB hub and plug it in to another socket you get an AODT at FC2244FC (+416C in XHCI driver) so there still seems to be a breakpoint in there. After this error the mouse still moves around but the other USB drives vanish and the machine is stiffed, requiring power off/on.

The problem with Director appears to be related to the combination of the XHCI driver and a USB hub into which is plugged a pen drive, SATA drive and wireless keyboard/mouse. With the hub unplugged, Director works fine.