How did the firmware update evaporate from my board?



  • @streamliner I just tried to update my firmware on the maestro and everything went kaput! I mean everything, I once had an operating 3d printer and now I do not. I tried to load the old images for macros, and sys and json etc the five or six that I saved as the firmware for the unit. I tried to upload them and use them all over again and I cannot. Do you have any advice for me? I was running version 2.01 beta and I was trying to get 2.02 because I need to be able to do some important things with my menu item. I tried the update your firmware actions that are recommended on the web and I could not do it, all the ay back to version 3, no the board will not even announce it's connection to the USB even after changing the commands as instructed. Not a computer expert and man these boards really require that if you are going to make any changes or try to improve things in the firmware division.



  • I even was able to manipulate pressure advance and now NOTHING!



  • It's not clear from your description what state your board is actually in and what you've tried.

    If you plug it into USB do any lights come on?
    Does it show up in device manager?
    Have you tried different USB ports or micro USB cables?
    If you connect it back up to the printer do any lights come on?
    If so, can you ping the IP address?
    What happened when you tried to update to 2.02?
    How did you try to update it?


  • administrators



  • @phaedrux The lights come on, yes, the communication is there. Initially I was able to scan the board and g et the usb, and then after the board was scanned, I was not able to pull up the screen function in oder to inquire about the firmware version. I was initially able to connect with Pronterface and use Gcode to move forward on installing the new firmware version, but that failed and subsequently Proterface said that the board was not configured. Each step on the fallback procedure I was able to communicate initially and then after the initial step the board is no longer able to be connected bcause the board is not configured, device not configured.



  • @dc42 This great advice, but I use a MAC is there a MAC procedure? I am sure that there is one but it has not been widely published. So the third options is of course a decent one, but man Apple was the largest company on the planet for a few weeks. I suspect that I need to figure the process out from that aspect which really is so much more of a challenge than I bargained for. Is there a fallback 3 that you know of for mac?



  • @phaedrux said in How did the firmware update evaporate from my board?:

    It's not clear from your description what state your board is actually in and what you've tried.
    If you plug it into USB do any lights come on?

    Yes lights come on

    Does it show up in device manager?
    It does not appear on any device communication suite, neither Pronterface nor Arduino IDE, it does not appear on the port manager in arduino, although it did initially, then stopped doing so.

    Have you tried different USB ports or micro USB cables?
    The cables I a using are new and worked BEFORE the firmware installation

    If you connect it back up to the printer do any lights come on?
    All of the requisite lights come on the red communication lights for the USB, the network lights, the blue light, all of the lights come on.

    If so, can you ping the IP address?
    I have tried pinging the IP several ways, but the process prescribed by the Duet instructions does not provide an IP. Once I got a USB port given by the nework scan, and then went to screen the board to get the firmware version and the ISP and firmeware version never appeared, the message was that the device was not configured.

    What happened when you tried to update to 2.02?
    I was able to upload the file confirm the installation the board downloaded the information and at the end the message was that the device was not configured. So I conneted, uploaded teh firmware 2.02, approved the installation and the last step determined that the board was not configured.

    How did you try to update it?
    I downloaded the firmware from the suite, insured that the right file was in the sys folder (this was a little different, the title was the same except for the last letter, I included both in my sys folder, this may have done it, but how can I know?) Uploaded the entire thing the firmware onto the duet website and then got an error at the end. I tried to load it using Pronterface, I got to the step where the G code instructs to install the firmware and then Pronterface said the device was not configured. Each step said essentially that everything is great until the very last step.


  • administrators

    @novaprint said in How did the firmware update evaporate from my board?:

    @dc42 This great advice, but I use a MAC is there a MAC procedure? I am sure that there is one but it has not been widely published. So the third options is of course a decent one, but man Apple was the largest company on the planet for a few weeks. I suspect that I need to figure the process out from that aspect which really is so much more of a challenge than I bargained for. Is there a fallback 3 that you know of for mac?

    Yes, there is a version of Bossa for Mac. What I don't know (because I don't have a Mac) is how you identify the correct USB port.

    Ignore messages from Pronterface saying the device isn't configured, it's probably assuming that it's talking to Marlin, and you may have Marlin emulation turned off. Use a terminal emulator instead.



  • @dc42 MACs have a terminal program that they come with as the standard MAC suite. The dev.tty command yields no information about any connected boards for me right now. It DID say that I hada USB connection and then there was none. This is so confounding.



  • @dc42 As I said before I am no compuer expert, is it possible to use the lennox based SAM-BA version 2.17 using a raspberry Pi?


  • administrators

    @novaprint On Mac OS X the Bossa port shows up as /dev/tty.usbmodem17101 or similar. This is what you'd have to specify in BOSSA (available here for Mac: https://github.com/shumatech/BOSSA/releases)

    The command to flash your DuetM would look like this: bossac --port=/dev/tty.usbmodem17101-b -U -e -w -v ./DuetMaestroFirmware.bin -R
    This should be run from a Terminal.



  • @chrishamm Thank you I will try those when I get home tonight.



  • @chrishamm well, I tried to install the bossa, and the version newwest version would not work with my operating system. I used the 1.8 instead of the 1.9 and true to form the interface came up and I was going to start using it and the icon disappeared. I have reinstalled it a few too many times and the same result happens. I tried to use SAMBA on my raspberry pi and that did not work either. I need these things to work! Urgently.



  • @chrishamm I will use a work PC to see if I can get a result that is workable.

    meanwhile here is the report from 1.9.1 Process: bossa [1422]
    Path: /Applications/BOSSA.app/Contents/MacOS/bossa
    Identifier: ShumaTech.BOSSA
    Version: ???
    Code Type: X86-64 (Native)
    Parent Process: ??? [1]
    Responsible: bossa [1422]
    User ID: 501

    Date/Time: 2019-01-04 01:55:44.959 -0500
    OS Version: Mac OS X 10.11.6 (15G20015)
    Report Version: 11
    Anonymous UUID: FE0F58C0-2AE9-1D6E-0E29-A2AAB01BF59E

    Sleep/Wake UUID: F19B3E3D-7953-41D0-BF56-CE93B63DABCA

    Time Awake Since Boot: 8100 seconds
    Time Since Wake: 1700 seconds

    System Integrity Protection: enabled

    Crashed Thread: 0

    Exception Type: EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Exception Note: EXC_CORPSE_NOTIFY

    Application Specific Information:
    dyld: launch, loading dependent libraries

    Dyld Error Message:
    Library not loaded: /usr/local/opt/libpng/lib/libpng16.16.dylib
    Referenced from: /Applications/BOSSA.app/Contents/MacOS/bossa
    Reason: image not found

    Binary Images:
    0x7fff6386a000 - 0x7fff638a1a47 dyld (360.22) <C8E77F6D-CE86-3C5B-8576-2584A799B51E> /usr/lib/dyld
    0x7fff8c6ed000 - 0x7fff8c6fbfff com.apple.opengl (12.1.0 - 12.1.0) <B9CE1265-6D68-3BE3-8345-90F9402F5DF3> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff8e412000 - 0x7fff8e412fff com.apple.Carbon (154 - 157) <8F6ED602-5943-3E29-A793-BC331E2C183D> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff8f233000 - 0x7fff8f233fff com.apple.Cocoa (6.11 - 22) <807787AB-D231-3F51-A99B-A9314623C571> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff8f871000 - 0x7fff8fa17ff7 com.apple.audio.toolbox.AudioToolbox (1.13 - 1.13) <370E95BC-956C-3962-86CC-0A14CF6A0389> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff9c5b4000 - 0x7fff9c5b5ffb libSystem.B.dylib (1226.10.1) <2CBB584D-A69C-36AA-A432-8E4E334EA589> /usr/lib/libSystem.B.dylib
    0x7fff9ca27000 - 0x7fff9ca9cfff com.apple.framework.IOKit (2.0.2 - 1179.50.3) <80452F8B-D168-3848-A5F6-3CF96EBEDD5D> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit

    Model: MacBookPro8,2, BootROM MBP81.004F.B00, 4 processors, Intel Core i7, 2.2 GHz, 8 GB, SMC 1.69f3
    Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In
    Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 512 MB
    Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x859B, 0x435434473353313333394D2E43313646314B
    Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x859B, 0x435434473353313333394D2E43313646314B
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.102.30)
    Bluetooth: Version 4.4.6f2, 3 services, 18 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en1
    Serial ATA Device: Samsung SSD 850 EVO 500GB, 500.11 GB
    Serial ATA Device: MATSHITADVD-R UJ-8A8
    USB Device: USB 2.0 Bus
    USB Device: FaceTime HD Camera (Built-in)
    USB Device: Hub
    USB Device: Apple Internal Keyboard / Trackpad
    USB Device: BRCM2070 Hub
    USB Device: Bluetooth USB Host Controller
    USB Device: USB 2.0 Bus
    USB Device: Hub
    USB Device: IR Receiver
    Thunderbolt Bus: MacBook Pro, Apple Inc., 25.1


  • administrators

    To upload firmware to a Duet WiFi/Ethernet you can use Bossa 1.8 or 1.9, or SAMBA 2.16 or 2.17. To upload to a Maestro you need Bossa 1.9 (SAMBA would also work if you had a compatible processor/board definition for it).



  • @dc42 Here we go so I am using Bassa, the 64 bit version as list, although my computer says it is a 32 bit version I go to write Duet2 combined firmware and it starts out, gets to around 18 percent and says that it has failed to write. the bossa window says that it is connected to ATSAM4S8. I clicked verify, and it would get to around 90 percent and then say that it was not able to complete and then just make sure that know how is boss, BOSSA says that if cannot connect after a few minutes. I reset the board. I did not see anything about moving the jumper back perhaps I need to do that. The board appeared after the reset was done.



  • @dc42 BOSSA direct quote FLASH COMMAND FAILED

    I have tried to write to flash I tried to write in general, nothing works ojh BTW the BOSSA directions I seem to be missing if BOSSA works I am not sure how to make it work. Just to keep everyone on the same page this is the BOSSA 1.91



  • @dc42 Even better I tried SAMBA and used the board code at91sam4e8-ek (invalid chip ID) and the com port that SAMBA came up with and the program said that it could not connect with the device. I used SAMBA 2.18 and also 2.17 just in case I was messing up. Down three days I a just not in a good place right now. Is it possible that the Maestro has a different designator for the board somehow? The first identifier on the SAMBA seemed to connect, but I did not try to use it. It seemed like that would mess things up even more.



  • @dc42 I made a mistake and endorsed the at91sam484s8-ek and the SAMBA worked. Pronterface detects the board, but it will not actually talk to the Maestro, it says that it is connecting...., the board is detected, but that is just about it. Also the screen in terminal will not report anything back. maybe I will go to the fallback two and see if I can get it to actually work, but I do not have the IP number. Fallback two did not work either.



  • @novaprint Duet combined firmware is for DuetWifi/DuetEthernet board. As you have Maestro you should use DuetMaestroFirmware.bin


Log in to reply