Firmware update problem

Re: Firmware update problem

rayhicks — Tue, 11 Feb 2014 19:16:37 -0500

Quote
ozeng
In case anyone was wondering what happened since my last post; I gave up on using the mac to upgrade the firmware and used an old win box, which worked! Then I tried the web interface which did bizarre things but working was not one of them. Ian did his best trying to untangle too many variables, for which I am very grateful.

So after over 50+ hours spread over more than a month, I concluded the end result would never be a machine I could rely on to produce prototypes on time. I sent it thing back to RS. After much research I ordered a fully assembled dual head Makergear M2 running on Simple3D software which hopefully arrives this month. Both suppliers owe the reprap community heaps of course but apparently commercial gain seems to be needed to make everything work reliably and harmoniously.

I thank all the reprappers and open source people who have helped me and wish you the best of luck. i will watch with interest how things pan out.

Regards

Bill

Bill, it's a shame to hear that - but probably the sensible choice after your frustration. I've never had luck updating through the Mac, and initially had problems even connecting after restarting the duet (these went away for me after updating to OS X 10.9, but I still use a PC to flash). The inbuilt web interface is pretty basic and unreliable, and I've come to solely depend on Repetier Host on the Mac for printer control and printing (it may also work for your new machine) - when I get round to it I still plan on giving iamburney's web host a shot (so that my colleagues can access the printer too :P), it's looking very functional. My Ormerod is definitely producing good prototypes now, but still with some frustrations (not related to the machine itself or communications anymore, more the 3D modelling and slicing currently).

Hopefully the package you've bought will get you up back on track quickly,

Good luck,

Ray

Re: Firmware update problem

dc42 — Mon, 10 Feb 2014 11:18:20 -0500

Quote
dieterzar
Now my machine is behaving weird with the latest update, can't seem to get it to G92 Z0 for some reason. One more thing to go figure out....

Which firmware are you using, and what happens when you try G92 Z0?

Re: Firmware update problem

dieterzar — Mon, 10 Feb 2014 08:30:56 -0500

Yip, I did the update yesterday for the first time, it was on com6 on my machine as a serial port. After the erase and reset, it became some other device, usb modem I think on com17! Used bossac to flash it on that port and then it was back to com6 as a serial port. If I had not watched the serial ports under device manager, I would have figured I had trashed it.

Now my machine is behaving weird with the latest update, can't seem to get it to G92 Z0 for some reason. One more thing to go figure out....

Dieter

#257

Re: Firmware update problem

GregL — Mon, 10 Feb 2014 03:03:57 -0500

You are so right DC.
COM3 had clocked up to COM4. Definitely need to check AFTER the erase and reset.
Now to run your 057m - I like the new heater PID
Greg

Re: Firmware update problem

dc42 — Sat, 08 Feb 2014 10:08:25 -0500

Before you run bossac, you need to press the Erase button on the Duet and then the reset button. Then check Device Manager again - you will probably find that the port number has increased by 1.

Re: Firmware update problem

GregL — Sat, 08 Feb 2014 09:27:36 -0500

Just trying to update to DC's latest firmware, and I am consistently getting 'No device found on COM3' - three times now
1. Had not run the printer at all, connected up the USB, checked in Device Manager which said Arduino Due on COM3. Ran bossac, got that messge
2. Fired up Arduino serial port - connecting through COM3, sent M115 and reported back 057g firmware.Shut down Arduino. Ran bossac, got that messge
3. Fired up Pronterface (only worked after I got rid of that line 300 edit in printcore) - connecting through COM3, sent M115 and reported back 057g firmware.Shut down Pronterface. Ran bossac, got that messge.

Clueless of Rowlands Castle

Re: Firmware update problem

ozeng — Fri, 07 Feb 2014 20:40:12 -0500

In case anyone was wondering what happened since my last post; I gave up on using the mac to upgrade the firmware and used an old win box, which worked! Then I tried the web interface which did bizarre things but working was not one of them. Ian did his best trying to untangle too many variables, for which I am very grateful.

So after over 50+ hours spread over more than a month, I concluded the end result would never be a machine I could rely on to produce prototypes on time. I sent it thing back to RS. After much research I ordered a fully assembled dual head Makergear M2 running on Simple3D software which hopefully arrives this month. Both suppliers owe the reprap community heaps of course but apparently commercial gain seems to be needed to make everything work reliably and harmoniously.

