Duet wifi 1.04 restarting when uploading config files
-
Using Bossa should still be an option no matter what, so I think either the procedure hasn't been followed exactly or the USB cable isn't working.
-
What does Bossa identify the CPU as? Maybe China took some liberties in the BOM department?
-
@Phaedrux said in Duet wifi 1.04 restarting when uploading config files:
Using Bossa should still be an option no matter what, so I think either the procedure hasn't been followed exactly or the USB cable isn't working.
I followed the process described on the site at least 30 times, I even managed to run another identical wifi duet. The firmware is sent by bossa and, soon after, when connecting with YAT, the version I sent by bossa appears. I really am not making a mistake in the procedure. The cable is the same cable that worked with the other board. It is new and working properly.
The big problem is that the sending of the M997 S1 by YAT, or the apploading of the zip file by the dwc causes the board to restart. Once I managed to send the fw 2.04, but when printing the board it reset and the printer froze. From this point on, I can't send any more firmware versions. Only the bossa procedure seems to work, the others do not. -
@bearer said in Duet wifi 1.04 restarting when uploading config files:
What does Bossa identify the CPU as? Maybe China took some liberties in the BOM department?
It appears only as a bossa port in the list of devices, and the program recognizes it normally.
-
So if bossa works to flash the firmware and M115 reports the correct firmware is flashed, that's something.
Reasons for M997 or uploading of the zip file not working could be that DWC is out of date or you're missing some IAP files in the /sys folder required.
-
@Phaedrux said in Duet wifi 1.04 restarting when uploading config files:
So if bossa works to flash the firmware and M115 reports the correct firmware is flashed, that's something.
Reasons for M997 or uploading of the zip file not working could be that DWC is out of date or you're missing some IAP files in the /sys folder required.With each firmware version I tried to install, I installed the corresponding dwc together. I believe that the problem in the dwc is not.
I'm also not sure that bossa is doing its job properly. Right after uploading the firmware through the bossa, I try to use the yat with M997 S1 and the card restarts too.
The times I tried to print an object the machine froze in the middle of the job. I have no doubt that I bought a Chinese board. -
@RodrigoRMaraujo said in Duet wifi 1.04 restarting when uploading config files:
Right after uploading the firmware through the bossa, I try to use the yat with M997 S1 and the card restarts too.
M997 S1 or S0?
S1 is for the wifi server firmware.
If you send M997 S0 after flashing with bossa it would try to flash the firmware version on the SD card, which could be an older one than you just flashed using bossa. You don't need to do both bossa and M997. I wonder if that's part of the problem here. You've flashed a recent version with bossa, but then send M997 which flashes an older version again.
-
@Phaedrux said in Duet wifi 1.04 restarting when uploading config files:
If you send M997 S0 after flashing with bossa it would try to flash the firmware version on the SD card, which could be an older one than you just flashed using bossa. You don't need to do both bossa and M997. I wonder if that's part of the problem here. You've flashed a recent version with bossa, but then send M997 which flashes an older version again.
Friend, sorry, I know exactly what I'm doing. I always download the complete zip, upload Duet2CombinedFirmware.bin using samba or bossa and then immediately put all the files on the card, so that the M997 0: 1: 2 can get everything on the memory card. The card is always formatted and updated with the same version that I used in bossa or samba, I am not making this basic mistake.
-
I have today 4 duet wifi and I already had 2 maestro. I know the correct procedure and have performed it dozens of times. Only with this defective card I have already performed failback 3 more than 30 times with no success. The board is paralyzed when trying to print or when trying to save any file via dwc. It freezes and only resumes if I turn everything off and on again.
-
Could @dc42 comment on anything? Do I still have any salvation or is this board doomed?
