Raspberry Pi 4

EDIT : I see there is an EtherGENET module within the latest beta ROM… It is only 5.6K in size, but the source code for EtherGENET (latest beta source) is also 1/10 the size of the EtherUSB source code. Doing ‘*RMReinit EtherGENET’ returns ‘unsupported hardware configuration’ (from the Rpi3B+).

I believe that that’s a placeholder and isn’t expected to work.

I’ve compiled the RISC OS beta ROM with DDE29b;the version date under ‘info’ is 18th Feb 2020, but the modules are all from April. I also copied the updated files for EtherGENET, which compiled correctly.

I am stuck because I want to set up the EtherGENET in the configuration file, but I have to do it manually as I don’t have access to a suitable USB-C hub (reverse powered or otherwise), and can’t get one due to the covid lockdown.

Can anyone show what they are using in their !Boot.Choices.Internet.Startup file? My file is set up for the Pi 3B+,
and has some lines as follows :
|
| Interface: Ethernet over USB
|
RMEnsure EtherUSB 0.0 ……… . . . . . . . .
IfConfig -e ej0 192.168.2.22 netmask 255.255.0.0
CheckError
Set Inet$EtherTypeA <Inet$EtherType>
|
| Loopback
|
(… file continues)

What would be the equivalent set of lines for a manually configured IP + netmask for EtherGENET? Also is there a way for the Obey file to automatically select and set up either EtherUSB or EtherGENET depending on which module is found? I think that it might just crash when RMEnsure can’t find EtherUSB, preventing the system booting on the Rpi4.

Thank you for your advice; it would be so much easier if I had a USB-C hub, but it will be a minimum of 2-3 weeks before I can get one (the relevant shops are closed)

(Edit – the file described above also has, under hostname, another set of ‘Set’ commands, which set Inet$EtherIPAddr, Inet$EtherIPMask, and also sets Inet$EtherDevice EtherUSB.

I am guessing that at this stage, a card that can boot Ethernet on both the Pi3B+ and Pi4 can’t be easily made; however I guess I may need to have two files and manually select one or the other. I will try to see what happens but would be grateful for more advice on this!)

What would be the equivalent set of lines for a manually configured IP + netmask for EtherGENET?

|
| Interface: Broadcom_GENET
|
RMEnsure EtherGENET 0.01 RMLoad System:Modules.Network.EtherGENET
IfConfig -e ege0 192.168.1.208 netmask 255.255.255.0
CheckError

P.S. Plus the Autosense.EtherGENET file. It is in the build.

BCM2835.RiscOS.Sources.Networking.Ethernet.EtherGENET.AutoSense.EtherGENET

I am guessing that at this stage, a card that can boot Ethernet on both the Pi3B+ and Pi4 can’t be easily made;

No, your guess is wrong.

The Raspberry Pi 4 boots differently from Pi 3 and before: it ignores BOOTCODE.BIN (which on the Pi 3 loads START.ELF) as it has its boot loader on the PCB which loads START4.ELF. The CONFIG file also allows a different ROM image to be loaded by making a Pi4-specific kernel= allocation. The Pi4-specific ROM can use the USB OTG power socket for USB and Internet.

See here

The EtherGENET module is waiting to be merged. It is looking good so far.

Anyway I can get the sources to the working EtherGENET? I can’t see how to get the sources from the ROOL repository.

Anyway I can get the sources to the working EtherGENET? I can’t see how to get the sources from the ROOL repository.

Briefly:

• Use git to clone the original version of the component
• View the merge request in a web browser, and use the download button (next to “check out branch”) to download the “email patches”
• Use “git apply foo.patch” to apply the patch file (foo.patch) to your local copy of the component

The above steps will cope with situations where the merge request is coming from a private repository (if it was a public repo you could just clone it and check out the branch), and changes to binary files (the “plain diff” download option only includes the changes to text files)

I can’t see how to get the sources from the ROOL repository.

Neither can I see how to using git. All I did was to download the new files individually, rename them as required and manually place them in the build. In this case there are 15 files but it does not take long. And it worked, which is always encouraging.

This is the merge request. Click on Changes to see diffs of all the changed files. Click on the ‘View file’ button on the right then click on the ‘Download’ button on the right. Step down the files and repeat 14 times.

I hope this answer is not too disappointing with its complete lack of expertise.

Thanks David, that did the trick.

Use “git apply foo.patch”

I did try git apply before my initial post but it failed – probably user error I downloaded the ‘Plain diff’ and used that, don’t know if ‘email patches’ are different.

Anyway the pi4 works hires usb audio – my b+ doesn’t – but streaming high res over the network is still a problem even with the new ethernet driver. Looking forward to see how isochronous works on the xhci driver when it arrives.

Use “git apply foo.patch”

This is on a Mac BTW.

I have just got that to work. Obviously one needs to navigate to the EtherGENET folder to apply the patch!!

imac@iMacPro Ethernet % cd ethergenet
imac@iMacPro ethergenet % git apply 1.patch
1.patch:1619: trailing whitespace.
	sc->sc_tx.cidx = RD4(sc, GENET_TX_DMA_CONS_INDEX(qid)); 
1.patch:1631: trailing whitespace.
	sc->sc_rx.cidx = RD4(sc, GENET_RX_DMA_PROD_INDEX(qid)); 
1.patch:1763: trailing whitespace.
		case 0:  /* Pass errors */ 
1.patch:1923: trailing whitespace.
		if (nicunit[unit]->ctrl->running) 
