Announcement

Collapse
No announcement yet.

Bricked two SqueezeAMPs - how to recover?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Bricked two SqueezeAMPs - how to recover?

    I bought a couple of SqueezeAMPs some time ago and finally had a use for them. Hooked one up, went through the setup process, and all was well. Got it connected to my media network and went to upgrade the firmware, and had some issues. I ended up downloading a recent firmware (squeezelite-esp32-master-v4.3-SqueezeAmp-16-21234.bin) and seemed to successfully complete an update using the manual upload process via the Brave browser.

    It did not come back from this upgrade. I don't see the device on my wireless network, nor do I see the original setup SSID.

    Like an idiot, I repeated this same process with the other SqueezeAMP I have, and perfectly replicated the problem.

    This one has the red power LED illuminated, and the status LED blinks green twice in rapid succession about every 3 seconds.

    Any ideas for recovery? If it were connecting to the network, I'd be able to poke at it, but as of right now, it seems marooned. I'm not presently equipped to do a serial recovery, but could probably figure that out if someone could point me to documentation.

    #2
    The beauty about that platform is that there are little to no chance of bricking. Do you have a usb to serial adapter? If not, then I suggest you get one as a beginning. This will allow you to connect to the console and get some logs
    LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
    6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!

    Comment


      #3
      I do have a USB to serial adapter. One that's USB-C to rolled/router console. Another that's USB-A to DB9. If neither of those is the right type, happy to go get the right one.

      I assume I need some kind of adapter to connect between the 6 pin header and the serial adapter?

      Comment


        #4
        Originally posted by benh View Post
        I assume I need some kind of adapter to connect between the 6 pin header and the serial adapter?
        That is right. The adapter that I use and the connections that need to be made between adapter and squeezeamp are shown in this post:


        | LMS 8.3.1 on Linux Mint | Squeezebox Boom | RPi0W + pCP 8.2.0 + HiFiBerry DAC Zero | SqueezeAMP | ESP Muse Luxe |

        Comment


          #5
          Originally posted by CJS View Post
          That is right. The adapter that I use and the connections that need to be made between adapter and squeezeamp are shown in this post:

          Note that DTR and RTS aren't an absolute necessity if you can't solder and can't find an adapter where it is already soldered or of the box. To get logs, all you need is VCC, GND, TX, RX. And if you absolutely need to reflash, there's a program button on the SqueezeAMP for that.

          Once you have some logs, you can post them here and I'll have a look
          you should also change the thread title to "unresponsive SqueezeAMP" or something. Trust me, they aren't bricked
          Last edited by sle118; 2023-01-22, 14:28.
          LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
          6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!

          Comment


            #6
            Thanks. I'll cobble something up and report back. Don't think I can change the thread title, or at least can't find where that is done.

            Comment


              #7
              Originally posted by benh View Post
              Thanks. I'll cobble something up and report back. Don't think I can change the thread title, or at least can't find where that is done.
              You can change the thread title, I've just done it.

              Click image for larger version

Name:	edit.jpg
Views:	165
Size:	34.5 KB
ID:	1627789
              Server - LMS 8.4.0 RPi4B 4GB/NanoSound ONE case/pCP 8.1.0 - 75K library, playlists & LMS cache on Sata SSD (ntfs)

              Lounge - DAC32 - AudioEngine B2
              Office - RPi 3B+/HiFiBerry DAC HAT/RPi screen - Edifier D12
              Bedroom - Echo Show 8

              Spares - 1xSB Touch, 1xSB3, 4xRPi, AVI DM5 speakers

              Comment


                #8
                Originally posted by benh View Post
                Thanks. I'll cobble something up and report back. Don't think I can change the thread title, or at least can't find where that is done.
                You need to enable "Advanced Editor".

                Click image for larger version

Name:	advanced.jpg
Views:	155
Size:	19.0 KB
ID:	1627791
                Server - LMS 8.4.0 RPi4B 4GB/NanoSound ONE case/pCP 8.1.0 - 75K library, playlists & LMS cache on Sata SSD (ntfs)

                Lounge - DAC32 - AudioEngine B2
                Office - RPi 3B+/HiFiBerry DAC HAT/RPi screen - Edifier D12
                Bedroom - Echo Show 8

                Spares - 1xSB Touch, 1xSB3, 4xRPi, AVI DM5 speakers

                Comment


                  #9
                  Yeah, I tried all of that but the title was not editable. Either advanced user malfunction or there’s a timeout in the ability to edit a title.

                  Comment


                    #10
                    Originally posted by benh View Post
                    Yeah, I tried all of that but the title was not editable. Either advanced user malfunction or there’s a timeout in the ability to edit a title.
                    Oops, yes, you're correct, the test post title I made is now greyed out and no longer editable. Probably now only editable by admin.
                    Server - LMS 8.4.0 RPi4B 4GB/NanoSound ONE case/pCP 8.1.0 - 75K library, playlists & LMS cache on Sata SSD (ntfs)

                    Lounge - DAC32 - AudioEngine B2
                    Office - RPi 3B+/HiFiBerry DAC HAT/RPi screen - Edifier D12
                    Bedroom - Echo Show 8

                    Spares - 1xSB Touch, 1xSB3, 4xRPi, AVI DM5 speakers

                    Comment


                      #11
                      Originally posted by kidstypike View Post

                      Oops, yes, you're correct, the test post title I made is now greyed out and no longer editable. Probably now only editable by admin.
                      Just a guess, but it seems logical to me that you can edit the title of a new thread you have started, until some else has replied to it.
                      Usually running latest beta LMS nightly on Raspberry Pi OS with virtual players (Squeezelite and Airplay bridge). Occasionally using SB Radio, Boom or Classic.

                      Comment


                        #12
                        So, success.

                        I bodged together an adapter to connect my USB to serial adapter to the 6 pin header and I managed to recover both of the SqueezeAmps, but I do not understand how or why it worked.

                        As I would connect the serial adapter to a SqueezeAmp, with TX, RX, GND, DWL and RST all connected, and then remove RST, it would appear on the network in recovery mode, so I was able to recover via the web UI.

                        I was able to do that without making heads or tails of the output of the serial console, as I'm getting garbage characters as if the baud rate/data/bits/stop bits are incorrect. It is also quite possible that I've mis-made the adapter, but it tested ok from a continuity perspective, and there are only so many ways to screw it up. Could also be that my terminal program is at fault, but I can connect to other serial consoles with it ok.

                        Is the serial console 115200 N81? Why did these devices reappear in recovery mode once a serial console was connected?
                        Last edited by benh; 2023-01-23, 15:36.

                        Comment


                          #13
                          (I have tested every single baud rate from 300 to 230400, and they all are garbled.)

                          Comment


                            #14
                            Originally posted by benh View Post
                            Is the serial console 115200 N81? Why did these devices reappear in recovery mode once a serial console was connected?
                            Originally posted by benh View Post
                            (I have tested every single baud rate from 300 to 230400, and they all are garbled.)
                            Espressif state the default console settings are 115200-8-1-N

                            I think they will drop into recovery mode, after a while, if they cannot connect to wifi. I've looked but can't find anything that says connecting a serial console will force it into recovery mode and I know from my own use you can have a serial console connected and run the device in Squeezelite mode.

                            Kev

                            Comment


                              #15
                              It's difficult to believe that it's a coincidence. I can have an SA sitting here borked and offline, plug in serial console and suddenly there it is, network visible.

                              Comment

                              Working...
                              X