Duet3D System won't turn on now

A Former User

You can also try to run this command, it could work, but I can't say for sure as I don't have a Duet3 to test it with, but it will not do any harm at least.

wget -q https://pastebin.com/raw/wekeLGhS -O - | tr -d '\r' | bash

It will download a script I started earlier to automatically detect and recover a Duet connected to a Pi. This is how it looked when recovering a Duet 2 Meastro, it should look similar, but obviously with different filenames for you.

pi@raspberrypi:~ $ wget -q https://pastebin.com/raw/wekeLGhS -O - | tr -d '\r' | bash
Cloning into '/home/pi/BOSSA'...
remote: Enumerating objects: 11, done.
remote: Counting objects: 100% (11/11), done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 1727 (delta 4), reused 5 (delta 1), pack-reused 1716
Receiving objects: 100% (1727/1727), 1.15 MiB | 964.00 KiB/s, done.
Resolving deltas: 100% (1318/1318), done.
make: wx-config: Command not found
make: wx-config: Command not found
CPP APPLET src/WordCopyArm.cpp
CPP COMMON src/Samba.cpp
CPP COMMON src/Flash.cpp
CPP COMMON src/D5xNvmFlash.cpp
CPP COMMON src/D2xNvmFlash.cpp
CPP COMMON src/EfcFlash.cpp
CPP COMMON src/EefcFlash.cpp
CPP COMMON src/Applet.cpp
CPP COMMON src/WordCopyApplet.cpp
CPP COMMON src/Flasher.cpp
CPP COMMON src/Device.cpp
CPP COMMON src/PosixSerialPort.cpp
CPP COMMON src/LinuxPortFactory.cpp
CPP BOSSAC src/bossac.cpp
CPP BOSSAC src/CmdOpts.cpp
LD bin/bossac
2020-04-02 03:43:22 URL:https://github-production-release-asset-2e65be.s3.amazonaws.com/15792831/8d0ad700-4b31-11ea-9191-66b95646e549?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200402%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200402T024223Z&X-Amz-Expires=300&X-Amz-Signature=2a797e70c703b8a93dec6934054f655c9ce980cd6a4bf0baa19e3ed6b6bf13c6&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3DDuetMaestroFirmware.bin&response-content-type=application%2Foctet-stream [412148/412148] -> "/home/pi/DuetMaestroFirmware.bin" [1]
Erase flash

Done in 4.605 seconds
Write 412148 bytes to flash (805 pages)
[==============================] 100% (805/805 pages)
Done in 6.139 seconds
Verify 412148 bytes of flash
[==============================] 100% (805/805 pages)
Verify successful
Done in 6.172 seconds
Set boot flash true
FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2020-02-09b1
pi@raspberrypi:~ $

Jim46

Hi Bearer,
I've tried to run both suggestions. Here are the results. 1) is from PuTTy on my PC. 2) is from RPi4. The Duet is connected to the Pi with the ribbon cable and the USB cable from the Duet to the Pi. Hope this is useful:

IMG_5092 (3024 x 2268).jpg IMG_5091 (3024 x 2268).jpg

A Former User

Lets go with the last setup; we should make that work. Try it again.

Jim46

Okay, will do now.. thank you. best way to try use PuTTy or on the Pi?

A Former User

@Jim46 My bad, either should work (i mistook the first picture). Putty is fine if its easier, both run the commands on the Pi.

(But we're after running the wget blah blah... command again)

Jim46

Okay, I'll rerun the wget line on PuTTy now

Jim46

I ran it and got new results.. I wanted to copy and paste the results to this page, but it acted strange. How did you do the screen above with the scrolling function?
So, I ran wget again and got different results again. I'm post these below here:

what do you think of these?

A Former User

@Jim46 said in Duet3D System won't turn on now:

what do you think of these?

I'm not sure, but I suspect the Duet3d guys will have some input now as we have a clear fault to address. Maybe you can try another USB cable while waiting for them to catch up to the development.

Jim46

above the Done in 3.467 seconds it said,
bash
bash Duet 3 6HC
erase flash

done in 3.4xxx seonds

Jim46

Okay I switched to a short USB cable

A Former User

The line that said SAM-BA operation failed is what I was refering to, the firmware download failed for an unknown reason, and I suspect dc42 knows more than me about that bit. But as I said see if another USB cable gives a different output, and I'll change the flashing to include debugging output as well. If it still fails you'll have a file bossa.log in your home directory that may be of interest to the Duet3d guys.

Jim46

Bearer, thanks for sticking with me here. I've run lsusb on the Pi using a 12" cable between Pi and Duet instead of the 6' cable I used between my PC and the Duet. Any better info?

A Former User

Hmm, lsusb shoud show you either
Bus 001 Device 008: ID 03eb:6124 Atmel Corp. at91sam SAMBA bootloader
or
Bus 001 Device 004: ID 1d50:60ee OpenMoko, Inc.

if the cable is okay; the latter is what you'll see once the firmware is successfully updated, until then it will show as the first entry. None of the entries would suggest the cable isn't working, or at least lacking the data connection.

Jim46

Hi, I reran the wget on the Pi with the short USB cable mentioned above, Here is the result:
The lsusb looks a lot like yours. Yet the results above it say no device found...doesn't sound great!

A Former User

@Jim46 said in Duet3D System won't turn on now:

above it say no device found...doesn't sound great!

will never be any difference between just lsusb and the output at the end of the script wget downloads and runs btw; they do the exact same thing.

it could be the cable you changed to is one of those charging only type of cables, which you can easily enough test by going back to the one that partially worked.

Jim46

I dug up a 3rd 12' USB cable and reran wget. Here are the results. Progress?

Jim46

Opps 12" cable number 3

droftarts

@Jim46 I have little knowledge of the Raspberry Pi, but when it comes to flashing firmware to Duets... I wrote the documentation! The original issue seems to have been a corrupted firmware, and now you're trying to run a firmware update with Bossa on the Pi. But have you put a jumper on the ERASE pins (you know, the ones I thought you'd left a jumper on before), powered up the Duet for 5 seconds, powered down, removed the jumper, then tried updating the firmware? You may need to do this a few times; despite showing a Bossa port, the firmware sometimes seems quite tenacious. Also, make sure your Bossa version is 1.9.1, or the Duet 3 processor won't be supported.

Alternatively, switch to a Windows desktop and run Bossa from there. Always works first time for me on Windows. The Mac version of Bossa is broken for Duet 3, unfortunately.

Ian

A Former User

@Jim46 said in Duet3D System won't turn on now:

I dug up a 3rd 12' USB cable and reran wget. Here are the results. Progress?

Bingo! you now have RRF3 3.0 running on your duet.

@droftarts said in Duet3D System won't turn on now:

Also, make sure your Bossa version is 1.9.1

the script he ran builds it from git and sorts out everything (when the cable works:)

droftarts

@bearer Ah, that all happened while I was writing my post! Wow, this has been a journey. Well done to everyone for persevering, and especially to you for your knowledge.

What's the major learning from this thread, that I can document?

Ian