TS100 bricked #298
Comments
|
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 ***@***.***> 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
<#298>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACCF4f8SRJd76H_A8ZxZ28vclzPcuMleks5txMY4gaJpZM4T6rE1>
.
|
|
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. |
|
@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. |
|
Bought a brand new TS100 from amazon, and on first boot has the same issue. Ideally would like to have an advice how to get it working instead of just returning it to seller. |
|
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. |
|
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). |
|
Trying the alternative boot loader made things worse :( 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. |
|
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. |
|
Ah ok, thanks for the tip. |
|
If you are using dfu-util you will need a bin, not a .hex file. |
|
Hm, ok. Well, I'm back to the beginning anyway. Used the bin for the stock bootloader as I couldn't find any else. Thanks for trying :) |
|
@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). |
|
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: Also, I got a shorter USB cord just to make sure it's not the cable. |
|
@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. @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. |
|
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. |
|
I seem to have bricked my TS100 with my OSX computer I tried to correct the problem by using a W10 computer and reflash the original FW When I remove these files they seem to reappear and rebrick [sic] the device |
|
In this exact same issue, it was explained that those files need to be there. |
|
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 |
|
Hi, 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. |
|
I have tested your version v2.05.01 and v2.01 as said the bootloader is 3.4.3 |
|
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. |
|
thank you for your help 👍 |
|
I've let my daughter open it up hardware revision is 2.85 |
|
I've ordered a new one and hope that one has less issues :) |
|
@0xygen8 Any updates to this ? |
|
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 ***@***.***> 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
<#298 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AlW_xuIUEsV3C_6MCpkbk8_wUhmkhTR5ks5txPsAgaJpZM4T6rE1>
.
|
|
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... |
|
What happens when you power it with USB ? |
|
Screen is an stays black -- only when when I put it back in DFU mode the screen comes back |
|
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. |
|
And like I said in a previous comment. I honestly don't know if it's a windows 10 thing or the firmware itself. I'm guessing it's a windows 10 thing honestly and because I'm not a super computer genius, I'm definitely not going for round 3 of trying to flash the firmware over again and bricking a third ts100 that works just fine. |
|
My hunch: It's your windows. Or most likely that POS Norton suite I saw installed on some screenshot. If I were you, I'd try flashing stock or Ralin 2.04 on your supposedly dead iron using another PC. It's not normal that you killed two TS100, something is wrong with your computer. |
|
@Jasonstewart81 It's almost 100% certain that it's your computer that is the issue. I've loaded plenty of firmware images using Windows 10, it works fine so long as you dont mess with it (by installing MITM software). All firmware development up until 2.05 was performed on Windows 10, it works totally fine. If anything is trashing your firmware, its software you have on your computer. |
|
That Norton isn't even active. I even tried disabling all windows built in firewall and anti-virus software and still couldn't flash anything. All I ever get is what the original question that was asked happening. I can TRY on my laptop with windows 10, but I doubt it. I'd have to save the hex file to a thumb drive and transfer it that way because for some reason the wifi on my laptop died. Doesn't recognize the hardware for it anymore. |
|
@Jasonstewart81 If Norton is installed it keeps its hook in the OS active. Even if its not active. Generally if a computer has had Norton installed at any point in time then it wont work as those hooks just get left behind. Usually the trick here is people use a friends computer or work computer that hasnt had MITM stuff installed. |
|
Sorry, but what is MITM stuff? I'm assuming (Microsoft ___ ___ ___). |
|
Firstly Jason dont even think about trying tis on Iron no3 - this is intended ONLY to recover your already messed up iron. - you have the perfect subject for experimentation - and its almost impossible to make it worse - it can only get better. Another alternative to struggling with windows is use a linux live CD (actually a dvd). My recommendation would be linux mint - it's almost a windows clone and is intended for people who are curious about linux but who aren't willing to dedicate their lives to computers. It's about as simple as it gets. download the mint Cinnamon ISO (32 or 64bit) (https://linuxmint.com/download.php) Linux Mint is ready to use as is - you don't need to add anything else - not even a virus checker, because you aren't going online (and arguably linux doesn't need it). Once you are up and running you can try (re)flashing your broken iron(s?) without windows. All it costs is an hour of your time and (possibly) a DVD. If you use a USB memory stick - just reformat when done. A linux option is always handy to have around when trying to prove if a problem is windows or hardware related. |
|
I may try that on the old iron. I have absolutely NO plan to try it on my new one. Now my question is the last time I was screwing around with the old iron it showed up in device manager as "STM mass storage" if I remember correctly. Does it actually matter what it's being recognized as or as long as I am able to at least drop the hex file in the root of the visible drive will it work or do I need to somehow get a bootloader back on it and then flash firmware. That's where I'm stuck is not know the correct process from start to end. I wish I could just completely wipe this old iron clean of anything on it and start from scratch. |
|
Jason, just reading your comments - notice you say your WiFi stopped working (after an update perchance)? Just a stab in the dark. There is a hierarchy to driver updates. Using a linux live distro would be a good way to prove if your problem is a hardware problem or caused by a rogue driver. (Linux will usually load the correct driver on startup without prompting). |
|
Yes it matters what's detected - the iron has two states - a USB storage device (just plug it in and wait) - or |
|
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. |
|
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". |
|
In win Plugin +A gives USB drive IDd by serial - device manager shows no additional USB entries 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 |
help me! Link video Ts100 error BL Flash & electrocution: https://youtu.be/134pZ6Hqal4 |
|
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 See https://www.youtube.com/watch?v=eIMXdH0Yr2w ... 14:00 shows how its done! |
|
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 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. EDIT: Solved |
|
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. 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. |
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 |
|
every day is a skoolday 😃 |
can you send me a link what you put |
|
была аналогичная проблема - решилась другим компом (драйвер клавиатуры конфликтовал) |
|
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 |
|
or perhaps use a Linux LiveCD =) |
|
@zZ-JayBuck-Zz thanks |
|
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. |
|
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
<#298 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AV3UDAYOTFCD2H3AELHAAADVXK4WJANCNFSM4E7KWE2Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
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. |
and others
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 ...
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
These files are there, dunno if relevant.
Booting with button closest to tip goes to DFU 3.43, C4D3BC1A (E:) drive opens.
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?
The text was updated successfully, but these errors were encountered: