TS100 bricked

[zZ-JayBuck-Zz]

Please edit this template and fill out all the information you can (where relevant). Failure to provide essential information can delay the response you receive.

• I'm submitting a ...

  • [x] Bug report
  • [ ] Feature request
  • [ ] Translation

• Do you want to request a feature or report a bug? Bug

• What is the current behavior? Booting with button closest to tip goes to DFU 3.43, C4D3BC1A (E:) drive opens. These files are there, dunno if relevant.

When copying TS100 v2.04 to drive this occurs and the drive disappears.

After a minute or two E drive reappears as this.

TS100 does not power when plugged in now, and firmware from manufacture, returns with first error message.

TS100 is bricked, any help or should I just RMA it to Amazon?

[b0bje]

You seem to have a trash folder on the flash side ?! Also looks like a hidden osx folder .fseventd ? Delete those and retry the flash. Also if you use a tool like terracopy, it could mess with the flash, so I personally copy the hex file in a DOS cmd session.

On Fri, May 11, 2018 at 12:59 AM, zZ-JayBuck-Zz notifications@github.com wrote:

Please edit this template and fill out all the information you can (where relevant). Failure to provide essential information can delay the response you receive.

-

I'm submitting a ...

• Bug report
  • Feature request
  • Translation

• Do you want to request a feature or report a bug? Bug

• What is the current behavior? Booting with button closest to tip goes to DFU 3.43, C4D3BC1A (E:) drive opens. [image: image] https://user-images.githubusercontent.com/39174086/39898038-e2afb2ca-54ac-11e8-9eef-8c21ca6da0a2.png These files are there, dunno if relevant.

When copying TS100 v2.04 to drive this occurs and the drive disappears. [image: error] https://user-images.githubusercontent.com/39174086/39898195-a084d65e-54ad-11e8-80dc-3a221dadd68c.png

After a minute or two E drive reappears as this.

[image: e drive return] https://user-images.githubusercontent.com/39174086/39898226-c9fb1872-54ad-11e8-8f47-2c8ab3120cac.png

TS100 does not power when plugged in now, and firmware from manufacture, returns with first error message.

TS100 is bricked, any help or should I just RMA it to Amazon?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Ralim/ts100/issues/298, or mute the thread https://github.com/notifications/unsubscribe-auth/ACCF4f8SRJd76H_A8ZxZ28vclzPcuMleks5txMY4gaJpZM4T6rE1 .

[JohnEdwa]

As for the "Please insert disk error", mine ended up just being a dodgy USB cable that provided power but didn't have a solid connection for the data pins, so try with a different cable first.

@b0bje Those files and folders are there by default always, not really sure why.

[Ralim]

@b0bje Those folders are hard coded into their bootloader to appear, because otherwise both OS's (Windows and OSX) try and make them at mount time. Which doesnt work for the way they are trying to intercept writes and re-route to the decoder for HEX files.

@zZ-JayBuck-Zz Can you please test with a new USB cable first (to rule it out).

When you have my firmware loaded on the TS100 it will not enumerate as a USB device, however the bootloader prevents writes from overwriting it normally so it should not have managed to have been damaged.

If the bootloader is rejecting both official as well as my firmware that something is going odd with the bootloader code. If you have a ST programmer you can easily re-program the IC to re-load the bootloader code onto it.

Also a tiny point, I did once have this issue where the internal connector was going intermittent as the I forgot to put the little foam block into a new case I put on.

[karpilin]

Bought a brand new TS100 from amazon, and on first boot has the same issue. So far I have tried different usb cable and different usb port.

Ideally would like to have an advice how to get it working instead of just returning it to seller.

[krepa098]

I'm having exactly the same issue. Flashing it successfully on Windows10 seems to be impossible as it always fails with "not enough space", followed by the wired behaviour in picture 3 and of course the iron becomes unusable thereafter as the firmware seems to be gone. Also copying the file from CMD fails with the not enough space message.

I had some success using the Linux flash script though. It also fails most of the time creating a TS100.ERR file, but after a couple of tries (felt like a 100) on different USB ports it succeeds eventually showing a TS100.rdy file. I'm using a pretty long USB cable of doubtful quality. That might be part of the issue.

[Ralim]

I have since hear a report of the above happening to people who have any anti-virus that intercepts writes. Most of these also keep their hook in the OS even when turned off. This causes issues as the TS100 is hard coded to expect writes to the FAT partition in a very particular order, and any deviation from this can cause issues.

I have in the past recommended people to try an entirely different computer with different software (such as a friends) just to try a totally different OS base for testing.

Performance under Linux sometimes goes odd, but generally is fairly reliable if the file is copied over itself a couple of times.

