Unable to Flash Duet 6HC Firmware
-
@tdm418 said in Unable to Flash Duet 6HC Firmware:
@dc42 , I wired up the transformer and connected it, tried to flash the firmware again. It's a 12v 2A wall wart. The Bossa port as identified by the Device Manager has configured itself for a much higher throughput - 115k instead of 9600, as it was on USB. I'm assuming that the autoconfigure got it right, 8 data bit, no parity, 1 stop bit, no flow control.
Same result as before, with USB power only. Bossa has been sitting at 0% complete for about 45 minutes at this point.I think that either there is something very strange about your laptop configuration, or the microcontroller is faulty. Would you like your Duet 3 replaced under warranty?
-
@dc42 , I'm going to keep trying for a bit, but ultimately, yes, the warranty may be necessary.
I did just try to connect through Bossa under Opensuse and it doesn't recognize any connections at all.
If there is any troubleshooting that can be accomplished more easily with a Linux box, I'd love to give it a try first -
@tdm418 said in Unable to Flash Duet 6HC Firmware:
If there is any troubleshooting that can be accomplished more easily with a Linux box, I'd love to give it a try first
With an erased, reset, board, powered by USB or VIN, it should show up as /dev/ttyACM0. If it does not, nothing else is going to work.
This should be true on your SUSE box, or on the Duet provided image for a Pi.
-
So I have been playing with this some more with no positive results, but some results nevertheless.
For the most part, the Linux Bossa just will not connect at all. Occasionally, it will say that it cannot connect to ttyACM0, which seems to be a recognition of the port. I just tried changing permissions via chmod a+rw /dev/ttyACM0. I am now getting an error message of " Device Unsupported".
I really appreciate everyone's time in this venture tremendously, @dc42 ,@Danal ,@bearer . If this is just wasting time at this point, I'm fine with the warranty. If there is something else to be done, or something to be learned, I'll keep plugging away as long as possible. I fly home tomorrow afternoon, and can try to replicate this from my desktop. The desktop; however, was initially a lot more reluctant to make any connection at all, so that also might be a dead end. -
Oh, its always fun to see if you can get something like this back from the brink, so it is really up to you.
On the other hand, if an erased, reset, board is showing and disappearing as ACM0, it is unlikely to go farther. That boot behavior is pretty much "wired into" those chips, it is literally in ROM, and the USB interface is in hardware. If it doesn't work, something very fundamental is wrong.
-
I have now tried an additional 4 computers - one linux box, one mac, and two windows that are older OSs than mine. Still nothing recognized properly, so I'm afraid its time to move on.
@dc42 , I purchased this thru Matter Hackers, so I'm assuming warranty it thru them, or is there an alternate that you would prefer?
-
Yes, please contact Matter Hackers, and refer them to this post for authorisation to replace your Duet under warranty.
-
@Danal , @dc42 Please read on as I suspect that this situation might recur.
So I received a replacement board from MatterHackers and here's what happened:
Plugged the new board into the desktop via usb and it immediately recognized it as a Duet device and installed drivers. Huge relief.
As soon as the drivers were installed, the error message popped up about the "unrecognized USB device".
No problem, just short the jumper, push the reset, and it will be recognized, right??? NOPE!!!
All of a sudden I was reliving the exact same experience with the new board as the last one. Not recognized regardless of USB port, USB cable, or VIN power.
Tried it on the laptop and it recognized the port as Bossa, consistently. This was new. But every time I connected Bossa and tried to flash it, either Bossa locked up, threw an error message, or just refused the connection. But I was encouraged by the consistent recognition of the Bossa port by the Device Manager. Then I noticed that the laptop had had a pretty substantial windows update in the last couple of days, so it seemed appropriate to dig a little deeper.
Back to the desktop. Windows still didn't recognize anything, so I tried Opensuse. Tried putty, ssh, hardware recognition, and about 50 different commands that should have enumerated the Duet board as a tty device. Of course, nothing at all, no recognition, no active ports or devices, just... nothing.
I flashed an updated UEFI/bios, which seemed to have a bit of an effect. Meaning that it would occasionally, maybe 10% of the time, recognize the Bossa port.
So I started googling and reading blogs. Although they mostly consisted of more commands and diagnostics, one of the arduino blogs suggested moving the usb connection down by a level and running it off of a separate usb hub. This was kind of intriguing, first, because of both machines' different behavior after updating, and second, because I have always suspected that my desktop is just off a bit. It has a first generation Ryzen 7 CPU, and also what was a bleeding edge, first gen, X370 motherboard when I built it. But it always seemed to have weird USB issues, especially with the USB 3 integration, which was originally accomplisher by software, not hardware.
So I went to WalMart and bought the cheapest USB hub I could find, unpowered. Plugged it in, and I was able to flash both boards, the new one and the old “defective” one without a hitch. Also tried with the laptop, and after erasing the updated firmware, it also worked exactly as advertised.
All I can think of that there is a disconnect somewhere with the USB 3.0 protocol since this resolution worked across two very different machines, and the USB 3.0 seems to be the common denominator. Hopefully this will help someone else out, as it has taken a few weeks and probably over 300 attempts to get this ironed out.
Now that the board is functional, I’m sure that I’ll be hitting you guys up for help with something else. Thank you in advance… -
@tdm418, thanks for your comprehensive report. This may well help someone else, in fact there is another user having similar problems right now.
Did you have any other devices connected to and powered from the Duet 3 when you were trying to flash it using Bossa, such as a RPi or a PanelDue?
-
@dc42, no other devices. I did try to flash it utilizing the Pi, but that didn't work either.
-
@Danal said in Unable to Flash Duet 6HC Firmware:
Install Pre-reqs sudo apt update && sudo apt install -y libwxgtk3.0-dev libreadline-dev
Install bossagit clone https://github.com/shumatech/BOSSA
cd BOSSA
makepardon the necro threading, but just realized this could potentially be shortened to only build the command line version bossac if you wanna update the post to simplify (for those who would use a raspbian lite image)
apt update && sudo apt install -y git git clone https://github.com/shumatech/BOSSA ~/BOSSA cd ~/BOSSA make bossac -
@tdm418, did you solve the problem?
-
Thanks for your detailed description.
I can sum it up as: Windows is very weird about USB support. Most copies of Win on most hardware work OK. A few specific configurations are cranky as ... well, I can't think of a good metaphor.
What mystifies me is the Pi. That tends to "just work". So I'm curious: Exactly what model of hardware Pi, and where did the original SD card image originate? Did you happen to see if /dev/ACM* appeared (the bossa port)?
Thanks again for contributing toward future help.
-
@bearer said in Unable to Flash Duet 6HC Firmware:
@Danal said in Unable to Flash Duet 6HC Firmware:
Install Pre-reqs sudo apt update && sudo apt install -y libwxgtk3.0-dev libreadline-dev
Install bossagit clone https://github.com/shumatech/BOSSA
cd BOSSA
makepardon the necro threading, but just realized this could potentially be shortened to only build the command line version bossac if you wanna update the post to simplify (for those who would use a raspbian lite image)
apt update && sudo apt install -y git git clone https://github.com/shumatech/BOSSA ~/BOSSA cd ~/BOSSA make bossacOhhh... good point, THANKS!
-
@Danal I had a problem where I was getting errors (bad command: Q0) from the DWC when the config.g file was loaded. After searching the forum I found a post that stated the DWC was reading the comments in the config file as code and causing errors. The problem was known in a beta release and the 'sudo apt update' & install commands from the Pi was unable to resolve the problem.
So, I am trying to do a BOSSAC firmware update from the Pi (after failing to connect issues using BOSSA on my Mac and Ubuntu laptops). The Duet 3 wiring has been completed endstops, steppers and fans. Duet 3 is powered from the 24v power supply and the Pi is powered via the ribbon cable. Duet 3 has been erased via the erase pins (jumped - powered - un-jumped).
Q: Can I connect the Pi to the Duet 3 with a micro USB and then flash the DUET with the BOSSAC command without causing more problems?
-
@Max3D as you've erased the board there is little more trouble you can do with the usb port, at least when the pi is powered from the duet there is no chance if a usb ground loop so you'll be fine.
also maybe this bossac build can help?
MartinNYHC said in Duet 3 6HC - Firmware Upgrade - Flash locked:
-
@bearer Sorry for the late reply. I'm having a problem with the bossac command now. I'm going to open separate topic since this problem seems to be getting more complicated than it needs to be. Thank you.
