Incompatible with newest Raspberry Pi 4 Model B - 2 GB

[sftsk]

Hello, thank you so much for creating all of this!

Just wanted to finally give it a try and purchased a new Raspberry Pi. Unfortunately it won't boot with any of the images from the last release (Beta 6).

It displays this error when trying to boot:

start4.elf: is not compatible
This board requires newer software
Get the latest software from ...

Any idea what I could do? Are there any plans for releasing a new version/ beta soon?

[chiefwigms]

Duplicate to #331 - much of the reason for the image was to setup a wifi AP for the pi so that non-Z/Zymatic's could connect to it wirelessly. You could try to downgrade the firmware and flash, but I haven't tried (and don't really have much time)...

[tmack8001]

@sftsk thanks for flagging. I'm not sure if the issue reported earlier about building with pi-gen is the problem here or not. Though that said that isn't a great experience and we do intend for any RaspberryPi that has the right hardware (wireless) to be supported option in addition to any custom setup with custom configuration and DNS servers local resolving the right server info.

I'll see what I can do this week as I have a bit of time to dig in further from what has been investigated so far.

[tmack8001]

Interesting that we may be able to get away with the prior sha of pi-gen and simply do another sudo apt update && sudo apt upgrade prior to finishing the image to update to the latest OS that would contain the latest firmware for the inhouse built chips that RaspberryPi organization is starting to use for newer boards (similar to the Pi400 model).

[tmack8001]

In the background today (effectively using my MacBook as a small heat exchanger in the office) I'm building a fresh image for testing @sftsk . When finished I will upload it and share a link with you to verify if it works for this new board you have. If so I can go ahead and make the other images to publish a beta7 release (been almost a year since our last) this would also make first boot faster as there wouldn't be a year of git file change to pull onto the file system over the network.

Stay tuned will take some time to build.

[sftsk]

Hello @tmack8001, thanks a lot for working on this so swiftly. Will give the new image a try as soon as I get the link :)

[tmack8001]

@sftsk go ahead and try the image I created https://drive.google.com/file/d/1G7OWGLi3kExJuEVktNH-i3WvmqDDng3d/view?usp=sharing

Unfortunately, I failed to update the image name so when viewing the http://raspberry/about page it will still self identify as beta6 😜 . Let me know if this fixes the issues you were seeing or get another error message, unfortunately I don't have a newer board to test with (same errors likely to be seen on a Pi Zero 2 board).

[sftsk]

I managed to boot! All seems to be working so far (it is creating the PICOBREW) wifi, will let you know if I run into any trouble.

Amazing work 👏

[tmack8001]

The image I built for you @sftsk also has the appropriate packages for HDMI (desktop X11 and LXDE interfaces). Feel free to attach a monitor if you feel like it 🤪, was the image variant I last built so just issued a rebuild of it pulling in the latest firmware and rasbian release (Bullseye) into the image.

[sftsk]

Got it hooked up to a monitor and just playing around with everything 😄

[tmack8001]

@sftsk any issues arise today in setting things up?

[sftsk]

The setup seemed to work although my PicoBrew Z complained about not having access to the internet when connecting to the Pi every now and then. Could be that my wifi was overpowering the Pi wifi but will have to look into it with more time. Will let you know when I have hopefully managed to run a brew!

[chiefwigms]

The setup seemed to work although my PicoBrew Z complained about not having access to the internet when connecting to the Pi every now and then. Could be that my wifi was overpowering the Pi wifi but will have to look into it with more time. Will let you know when I have hopefully managed to run a brew!

I highly recommend using Ethernet with the z/zymatic!

[sftsk]

@chiefwigms will that "just" work? does the Pi connect to the Z Series via Ethernet and share everything necessary?

[chiefwigms]

@chiefwigms will that "just" work? does the Pi connect to the Z Series via Ethernet and share everything necessary?

Yep!

[tmack8001]