If you are having repeating issues with this, one alternative is to flash the replacement boot loader From Here.

This will change the boot loader for an open source DFU compatible one that is much easier to work with. (This can be an idea if you keep having issues on your machine, but it works fine on a friends).

[durd]

Trying the alternative boot loader made things worse :( It flashes, but after connecting the ts100 back to the computer no disk appears. I hear drivers being loaded, the chime from windows. But nothing :/

At first I was able to flash the manufacturers firmware after not being able to boot yours Ralim. Then I tried yours again, with same issue, no boot, just being able to enter DFU-mode. I then tried the alternative bootloader.

[Ralim]

The alternate bootloader is USB-DFU compliant, so it won't show up as a USB drive, but will work with dfu util and other programs.

[durd]

Ah ok, thanks for the tip. Downloading to the ts100 fails at 41%, tried manufacturers which fails too.

[Ralim]

If you are using dfu-util you will need a bin, not a .hex file.

[durd]

Hm, ok. Well, I'm back to the beginning anyway. Used the bin for the stock bootloader as I couldn't find any else. Anyway, guess I'm forced to stick around with the manufacturers firmware.

Thanks for trying :)

[Ralim]

@durd Happy to try and help further, but telling me it just doesnt boot doesnt give much information to go on. Give the (now) updated 2.05.01 a try, but if it fails usually it comes down to a hardware defect in your unit would be my guess (if it flashes correctly).

[krepa098]

So I also flashed the replacement boot loader and tried a firmware upload using the dfu-util. It fails at around 36%. Here's the output:

dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 1024
Copying data from PC to DFU device
Download        [=========                ]  37%        47104 bytes failed!
state(10) = dfuERROR, status(7) = Programmed memory failed verification

Also, I got a shorter USB cord just to make sure it's not the cable.

[durd]

@Ralim I'd be happy to help you more, but seeing as I wasn't getting any other errors than OP, there's not much else to post or mention. I tried as you suggested a different bootloader (no one else had tried so I posted that I had more trouble), which wasn't much easier to work with except with more help from you, which I'm of course grateful for!

I just now tried your re-uploaded 2.05.01-version, this worked perfectly with stock bootloader. I actually did have a pre-order of the TS80 in the cart at banggood, but couldn't order because the site became unreachable right when I was ready to order. So yeah, you actually saved me a bunch of money rescuing me from dfu-util-hell! :)

