10-25-2023, 10:16 AM
Bricked Dreamstation Go
I have a Respironics DreamStation Go. Yes, it's under recall, registered maybe 2 years ago, and I opted for a replacement and was notified a few days ago that that replacement is delayed indefinitely.
I haven't noticed any foam particles, so have been using the device. A few months ago, I ordered the humidifier, and found out that a firmward update was required to make the Go recognize the humidifier.
I inserted the supplied microSD card as instructed, and midway through the update, the screen stopped updating. I waited 12 hours (went to bed) overnight) to avoid interrupting the update just in case it happened to be doing something. In the morning, the screen was unchanged, still mid-update. So I crossed my fingers and power-cycled the unit to encounter a blank white screen. My Go is now bricked.
Of course there is no recourse, since nobody has a Go to replace this with, and Phillips is too busy with the recall to service an item that should be under recall anyway.
Has anyone else had a similar experience with a firmware upgrade? Is there any known recovery mechanism? I haven't yet pulled apart my go to see what microcontroller is used, but I imagine a last-ditch strategy would be to attempt to read out the firmware using a jtag or similar interface on the MCU in a working unit, and write the dumped firmware to my bricked unit.
Has anybody tried that? Or might anyone with a little engineering experience and a DS Go be willing to coordinate with me to dump a copy of the firmware so I can get my unit back up and running?
Most likely, any private data would be in EEPROM, either in the MCU or a separate EEPROM chip, and that could be excluded from a dump. I am thinking if I can get an intact flash firmware image written back to my MCU, that will be enough to get up and running.
Yes, I might eventually get a replacement Go, but in the meanwhile, I have some travel for which I don't want to bring my DS1 (which *was* replaced by Phillips after about 2 years).
Dave
I haven't noticed any foam particles, so have been using the device. A few months ago, I ordered the humidifier, and found out that a firmward update was required to make the Go recognize the humidifier.
I inserted the supplied microSD card as instructed, and midway through the update, the screen stopped updating. I waited 12 hours (went to bed) overnight) to avoid interrupting the update just in case it happened to be doing something. In the morning, the screen was unchanged, still mid-update. So I crossed my fingers and power-cycled the unit to encounter a blank white screen. My Go is now bricked.
Of course there is no recourse, since nobody has a Go to replace this with, and Phillips is too busy with the recall to service an item that should be under recall anyway.
Has anyone else had a similar experience with a firmware upgrade? Is there any known recovery mechanism? I haven't yet pulled apart my go to see what microcontroller is used, but I imagine a last-ditch strategy would be to attempt to read out the firmware using a jtag or similar interface on the MCU in a working unit, and write the dumped firmware to my bricked unit.
Has anybody tried that? Or might anyone with a little engineering experience and a DS Go be willing to coordinate with me to dump a copy of the firmware so I can get my unit back up and running?
Most likely, any private data would be in EEPROM, either in the MCU or a separate EEPROM chip, and that could be excluded from a dump. I am thinking if I can get an intact flash firmware image written back to my MCU, that will be enough to get up and running.
Yes, I might eventually get a replacement Go, but in the meanwhile, I have some travel for which I don't want to bring my DS1 (which *was* replaced by Phillips after about 2 years).
Dave
