Author Topic: CFW for KSGER/Quicko STM32 Soldering Stations (Read 666315 times)

DavidAlfa · « **Reply #3875 on:** January 07, 2024, 02:55:21 pm »

99.99% it's caused because it's not a genuine stm32, so until I find a way to detect them, and someone with a problematic controller helps by trying my tests, they will remain bugged.
You didn't run the flash test I posted earlier when I asked to, nor anything else, so what did you expect?
I'll come back in a week and see if it magically fixed itself?
Buy a genuine stm32 and replace it.

Hunghanh2009 · « **Reply #3876 on:** January 07, 2024, 05:34:02 pm »

So sorry! Because I haven't been on the forum for a long time, I don't know your request, so I'll just report the error I encountered.

Check genuine chip here? https://github.com/deividAlfa/stm32_soldering_iron_controller/blob/master/Readme_files/Programming.md#clone-detection

- KSGER oled v3:

Size: 128

STM32F103CBT6,
came with the board

Clone test: 20036410

v1.12.1: "hardfault" error
v1.12.2: works fine
v1.12.3: works fine
v1.12.4: works fine
v1.13.0: "hardfault" error

DavidAlfa · « **Reply #3877 on:** January 07, 2024, 07:03:15 pm »

Thanks. Understand this is not my job, nor I have 50 controllers to try. If you come 2 weeks after, I will have forgotten most, so I have to start again.
I tried the KSGER V3 build in my stm32cb103 and works just fine, so I keep suspecting there's something wrong with that stm32.

New build: v1.13.1-beta.

Now a hard fault will show additional info about the last saving states, which might shed some light about the issue.
Post a picture of the hard fault screen, not only the PC address.

No solution will ever happen unless people is willing to help!.

dcore · « **Reply #3878 on:** January 07, 2024, 08:18:49 pm »

#1 - KSGER v3 OLED:
STM32F103RCT6, came with the board.
Size: 65535
Page: 2
v1.13.0-beta runs ok.
-----
#2 - KSGER v3 OLED:
STM32F102R8T6, came with the board.
Size: 65535
Page: 2
v1.13.0-beta runs ok.
-----
#3 - KSGER v3 OLED:
STM32F103RET6, repaired/replaced.
Size: 512
Page: 2
v1.13.0-beta runs ok.
-----

----------
The only things I noticed using C245:
- version number displays 1.12.0
- with Temp:320C, boost_increase :30C, cold_boost:on
a) when boosting from temperature adjusting screen, boost goes to 350C.
b) when boosting from COLD sleep, boost goes to 370C and should it be 350C.

DavidAlfa · « **Reply #3879 on:** January 07, 2024, 08:53:43 pm »

Hmm clearly clone/fake stm32s. At least they work!
No way it showed 1.12.0? I downloaded the release binaries and they have "1.13.0" string inside...?
Fixed the cold boost! (Will be fixed in v1.13.1-beta, reuploading the release).

dcore · « **Reply #3880 on:** January 07, 2024, 09:10:16 pm »

You are right about the version number, somehow I had flashed and tested v1.12.2 (Beta), sorry about that.
I'll test the new v1.13.1-beta now.

DavidAlfa · « **Reply #3881 on:** January 07, 2024, 09:43:20 pm »

Updated the flash test to follow the actual detection method of the firmware.

BTW I checked the traffic statisics, less than 5% of Github visitors check the Operation manual...

Hunghanh2009 · « **Reply #3882 on:** January 08, 2024, 05:32:03 am »

Sorry David! I just got home from work and read your article carefully. Flash test results FLASH_TEST_KSGER_v3_OLED.zip:

STM32F103CBT6,
came with the board

CPUID: 411FC231
SIZE: 128 KB
PAGE : 1024 Bytes
Clone test: 20036410

v1.12.1: "hardfault" error
v1.12.2: works fine
v1.12.3: works fine
v1.12.4: works fine
v1.13.0: "hardfault" error

and hardfault screen KSGER_v3_OLED v1.13.1-beta:

iopia · « **Reply #3883 on:** January 08, 2024, 08:44:56 am »

KSGER_v2_OLED

stm32f103cbu6
came with the board

CPUID: 411FC231
SIZE: 65535 KB
PAGE : 1024 Bytes

Clone test: 20036410

v1.13.1: works fine

asupsp700 · « **Reply #3884 on:** January 08, 2024, 09:30:57 am »

David, firmware KSGER.OLED2 V1.13.1 beta. The profile of the stings and the set temperature are not saved when turned off....
https://youtu.be/6U2d_EGw3Tk

DavidAlfa · « **Reply #3885 on:** January 08, 2024, 09:41:58 am »

Battery enabled?
If not, are you waiting at least 3 seconds after changing? Otherwise it won't be saved.

asupsp700 · « **Reply #3886 on:** January 08, 2024, 09:43:55 am »

Battery ON.Everything was saved on the previous firmware 1.12.3...

DavidAlfa · « **Reply #3887 on:** January 08, 2024, 01:31:41 pm »

Ok. Try battery off, just to test if it works.

asupsp700 · « **Reply #3888 on:** January 08, 2024, 02:31:46 pm »

Quote from: DavidAlfa on January 08, 2024, 01:31:41 pm

Ok. Try battery off, just to test if it works.