@sftsk what likely is happening there is your network the Pi is attached to is switching over to 5.0ghz and effectively knocking the Picobrew device off since it only supports 2.4ghz and not the higher frequency. Since the Pi has a single WiFi interface that we overload for dual purposes to act as both an access point and as a client (connecting to your wifi simply for exposure and updates, it isn't needed BTW).

How did you configure WiFi? Edit the wpa_supplicant.conf file or via the UI?

[sftsk]

I had it set up through wpa_supplicant.conf & also added the bssid in there.

I have now used an ethernet cable and so far the connection seems stable. Will hopefully brew on Friday or the weekend.

[tmack8001]

Hrm, what is your local wifi hardware? There are a few I know about that get around the BSSID somehow... Not really sure as to the details as how or why they do, but somehow they do.

[sftsk]

I have this https://amplifi.com/alien mesh system. Every base station has their own individual bssid for 2.5ghz & 5ghz. Anyway with the ethernet cable the connection is stable, it stayed connected through the night.

[tmack8001]

Looking at the documentation this "band steering" enabled by default. This is what other mesh systems have and when disabled will prevent the Pi from jumping/steering from the 2.4ghz network signal up to the undesired (but device supported/capable) 5ghz signal.

https://help.amplifi.com/hc/en-us/articles/219132457-Configuring-Band-and-Router-Steering

Typically in a network setup this is helpful as to not congest the lower frequency (less bandwidth). Though in this case the Pi is capable of both, though the client of the Pi is not (Picobrew hardware. Since we are using the wifi of the Pi in "dual mode", both as a client and server/access point it doesn't know how to communicate to the upstream connection what capabilities its own clients have and support. Not sure what the router/access points do specifically to band steer, but from investigating with others some can get around an explicit bssid configuration and others can't.

[tmack8001]

Also not unique to us... Several postings in raspberrypi forums about this "seemingly odd " behavior where our explicit channel limitation and use of bssid gets overridden during the AP broadcast and connection establishment requests.

https://forums.raspberrypi.com/viewtopic.php?t=261222

[sftsk]

Looking good so far, wish me luck :)

Thanks @tmack8001 for all your help. I will stick with ethernet as I haven't encountered any problem with it. Will give a final confirmation when the brew is done but I think you can close this issue/ release the new image.

[sftsk]

Brew is done and all went without issues 👏

[tmack8001]

Ok thanks for confirming your session went flawlessly. I won't mark a release yet as I want to get more wireless interface testing performed first.

Though same time I think this buster release simply with new firmware and software pulled is likely not to pose any problems there. The later bullseye release (latest Raspbian OS) will be blocked on further testing due to some changes in the image creation software we use. I think I might have resolved that with a slight package modification yesterday as well 😉🤔.

[tmack8001]

Beta8 is what will fix this issue. Have had one test user state there is an issue with the WiFi stuff will be debugging and fixing that this week.

[kennethN-Pico]

@tmack8001 apologies if I am missing this information elsewhere. I also get the message as per the top of this thread. Would it be possible for me to download a later than beta 6 version that I can try please? Please point me in the right direction.

start4.elf: is not compatible This board requires newer software Get the latest software from ...

[alearnedape]

Is Beta8 available for download? Pi's have finally come down in price and I got one but am facing the same issue. Any help greatly appreciated!

@tmack8001 apologies if I am missing this information elsewhere. I also get the message as per the top of this thread. Would it be possible for me to download a later than beta 6 version that I can try please? Please point me in the right direction.

start4.elf: is not compatible This board requires newer software Get the latest software from ...

[tmack8001]

I finally have been able to get my hands on a new board to test with this next week.

I'm almost certain a new Raspbian OS install will work fine, but given the test image I earlier provided still had issues I want to do some testing myself before releasing again to folks.

Sorry for the delays as it has been hard to get my hands on an updated board myself given every time I go check inventories after receiving an alert sites are sold out or not available to my user. Local hardware and tinkering stores have been sold out or have otherwise dropped inventory around me too. Did pop into a store pop up RaspberryPi Foundation store... but didn't want to wait around the entire mall so simply left. Some folks started standing in line the night before!?! Insane.

[kennethN-Pico]

Thanks so much Trevor.

From: Trevor Mack @.> Sent: Saturday, August 12, 2023 8:17 PM To: chiefwigms/picobrew_pico @.> Cc: kennethN-Pico @.>; Comment @.> Subject: Re: [chiefwigms/picobrew_pico] Incompatible with newest Raspberry Pi 4 Model B - 2 GB (Issue #334)

I finally have been able to get my hands on a new board to test with this next week.

I'm almost certain a new Raspbian OS install will work fine, but given the test image I earlier provided still had issues I want to do some testing myself before releasing again to folks.

Sorry for the delays as it has been hard to get my hands on an updated board myself given every time I go check inventories after receiving an alert sites are sold out or not available to my user. Local hardware and tinkering stores have been sold out or have otherwise dropped inventory around me too. Did pop into a store pop up RaspberryPi Foundation store... but didn't want to wait around the entire mall so simply left. Some folks started standing in line the night before!?! Insane.

- Reply to this email directly, view it on GitHubhttps://github.com/chiefwigms/picobrew_pico/issues/334#issuecomment-1676039518, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASJ2FKQ3ZDP6EMM54CUSWM3XU7CC7ANCNFSM5QTVTPGA. You are receiving this because you commented.Message ID: @.**@.>>

[tmack8001]

I will be uploading rest images to this drive folder - https://drive.google.com/drive/folders/1pxt0ivVPzOXRseO6Lk39lHK9z2dJJBu3?usp=drive_link

There is a "lite" image (beta6 - forgot to change the name) there now, more are building right now that I'll need to process and upload.

[kennethN-Pico]

Hi Trevor, I have managed to boot up on the "lite" image referenced above. The PICOBREW SSID is also visible. That is all I can test right now. Will update you once I fire up my Pico S and connect.

[tmack8001]

OK good. I realized I didn't get a large enough sd card for use as a dedicated raspberry pi image building device so waiting on getting a new larger sized one for that before I can build the larger images for the desktop experience which is a bit more user friendly if using a monitor vs a headless server install.

With the desktop experience I also found a way to automatically start chromium pointed to the raspberry pi server to open in full screen (similar to TiltPi and other RPi based products do)

[tmack8001]

Another user on Facebook is stating that they were able to successfully boot up with the "latest-lite" image build I pushed today, though can't get their Z to see recipes from the Pi server and when connecting to their home WiFi doesn't provide the Pi with an IP address.

[tmack8001]

Same user after a bit of debugging has been able to connect a Z to the newly built Pi 4 (new broadcom board) and pull recipes to start a brew day. The Ethernet as well as upstream WiFi association for them doesn't work though so that is another thing to investigate.

[kennethN-Pico]

My Pico S is connecting to the PICOBREW AP no problem. The Pi 4 is also connected to my home network no problem. I have imported a couple of recipes into the Pi library. However, the Pico S does not see the recipes. Still the standard menu options on the Pico S.

Edit: I rebooted things a few times and now it seems good.

[tmack8001]

For the smaller machines (c/s/pro) you need to tell it you are brewing a PicoPak and then continue past the error message and it will ask which recipe you are brewing.

These machine types were never intended to be used without PicoPaks except for the manual brew option Picobrew built, so we are hacking around the interaction of a PicoPak with a malformed or misconfigured RFID which can't be read.

Is this the process you tried?

[kennethN-Pico]

Yes, that is how I eventually got there.

Thank you so much for this amazing solution!

[tmack8001]

@kennethN-Pico if there is something that could be improved in the documentation for new users let us know.

I'll be making this image an official release soon, I just received a new larger SD card to be able to use for the HDMI enabled images (built on top of "full" RaspbianOS) and will be transferring my build environment over to that in the coming days.

[rompstar]

this is great / just install on Pi 4 Model B / from your Google Drive, works!