Raspberry Pi 400
Chris Johns (8262) 242 posts |
It’s the Master Compact of 2020 |
Rob Andrews (112) 164 posts |
The only thing missing is a ssd interface on the board still have to hang it off the usb |
Clive Semmens (2335) 3276 posts |
That’s not too bad with USB3 – when RISCOS can do that. |
Rob Andrews (112) 164 posts |
Thats great but it would have been a much better machine if it had a slot to pop in an SSD or MVME drive even if it was connected via USB hub |
James Pankhurst (8374) 126 posts |
I still remember, not necessarily fondly, the old “Dongle Dangler”, a 25pin parallel to parallel connector with ribbon cable for attaching protection devices. |
Chris Gransden (337) 1207 posts |
I just tried booting RISC OS on a Rpi 400. It hangs at ‘InitSDIODriver’. |
Chris Gransden (337) 1207 posts |
Unplugging SDIODriver gets past it. This message posted using a Rpi 400 running RISC OS. |
Chris Gransden (337) 1207 posts |
Running stable at 2.2 GHz. Idle temperature is 34C according to CPUClock.
|
Steve Pampling (1551) 8172 posts |
Got it! – call it “Home” because… …“wherever I lay my Hat that’s my home” (OK, I’ll get my coat, eventually) |
Steve Pampling (1551) 8172 posts |
Slightly less fixing than I expected. That a full RO Direct install? |
Chris Hall (132) 3559 posts |
I think that the Rpi 400 is based on the CM4 and the specific revision number (which identifies the Pi model number and revision) is used by the RISC OS HAL to determine the memory layout of the GPIO system and other things. As the CM4 came out after 5.28 was frozen, it has not yet been catered for. The Pi 400 came out after 5.28 had been released. In other words the list of revision numbers known to RISC OS, to decide where in memory certain things are, which are hardware dependent, does not yet include the Compute Module 4 or the Pi 400. SDIO, presumably, is one of the things affected. GPIO may not work either? An update to HAL_BCM2835 will no doubt appear in due course. The revision codes on the Pi Foundation site have not yet been fully updated to include CM4. The utility !ScreenHelp will display the revision code of a Pi. It can be inferred that CM4 and Pi 400 have codes of the form (where the final number, 1, is the assumed revision number):
whether the revision number differs between those fitted with wireless and those fitted with eMMc storage remains to be seen, the CM3 did not distinguish between eMMc fitted or not. |
Chris Gransden (337) 1207 posts |
The revision code of the Pi 400 is C03130 according to the bootloader splash screen. |
Chris Gransden (337) 1207 posts |
Looks like the thermal problems are completely solved. The highest temperature under load so far is about 40C. |
Chris Hall (132) 3559 posts |
Is it firmware changes that have solved it or a different physical layout of the Pi 400 board? |
Jay (408) 34 posts |
Hi Chris, I am just getting nothing at boot, just a black screen and flashing cursor, how do you bypass this? Thanks. |
Rick Murray (539) 13851 posts |
Wasn’t that a three box design (keyboard, boxy bit, monitor), with the bit at the back just holding floppies? Yeah… I’m sure it’s the same box they put the FileStore into.
Have you watched any of the teardown videos on YouTube? The weight of the device is a bloody big metal heatsink.
AIM – for Accident In the Making. |
Chris Gransden (337) 1207 posts |
Try updating to the latest fixup4/dat and start4/elf. https://github.com/raspberrypi/firmware/raw/master/boot/start4.elf |
Chris Gransden (337) 1207 posts |
There’s a new CPU revision ‘C0’ and the heat sink is about the size of the keyboard. |
Jay (408) 34 posts |
Yeah, not working unfortunately even with those updated firmware files. :( nevermind. |
David Pitt (3386) 1248 posts |
Finally!!!!!! Hello from RISC OS on the Raspberry Pi 400. Unplugging SDIODriver does allow RISC OS to start but with the slight disadvantage that the SD drive icon is not there. Long story short, I have two USB sticks on the case one FAT32 with the firmware and the other as SCSI with RISC OS, having failed to make a partioned USB drive. Boot from USB is enabled by default. (The rear USB sockets are too close together for the rather portly pens I have.) |
Chris Gransden (337) 1207 posts |
Also make sure you are booting from USB. |
Jay (408) 34 posts |
Just writing to a USB drive now, thanks for the tips. |
Chris Evans (457) 1614 posts |
We initially tried 5.28 and had the same problem as Jay, updating just the firmware didn’t fix it but adding the latest 5.29 ROM did. So it seems you need 5.29 (latest?) and latest firmware inc. start4.elf and fixup4.dat |
David Pitt (3386) 1248 posts |
OS5.28 is working here with this firmware. bootcode.bin 15Oct20 fixup.dat 29Oct20 fixup4.dat 29Oct20 start.elf 29Oct20 start4.elf 29Oct20 Booting from a Fat32FS USB pen, and with SDIODriver unplugged. |
Jay (408) 34 posts |
Newbie question, how do you unplug SDIODriver? |