CFW for KSGER/Quicko STM32 Soldering Stations

[mastershake]

Can you post the exact file you used? So I can add it to the project.
Are V2./v2.1 files available too?

3.1 firmware has been in this thread for a long time i posted it a good while back in this thread. the only difference are the branding when it boots and there are a couple other minor changes that were made to the 3.1snew firmware. it flashes just like any other firmware just do a full reset afterwards but its been available for a long time. im surprised you missed it back then. https://www.eevblog.com/forum/reviews/stm32-oled-digital-soldering-station-for-t12-handle/msg3456602/#msg3456602

i also posted it in the other ksger thread all the way back in feb. https://www.eevblog.com/forum/reviews/ksger-t12-stm32-v3-1s-soldering-station/msg3480024/#msg3480024

[ricktendo]

I tried converting the hex to bin, hex edited the strings, but for some reason the iron will not boot after flashing the modded bin. Restored original hex/bin and it boots fine again (settings also preserved after erasing)

[DavidAlfa]

It reminds me when I patched the OLED code to adjust the offset, the controller was completely dead after changing only 1 byte.
Does the converted bin work without modification? Then it definitely has tamper protection.

[ricktendo]

Yes if I flash the bin I converted using objcopy it works normally, what is strange is that the Russians have a reverse encoder firmware mod and it appears they did it by just by modding a few bytes

https://drive.google.com/drive/folders/1Clt8zoYeoTd0hvxemXFKrErCIIeV06nu

Edit: Looks like they patched some bytes on the end of the file, could it be checksum?

[DavidAlfa]

Yeah, probably a checksum. I'm not interested in reversing the ksger firmware.

Added the firmwares and mirrored the keygen inside repo, so if the keygen site dissapears, there will be a backup.

[groff]

Hello,
I'm following this thred for a couple of weeks, interesting project. Thank you for CFW. Here is my little help with original firmware of QUECOO T12-955 (KSGER v2.1S). I tried to back up original FW and i did it. Also try to flash with CFW from BOARDS_KSGER_[v2] and it's work very well. Flashing again with my back up file, OK too. I've read and programmed STM32 with TNM5000 programmer, so this is back up file. Here is pic of board and backup FW.

[wickated]

this board is 100% same across quecoo and ksger. almost. this one dont have quartz but do have quartz cap load

aaah forgot to say David im using only hq quecoo hw 

[DavidAlfa]

Maybe they're the same company now, or there's a 3rd one providing these boards. Who knows.
Yep, the smd are usually placed at once in a pick and place machine, but probably the rest of parts are soldered by hand.
Seems they became smart enough to realize placing a clock that uses 1/2 of the screen was not a good idea.
Thus, they removed that step from manual production step.
It's likely thet these parts will be removed eventually from the smd process too.

[mastershake]

the ksger boards are sold under a few brands now ive seen they are identical literally in every way. could be one company dropping different brands on them now

[ntchris]

Hello,
I'm following this thred for a couple of weeks, interesting project. Thank you for CFW. Here is my little help with original firmware of QUECOO T12-955 (KSGER v2.1S). I tried to back up original FW and i did it. Also try to flash with CFW from BOARDS_KSGER_[v2] and it's work very well. Flashing again with my back up file, OK too. I've read and programmed STM32 with TNM5000 programmer, so this is back up file. Here is pic of board and backup FW.

Dear groff , do you mind share how did you backup the ksger fw ? Is it encryped/read protected ?
Did you have to desolder it from the Ksger pcb and solder it to your own breakout pcb ?
And did you use the bluepill to run time attack app?
Thanks!

[ntchris]

Hi David, I have spent my whole Friday and Saturday to tried /add/mod/add the ksger pcb and the open source on my KSGER OLED 3.0 black pcb, it works well, I don't think I need to go back to ksger.

But there is one thing, seems the project currently only supports F101 ( BOARDS\KSGER\[v3]\STM32F101 ), I know it's compatible with F103,  but currently there is no direct/native support for F103  (no BOARDS\KSGER\[v3]\STM32F103 ), so I made a F103 variant for it, all pins are identical to the F101 (BOARDS\KSGER\[v3]\STM32F101) setting,
loaded the F103 bin to my board,  tested, it works well on my F103RB mcu, buzzer, oled, encoder, temperature sensing etc.

Even though it's working fine but this stm32 ide and the 64pin mcu and it's clock is quite new to me so could you please take a look see if there is some error need to be fixed, especially the clock frequency part ? 
thanks.

[DavidAlfa]

Hello, I already answered in the pull request.

Sad that you spent so much time on that.
Actually it's much easier: Edit the .ioc and the project files, replace all 101CBTx entries with 103RBTx, copy and edit the linker script, changing the line that sets the RAM size, update the project linker settings to use that file, and done!

It's a good idea to ask before doing such things, didn't you wonder why there wasn't a RB profile?
There's no 64 pin build anymore, because there's no need to do so, I unified v2 and v3 builds using 101CB because everything is compatible. Less mess with files.
I will never have a build for each stm32 type (101c,102c,103c,101r,102r,103r...) and every controller type (v1.5, v2,v3).
Multiply that, and make these builds by hand every time. That's a lot of work, and why? The result will be the same. The project needs to be compatible with all, so it's designed to use 10KB max.
The extra RAM will do nothing, there isn't any benefit.
48 and 64pin boards use the same pins, so it's just a waste of time.
Flash the current v3.x build in your RB, and you'll see...

