Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Return to the problem of installing firmware 2.16 on TS100 with DFU 3.48 #1214

Closed
PUF52 opened this issue Feb 5, 2022 · 132 comments
Closed

Return to the problem of installing firmware 2.16 on TS100 with DFU 3.48 #1214

PUF52 opened this issue Feb 5, 2022 · 132 comments
Assignees
Labels
Hardware Issue May be PCB/HW design related.

Comments

@PUF52
Copy link

PUF52 commented Feb 5, 2022

Ralim, although you closed this problem, it remained for me. Not a single firmware is loaded on the soldering iron, except for the Chinese stock 2.20, including your 2.16. after downloading and copying. I can not solve this problem myself and I ask for your help. On two other soldering irons with DFU 3.45, everything happens normally and without problems. I also loaded your corrected firmware - the behavior is similar, the soldering iron falls off the computer.

05.02.2022.18-27-13.mp4
@discip
Copy link
Collaborator

discip commented Feb 5, 2022

@PUF52
Since this seems to be related to DFU3.48 you should consider sticking to the already existing issue #1177 like @tichy158 & @Gansgod did.

Maybe try

  1. removing any Cyrillic letters from the files name
  2. copying the file using drag & drop

Or you could try the DFU bootloader by @Ralim.

Before doing anything though read the docs carefully Readme, Backup & Bootloader

He tried it on his TS100, TS80 & TS80P and I also tried it on my TS80P.
I am currently running the latest build successfully!

@discip
Copy link
Collaborator

discip commented Feb 5, 2022

Seems you are not the only one facing this issue, so maybe some fellow sufferer is brave enough to try the custom bootloader for you. 😊

@PUF52
Copy link
Author

PUF52 commented Feb 5, 2022

Replacing Cyrillic letters with English did not give anything. I'm afraid to flash an alternative bootloader myself, because I don't consider myself a specialist, I'm afraid of a brick.

@PUF52
Copy link
Author

PUF52 commented Feb 5, 2022

Here is an interesting behavior of the firmware is visible. Now I remember the following: after receiving a soldering iron with firmware 2.20, I immediately flashed it to the Ralim 2.16 version and it behaved like Dima Stebev, a lot of artifacts, bugs, etc. Then, after modifications by Ralim (after requests from users) of firmware 2.16, I also flashed the modified firmware. And so, after that, leapfrog began - the soldering iron falls off the computer and no firmware gets on the soldering iron. What is it. The soldering iron itself somehow reconfigured. For the first time, 2.16, although it crookedly stood on the soldering iron, but then nothing. Unclear.

@PUF52
Copy link
Author

PUF52 commented Feb 5, 2022

Ralim? good evening, and if I give you access to my computer through Team Vie
Ver, can you remotely change the bootloader for me?

@Ralim
Copy link
Owner

Ralim commented Feb 5, 2022

Hia,
That error your are seeing is NOT because of the firmware itself, but it is usually a sign of the bootloader having issues.

So far historically it has been fixed by:

  • Different USB cable
  • Different USB port
  • Different Operating system
  • Different computer
  • Delete any failed .ERR or .RDY files on the drive (but leave other files alone)

Most likely you have something on your computer such as anti-virus that is interfering with the file copy.

Always make sure file names are in english and are kept short, as their firmware does not handle Russian characters and can cause issues.

You wont be able to change the bootloader either until you resolve this.

Sorry for the delay, timezone overlap means I'm not really around when you are much :)

@PUF52
Copy link
Author

PUF52 commented Feb 6, 2022

Greetings. Tried all your suggestions, no progress. I understand that the firmware has nothing to do with it, it's all about the bootloader. How to downgrade DFU. I'm at a dead end.

@PUF52
Copy link
Author

PUF52 commented Feb 6, 2022

By the way, I tried to install your modified firmware 2.16 on my backup soldering iron with DFU 3.45. Everything went well, the modified firmware got up successfully, which once again confirms that the problem lies in the bootloader. Is there a way to downgrade the DFU version?

@JugglerLKR
Copy link
Contributor

@PUF52 Do DFU 3.48 works as expected when flashing stock firmwares?

@PUF52
Copy link
Author

PUF52 commented Feb 6, 2022

Of the stock, it only works correctly with v2.20, with which the soldering iron came.

@paulfertser
Copy link
Contributor

paulfertser commented Feb 6, 2022 via email

@PUF52
Copy link
Author

PUF52 commented Feb 6, 2022

