# PIng1D Firmware update failure via companion **URL:** \ **Category:** Ping Sonar Devices\ **Created:** [December 26, 2019, 5:11am UTC](https://discuss.bluerobotics.com/t/ping1d-firmware-update-failure-via-companion/6608 "2019-12-26T05:11:29Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![EspReSso](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/espresso/32/5133_2.png) [@EspReSso](https://discuss.bluerobotics.com/u/EspReSso)\ **Post date:** [December 26, 2019, 5:11am UTC](https://discuss.bluerobotics.com/t/ping1d-firmware-update-failure-via-companion/6608/1 "2019-12-26T05:11:29Z")
Unable to update the firmware on a Ping running v3.26 to v3.27 via companion 0.0.18 Stopping proxy server… Opening /dev/serial/ping/Ping1D-id-0-t-1-m-1-v-3.26 at 115200 bps Sending device to bootloader… Traceback (most recent call last): File “/home/pi/companion/tools/PingBootloader.py”, line 51, in bootloader\_msg = PingMessage(pingmessage.PING1D\_GOTO\_BOOTLOADER) AttributeError: ‘module’ object has no attribute ‘PING1D\_GOTO\_BOOTLOADER’ ---
**Author:** ![erik1](https://avatars.discourse-cdn.com/v4/letter/e/8e8cbc/32.png) [@erik1](https://discuss.bluerobotics.com/u/erik1)\ **Post date:** [December 26, 2019, 4:01pm UTC](https://discuss.bluerobotics.com/t/ping1d-firmware-update-failure-via-companion/6608/2 "2019-12-26T16:01:27Z")
I have similar issue how to solve this problem…please let me know, appreciate for helping … really need help. ---
**Author:** ![EspReSso](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/espresso/32/5133_2.png) [@EspReSso](https://discuss.bluerobotics.com/u/EspReSso)\ **Post date:** [December 27, 2019, 8:48pm UTC](https://discuss.bluerobotics.com/t/ping1d-firmware-update-failure-via-companion/6608/3 "2019-12-27T20:48:36Z")
Additional information, if I close the screen and attempt it manually it fails to init the device. ./stm32flash\_armv7l -v -g 0x0 -b 115200 -w /home/pi/Ping-V3.27\_115kb.hex /dev/serial/ping/Ping1D-id-0-t-1-m-1-v-3.26 stm32flash 0.5 [http://stm32flash.sourceforge.net/](http://stm32flash.sourceforge.net/) Using Parser : Intel HEX Interface serial\_posix: 115200 8E1 Failed to init device. ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [January 2, 2020, 4:39pm UTC](https://discuss.bluerobotics.com/t/ping1d-firmware-update-failure-via-companion/6608/4 "2020-01-02T16:39:58Z")
Hi, Thank you for reporting this problem. I opened [an issue to track it](https://github.com/bluerobotics/companion/issues/285). ---
**Author:** ![EspReSso](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/espresso/32/5133_2.png) [@EspReSso](https://discuss.bluerobotics.com/u/EspReSso)\ **Post date:** [January 4, 2020, 12:50am UTC](https://discuss.bluerobotics.com/t/ping1d-firmware-update-failure-via-companion/6608/5 "2020-01-04T00:50:35Z")
Thank you very much for that Willian, appreciate it. Out of curiosity, do you know what changes were between the v3.26 to v3.27 (I haven’t been able to find release info)? Wondering if it is worth doing a tear down to direct update it now if the changes are fairly important or wait until next time I do. ---
**Author:** ![patrickelectric](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/patrickelectric/32/2162_2.png) [@patrickelectric](https://discuss.bluerobotics.com/u/patrickelectric)\ **Post date:** [January 5, 2020, 6:19pm UTC](https://discuss.bluerobotics.com/t/ping1d-firmware-update-failure-via-companion/6608/6 "2020-01-05T18:19:35Z")
Hi, The 3.26 to 3.37 update aims to fix some problems related to protocol implementation to work with the last version of our libraries and programs ---
**Author:** ![305155973](https://avatars.discourse-cdn.com/v4/letter/3/35a633/32.png) [@305155973](https://discuss.bluerobotics.com/u/305155973)\ **Post date:** [March 8, 2024, 2:21am UTC](https://discuss.bluerobotics.com/t/ping1d-firmware-update-failure-via-companion/6608/7 "2024-03-08T02:21:56Z")
had the same problem when manually updating firmware for a Ping1D ![Manual Update Error](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/8/81909518fcf0303ddf3c8eb0e9875a4525dfa8a9.jpeg)