How did the firmware update evaporate from my board?

NOVAprint

@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

dc42

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).

NOVAprint

@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.

NOVAprint

@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

NOVAprint

@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.

NOVAprint

@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.

aidar

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

dc42

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

@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.

Can you confirm that the firmware you flashed was DuetMaestroFirmware.bin? In SAMBA, after writing it did you compare/verify it?

NOVAprint

@dc42 Was that the right thing to do the identifier? WAs that an actual mistake or was I supposed to do that? I will compare right now.

NOVAprint

@dc42 Ok so, I loaded the wrong version of the software onto the at91sam4s8-ek. I used the duet maestro firmware and it works the firmware did not evaporate, but it really did give me a hell of a time I suspect that I tried to load teh combined firmware in the inital problem that presented as well. Lost three days because I read someowhere that it was recommneded that the combined be used, but if you have a Maestro, use the maestro bin, not anything else, until something changes.

NOVAprint

Now my motors are making more noise, is there a simple way to address that? more noise after the new firmware which of course should not be happening any ideas?

Phaedrux

At least this should be a one time operation. Now that you're up and running the firmware update for 2.02+ consists of uploading a single zip file to the settings>general page on the DWC.

patakopecek

@novaprint you propably had stealthchop on, so just turn it on again

NOVAprint

@patakopecek I think that you may be right, how do I put stealth chop on again? I think that I went to this:
M569 P0 S1 D3 F1 ; Drive 0 goes forwards,
M569 P1 S1 D3 F1 ; Drive 1 goes forwards,
M569 P2 S1 D3 F1 ; Drive 2 goes forwards,

I think that the D3 now represents stealth chop, unless there is some other thing that i am missing.

NOVAprint

So I was making some physical adjustments to my unit nothing terribly alarming, I generated a little bit of shavings from my drill, who hasn't? Anyhow I went to print something, loaded the file (first time after all this) the heat bed is not heating, the hot end is so I hit emergency disconnect and that is the last I talked to my board. Now the board will not connect to anything again.
Resolved to install the firmware again and the erase function will not work, BOSSA nor SAMBA will connect. Hold the erase button for a fifteen seconds no indication that the board has been made discoverable, Pronterface will not connect, nor will DWC. FML

The board stayed in the enclosure the whole time I was working on it, there was no extraordinary movement or issues when I was doing any of this, no wiring work no holes in the board.

NOVAprint

reset led will not light even with erase jumpered.

NOVAprint

@novaprint The heat bed worked before BTW I am not sure why the temp was not going up. Does it sound like I burned the board with shavings from my drill?

NOVAprint

@novaprint I tried another USB coard and it I still cannot connect with the board.

NOVAprint

I disconnected everything from the board and tried the rest function. No reaction.

dc42

Unless the board is faulty, the only reasons we know of that the firmware gets erased are if you use the Erase button or jumper, or send M999 P"ERASE" to it, or the board is subjected to some type of mis-wiring that causes a transient to be fed into the +5V or +3.3v rail.

After using the Erase jumper, you need to remove it and then press the Reset button before the board is discoverable.

I suggest you check again that the correct LEDs (and no others) are illuminated.