Duet 2 Wifi bricked after firmware update
-
Hi!
I tried to update my Duet 2 wifi board and now I can not connect to it.
It just says "Failed to connect to 192.168.1.61 Incompatible firmware version"
I tried to upload DuetWebControl-SD. I think that was not the right one
What to do now? -
@lofytume post an output of M122
-
@jay_s_uk I can not get connection so I can not post anything to console
-
@lofytume well then where are you seeing the failed to connect message?
-
@jay_s_uk When I try to connect over Wi-Fi with browser.
-
@lofytume never seen that message before. Can you post a screenshot?
And if you can't get USB to connect you may have bigger issues. I would investigate getting that to work otherwise its going to make things very difficultOwns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
-
@jay_s_uk I'm able to connect with YAT via USB. Tho M122 seem to do nothing
-
@lofytume Restarted and now M122 gave me this:
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.02 or later<LF>Board ID: 08DGM-917NK-F23T0-6J1F0-3SJ6P-TY8WG<LF>Used output buffers: 1 of 24 (21 max)<LF>=== RTOS ===<LF>Static ram: 30516<LF>Dynamic ram: 91160 of which 0 recycled<LF>Exception stack ram used: 272<LF>Never used ram: 9124<LF>Tasks: NETWORK(ready,776) HEAT(blocked,1464) MAIN(running,4124) IDLE(ready,156)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 00:00:24 ago, cause: power up<LF>Last software reset at 2022-03-14 11:56, reason: User, spinning module GCodes, available RAM 11520 bytes (slot 0)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 0<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 0<LF>MCU temperature: min 16.8, current 19.5, max 19.6<LF>Supply voltage: min 0.5, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power g[Warning: Maximal number of characters per line exceeded! Check the line break settings in Terminal > Settings > Text or increase the limit in Terminal > Settings > Advanced.] -
@lofytume you need to make changes to YAT to get a proper output
See here https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet#yat-settings
Once sorted, resend M122 and it should be complete and in a more readable layout. Then post it here -
-
@lofytume I think you should start by updating the firmware as 3.0 is very old.
You'll need to make sure you have the 3.3 firmware release and put it in the folder called sys, along with the iap file from the 3.3 release. Also put the wifi firmware in there. The latest is version 1.26
SendingM997 S0:1will update them both.
Then finally, update the version of DWC but overwriting the files in the www folder with the 3.3 release from GitHub -
How did you update the firmware the first time? What file did you use?
You might be able to use Bossa to update the firmware directly as well.
https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards
-
@phaedrux I used DuetWebControl-SD.zip and updated it from the DWC
-
@lofytume said in Duet 2 Wifi bricked after firmware update:
DuetWebControl-SD.zip
That's just the web interface files, not the firmware.
What version of DWC files were you trying to upload? What is the URL that you used to get that file?
