revpi core S : piCtory & all apps loss after a bookworm update

[LXNM]

Hello,

In order to use codesys on my revpiCore S, I had to upgrade the revpi image with bookworm 64bits default (05-2025).

I found the tutorials very clear & useful, but after rebooting the PLC, I didn't found piCtory or any other app on the GUI. I tried a factory-reset from the terminal, I also I threw a bottle into the sea with revpi-sos message...

Is this problem occured to anybody? Any tips that will help me move forward will be welcome.

Thank you for reading this desperate message

Have a nice day.

Alex

[Matii]

Hi LXNM,

Would you please share the update steps with me.

I failed at the step: RPIBOOT, usb cable connection and recognize it as a USB Disk.

Thanks a lot.

Matii

[LXNM]

Hi Matii,

theses are the steps for rebooting I used with my revpi core S:
1/the plc must be powered off and unplugged from the elec socket
2/start rpi boot, it must display a command like "waiting for bcm..."
3/ then, you can power on your revpi and see the screen with rpi boot shows a detection message.
4/ if windows suggest you to format your device, answer NO (any time it suggest you to do that)

For the topic about the loss of apps after a debian update toward bookworm, pictory was available via webserver...

I think I can close the subject.

Have a nice day Matii

[RamiGspo]

Hi Alex,
Thanks a lot for sharing your experience — it’s great to see the community helping each other out.

Regarding your issue, Alex:
After flashing a new image, the system is reset to a clean state — this means custom configurations and applications are not automatically preserved unless you saved and restored your configuration beforehand.

To avoid this in the future, we strongly recommend saving your image before flashing.
Here's how:
https://revolutionpi.com/documentation/ ... -the-image

If no backup was done, the configuration and software need to be manually reinstalled or reconfigured.

Once you’ve flashed the device, you can set things up again using Cockpit, the management interface.
🛠 Here’s the Cockpit documentation:
https://revolutionpi.com/documentation/cockpit/

From Cockpit, you’ll also find access to piCtory:
https://revolutionpi.com/documentation/pictory/

---

Now you Matii

If you're having trouble with the RPiBoot step and getting your device recognized as a USB disk, here’s a couple of things to check:

The full steps for flashing a Revolution Pi device under Windows are documented here:
https://revolutionpi.com/documentation/ ... -the-image

Important: Make sure you're using the latest version of RPiBoot.
Older versions do not support newer RevPi models (like the RevPi Connect 5), which can lead to detection issues during the flashing process.

Also, just to recap from your earlier message and Alex’s helpful reply, please make sure to follow this exact connection order:
- Disconnect the RevPi from power supply.
- Connect the mini-USB cable to your RevPi and Computer first!
- Then connect the RevPi to the power supply.

After this, you should be able to run RPiBoot successfully.

If you power the device before connecting the USB cable, RPiBoot will not detect the device properly.

After flashing, make sure to do the following:
- Disconnect the power supply from the RevPi.
- Disconnect the mini-USB cable from the RevPi.
- Reconnect the power supply to the RevPi.

Let us know if you need help with any specific step.

Best regards,

RamiGspo

[LXNM]

Thank you so much RamiGspo for answering,

I was really happy to answer Matii, because I think it's really important to share knowledge in an era of "open-source-but-not-so-easy-to-find" tips.

I'm not a buff in software like debian (I usually work with industrials IDE (unitronics, schneider electric...)). Nevertheless I wanted to give a chance to another solution, considering the kunbus wesite's industrial stories.

Thank you for confirming my decision to purchase a kunbus product

@Matii: good luck in your learning path.

Best regards.

Alex