halfferzer, If I knew how it's done

@JugglerLKR
Copy link
Contributor

JugglerLKR commented Feb 6, 2022

halfferzer, If I knew how it's done

just flash it as you do with regular firmware. if it flashes ok (force_blank_flash.RDY), then flash Ralim's 2.16.
BTW, I see stock firmares has 8.3 names. it is for compatibility or just a coincidence?

@PUF52
Copy link
Author

PUF52 commented Feb 6, 2022

Send me this file, I can not understand and find it

@JugglerLKR
Copy link
Contributor

Send me this file, I can not understand and find it

There is a link above https://github.com/Ralim/ts100/blob/master/Development%20Resources/force_blank_flash.hex

Download and flash it.

There is no PM on github so I reply in russian here:
Скачай файл по ссылке. Прошей в паяльник. Это файл для очистки флеша, но он не стриает dfu. Потом прошей прошивку Ralimа.

@PUF52
Copy link
Author

PUF52 commented Feb 6, 2022

I can't figure out where to download this file.

@paulfertser
Copy link
Contributor

paulfertser commented Feb 6, 2022 via email

@PUF52
Copy link
Author

PUF52 commented Feb 6, 2022

I can't find it, just send me the file

@PUF52
Copy link
Author

PUF52 commented Feb 6, 2022

I couldn't find the download from your links.

@discip
Copy link
Collaborator

discip commented Feb 6, 2022

@PUF52
Here you go.
force_blank_flash.zip

@PUF52
Copy link
Author

PUF52 commented Feb 6, 2022 via email

@paulfertser
Copy link
Contributor

paulfertser commented Feb 6, 2022 via email

@PUF52
Copy link
Author

PUF52 commented Feb 6, 2022

Может быть, имя файла имеет значение? Можете ли вы переименовать его в то же имя, что и "мини" прошивка, которая работает? Пожалуйста, попробуйте именно так и со всеми буквами в одном регистре. Если цель по-прежнему отключается от компьютера, попробуйте разрезать файл пополам (это текстовый файл, вы можете отредактировать его и удалить половину строк).

Сделал, но не помогло

@JugglerLKR
Copy link
Contributor

JugglerLKR commented Feb 6, 2022

Сделал, но не помогло

Try booting from USB/CD latest Ubuntu and try flashing iron in it. If there is a problem with your windows installation, it should solve it. Or you can try any Windows 10 based PE bootable ISO with latest drivers in it. Try booting windows in safe mode with minimum drivers enables (only usb has to work). Also, as already mentioned eralier, try different micro-usb cable (better use ones that comes with phones). Remove all other usb devices. Do not use hub/extenders. Do not flash from front USB, connect cable to rear usb (if your PC has both usb 2.0 and 3.0 use 2.0 first). Then, try another computer.

@PUF52
Copy link
Author

PUF52 commented Feb 6, 2022

Tried everything - to no avail

@discip
Copy link
Collaborator

discip commented Feb 6, 2022

Still assuming the bootloader is the culprit. 😉

@PUF52
Copy link
Author

PUF52 commented Feb 6, 2022

I agree

@JugglerLKR
Copy link
Contributor

In the video iron disconnects while copying file.. This means flashing stock 2.20 from miniware also will not work.

@PUF52
Copy link
Author

PUF52 commented Feb 6, 2022

Stock sews beautifully

@PUF52
Copy link
Author

PUF52 commented Feb 11, 2022

But what about this? Is 3.5 the same as 3.50?

@Ralim
Copy link
Owner

Ralim commented Feb 11, 2022

That is for a different iron (TS80P) not the TS100.
Miniware has a different "build" of their bootloader for each iron. They are not always interchangeable.

@Gansgod
Copy link

Gansgod commented Feb 13, 2022

I managed to solve the firmware problem on my TS100 soldering iron with DFU 3.48 (many thanks to the user "JugglerLKR", he suggested what to do)
You need to install UBUNTU 18.04. It is on this version that the soldering iron is flashed without problems.
If someone needs explanations in Russian, you can write to me in telegram - Egor_138

@JugglerLKR
Copy link
Contributor

JugglerLKR commented Feb 13, 2022

I managed to solve the firmware problem on my TS100 soldering iron with DFU 3.48 (many thanks to the user "JugglerLKR", he suggested what to do) You need to install UBUNTU 18.04. It is on this version that the soldering iron is flashed without problems. If someone needs explanations in Russian, you can write to me in telegram - Egor_138

