-
-
Notifications
You must be signed in to change notification settings - Fork 744
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
Add support of OLED screen for TS101 (new HW revision of display/PCB?) #2063
Comments
Could you, please, honestly remember: did you use the device with the original Miniware firmware before flashing IronOS?
No, it's not irrelevant. Let this decide to people who may have time & knowledge to help without telepathic skills. ;) Although some details during report may seem insignificant, for any good bug report the more information you provide, the better (even if it won't be needed in the end). So... could you tell, please, what power adapter did you use exactly right before it happened? Did you attach power cable over DC barrel connector or over USB-C port? |
@ia Thanks for the tips.
Yes, and the original firmware works normally. I think this might indicate some hardware revision that changes the screen model?
I've tried all possible options (DC connector, dumb 5V USB-A to USB-C, and 30W Apple Adapter that comes with my MacBook), and they all have the same issue. Therefore I say that it's irrelevant. Also it happens right after I flashed the firmware, so the adapter I'm using right before it happened is my MacBook Pro 2021. |
I had to ask, because recently there was a very similar comment. Here is the statement that it did happen only because of unlucky power source through DC barrel. I thought it may be related.
Could you try to flash the original firmware back? Even if screen doesn't work, if it's only OLED issue with IronOS, then you could try go to DFU mode and flash the Miniware firmware to see if the screen works again. |
I also purchased a TS101 recently (edit: actually Aug 2024, so not soooo recent). I upgraded first to v2.22 without problems (the display was small, as expected). (it does not likely help the OP, since everything seems to work fine for me - in my case only a big "thank you" to the maintainers for the great work!) |
@ia Sorry for the late reply. Just flashed back to original firmware (TS101AppV210.zip). It works without issue, no display corruptions. All function works properly. |
So we just eliminated the theory about OLED corruption by bad power source, in your case. I'm sincerely happy to know that physically your screen works and that it hasn't been damaged. Now, could you, please, try the stable release of v2.22 build on your TS101 and report results back? Thanks. |
It is still corrupted with v2.22. output.mp4 |
Stupid question: which file did you put on the device? (language and extension) |
TS101_EN.hex |
ts101_en.hex sounds good. When flashing, what is displayed as DFU version? |
DFU:1.06
Yes.
No these are not stupid questions; I appreciate your help very much. |
@Ralim, could you look at this when you have time, please?
Probably this is the most reasonable assumption so far: it seems Miniware did start to change OLED screen model in TS101, so hardware-related code to control the screen doesn't work properly anymore. And, @Ralim, is there any way to get OLED model like we do it with accelerometers, for example? @showier-drastic, I'm not familiar with a hardware construction & case of TS101, but, at your own risk, you could very carefully disassemble your TS101 to see if there is any ID on or around OLED screen (to get the exact model). Another suggestion (a bit crazy though) - you could play a social engineering card a bit: write to Miniware official support email/contact, tell them that you damaged OLED, but you did replace it yourself by re-soldering, but now it doesn't work (you could attach photo that you showed us here) and ask them something like: "could you, tell me, please, which OLED screen exactly (manufacturer/model/id) I should buy to replace it successfully?" (believe it or not, but Miniware is very unfriendly about sharing any information about their devices & hardware willingfully). |
Is it possible that we can try some code with similar OLED models? I'm willing to collaborate on trying to flash and debug.
Unfortunately it seems that it's impossible to see the screen model without doing damage to the iron: https://www.ifixit.com/Guide/Disassembling+Miniware+TS101+soldering+iron/169989 Maybe I can try some social engineering as you mentioned, let's see if that works out. |
But what about this TS101 disassemble howto? It looks "less damaging" as far as I understand, and as the title says. Sorry, I'm shooting in the dark here, since I don't own TS101 myself, but still trying to help with everything I can. Oh, and another question: where did you get your TS101? Is there at least smallest chance that it may be some kind of clone, but not originally produced by Miniware? |
Thanks for this, but I do not feel that I can remove the glass without breaking it, so unless it's absolutely necessary, I prefer not to try this way. To me the screen issue sounds like it might be resolved by tweaking OLED registers, I will probably try to debug the firmware when I have some time.
On a taobao shop (购百应科技). It seems to have a high sales volume. |
No problem, thanks for checking out anyway.
Yeah, as far as I understand, this is the exact root cause - if they changed hardware revision of OLED model, then the calls to support new model should be added as well. However, without knowing the exact model and its datasheet, there is not so much we can do, I guess. :( Oh, I have another theory: they could keep the same OLED model, but may change PCB design a bit with modification to traces between, let's say, MCU and OLED, so in this case a new pinout "map" could be a good start. Visual inspection (even with cheapest usb microscope) and multimeter (in signal tracing mode with very thin probes) are the best friends here (take-out of the main PCB from the main shell is still required though, and there is no any guarantee that even that will help right away, so just leaving this advice for the bravest ones). Another question! If you have opportunity and mood to keep experiments with (re-)flashing, or maybe you have this information from the previous run of IronOS on your device: even without OLED displaying info properly, did you notice that IronOS works in general, anyway? I.e., if you flash IronOS, and on the first power-on you press
Just one more thing on that - what was the exact date of you placing the order? And date of you receiving your TS101? This may help, if we will start to receive the similar reports soon. P.S. Thank you for keeping in touch, it's a rare thing around here in the issue tracker. But if you don't mind, I would like to update the title since we established this as the fact that luckily your OLED is not corrupted. :) |
A quick find is that the PCB revision number of mine and whitequarks' (in your disassemble guide) are the same (V1.51A). So the possibility of this should be somewhat low.
Roughly 3 weeks ago.
Thanks for your help too. It's very important to get in touch. |
The rest of IronOS's functionality seems to be working. If I press the + button, the tip heats up, and I can tell that the temperature numbers are changing from the corrupted image. If I press the - button, some animation happens. Screen rotation works too, as shown in my video. |
Good catch. Didn't pay attention to this myself.
Yes... unless they did it without renaming the version on the PCB. Not sure how much this probable though. :/
Although at this point I don't have much to comment/provide anymore, unfortunately. :( |
Hia, This definitely screams of a bad OLED init sequence. It's most likely one of these : IronOS/source/Core/Drivers/OLED.cpp Line 36 in 4ce63fa
I would be suspect its lines 39-42 (inclusive); as those do change with different clones of the OLED's. If your able to build locally, changing those +-1 to see results can often be telling? |
Yeah, but that was due to constant voltage fluctuation (got a PSU that trades voltage for amps, not the opposite as it should...)
This thing with PSU and voltage spikes provokes only converter part of the circuit to fail, in my case it was the same capacitor and transistor over and over again, i have no idea why something else didn't fail on PCB, but ok |
In the meantime, maybe an hint could be added to the README in the "Miniware TS101" notes, linking to this issue: |
Describe the bug
After flashing 2.23-RC1 on a newly-purchased TS101, the display is not working properly.
To Reproduce
Expected behavior
Displays correctly
output.mp4
Details of your device:
Additional context
The text was updated successfully, but these errors were encountered: