Help reinstalling firmware using SAM-BA for duet wifi



  • Hey all,

    I hit the erase button while installing my duet…. Followed the wiki fallback procedure 3 as Duet not Bossa was showing up in the device manager. Downloaded SAM-BA 2.17. Connected DUET via USB pressed and held the erase button for 3 seconds then pressed the reset button. Bossa port showed up in device manager so continued with the instructions in the wiki. Connected using SAM-BA 2.17, running as administrator, to board at91sam4e8-ek. Sent the firmware .bin "DuetWiFiFirmware-1.20RC1.bin" and clicked send and locked regions 0 to 43. Left address at 0x400000. Clicked the execute scripts (boot from flash (GPNVM1) and get an error message. I checked the download size of the firmware with DuetWiFiFirmware-1.20RC1.bin being 353,856 bytes. It seems very similar to a recent post here https://www.duet3d.com/forum/thread.php?id=3653

    Log below.

    oading history file … 0 events added
    SAM-BA console display active (Tcl8.5.9 / Tk8.5.9)
    (sam-ba_2.17) 1 %
    (sam-ba_2.17) 1 % send_file {Flash} "C:/Users/XXXXXXXXX/Desktop/DuetWiFiFirmware-1.20RC1.bin" 0x400000 0
    -I- Send File C:/Users/nkariger/Desktop/DuetWiFiFirmware-1.20RC1.bin at address 0x400000
    first_sector 0 last_sector 43
    -I- Writing: 0x10000 bytes at 0x0 (buffer addr : 0x20002128)
    -I- 0x10000 bytes written by applet
    -I- Writing: 0x10000 bytes at 0x10000 (buffer addr : 0x20002128)
    -I- 0x10000 bytes written by applet
    -I- Writing: 0x10000 bytes at 0x20000 (buffer addr : 0x20002128)
    -I- 0x10000 bytes written by applet
    -I- Writing: 0x10000 bytes at 0x30000 (buffer addr : 0x20002128)
    -I- 0x10000 bytes written by applet
    -I- Writing: 0x10000 bytes at 0x40000 (buffer addr : 0x20002128)
    -I- 0x10000 bytes written by applet
    -I- Writing: 0x6640 bytes at 0x50000 (buffer addr : 0x20002128)
    -I- 0x6640 bytes written by applet
    -I- Sector 0 locked
    -I- Sector 1 locked
    -I- Sector 2 locked
    -I- Sector 3 locked
    -I- Sector 4 locked
    -I- Sector 5 locked
    -I- Sector 6 locked
    -I- Sector 7 locked
    -I- Sector 8 locked
    -I- Sector 9 locked
    -I- Sector 10 locked
    -I- Sector 11 locked
    -I- Sector 12 locked
    -I- Sector 13 locked
    -I- Sector 14 locked
    -I- Sector 15 locked
    -I- Sector 16 locked
    -I- Sector 17 locked
    -I- Sector 18 locked
    -I- Sector 19 locked
    -I- Sector 20 locked
    -I- Sector 21 locked
    -I- Sector 22 locked
    -I- Sector 23 locked
    -I- Sector 24 locked
    -I- Sector 25 locked
    -I- Sector 26 locked
    -I- Sector 27 locked
    -I- Sector 28 locked
    -I- Sector 29 locked
    -I- Sector 30 locked
    -I- Sector 31 locked
    -I- Sector 32 locked
    -I- Sector 33 locked
    -I- Sector 34 locked
    -I- Sector 35 locked
    -I- Sector 36 locked
    -I- Sector 37 locked
    -I- Sector 38 locked
    -I- Sector 39 locked
    -I- Sector 40 locked
    -I- Sector 41 locked
    -I- Sector 42 locked
    -I- Sector 43 locked
    (sam-ba_2.17) 1 % FLASH::ScriptGPNMV 2
    -E- Set GPNVM1 failed
    (sam-ba_2.17) 1 %

    if i enable flash access then send the firmware file and then execute boot from flash I get this
    (sam-ba_2.17) 1 % FLASH::Init
    -I- Loading applet applet-flash-sam4e8.bin at address 0x20000800
    -I- Memory Size : 0x80000 bytes
    -I- Buffer address : 0x20002128
    -I- Buffer size: 0x10000 bytes
    -I- Applet initialization done
    (sam-ba_2.17) 1 % send_file {Flash} "C:/Users/nkariger/Desktop/DuetWiFiFirmware-1.20RC1.bin" 0x400000 0
    -I- Send File C:/Users/nkariger/Desktop/DuetWiFiFirmware-1.20RC1.bin at address 0x400000
    first_sector 0 last_sector 43
    -I- Writing: 0x10000 bytes at 0x0 (buffer addr : 0x20002128)
    -I- Sector 0 unlocked
    -I- Sector 1 unlocked
    -I- Sector 2 unlocked
    -I- Sector 3 unlocked
    -I- Sector 4 unlocked
    -I- Sector 5 unlocked
    -I- Sector 6 unlocked
    -I- Sector 7 unlocked
    -I- Sector 8 unlocked
    -I- Sector 9 unlocked
    -I- Sector 10 unlocked
    -I- Sector 11 unlocked
    -I- Sector 12 unlocked
    -I- Sector 13 unlocked
    -I- Sector 14 unlocked
    -I- Sector 15 unlocked
    -I- Sector 16 unlocked
    -I- Sector 17 unlocked
    -I- Sector 18 unlocked
    -I- Sector 19 unlocked
    -I- Sector 20 unlocked
    -I- Sector 21 unlocked
    -I- Sector 22 unlocked
    -I- Sector 23 unlocked
    -I- Sector 24 unlocked
    -I- Sector 25 unlocked
    -I- Sector 26 unlocked
    -I- Sector 27 unlocked
    -I- Sector 28 unlocked
    -I- Sector 29 unlocked
    -I- Sector 30 unlocked
    -I- Sector 31 unlocked
    -I- Sector 32 unlocked
    -I- Sector 33 unlocked
    -I- Sector 34 unlocked
    -I- Sector 35 unlocked
    -I- Sector 36 unlocked
    -I- Sector 37 unlocked
    -I- Sector 38 unlocked
    -I- Sector 39 unlocked
    -I- Sector 40 unlocked
    -I- Sector 41 unlocked
    -I- Sector 42 unlocked
    -I- Sector 43 unlocked
    -I- Writing: 0x10000 bytes at 0x0 (buffer addr : 0x20002128)
    -I- 0x10000 bytes written by applet
    -I- Writing: 0x10000 bytes at 0x10000 (buffer addr : 0x20002128)
    -I- 0x10000 bytes written by applet
    -I- Writing: 0x10000 bytes at 0x20000 (buffer addr : 0x20002128)
    -I- 0x10000 bytes written by applet
    -I- Writing: 0x10000 bytes at 0x30000 (buffer addr : 0x20002128)
    -I- 0x10000 bytes written by applet
    -I- Writing: 0x10000 bytes at 0x40000 (buffer addr : 0x20002128)
    -I- 0x10000 bytes written by applet
    -I- Writing: 0x6640 bytes at 0x50000 (buffer addr : 0x20002128)
    -I- 0x6640 bytes written by applet
    -I- Sector 0 locked
    -I- Sector 1 locked
    -I- Sector 2 locked
    -I- Sector 3 locked
    -I- Sector 4 locked
    -I- Sector 5 locked
    -I- Sector 6 locked
    -I- Sector 7 locked
    -I- Sector 8 locked
    -I- Sector 9 locked
    -I- Sector 10 locked
    -I- Sector 11 locked
    -I- Sector 12 locked
    -I- Sector 13 locked
    -I- Sector 14 locked
    -I- Sector 15 locked
    -I- Sector 16 locked
    -I- Sector 17 locked
    -I- Sector 18 locked
    -I- Sector 19 locked
    -I- Sector 20 locked
    -I- Sector 21 locked
    -I- Sector 22 locked
    -I- Sector 23 locked
    -I- Sector 24 locked
    -I- Sector 25 locked
    -I- Sector 26 locked
    -I- Sector 27 locked
    -I- Sector 28 locked
    -I- Sector 29 locked
    -I- Sector 30 locked
    -I- Sector 31 locked
    -I- Sector 32 locked
    -I- Sector 33 locked
    -I- Sector 34 locked
    -I- Sector 35 locked
    -I- Sector 36 locked
    -I- Sector 37 locked
    -I- Sector 38 locked
    -I- Sector 39 locked
    -I- Sector 40 locked
    -I- Sector 41 locked
    -I- Sector 42 locked
    -I- Sector 43 locked
    (sam-ba_2.17) 1 % FLASH::ScriptGPNMV 2
    -I- GPNVM1 set
    (sam-ba_2.17) 1 %

    However at this point it seems like all is ok, I exit SAM-BA then hit the reset button on the duet wifi but nothing ever shows in the device manager. I have tried a few USB cables and all the ports on my PC as well as another laptop I have. It also looks like Bossa 1.8 now works with duet wifi. Tried this as suggested in the wiki but I get the same result. Both SAM-BA 2.17 and Bossa 1.8 fail the verification/ Any suggestions?
    THanks


  • administrators

    I'm sorry you are having problems getting the firmware reinstalled. Here are some suggestions:

    1. If you are providing USB power only from a laptop, it's possible that there is insufficient USB power. So trey a powered USB hub, or a USB port on a PC; or provide VIN power at the same time (read the notes on using USB power first).

    2. In case the firmware wasn't fully erased when you accidentally hit the Erase button, press it for a second and release it, then press Reset.

    If you use Bossa 1.8, what error message(s) does it give? Don't forget to check Erase All, Lock and Boot from Flash if you use the interactive version.



  • Hey dc42, thanks for the response. I did try using the power supply (24 volts) to power the board as well. Also used 2 of my powered USB hubs. When using Bossa 1.8 I did check erase all, lock, and boot from flash. Bossa always gives me an error on the file size check. I am at work right now but i remember it had something like 56 bytes and 15 page errors? Cant remember the exact numbers right now and it always was different when I tried the process again. I must have tried 100 times last night. I have done this before so I am thinking the duet wifi might be bad? Its about a year and a half old. The whole reason i erased/reset was because it started to do odd things. I would get heater faults even though wiring was solid and was just working as well as the wifi would turn off. I wish i got some debug messages for you now but i was wrapped up in getting it working. I have ordered a new board but will try Bossa agian and see if I get any messages and post them. Thanks for your help, love my duet wifi!


  • administrators

    It does sound that the processor has developed a fault. Forum user W3DRK, who is based in the US, may be able to replace it for you.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.