hi, just got r_e_c_u_r built and running on a new rpi 3b+ (same gen that gives people trouble with vserpi images). it took some rounds of troubleshooting to get it going, so i thought i’d share what worked.
-
flashed the most recent image with balena and tried to boot up. got a failure to boot, with no display and the 4-7 flashing light pattern.
-
noticed the post/discussions about waaave pool not running on some newer rpi 3b+. Followed the “updating firmware only” section of https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003476-WP/Updating-Pi-firmware.pdf to replace the four .elf files and corresponding fixup.dat files in the boot partition with updated ones.
-
booted up! got a splash screen and some action on the hdmi display, but the lcd screen (waveshare 3.5(A)) stayed blank white, and eventually nothing else happened.
-
i randomly didn’t have a lot of useful things around to solve the problem where i was working (ethernet cable, usb keyboard/mouse, haha). so i tried re-flashing the sd card using the raspbian imager with the r_e_c_u_r image as the source. i thought i could try to add some wifi configs in and try to ssh over the network (now sort of understand why that didn’t end up working).
-
back to flashing lights and no boots. i had to re-update the 2019 firmware provided in the r_e_c_u_r image
-
booted up, with multiple errors related to a missing systemd target caused by the commandline.txt edits inserted by imager failing to run. but weirdly, all those errors displayed on the now-working lcd screen. once it had finished failing to run systemd scripts, it fell back to safe mode… and booted up a fulling working r_e_c_u_r, with both screens working as expected.
-
I went back and deleted the systemd calls that had been added by Imager from boot/commandline.txt, and now everything boots normally, no errors.
Not sure how the LCD screen got ironed out by my failed attempt at wifi configuration; wish I could be more conclusive. I can only guess that the firstrun.sh script that imager ran fixed up some other driver or file for the display. Anyway, if anyone runs into this, maybe this will get you going.