Duet3D System won't turn on now

droftarts

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

@Jim46
The port name is shown as "BOSSA Program Port" in YAT, I believe that means the Duet is in programming mode, hence why it won't reply to gcode commands.

Also, is the DIAG light flashing? (This indicates the firmware is running.) In your pictures earlier, it looks dimly lit (which it would be if there's a jumper on the erase pins, and not flashing). Also, it looks like you have a jumper on the 'erase' pins of the Duet! That's the pin next to the three 5V select pins. Remove it!

(Edited for clarity)

Ian

A Former User

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

Also, it looks like you have a jumper on the 'erase' pins of the Duet!

.. how about that ..!

Jim46

Hi Guys, here is a pic of the Duet3d powered by USB 2.0 from the PC It is how it was out of the box. As far as I can tell there is nothing on the erase pins near the Atmel D3M chip. Any place else a concern? I'm trying Nexxcat recommendation, but this is where I started with Tony helping remotely. I'll let you know what happens.
![0_1585762105791_IMG_5090.JPG](Uploading 100%)
I'm getting a server parsing error when I try to upload this photo. What's happening? I'll try to reboot and upload again.

Jim46

A Former User

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

I'm trying Nexxcat recommendation, but this is where I started with Tony helping remotely.

as long as the serial port is called BOSSA you will need to complete the firmware update procedure. If using the Bossa program doesn't help report back and I'll post instructions for using the command line version as that seems to help some struggling with the flashing.

I'm getting a server parsing error when I try to upload this photo. What's happening? I'll try to reboot and upload again.

I'm seeing a lot of that myself; reload the page and trying again usually sufficient.

Jim46

Trying the Duet Web Control process doesn't work as it says unable to connect as DCS is unavailable. So back to square one. what happens if you press the reset button?

A Former User

If you're trying Duet Web Control I presume you sorted out the firmware update issue and sending M115 to the board now gives you a response?

Jim46

Not really, the DWC isn't working. So I.'m dead in the water. The BOSSA is om y RPi, but all the files are empty. I tried to follow this procedure:
o update via USB (using a Raspberry Pi host):
Part1: Install bossa on the Pi with these commands:
sudo apt update && sudo apt install -y libwxgtk3.0-dev libreadline-dev
git clone https://github.com/shumatech/BOSSA
cd BOSSA
make
Part 2: Connect the Duet to the Pi.
Use a data capable USB cable from any port on the Pi to the Duet.
It is OK to power the Duet from only the USB (which implies the Pi has its own power)
It is OK to power the Duet with VIN
Do one or the other; do not power both ways.
If the Pi is part of a Duet 3 with ribbon cable, it is OK to leave this attached.
Part 3: Obtain firmware
If the Pi is part of a Duet 3, firmware will be in /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin

The Pi4 screen came back and said, bash /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin there is no such file or directory.
Looks like I need a simple and clear way to get past this stumbling block.
Jim

A Former User

DWC isn't going to work until the Duet stops showing up as a BOSSA serial port; so until that is fixed it will not function as this implies the firmware that makes the Duet function has been erased/corrupted.

If you now have the Duet connected to your Pi (edit: with the USB cable!) can you please run the command lsusb from the SSH shell on the Pi and confirm it has a line that says something like Bus 001 Device 008: ID 03eb:6124 Atmel Corp. at91sam SAMBA bootloader the first part can vary a little.

If, and only if you do, we can proceed to flash the firmware from the Pi. (if you don't please copy paste or take a picture of what you do have)

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.