1.patch:2082: trailing whitespace.
	nicunit[unit]->filters = NULL; 
warning: squelched 9 whitespace errors
warning: 14 lines add whitespace errors.
imac@iMacPro ethergenet % 

It should be possible to handle, or suppress, white space errors, but that might take me a bit longer!!

Anyway the new and modified files did appear in the source.

The ROM was built and it works!!

Thanks that’s good to know for future reference. It turned out that 1.diff from the ‘Plain diff’ option doesn’t work but 1.patch from the ‘Email patches’ option – which also just saves and doesn’t email anything – works. Who knew that plumping for 1 of 2 options would result in picking the wrong one.

*Configure EGELink 0 Auto
*Configure EGEAdvertise 0 10 Half Full 100 Half Full 1000
*Configure EGEFlowControl 0 Full

Something goes wrong with my settings.
Have try this and *Status tells me is ok.
Perform SaveCMOS… Restart my system … falls back to the old settigs. LoadCMOS… the new settings are inside.
Copy the new CMOS to the SDCard… Restart… falls back…
All I try falls back to the very slow old settings.
I’m not use a GB Network, only 100MB/s. All the other e.g. Ti are connected with this in full duplex. WiFi-HAT with 54MB/s.

I had no problems. After I configured the module I just used shutdown and clicked on restart. Can you change other configuration options? – it may be an sd card problem.

If I check the CMOS date on my card it is changed. New date, new time but it looks like it will not be loaded.
Is my Pi3B+ card. Have changed the needed files in Loader, update !Boot and add the autosense part …
Other changes needed? Entrys in config.txt?
Many thanks.

config/txt should have a couple of ‘ramfs’ lines pointing to the CMOS file. I don’t have my Pi handy at the moment so I can’t say exactly what they should say.

config/txt should have a couple of ‘ramfs’ lines pointing to the CMOS file.

# New lines for separate CMOS file
ramfsfile=CMOS
ramfsaddr=0x508000
#

Some possibilities:

1. You have two CMOS files on your SD card (SDFS:$.!Boot.Loader.CMOS and SDFS:$.CMOS).
   Solution: Rename $.CMOS (e.g. to CMOS-copy) and restart with Ctrl-Break.
2. Due to delayed writes, the update of the CMOS file didn’t happen before the restart.
   Solution: Double-dismount the SD card before restarting.

Thanks for the information.
Have take a look to config/txt before I go to work.
ramfsfile=CMOS I have seen,
ramfsaddr=0×508000 is not inside, I’m sure.
Will try if I back at home.

Edit: Is working now. Was like I wrote but not sure why the second line was lost.
Thanks a lot.

For the people who get the ROM working (EtherGENET or otherwise), what is the date on the Switcher ‘Info’ box? Mine is Feb 2020 and just checking that is correct (as the modules are mainly from April!)

My ethernet on the Pi4 works without the file EtherGENet.

Mine is Feb 2020

Mine shows 28-Apr-20

My ROM says May 2020 now – it was because I don’t have an RTC on my Pi, so it showed Feb 2020 on my build. My current Pi4 config is as follows:

RPi4, 4GB;
– eeprom updated today with Raspbian (it wasn’t out of date (Sep 2019 eeprom)
– latest fixup4.dat and start4.elf files, from RPi github (updated on their github yesterday)
– CMOS file from Pi3B+, or ‘no CMOS’ file (tried both)
– only power + HDMI connected.

The end result is that it continues to get ‘stuck’ where it says ‘init mod SDIODriver’, with the cursor stuck after the ‘r’ of driver. I can’t use a keyboard or mouse due to no back-powered USB-C port (I borrowed one from a friend but it doesn’t have the back-power feature).

Has anyone got stuck at this point previously when trying RISCOS on the RPi4? I know it isn’t supported but I am so close to getting a VNC RPi4 and would really appreciate more RAM, fast Ethernet + CPU (for better VNC and for some mathematical ‘hobby’ programming I am doing) – Thank you for any advice :)

Todays Rpi beta ROM should include the new etherGENET module so you could try that to see if that works.

If you have set up the sdcard on another raspberry pi you will need to change the cmos with

*Configure EGELink 0 Auto
*Configure EGEAdvertise 0 10 Half Full 100 Half Full 1000
*Configure EGEFlowControl 0 Full

before using the pi4 as otherwise the networking won’t work and as you don’t have a keyboard you can’t change it on the pi4. There may be other problems if you have set up the card to use etherusb

You can power the pi from the gpio ports then plug a normal hub in the usbc socket – thats what I do.

Edit: It occurs to me that you won’t have those configuration options on another pi as the EtherGENET module won’t initialise.

Thank you! Am downloading the beta disc image and beta ROM right now – will see if it works. I think I will power the RPi from the GPIO pins if I can get to a stage where it boots and ‘needs a keyboard’ – as the version I compiled hangs during early initialisation still!

Try Pi4cmos.zip

It contains the files from my !Boot.loader directory – the riscos module has a modified USB module but that shouldn’t matter to you.

It also contains the !boot.choices.internet folder which sets up the internet and a file in !boot.choices.boot.Tasks which sets up pi4Ram and Pi4Disc shares.

That should get you to the point where you can modify it from another machine.

Should work – though it is untested.

Edit i forgot the InetSetup.AutoSense.EtherGENET
file – now included.

Note that the EtherGENET CMOS code was tweaked so that the default CMOS values should be sensible – so you’ll probably only need to manually configure it if you’ve previously used (and reconfigured) the earlier version from the merge request which had the bad defaults.