Pi 5 Module for G2
Re: Pi 5 Module for G2
Everything is working great now even the dedicated NIC. When using the dedicated NIC absolutely no difference in network/ radio / Thetis performance. Jerrys monitoring app proves it. It was a must with my 7000 to utilize the dedicated NIC to run Thetis without VAC overflows. CMASIO also needed the dedicated NIC to limit audio artifacts. With the G2 and p2app no issues at all simply placing the G2 on your network, and as a bonus you have Ethernet connectivity with your pi OS in lieu of wireless.
Vin KD1GA
Re: Pi 5 Module for G2
This is the difference between the extremely mature and proven Linux network protocol stack vs. the very primitive protocol stack in the legacy openHPSDR FPGA firmware.
What is this "Jerry's monitoring app" you write about?
What is this "Jerry's monitoring app" you write about?
Re: Pi 5 Module for G2
You are absolutely correct. The protocol 2 firmwar for the 7000 series was definitely lacking and never officially supported as you know. The P2 app firmware for the G2 is rock solid and really a pleasure to deal with Jerry‘s monitoring app is simply an app that he added to his image, it monitors network activity Processor, load and ram usage really pretty cool.
Vin KD1GA
-
ianferrell
- Posts: 1
- Joined: Sun Aug 31, 2025 4:32 pm
Re: Pi 5 Module for G2
I've just upgraded my G2 Ultra w/ an official raspberry pi CM5 4gb w/ 32gb of MMC. First note that I would recomend using a lite and sticking to just using an sd card. I got it to work, it boots really fast but dealing w/ the microusb port was annoying. I've got the XDMA driver working and I can run thetis.
Second is a question, has anyone got the 8" display built into the g2 ultra to work with bookworm and the official pi cm5? What's the config.txt need to be? I found https://github.com/ramdor/G2Tools but the G2U8 config doesn't find the display at all. If I add ,dsi0 then I see dmesg logs indicating something is going on and the backlight comes on but doesn't show anything. I maybe confused and actually have a hardware issue, but I'd like some confirmation of what display config actually should work a CM5 in a G2 8" running bookworm.
Edit: just tried booting again with device_tree=bcm2712-rpi-cm5-cm4io.dtb in config.txt and it once again won't boot and says "os not compatible with CM5" ... " bcm2712-rpi-cm5-cm4io.dtb not found" I checked that it was in the /boot folder first as I've been down this path before, and had to then take the lid off again and the audio board and then plug in a microusb cable.
Last time I fixed that I spent a few hours first getting the thing to network boot but apparently the installer images won't really boot like that... was just hoping to be able to mount the boot partition and edit the config.txt file back without taking the radio back apart, but being non-UEFI makes just booting these things so weird and frustrating.
Second is a question, has anyone got the 8" display built into the g2 ultra to work with bookworm and the official pi cm5? What's the config.txt need to be? I found https://github.com/ramdor/G2Tools but the G2U8 config doesn't find the display at all. If I add ,dsi0 then I see dmesg logs indicating something is going on and the backlight comes on but doesn't show anything. I maybe confused and actually have a hardware issue, but I'd like some confirmation of what display config actually should work a CM5 in a G2 8" running bookworm.
Edit: just tried booting again with device_tree=bcm2712-rpi-cm5-cm4io.dtb in config.txt and it once again won't boot and says "os not compatible with CM5" ... " bcm2712-rpi-cm5-cm4io.dtb not found" I checked that it was in the /boot folder first as I've been down this path before, and had to then take the lid off again and the audio board and then plug in a microusb cable.
Last time I fixed that I spent a few hours first getting the thing to network boot but apparently the installer images won't really boot like that... was just hoping to be able to mount the boot partition and edit the config.txt file back without taking the radio back apart, but being non-UEFI makes just booting these things so weird and frustrating.