I thank all the reprappers and open source people who have helped me and wish you the best of luck. i will watch with interest how things pan out.

Regards

Bill

Re: Firmware update problem

Ormerod1234 — Wed, 05 Feb 2014 06:54:47 -0500

Thanks allot, dc42 now the printer is working. You saved me lots of frustration.

Re: Firmware update problem

dc42 — Tue, 04 Feb 2014 17:12:39 -0500

You appear to have downloaded the wrong file (the one you are programming is much too short). Probably, you have downloaded the html page that describes the RepRapFirmwarexx.bin file instead of the file itself. Download it again. This time, follow the link to the file, then press the Raw button.

Re: Firmware update problem

Ormerod1234 — Tue, 04 Feb 2014 16:39:51 -0500

thanks for the answer dc42,
the same resulte i also get but the board stays on bossac programming device.
I tryed it again, it was sucessfully but still stays on as an bossac programming device.

Re: Firmware update problem

dc42 — Tue, 04 Feb 2014 16:06:17 -0500

If the Duet is showing as the bossac programming device, that means that you have not used bossac successfully to program it. When you run bossac, if it runs succesffuly you should see something like this:

C:\Users\David>C:\Arduino-1.5.4\hardware\tools\bossac.exe --port=COM12 -U true -e -w -v -b C:\Users\David\Eclipse\RepRapFirmware\Release\RepRapFirmware.bin -R
Erase flash
Write 170900 bytes to flash
[==============================] 100% (668/668 pages)
Verify 170900 bytes of flash
[==============================] 100% (668/668 pages)
Verify successful
Set boot flash true
CPU reset.

C:\Users\David>

Re: Firmware update problem

Ormerod1234 — Tue, 04 Feb 2014 15:26:35 -0500

Hello Everyone,

After updating the Duet-Board, the board is noticed as bossac programming device and I'm not able to connect to the Board with the arduino Ide nor with pronterface.
So my question is how can I change the driver from bossac programming device back to arduino due.
Thanks in advance

Re: Firmware update problem

ozeng — Sat, 01 Feb 2014 18:45:32 -0500

All this has been covered earlier in this thread I'm afraid. Arduino cannot see the Arduino Due (native USB port) after the erase and reset buttons have been pressed; end of story.

Thanks for trying. I hope I don't have4 to wait another month to get this thing working.

Cheers

Bill

Re: Firmware update problem

dc42 — Sat, 01 Feb 2014 04:15:52 -0500

Very strange. Two suggestions:

1. Have you eliminated power supply issues? The 3.3V regulator on the Duet board is very marginal when the Duet is powered only from the USB port. I don't know what sort of a mac you are using, but especially if it is a laptop, the USB power could be marginal.

2. Do you have a friend with a Linux or Windows computer who could try programming the Duet?

Re: Firmware update problem

ozeng — Fri, 31 Jan 2014 20:07:34 -0500

Yes I have. i created 'modem 3' for the purpose and used the defaults, which worked as it should have until pressing erase and delete.

Note that when the new board arrived, its usb port appeared again without me doing anything. This means that the communication problem is on the board and/or the reprap software bundle, not the computer.

Re: Firmware update problem

dc42 — Fri, 31 Jan 2014 18:10:19 -0500

I don't know if it's any help, but have you seen this on page [arduino.cc]:

>>
Installing Drivers for the Due

OSX

No driver installation is necessary on OSX. Depending on the version of the OS you're running, you may get a dialog box asking you if you wish to open the “Network Preferences”. Click the "Network Preferences..." button, then click "Apply". The Due will show up as “Not Configured”, but it is still working. You can quit the System Preferences.
<<

Re: Firmware update problem

ozeng — Fri, 31 Jan 2014 17:49:09 -0500

Thanks dc42, but you can't "select "Arduino Due (native USB port)" because the port is deleted when you press the erase and reset buttons on the duet.

Yes, the terminal command "ls" lists all usb ports, like this (before erase/reset):

[Macintosh:/applications] bill% ls /dev/cu.*
/dev/cu.BillsiPhone-Wirel
/dev/cu.Bluetooth-Modem
/dev/cu.usbmodemfa131
/dev/cu.Bluetooth-Incoming-Port
/dev/cu.usbmodem24680241