@krepa098 as Ralim mentioned, you need to use a .bin-file. Grab the stock one from the same link and apply that. Then download the 2.05.01 again (even though github says it hasn't been updated) and try again. Mine worked with this.

[krepa098]

Sorry, my bad. I uploaded the .HEX instead of the .bin file. It is now working flawlessly. Thank you very much for providing the replacement boot loader. It seems to be absolutely reliable.

> dfu-util -D TS100_EN.bin
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 1024
Copying data from PC to DFU device
Download        [=========================] 100%        40108 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present
dfu-util: unable to read DFU status after completion

[0xygen8]

I seem to have bricked my TS100 with my OSX computer I can still enter DFU mode by hand and reflash the original 2.18 fw but when press a lot of buttons in normal mode the screen locks up

I tried to correct the problem by using a W10 computer and reflash the original FW but every time I enter the DFU mode I see the troubling files and dirs

drwxrwxrwx  1 0xygen8   staff    512 Nov 25  2014 .Trashes
-rwxrwxrwx  1 0xygen8   staff   4096 Nov 25  2014 ._.Trashes
drwxrwxrwx  1 0xygen8   staff    512 Aug 12 18:00 .fseventsd
drwxrwxrwx  1 0xygen8   staff    512 Oct 29  2014 System Volume Information

When I remove these files they seem to reappear and rebrick [sic] the device Is there a way to fix this?

[JohnEdwa]

In this exact same issue, it was explained that those files need to be there.

[0xygen8]

Ok -- I seem to have skipped that post, but still I can flash the latest firmware to the 3.4.3 Bootloader (result RDY) but when I reboot it it does nothing (sometimes just random pixels on screen) the only way I can us it when I reflash the original 2.18 fw and then 1 out of 10 boots the screen works and I can use it puzzled... (before I flashed it with this firmware it worked fine)

[Ralim]

Hi, Can you please confirm exactly which firmware you have flashed? What hardware revision is your iron ?

It is almost impossible for this firmware to break anything, how long did you use your iron with the original firmware for? I have noticed a recent uptick in units with screen issues, which show up as random dots. This firmware can make these occur more often as it runs the i2c bus faster than the old stock firmwares (such as 2.12) however, even the newer miniware firmwares run the bus faster.

[0xygen8]

I have tested your version v2.05.01 and v2.01 as said the bootloader is 3.4.3 How do I get the hardware revision of the board? going back to 2.18 (original) somewhat fixes the dots but I used the iron for a day with the original fw for a simple project (1 hour without problems) if I flash your FW (and get a RDY) the display never works (all black) when flashing back to 2.18 and pressing the B button a lot the screen now goes haywire (showing text mirrored or several pixels shifted up)

[Ralim]

The only real way to get the hardware rev is to be able to boot the firmware, however by the looks of that, something on your I2C bus is not playing fair, and is locking up the device and preventing memory writes to the lcd. This is usually a hardware issue, especially considering how hard it is to replicate.

This usually shows up when the screen is re-drawn and an error occurs on the I2C bus. Which would explain why the original firmware also shows this on rapid screen changes. Any chance you have taken the back cover off your unit and checked for damage?

[0xygen8]

thank you for your help 👍
I will open it when I am back from my business trip and report it here

[0xygen8]

I've let my daughter open it up hardware revision is 2.85

[0xygen8]

I've ordered a new one and hope that one has less issues :)

[Ralim]

@0xygen8 Any updates to this ?

[zZ-JayBuck-Zz]

Hey Guy sorry I gave up on this. I have returned it. Thank you for all you help. If I try again I will let you know

On Fri, May 11, 2018 at 3:44 AM, Ben V. Brown notifications@github.com wrote:

@b0bje https://github.com/b0bje Those folders are hard coded into their bootloader to appear, because otherwise both OS's (Windows and OSX) try and make them at mount time. Which doesnt work for the way they are trying to intercept writes and re-route to the decoder for HEX files.

@zZ-JayBuck-Zz https://github.com/zZ-JayBuck-Zz Can you please test with a new USB cable first (to rule it out).

When you have my firmware loaded on the TS100 it will not enumerate as a USB device, however the bootloader prevents writes from overwriting it normally so it should not have managed to have been damaged.

If the bootloader is rejecting both official as well as my firmware that something is going odd with the bootloader code. If you have a ST programmer you can easily re-program the IC to re-load the bootloader code onto it.

Also a tiny point, I did once have this issue where the internal connector was going intermittent as the I forgot to put the little foam block into a new case I put on.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Ralim/ts100/issues/298#issuecomment-388243348, or mute the thread https://github.com/notifications/unsubscribe-auth/AlW_xuIUEsV3C_6MCpkbk8_wUhmkhTR5ks5txPsAgaJpZM4T6rE1 .

[0xygen8]

I have received a new ts100 and to be sure I'll use it for several months to be sure it has no issues before I'll re-flash it -- the strange thing is that (old ts100 with issues) It does not take the new firmware (yes I see a RDY file) but when I power it with 20v it does not do anything...

[Ralim]

What happens when you power it with USB ?

[0xygen8]

Screen is an stays black -- only when when I put it back in DFU mode the screen comes back

[Ralim]

Interesting that your screen is only failing when not under DFU. There have been some reports of the OLED screens failing but yours appears to be working when in DFU mode. I'll try and make a slowed down I2C version to test on your unit, since the OLED initialization code appears to be working, and it runs at a slower speed.

[0xygen8]

That would be super thank you

[centuryrehab]

Hi. I just received my TS-100. I tried to flash it with a few computers and I get the same dots on mine or nothing at all.

The ts100-dapboot.hex just shows BL Loader and the buttons won't do anything.

I can fix it by flashing the default firmware from their website.

I wonder if new TS-100's all have this issue? Is mine a clone?

[dhiltonp]

@centuryrehab: dapboot isn't very common, are you following the instructions in the wiki?

[0xygen8]

did you make the slower I2C version? so I can test if that fixes the issue

[0xygen8]

is there anything else I can do to salvage this unit? debug something, flash in a different way upgrade DFU...

[ghost]

Just got my TS100 today and i wanted to flash the ralim FW according to some ytb videos. I dragged over the file to the usb drive and when i copied it over, the flash drive was empty, it showed an error "not enough space for this file system", the disconnected and showed up again as E drive which says "insert E drive". The iron is dead, doesnt power up with 19V source or USB in config mode. Tried flashing back the stock firmware, ends with the same error. Any tips? Edit: I tried flashing the original bootloader, no luck, tried flashing dapboot, that went OK but now it does not show up as a USB drive. What now?

[FFY00]

@Ralim just saw this. I have the exact same issue as @0xygen8, in the original firmware the device is still functional but the screen usually gets messed up. I can debug it once my ST LINK or Bus Pirate arrive.

[Ralim]

@ExtraThiccDave If you flash dapboot then its no longer a usb drive but instead a usb DFU device (read the documentation on what your flashing).

@FFY00 If you do get a ST-link it might be worth checking for anything odd / writing the image directly. (you can just program the hex).

[ghost]

@Ralim Thanks! I discovered it like 20 minutes after writing that comment. I downloaded dfu-util, connected the iron, but when i run the command for DFU device list, it shows as no devices detected. Tried different USB cables (i had good quality cable to begin with), nothing. Same "BL flasher" screen shows when i only connect power as well, doesnt need to be usb. Do you have any ideas? Seems to me like my unit is defective. Thanks a lot!

[Ralim]

@ExtraThiccDave Try a different usb port / usb controller. Miniware didnt include a crystal so its clocks typically just out of spec (especially if room temp isnt 25c). Often a different controller helps. Intel ones tend to be better.

[ghost]

@ExtraThiccDave Try a different usb port / usb controller. Miniware didnt include a crystal so its clocks typically just out of spec (especially if room temp isnt 25c). Often a different controller helps. Intel ones tend to be better.

Ok, so I tried all USB ports on my Ryzen system and my Intel laptop. No luck. Room temp is around 21°C. I'm really out of ideas at this point.

[ghost]

Anyone got any ideas? This is how it behaves atm. I flashed the dapboot.hex as last resort, hoping i could flash 2.05 bin file. https://photos.app.goo.gl/p8quXhyZNQCQKP667

[ghost]

@Ralim would it be possible to replace the STM32 daughterboard and fix the issue? Or are the firmware and bootloader on the main PCB.

[Ralim]

Once you have flashed the dap boot software, it replaces the miniware one, so now you need to boot it up while holding the front button to enter the dap boot bootloader. When it says "Done" thats it replacing the original bootloader.

But yeah its totally possible to reprogram the riser board, all code is on there. Also if you cant get it working, im happy to re-flash the daughter board for you at the cost of postage if you wanted (I'm in Australia though). You can also use any st-link etc to re-program it as well.

[ghost]

@Ralim I just spent 3 minutes banging my head against the table XD I forgot to hold down the front button. Now it's being detected by DFU-UTIL. Thanks! I'll try to use web DFU and flash 2.05. If i wanted to put the stock bootloader back, would i have to reflash the ROM afterwards? In the worst case i'd attempt to ship it to you or get a replacement from miniware, i don't like the idea of returning the whole iron when only the daughterboard is bad. EDIT: After flashing original DFU 3.43 through DFU UTIL, the iron sparked back to life, then i flashed TS100-EN.hex with success and i am back and running, thanks to everyone and @Ralim !

[FFY00]

Weird. When I flashed dapboot ( ts100-dapboot.hex) it did not replace DFU, it replace the firmware. When I start the iron normally it just shows BL Flash, if I start it pressing the front button it goes to DFU.

[FFY00]

@Ralim can you tell me what to change to make a firmware version with a slowed down I2C bus like you were talking above? I can compile it myself. It might be a while for my ST LINK to arrive since I ordered it from China.

[whitehoose]

That's won me an extra week's pocket money. Not having a ts100 I didn't know the process in detail, and I've no wish to try replacing bootloaders. So I've been biting my tongue, but I had that feeling that what you were describing a negligent discharge, own goal or whatever you want to call it ... was what most likely what you were experiencing.

My advice would be when the st-link arrives, go somewhere with deep water and throw the st-link as far out into it as you can manage.

If you bought from banggood, they ask you to give them video evidence of the whatever it is either doing, or not doing whatever it is you're complaining about. If you convince them they repost the entire item as it comes in the box. (My ts80 died and that was what they did for me) seemed a shame moboard faulty rest of h/W hardly used, so I then contacted mini to see if they would sell me the bits to resurrect the dead iron. I told my tale of woe and the guy in tech support said he would like to see what the damage was and if I posted out the motherboard he would like to try and fix it. I did, he did and within a couple of weeks I was the proud owner of a second, working Iron. The follow up from both seller and manufacturer was excellent.

[dvdsk]

I had the exact symptoms as @zZ-JayBuck-Zz but then on a TS80. Switching to a USB 2.0 port did the trick for me. This was on a Ryzen B350 motherboard.

[whitehoose]

USB is a weird beast. Windows sees it either as a network port or a SCSI device. In both cases it assigns a unique device ID - just how that's arrived at involves date and time plus the USB port id. Problem is it stores it forever! Using windows 10's idiot proof restore/rebuild option that means everything you've ever plugged in, for non tech types that means the caches will probably never be cleared for the machine's life. Google "reset usb ports windows xx" xx=your flavour of win.

Not something to do regularly, but if you know a device is good else were worth a bash. The downside is you'll have to reinstall all your USB devices, not the end of the world in my book - but some folk don't realise.