@dc42 I have a bossa port in Windows Device Manager (Win 10 Pro) and in Ubuntu 20.04 I see Bus 004 Device 002: ID 03eb:6124 Atmel Corp. at91sam SAMBA bootloader when I 'lsusb'.
I am getting a Windows SAM-BA error: "SAM-BA error h_handle returned zero".
I am getting a Windows BOSSA error "Could not connect to device on COM9".
In Linux:
~/BOSSA/bin/bossac -e -w -v -b /home/nvidia/Downloads/Duet3Firmware_MB6HC.bin
No device found on /dev/ttyACM0
Both Windows and Linux machines can see it yet it errors out or refuses to connect. Is this a permissions thing? Is it a configuration issue? Are there jumpers/pins that could be mis-configured?
The documentation is terrible. It is conflicting, confusing, outdated, etc. I have seen others ask about the ribbon cable: The documentation states that a cable over 150mm is a problem yet the board was shipped from the factory with a 200mm cable.
The documentation states to install SAM-BA v. 2.17 yet the photo on the website is of SAM-BA v. 2.16. It also says that you will get connection errors (I am getting connection errors) if you specify the wrong board. Exactly what version of SAM-BA should be installed on a Windows 10 machine and exactly how do I find out or confirm which board/chip I have?
The documentation does not mention a MicroSD card during the erase/re-flash procedure. Should the MicroSD card be installed in the MB6HC board during the erase/re-flash process? What state (file structure, format, etc.) should the MicroSD card be in during the failback#2 procedure?
USB Cable: The documentation states "if it doesn't work, try new/different usb cable" however the board does not ship with a USB cable. What are the required specifications of the USB connection/cable?
I'd appreciate any help trying to flash firmware onto this $250 paperweight. Thanks.