and then this after erase/reset:

[Macintosh:/applications] bill% ls /dev/cu.*
/dev/cu.BillsiPhone-Wirel
/dev/cu.Bluetooth-Incoming-Port
/dev/cu.Bluetooth-Modem
/dev/cu.usbmodem24680241

The same happens with the reprap apps. and a more general search of the /dev directory ( ls /dev/*) can't find usbmodemfa131 either

However, the system information network DOES show the port before and after erase/reset like this (with the duet unplugged and after restarting the mac):

USB Modem:

Type: PPP (PPPSerial)
Hardware: Modem
BSD Device Name: usbmodem24680241
IPv4:
Configuration Method: PPP
IPv6:
Configuration Method: Automatic
Proxies:
FTP Passive Mode: Yes
Service Order: 0

USB Modem 2:

Type: PPP (PPPSerial)
Hardware: Modem
BSD Device Name: usbmodem24680241
IPv4:
Configuration Method: PPP
IPv6:
Configuration Method: Automatic
Proxies:
FTP Passive Mode: Yes
Service Order: 1

USB Modem 3:

Type: PPP (PPPSerial)
Hardware: Modem
BSD Device Name: usbmodemfa131
IPv4:
Configuration Method: PPP
IPv6:
Configuration Method: Automatic
Proxies:
FTP Passive Mode: Yes
Service Order: 2

So, have I configured this port incorrectly???

This looks promising.

Re: Firmware update problem

dc42 — Fri, 31 Jan 2014 04:18:49 -0500

Another suggestion.

1. Disconnect Duet from Mac.
2. Load Arduino IDE.
3. In Tools->Board select "Arduino Due (native USB port).
4. In Tools->Port see what port names are available.
5. Connect Duet to Mac and give it a few seconds to start up.
6. Re-select Tools->Port and see what additional port name is available.
7. Exit Arduino IDE
7. Try the bossac command with that port name.

Re: Firmware update problem

dc42 — Fri, 31 Jan 2014 04:06:04 -0500

Quote
ozeng
Thanks dc42,

does that mean I can fabricate an address from the one that used to work, namely: /dev/cu.usbmodemfa131 ?

I don't know. Isn't there some way you can enumerate the devices attached to the Mac?

You might like to google "arduino due mac programming problem" or similar (note "due" not "duet", because the Duet board is based on the Arduino Due). I did and found this thread: [forum.arduino.cc] (not sure if this has already been mentioned in this thread).

Re: Firmware update problem

ozeng — Thu, 30 Jan 2014 21:14:36 -0500

Thanks dc42,

does that mean I can fabricate an address from the one that used to work, namely: /dev/cu.usbmodemfa131 ?

Re: Firmware update problem

dc42 — Thu, 30 Jan 2014 21:03:26 -0500

Quote
ozeng
Basically the erase and reset buttons delete the usb port and so bossac can't talk to the duet

Pressing erase and then reset causes the comms USB port to disappear, and the programming port to appear as a different port. At least, this is what happens when running Windows or Linux. ~~The comms and programming ports use different device drivers - the comms port is a fairly standard serial-over-USB emulation, while the programming port is something else.~~

EDIT: deleted that last bit because I am not sure of it.

Re: Firmware update problem

ozeng — Thu, 30 Jan 2014 20:49:42 -0500

Thanks for trying Ian, but none of that worked. And I don't have the coding skills to use the commands in the above list. Although, if bossac has an "erase flash" command, why do we use the buttons on the board? Basically the erase and reset buttons delete the usb port and so bossac can't talk to the duet. Too late for me now, but could lead to a solution.

I can't afford to spend any more time on this. If someone can put the new firmware on a board and send it to me I'd be able to use it while the software problem is sorted.

I would really appreciate getting something for my time and money after all this effort.

Regards,

Bill

Re: Firmware update problem

droftarts — Tue, 28 Jan 2014 05:56:03 -0500

Hi ozeng

Sorry for the continued problems. You know from the forum thread that I have tested the firmware updating, and the problems that I had with various versions of Mac OS X. So it's still not clear to me what the problem is with your Mac, which I think you updated to Mac OS X 10.9?

Sending boards with outdated firmware IS annoying, and our manufacturer has been given specific instructions MANY times to put the latest firmware on the boards, but persists putting the initial firmware on. However, we will need to get the firmware updating correct for you, or you will ultimately fall behind in features as the firmware progresses in the future.

I have two potential command line changes for you to try:
1. Leave out "--port=/dev/cu.usbmodemfa131 -U true". This version of the command does not force the USB port, leaving bossac to find the correct port automatically. I have not been able to test this myself (I'm working from home, and without a Duet), but it has been reported that this works.
2. Leave out "-R" from the end of the command. It may be the reset at the end of the flash happens too fast. Manually reset a few seconds after the flash has finished. Again, I haven't been able to test this. This is actually the most likely problem, I think, as the board shows up after 'erase' then 'reset' has been sent, but not after the firmware flash, so something is clearly going wrong during or just after the flash.

So, please could you try:
1. Disconnect USB, turn off ATX power, disconnect ethernet, eject SD card.
2. Plug in USB. LED light next to USB connector should turn on. Wait for 10 seconds.
3. Press 'erase' button on Duet board. Release, then press reset button on Duet board.
4. Open a Terminal window. cd to the directory where the latest RepRapFirmware is. (This should be an extracted zip of the WHOLE firmware repo, obtained by pressing the 'Download ZIP' button on the right hand side of the page here: [github.com] )
5. Send the following command (change the firmware file name to match the firmware you have):

/Applications/Arduino.app/Contents/Resources/Java/hardware/tools/bossac -e -w -v -b RepRapFirmware-XXX-DD-MM-YYYY.bin -R

or if that doesn't work:

/Applications/Arduino.app/Contents/Resources/Java/hardware/tools/bossac -e -w -v -b RepRapFirmware-XXX-DD-MM-YYYY.bin

If it still doesn't work, have you tried the other USB ports on your Mac?

For reference, here's a list of the man page for bossac, from the version on my Mac:

Ians-MacBook-Pro:tools Ian$ ./bossac -h
Usage: bossac [OPTION...] [FILE]
Basic Open Source SAM-BA Application (BOSSA) Version 1.3a
Flash programmer for Atmel SAM devices.
Copyright (c) 2011-2012 ShumaTech (http://www.shumatech.com)

Examples:
  bossac -e -w -v -b image.bin   # Erase flash, write flash with image.bin,
                                 # verify the write, and set boot from flash
  bossac -r0x10000 image.bin     # Read 64KB from flash and store in image.bin

Options:
  -e, --erase           erase the entire flash
  -w, --write           write FILE to the flash; accelerated when
                        combined with erase option
  -r, --read[=SIZE]     read SIZE from flash and store in FILE;
                        read entire flash if SIZE not specified
  -v, --verify          verify FILE matches flash contents
  -p, --port=PORT       use serial PORT to communicate to device;
                        default behavior is to auto-scan all serial ports
  -b, --boot[=BOOL]     boot from ROM if BOOL is 0;
                        boot from FLASH if BOOL is 1 [default];
                        option is ignored on unsupported devices
  -c, --bod[=BOOL]      no brownout detection if BOOL is 0;
                        brownout detection is on if BOOL is 1 [default]
  -t, --bor[=BOOL]      no brownout reset if BOOL is 0;
                        brownout reset is on if BOOL is 1 [default]
  -l, --lock[=REGION]   lock the flash REGION as a comma-separated list;
                        lock all if not given [default]
  -u, --unlock[=REGION] unlock the flash REGION as a comma-separated list;
                        unlock all if not given [default]
  -s, --security        set the flash security flag
  -i, --info            display device information
  -d, --debug           print debug messages
  -h, --help            display this help text
  -U, --force_usb_port=true/false override USB port autodetection
  -R, --reset           reset CPU (if supported)

We are trying to get this right, and make sure everyone can update the firmware, so everyone can reap the benefits of updated firmware.

Ian
RepRapPro tech support

Re: Firmware update problem

ozeng — Tue, 28 Jan 2014 00:51:51 -0500

Ian,

The new card arrived, initial connection worked fine, ports showed up as expected, checked everything was as it should be (and did screenshots), M code tests fine (apart from one thermocouple o/c). But the M115 got: "invalid M Code: M115", so the new firmware hadn't been installed! (why?). So I followed the instructions on updating the firmware again: same problem exactly. And the port has vanished again.

[Macintosh:/applications] bill% ls /dev/cu.*
/dev/cu.BillsiPhone-Wirel /dev/cu.Bluetooth-Modem /dev/cu.usbmodemfa131
/dev/cu.Bluetooth-Incoming-Port /dev/cu.usbmodem24680241
[Macintosh:/applications] bill% /Applications/Arduino.app/Contents/Resources/Java/hardware/tools/bossac --port=/dev/cu.usbmodemfa131 -U true -e -w -v -b RepRapFirmware-057a-16-01-2014.bin -R
No device found on /dev/cu.usbmodemfa131

[Macintosh:/applications] bill% /Applications/Arduino.app/Contents/Resources/Java/hardware/tools/bossac --port=dev/cu.usbmodemfa131 -U true -e -w -v -b RepRapFirmware-057a-16-01-2014.bin -R
No device found on dev/cu.usbmodemfa131

Attempting to open serial monitor gives "Board at /dev/cu.usbmodemfa131 is not available" and pressing the "copy error message" gives: "Arduino: 1.5.5 (Mac OS X), Board: "Arduino Due (Native USB Port)"

We clearly have a procedure problem, unless I've had 3 bad cards. Are you assuming programming knowledge that is not obvious to a non-programmer?

Re: Firmware update problem

ozeng — Tue, 21 Jan 2014 06:24:53 -0500

Thanks for that Ian, I'll get back to some real work and tackle the Ormerod in a week.

The replacement board had the two frame lugs through and soldered, the first had the lugs bent back, presumably by a misaligned placement jig. Four lugs would definitely be better as two only protect against bending in one direction, so the data connections have to take the load. Contractors.

Judging by the pain that results, maybe a minute spent per unit with a big lens would be worthwhile.

Cheers

Bill

Re: Firmware update problem

reprappro — Tue, 21 Jan 2014 05:15:20 -0500

Hi ozeng

Yes, I've ordered you a new Duet, should go out today. I guessed that this was your first card. I'm not sure that the two small vias either side of the ground pad are significant - there's no pin on the USB socket that connects with them. There are two tiny lugs on the bottom, but they don't line up with the visa, and I have no idea if they are supposed to. Yes, it is impossible to see if the solder is making contact with the data tabs, or if the track/pad has lifted, unless you have a microscope and are prepared to flex the socket, which may damage an otherwise working socket.

Ian
RepRapPro tech support

Re: Firmware update problem

ozeng — Tue, 21 Jan 2014 04:28:27 -0500

Sorry TMD, that comment was meant for Ian. The picture was of the card delivered with the kit; I now have a replacement card which seems to be giving problems as well. My point was that it's impossible to see if the solder is making contact with the data tabs as they are under the socket.

The white bits could be flux or remnants of the solder carrier, assuming the solder is printed on before going into the oven - or am I out of date on the pcb soldering technology?

Re: Firmware update problem

TMD_RS436 — Tue, 21 Jan 2014 02:16:52 -0500

Quote
ozeng
There are 5 soldered connections on the duet board apart from the grounding/support ones (see attached pic of my 1st board) - I don't have the gear or skills to resolder them.

Well that doesn't look good :(

Well sad to say its lost one or two pads which are used for the D+ and D- data lines pins 2 and 3 so the USB would no longer work.

It is fixable by scraping off some solder resist on the tracks leading to the missing pads, put some solder on them then re-solder the USB socket back on(solder the four mounting pins first to hold in place, then solder the 5 pins), but this will be an issue due to not having the means to resolve this issue.
I would wait to hear what Ian says about it, it may be a covered by a warranty replacement.

By the way what is that white stuff on the board?

Paul

Re: Firmware update problem

ozeng — Tue, 21 Jan 2014 01:30:44 -0500

There are 5 soldered connections on the duet board apart from the grounding/support ones (see attached pic of my 1st board) - I don't have the gear or skills to resolder them.

Re: Firmware update problem

ozeng — Sun, 19 Jan 2014 20:13:24 -0500

Ok, I installed mavericks - no change except that bossa and arduino can now see the usbmodem24680241 port (usbmodemfd131 didn't come back)

So please send me another card, preferably with the latest firmware.

Cheers

Bill