[ricktendo]

Check out this cool settings menu! (also check out the funny No Iron screen)

[DavidAlfa]

When are you starting to work on it? 

[ygi]

I think the graphic "no iron" screen would be an improvement but I'm definitely not a fan of the settings menu. The guy in the video seems to only have 3-4 options in his menu so it works for him but I don't see how cycling through 60 icons to find the desired option would be a good thing.

[DavidAlfa]

Maybe I wasn't clear enough of the current state of the project.

Only
Bugfixing
And little
things
No major
reworks
taking
my time
my life
and my tips

If you want something like that
time to fork and make your own

[wickated]

i dunno why anyone should want something more of this project. fw is already on its top state. i even think some features are overkill. all u already have 4 cool icons, why more? 
i personally dislike project with hot air plugin, cuz hot air turbine handle sucks hard compared to 857dw.
i`d prefer project with multichannel, huge pixel density screen and other sort of jbc compatibilty. but it should be completely new project requiring build from scratch for pcb and everything else, this is 1) not fun , 2) compared in price with professional stations

[mastershake]

Check out this cool settings menu! (also check out the funny No Iron screen)

i could swear ive seen that version somewhere before. i wish i could remember if it was handskit or who it was. he may have modified it but im positive i saw another brand with that setting menu and sleep icon. hmmmm now its going to drive me crazy trying to remember

[groff]

Hello,
I'm following this thred for a couple of weeks, interesting project. Thank you for CFW. Here is my little help with original firmware of QUECOO T12-955 (KSGER v2.1S). I tried to back up original FW and i did it. Also try to flash with CFW from BOARDS_KSGER_[v2] and it's work very well. Flashing again with my back up file, OK too. I've read and programmed STM32 with TNM5000 programmer, so this is back up file. Here is pic of board and backup FW.

Dear groff , do you mind share how did you backup the ksger fw ? Is it encryped/read protected ?
Did you have to desolder it from the Ksger pcb and solder it to your own breakout pcb ?
And did you use the bluepill to run time attack app?
Thanks!

It's a long story  . Just kidding, it wasn't read protect. Maybe producer forgot to enable "read protection"  . Readed with SWD connection without desoldering. That's all. 
Not encrypted. On this board no need for activation code.

[ntchris]

Hello, I already answered in the pull request.

Sad that you spent so much time on that.
Actually it's much easier: Edit the .ioc and the project files, replace all 101CBTx entries with 103RBTx, copy and edit the linker script, changing the line that sets the RAM size, update the project linker settings to use that file, and done!

It's a good idea to ask before doing such things, didn't you wonder why there wasn't a RB profile?
There's no 64 pin build anymore, because there's no need to do so, I unified v2 and v3 builds using 101CB because everything is compatible. Less mess with files.
I will never have a build for each stm32 type (101c,102c,103c,101r,102r,103r...) and every controller type (v1.5, v2,v3).
Multiply that, and make these builds by hand every time. That's a lot of work, and why? The result will be the same. The project needs to be compatible with all, so it's designed to use 10KB max.
The extra RAM will do nothing, there isn't any benefit.
48 and 64pin boards use the same pins, so it's just a waste of time.
Flash the current v3.x build in your RB, and you'll see...

Yes I flashed the F101 build from BOARDS/KSGER/[v3]/STM32F101 at the very beginning, it works very well already.
But then I noticed F103 and F101 are quite different, other than pins and ram, the speed is 72MH vs 36Mhz, so I think maybe a F103 build can utilize the full computing power of the F103 ?
Regardless, it's still a good learning experience for the stm32 and ide, I'll just  keep the F103 build for my ksger F103.
and for those wants to try the F103 FW: attached

My original plan was to test your fw for reed/magnet switch, so when user put the handle on handle rest, it enters standby mode immediately (magnet triggers the reed switch) , so it doesn't burn the iron for air, the Ksger 3.0 fw doesn't support this setting well...but it seems the custom firmware already supports this feature well enough, nothing is needed to add.
Thanks.

[wickated]

afair fw is built for lowest resources possible, so u cant get any additional performance boost from x2 cpu clock. or just small fps boost on spi screen.
stand switch support was always in fw, even in stock. not hard to diy.

[DavidAlfa]

I would do that if there was an automatic building method, but by hand, no way, keep it simple.
Except Ksger v2 (limited by the screen interface), all others are very fast. Simply there's no need for more speed. It's like cruising in the highway, you don't need 400hp for that.
There's a lot of unused power already.

I thought to manually adjust the speed by detecting the CPU, but there's no option for that, the mcu id shows the revision (A,B, C...), family (32F10xx) and flash density (Low, high, XL..), but as far as I know, there's no way to detect if it's a 101,102 or 103.

[DavidAlfa]

German translation will be disabled in the next build if it doesn't get fixed in time.
I don't like adding half-made features, please finish it...

[wickated]

hello i just noticed recently that displaytemp is now locked once it reaches settemp instead of 5c threshold. so u thought this behaviour is much better than before? (again, i just ask, no offence) maybe this could be switchable in menu?

[Polf]

David, I've installed your latest software release. On github it is written 21-09-29, and in SYSTEM I read 21-09-23. Where is the typo?