Updated Upgrading Firmware (markdown)

Upgrading-Firmware.md

@@ -10,7 +10,7 @@ Please note that you need to use the windows explorer for file copying. Using Te
 2. The unit will appear as a USB drive.
 3. Drag the .hex file onto the USB drive.
 4. The unit will disconnect and reconnect.
-5. The filename will have changed to end in .RDY or .ERR
+5. The filename will have changed to end in .RDY or .ERR or .NOT
 6. If it ends with .RDY you're done! Otherwise, something went wrong
 7. Disconnect the USB and power up the iron. You're good to go.
 
@@ -21,13 +21,35 @@ sgr1ff1n (Shane) commented in [issue 11](https://github.com/Ralim/ts100/issues/1
 > I just wanted to say that I was able to update the firmware on my ts100 from the stock version to 1.08 found in this repository using my Mac. I simply followed the same steps however through Finder. I have a MacBook Pro (13-inch, Mid 2012) running Sierra 10.12.4 (16E195).
 # Linux
 
-Balrog-kun contributed a note in [issue 11](https://github.com/Ralim/ts100/issues/11) to note that the following method allowed them to upgrade the firmware under Linux.
+There have been reports of successful flashing but also repeatability issues and no magic recipe yet. Tests and comments are collected in [issue 11](https://github.com/Ralim/ts100/issues/11).
 
-> Also, I've just updated to 1.08 from Linux but it wasn't automatic. Just copying the file to the automounted volume would cause the file to be renamed TS100.NOT and TS100.ERR if I tried it from the command line.
+You may try, without any guarantee of success. The general procedure is the same as for Windows, the differences are in the way to mount the unit and copy the firmware.
+Remember that after flashing, the firmware filename will have changed to end in `.RDY` or `.ERR` or `.NOT` and only `.RDY` means the flashing was successful!
 
-> So I disabled automounting with `$ gsettings set org.gnome.desktop.media-handling automount false` (or as indicated by googling "disable gnome automount"), unplugged and replugged, then mounted the volume as _msdos_ instead of _vfat _type using, in my case, ` mkdir tmp; mount -t msdos /dev/sdc tmp` (as root) and `cp /home/user/Downloads/ts100.hex tmp/TS100.HEX; sync`. I'm not sure which part is the key to making it work really, possibly the msdos FS type. Automounting can be re-enabled once you see 1.08 on the TS-100 display.
+So far, what we know:
 
-Note: The destination file name must be all caps.
+* The unit has to be mounted as ```msdos``` type (thanks @balrog-kun for having spotted it). You may disable automount, but unmounting the automounted drive and remounting as msdos works fine.
+* It is recommended to use an all-caps filename for the firmware, even if successful flashing were done with lower case names.
+* Avoid USB hubs, plug directly in your computer.
+* If it fails, try again several times the procedure.
 
-## However
+Example, to be run as root, once the unit has been plugged in DFU mode and auto-mounted:
-User doegox has commented on Issue #11 that they could not get the unit's DFU updated to work under Linux. So that this point it is unknown if there is a reliable method that works under Linux.
+
+```bash
+FW=ts100.hex
+unset NAME
+eval $(lsblk -P -p -d --output NAME,MODEL|grep "DFU Disk")
+[ -z ${NAME+x} ] && exit 1  # Could not find DFU device
+umount "$NAME"
+mkdir /tmp/mntdfu
+mount -t msdos "$NAME" /tmp/mntdfu
+cp "$FW" "/tmp/mntdfu/$(basename $FW|tr a-z A-Z)"
+sync
+umount /tmp/mntdfu
+rmdir /tmp/mntdfu
+```
+
+Device will reboot and automount will rerun if not disabled.
+Check the extension of your firmware, it should be `.RDY` now.
+
+@awigen has also contributed a script [flash_ts100_linux.sh](https://github.com/Ralim/ts100/blob/master/flash/flash_ts100_linux.sh) you may try.