@Ralim ofcourse this needs more testing - but I'd suggest temporary add Ubuntu exaclty 18 version (Bionic Beaver) as a recommended bootable OS for those having troubles in windows.
As proverb says - Once is luck, twice is coincidence, three times is a pattern.

@PUF52
Copy link
Author

PUF52 commented Feb 14, 2022

@Ralim,

Ралим, привет. Вы, наверное, знаете, что с большой помощью Juggler я смог прошить свой паяльник на 2.16. Но иногда этот экран выскакивает при включении. Где-то 1 тайм из 10. Что это может быть? 20220210_202322
Hello. Maybe you did not pay attention to my question earlier, but such a screen appears on firmware 2.17. Annoys. What is it and how is it treated?
Uploading 20220214_104917.jpg…

@PUF52
Copy link
Author

PUF52 commented Feb 14, 2022

@Ралим, Hello. Maybe you did not pay attention to my question earlier, but such a screen appears on firmware 2.17. Annoys. What is it and how is it treated?

@Eugene-Market
Copy link

@PUF52
friend, I understand that you can not wait to start working with this firmware, but please, do not endlessly mention people, they are also trying

@PUF52
Copy link
Author

PUF52 commented Feb 14, 2022

@PUF52 друг, я понимаю, что тебе не терпится начать работать с этой прошивкой, но, пожалуйста, не надо бесконечно встречать людей, они тоже стараются

Евгений-Маркет Hello. I don't quite understand why you are so outraged by my repeated question. Are you always satisfied with the lack of an answer? I just reminded in the correct form about myself and about the question that I asked 3 days ago. Maybe the person simply did not pay attention to him or forgot about the answer. That's what this forum is for.

@Ralim
Copy link
Owner

Ralim commented Feb 14, 2022

I have not forgotten, but been busy working on other things for a bit.

To confirm, does this screen always show or is it only on some boots?

It looks suspiciously like the poorly soldered I2C issue that has affected some Pinecil's but not confident on that given the quirky I2C of the GD32F103.

@PUF52
Copy link
Author

PUF52 commented Feb 14, 2022

Ralim, thanks, but the problem is not what you suggested. It's all right there. The problem is in the power supply, which apparently was solved by soldering a 0.1 uF ceramic capacitor inside the soldering iron right on the power socket. Pre-tested 100 times, supplying and disconnecting +24 V power to the soldering iron. There were no failures, but we still need to test. Thank you for participating in my problem. The most interesting thing is that on another soldering iron with DFU 3.45, STM32 and firmware 2.17, when powered by the same power supply, I have never seen such a screen. Like this.

@Ralim
Copy link
Owner

Ralim commented Feb 14, 2022

I would be curious if you tested a capacitor on the vdd rail as well; wonder if the gd32f103 is not starting up well from reset.

Could also be reset pull-up or a poorly seated daughter board. Searching back through the old git issues there was discussion of a similar issue that turned out to be the small PCB being just slightly loose.

@Eugene-Market
Copy link

@PUF52
how did you come to the conclusion that you need to solder the capacitor, and specifically into the mains outlet, why not 24 volts (or 12)?

@PUF52
Copy link
Author

PUF52 commented Feb 14, 2022

Eugene-Market, оutlet, it's just for +24 V and ground

@PUF52
Copy link
Author

PUF52 commented Feb 14, 2022

How did you agree? Well, firstly, I have such a block, with very good parameters of 5A and 24 V and low ripples, including those of a pulsed nature. Secondly, such a screen appeared before the logo appeared, that is, before the soldering iron was turned on, so I decided to solder a capacitor to +24 V and ground, that is, to filter out power interference. Now I will attach a photo of the power supply, on which everything worked clearly and without failures.

@PUF52
Copy link
Author

PUF52 commented Feb 14, 2022

20220214_192746

@PUF52
Copy link
Author

PUF52 commented Feb 15, 2022

Ralim, hello. In general, after 2 days of testing my soldering iron with a capacitor in the +24 V supply, I came to the conclusion that this measure is not as effective as it seemed to me at the beginning. The screen with artifacts still sometimes appears. Much less often than without it, but still appears. That's not what worries me, but something else. Can you still try to answer me, suggest why the other two soldering irons, but with STM32, firmware 2.17 and DFU3.45, work flawlessly on this power supply? That is, these soldering irons are completely satisfied with this power supply, moreover, both before and after revision? For me it's a mystery. It seems that this behavior occurs at the program level.

