The Industrial Raspberry Pi Forum

Hi
im trying to start a connect se, but i cannot access the cockpit.

I have connection through ssh

i have tried flashing with a new image of bookworm 8/2025 (twice)

i have flashed it with an older image of bookworm (5/2025 ?)

all i get is a loading screen that seems to refresh
any suggestions are much appreciated

i have tried a lot of different things, since i wrote this post and now i have a working unit

I flashed the rev pi with bullseye, which resulted in no IP-connection, so i flashed it again with bookworm.

this resulted in it , as with bullseye, it did not get an IP, so i did this:

Step 1: Access the RevPi storage via rpiboot

Power off the RevPi Connect SE by disconnecting its power supply.

Connect your Windows PC to the micro-USB service port on the RevPi.

Launch the rpiboot.exe tool on your Windows PC.

Reconnect the power supply to the RevPi. Its eMMC storage will appear as a removable drive in Windows File Explorer.

Step 2: Edit cmdline.txt to add a static IP

Navigate to the boot partition of the newly mounted drive and open the firmware folder.

Right-click cmdline.txt and select Edit with Notepad++.

Add the ip parameter to the end of the single line in the file. The format is ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>.

For example, to set a static IP of 192.168.1.200 on the eth0 interface with a gateway of 192.168.1.1 and a subnet mask of 255.255.255.0, the entry would look like this: ip=192.168.1.200::192.168.1.1:255.255.255.0:revpi:eth0:off

and connectet (ssh) again to the new IP.

Then the rev pi prompted for serial number (found on the front of the device) and the physical adress (MAC, also found on the front)

After this everything is working and i can now (after struggling with this for way to many workdays) continue and hjopefully get a result before my deadline

Hi kbt. First it's great you got it working!

Since we only support the current and the last version of debian we're currently on with our images and packages (currently on bookworm, so we're still supporting bullseye), it's recommended you stick to bookworm. We will most likely be upgrading to trixie in the foreseeable future, at which point bullseye will be outdated and unsupported and will not receive any more updates from our side.

It's odd that you didn't receive an IP address when starting your RevPi. This is not a behaviour we have seen on our side yet. NetworkManager should broadcast DHCP requests on the network, so if the network is running a DHCP server an IP address should be offered by the DHCP server for the RevPi to use. Can you think of a reason why this didn't happen for you? The NetworkManager logs should be helpful here and can be viewed with the command "sudo journalctl -u NetworkManager". Look for lines containing "dhcp"; it should show that it is trying to get at least an IPv4 address with DHCP.

Thanks for the feedback!