David, I disabled the battery in the menu - "BATTERY OFF" - the settings are saved.
The voltage on the battery is 3.2 - It is new

....
On 1.12.3 - Settings were saved when the battery was on

.

DavidAlfa · « **Reply #3889 on:** January 08, 2024, 02:58:27 pm »

No worries, such bugs can easily happen after reworking the settings again.
If it was the battery, you would get a warning message at boot.
I have to work, sleep, eat,... trying the entire firmware for every release is just impossible

.
Fixed in v1.13.2-beta.

REWEREWE · « **Reply #3890 on:** January 08, 2024, 03:11:44 pm »

Geehy APM32F103RBT6 clone, debugging doesn't work
CPUID: 412fc231
SIZE: 128 KB
PAGE : 1024 Bytes
Clone test: 20036410

1.13.2 beta
The selection of tips after switching off occurs correctly

asupsp700 · « **Reply #3891 on:** January 08, 2024, 03:21:29 pm »

Of course David, I understand. You are a living person and this job is not your income! You make cool firmware! Thanks for corrections.

I updated it to 1.13.2. Everything is fine! Settings are now saved when the battery is on!

oleg401169 · « **Reply #3892 on:** January 09, 2024, 05:53:50 pm »

David, I had a small problem - when installing firmware 1.13.2 on one station the firmware installed normally, but on the second the hard vault screen popped up. Previously, I had 1.13.0 on both. The one that works in t12 mode, the firmware installed normally, but the one that works in c245 mode, the firmware caused an error, I had to roll back to 1.13.0. Both stations, although custom, are assembled from the same parts, the only difference is in the operating mode. Although I am still inclined to believe that the problem is in the hardware, although strangely, on the second station the new version was installed and works without problems.

DavidAlfa · « **Reply #3893 on:** January 09, 2024, 06:57:43 pm »

Do you know all the information shown in the hard fault screen is for something, not just made to look fancy? It's the only hint I have to track a fault.
How many times do I need to repeat it...?

Anyone having an error screen, post:
- Firmware version and type (Ksger V2, etc).
- The error message, or a screen picture if it's hard fault.
- The result of flash test attached in few post back in Page 154.

It's strange because the differences between the different 1.13.x versions are minimal.
Can't tell until I see the hard fault screen.

dcore · « **Reply #3894 on:** January 10, 2024, 10:20:50 am »

#1 - KSGER v3 OLED:
STM32F103RCT6, came with the board.
CPUID: 411FC231
Size: 65535
Page: 1024

v1.13.2-beta works well, tested with C245.
I noticed that ST-LINK/Cube shows 2K page and 512K flash for this unit.

: Device ID:0x414
: Device family :STM32F10xx High-density

-----
#2 - KSGER v3 OLED:
STM32F102R8T6, came with the board.
CPUID: 411FC231
Size: 65535
Page: 1024

v1.13.2-beta works well, tested with C245.
ST-LINK/Cube shows 1K page and 128K flash for this unit.
: Device ID:0x410
: Device family :STM32F10xx Medium-density

-----
#3 - KSGER v3 OLED:
STM32F103RET6, repaired/replaced.
CPUID: 411FC231
Size: 512
Page: 2048

v1.13.2-beta works well, tested with C245.
ST-LINK/Cube shows 2K page and 512K flash for this unit.
: Device ID:0x414
: Device flash Size : 512KBytes
: Device family :STM32F10xx High-density

-----

Cold boost is ok.
Thank you!

DavidAlfa · « **Reply #3895 on:** January 10, 2024, 11:11:42 am »

MCUs reporting 65535 are 100% fakes.
If the flash was really 2K the firmware would not work, causing hardfault or settings error bottloop.

Hunghanh2009 · « **Reply #3896 on:** January 10, 2024, 02:25:50 pm »

Hi daivd.

STM32F103CBT6
CPUID: 411FC231
SIZE: 128 KB
PAGE : 1024 Bytes
Clone test: 20036410

Green board Version KSGER_v3_OLED v1.13.2 has a hardfault error.

Black board Version KSGER_v3_OLED v1.13.2 works stably.

Both MCUs have the same parameters for flash test and clone test.
But the engraved shape on the MCU seems a bit different.

Looks like this error is related to the MCU, right David?

DavidAlfa · « **Reply #3897 on:** January 10, 2024, 11:20:49 pm »

Yes, it seems a problem with the way that stm32 clone works, it's crashing when resetting the tips to default.
We could try forcing the page size to 2KB and see what happens.

Read the failing stm32 and post the .bin file, it's strange that it's crashing at FLASH_WaitForLastOperation.
I wonder if that clone has a much larger page size and it's erasing part of the firmware.

Polf · « **Reply #3898 on:** January 14, 2024, 12:05:10 pm »

Dear David, I am using your v1.13.3 firmware for the KSGER V.2 and V.3 controllers. There were no errors after applying the firmware. I have a question, maybe I should have asked it earlier. As before, there is a Def temp item in Iron menu. If you turn on the controller for the first time after flashing, the soldering iron heats up to this temperature. If you change the temperature later, it will be saved for the next turn on. Perhaps this menu item is no longer needed?

DavidAlfa · « **Reply #3899 on:** January 14, 2024, 08:37:50 pm »

Yes, I also thought the other day, will eventually be deleted


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: CFW for KSGER/Quicko STM32 Soldering Stations (Read 666315 times)

Share me