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?

[whitehoose]

Yes it matters what's detected - the iron has two states - a USB storage device (just plug it in and wait) - or A DFU device waiting to be flashed (plugged in while pressing A)

[Jasonstewart81]

Yeah the wifi on my laptop took a crap. It could possibly have been from an update. I've tried getting on my desktop computer on HP's website to download the driver for my particular laptop, but with no success. I can't remember what the error message was, but I think it had said something about hardware not found or unrecognized. I can't remember exactly.

[Jasonstewart81]

Unfortunately I'm at work now, but when I get home I'll plug in the ts100 and see what it says because I can't remember 100% what state it's in when I plug it in. I swear it was "STM mass storage".

[whitehoose]

In win Plugin +A gives USB drive IDd by serial - device manager shows no additional USB entries Storage shows DFU virtual drive 1.96Mb populated with the usual windows detritus. With no button pressed windows reports unidentified device.

I always use Mint as my main Operating system, only reach for windows for games and a few progs I can't live without. I'm not a linux fanboy - I just feel more in charge. Windows tends to take over and will "help" you drive off the cliff. Linux is less autpilot and so you have to point to where you want to be.

Its very different to windows even though they look quite similar. Good for investigating system problems

[huynhdesign]

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.

help me! Link video Ts100 error BL Flash & electrocution: https://youtu.be/134pZ6Hqal4

[whitehoose]

Can't actually make out the neon tester glowing - I'm guessing that's what you are trying to show that because the neon is on - there must be over 80 on the output lines.

It looks like you're using an unisolated capacitive dropper or switch mode PSU which is working with reference to 220 or 110v ac Probably nothing wrong (never say never), with the operation or wiring of the PSU. Just using a PSU that's unsuitable for a "safe" tip iron that aims to present a grounded tip. You'll need to test all your PSUs to find one that uses a "proper" transformer that isolates mains and output.

See https://www.youtube.com/watch?v=eIMXdH0Yr2w ... 14:00 shows how its done!

[ghost]

Hey everyone, after a long time of not being used, I fired up my TS100 and it was dead. Tried flashing the latest Ralim firmware, but that went as usual, it got bricked. Last time this happened to me, I used the dapboot and flashed a new firmware through WebUSB, however, now, the DFU mode seems dead too. This is what it looks like in windows device manager I tried updating the driver using Zadig to WinUSB, but that doesn't result in anything. None of the available DFU programs seem to recognize the device, Zadig needs to be forced to show all devices, Walkera Dfuse doesn't detect the device at all and dfu-util says it can't open the TS100.

Do you guys have any tips? I flashed the dapboot bootloader like last time, did everything the same, held the front button when connecting but nada, still doesn't work. Thanks for any tips guys.

EDIT: Solved

[whitehoose]

Windows can get a bit silly about "protecting" it's system folders also because of the system's wordy directory system, it's easy to exceed the (depending on which version you use) maximum 128 or 256 character limit for a statement path. Something to try with Windows is create a folder in the root c:\100update or if possible on a non-system drive D:\100update or E:\100update. and drag and drop from there. if not try the command line copy command.

Other thing is it's pretty rare to corrupt the DFU system by accident (I've never managed to corrupt mine). As with all firmware and low level changes its far more likely that you'll damage the boot loader while rewriting it - so avoid doing it "just in case" it should be a last resort. Ralim's updates are pretty safe - in the 18 months I've been reading these forums I cant think I've seen a single "spontaneous" DFU problem - its always been as a result of novice destruction.

Windows is the same - when a user (or microsoft) updates a working system its pretty much guaranteed to brick the system. Updates and fixes are best only applied to improve problems. Version chasers (especially inexperienced ones) always fall foul of the "if it 'aint broke" trap.

[ghost]

Windows can get a bit silly about "protecting" it's system folders also because of the system's wordy directory system, it's easy to exceed the (depending on which version you use) maximum 128 or 256 character limit for a statement path. Something to try with Windows is create a folder in the root c:\100update or if possible on a non-system drive D:\100update or E:\100update. and drag and drop from there. if not try the command line copy command.

Other thing is it's pretty rare to corrupt the DFU system by accident (I've never managed to corrupt mine). As with all firmware and low level changes its far more likely that you'll damage the boot loader while rewriting it - so avoid doing it "just in case" it should be a last resort. Ralim's updates are pretty safe - in the 18 months I've been reading these forums I cant think I've seen a single "spontaneous" DFU problem - its always been as a result of novice destruction.

Windows is the same - when a user (or microsoft) updates a working system its pretty much guaranteed to brick the system. Updates and fixes are best only applied to improve problems. Version chasers (especially inexperienced ones) always fall foul of the "if it 'aint broke" trap.

I tried making the folder in the system root, but that didn't work either. Turns out after a lot of googling that people with programmable mechanical keyboards have the same problem and it is caused by Sim Racing hardware by Thrustmaster, they use DFU for their gear and the Guillemot driver conflicts with any other DFU device. I had to go to a totally different PC where everything worked fine. What a weird coincidence haha

[whitehoose]

every day is a skoolday :smiley:

[mitko3]

Извинявай моя грешка. Качих .HEX вместо .bin файла. Сега работи безупречно. Благодаря ви много, че предоставихте резервния зареждащ файл. Изглежда, че е абсолютно надежден.

> 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

can you send me a link what you put

[cweater]

была аналогичная проблема - решилась другим компом (драйвер клавиатуры конфликтовал)

[voxu123]

Hey guys quick fix from me. My windows PC kept me away from updating the firmware on my TS100 thus I thought that I got it bricked. I only could enter DFU mode and under the DC voltage or Li-Po it wasn't reacting on anything (not heating up) The fix that worked for me is I tried my GF's Apple laptop that flawlessly imported the hex file into the TS100 and it's working fine again. So my fix is that if it's not working use an Apple laptop or PC and should work :d

[CRImier]

or perhaps use a Linux LiveCD =)

[discip]

@zZ-JayBuck-Zz Please don't forget to close, if solved. 😊

thanks

[thenated0g]

I just had this problem and was able to fix it by switching to a different computer. That was all i did different. Both windows 10. Funny thing is the one it worked on has a add on anti virus program.

[voxu123]

I got it fixed too. My fix was similar to yours but switching from windows 10 to Mac OS. No idea why that helped but I'm glad it did lol.

On Wed, Aug 3, 2022, 20:43 thenated0g @.***> wrote:

I just had this problem and was able to fix it by switching to a different computer. That was all i did different. Both windows 10. Funny thing is the one it worked on has a add on anti virus program.

— Reply to this email directly, view it on GitHub https://github.com/Ralim/IronOS/issues/298#issuecomment-1204342697, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV3UDAYOTFCD2H3AELHAAADVXK4WJANCNFSM4E7KWE2Q . You are receiving this because you commented.Message ID: @.***>

[thenated0g]

Once the new firmware was on i was able to go back to my original pc and use it for the logo.hex copy/paste.