@PUF52
Copy link
Author

PUF52 commented Feb 15, 2022

I do not
I ask for a specific answer, I ask you to express your thoughts on this bug.

@Ralim
Copy link
Owner

Ralim commented Feb 15, 2022

Please keep in mind that the two irons you are using are running entirely different processors that are not exact copies. Also you are comparing across batches, with different hardware.

One test that is worth doing to rule out a bunch of the hardware is to swap the processor small PCB's and check if the issue follows the one with the GD32 processor or not.

The dots can be caused by issues on the board that is not the MCU and so it's worth figuring that out first.

It could definitely be software, but I've been unable to reproduce it here.

@PUF52
Copy link
Author

PUF52 commented Feb 16, 2022

Thank you. I will definitely do it when I have free time.

@PUF52
Copy link
Author

PUF52 commented Feb 17, 2022

Ralim, hello. I hasten to inform you that I still managed to defeat the stupid screen with artifacts when the soldering iron was turned on. I'm guilty, I confess. I did not heed your first advice to check the soldering of the OLED screen. The problem was exactly that. I carefully soldered everything and the sore was gone, the capacitor was thrown out, the power supply was the same. Before that, I rearranged the scarves of microcontrollers. On a scarf with STM32, the same screen with artifacts appeared, the conclusion is: firmware and hardware have nothing to do with it, you need to solder the screen, I did it and lo and behold, everything works without failures, clearly and as it should. So, thank you so much for participating in my problem and helping. For me, science - listen to experienced and literate people and everything will be OK.

@discip
Copy link
Collaborator

discip commented Feb 17, 2022

@PUF52
If that is fixed, please consider closing this issue.

thanks

@PUF52
Copy link
Author

PUF52 commented Feb 17, 2022

I do not mind. We are waiting for a new firmware version in which you would be able to implement sound alerts. It would be great.

@Ralim Ralim added the Hardware Issue May be PCB/HW design related. label Feb 17, 2022
@Ralim
Copy link
Owner

Ralim commented Feb 17, 2022

@PUF52

Thank you for doing to test with swapping the main control boards.
Thank you also for reporting back after resoldering the OLED, it is very good to know that this was the root cause of the issue. Weak connections to the OLED can be tricky to diagnose as they can be temperature sensitive and you can often get away with a bad connection if you run things slow enough.

Sound alerts are not part of this issue, so I will close this issue out :)

@axtingushed
Copy link

This is what is not clear. Why does firmware 2.20 like DFU3.48 and it is successfully installed on a soldering iron, but any other firmware does not like it. Maybe it's in the firmware and DFU? in their incompatibility.

откуда ты взял китайскую прошивку? я пробую ставить (прошивку с сайта miniware), у меня все также отваливается привод

@axtingushed
Copy link

@PUF52 как с тобой можно связаться?

@emmaly
Copy link

emmaly commented Aug 28, 2022

I managed to solve the firmware problem on my TS100 soldering iron with DFU 3.48 (many thanks to the user "JugglerLKR", he suggested what to do) You need to install UBUNTU 18.04. It is on this version that the soldering iron is flashed without problems. If someone needs explanations in Russian, you can write to me in telegram - Egor_138

@Ralim ofcourse this needs more testing - but I'd suggest temporary add Ubuntu exaclty 18 version (Bionic Beaver) as a recommended bootable OS for those having troubles in windows. As proverb says - Once is luck, twice is coincidence, three times is a pattern.

At the risk of adding noise, but hopefully adding another data point instead, I will share that I also had success with this (flash/copy from Ubuntu 18.04.6) as well. I had been reading through this whole saga so dejected, thinking I had no way forward...

I used the Ubuntu 18.04.6 boot media in "try it out first" mode (because installing it is unnecessary), used the iron's virtual disk via Ubuntu's automatic mounting (though I didn't notice it had mounted, so I tried to manually mount it myself via mkdir sdb; sudo mount -t msdos /dev/sdb sdb, but it said it was already mounted elsewhere as vfat), used cp TS100_EN.hex /media/ubuntu/12345678 (where 12345678 was probably unique to my iron?), and then umount /media/ubuntu/12345678. Started up the iron and I had full success as far as I can tell so far. Via Windows 11 it fails just like the others have described.

If I hadn't seen @Gansgod's comment quoted above. Thank you (and @JugglerLKR) both so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Hardware Issue May be PCB/HW design related.
Projects
None yet
Development

No branches or pull requests

9 participants