CFW for KSGER/Quicko STM32 Soldering Stations

[DavidAlfa]

Does this one have the same issue as well? Can't test the F072 anymore.

[ricktendo]

Btw, because you have a battery installed you can enable the "HAS_BATTERY" option in the config.h to have the option to remember the last used tip temperature.

What are the chances of adding HAS_BATTERY toggle in Iron settings?

[TheInvisible]

Does this one have the same issue as well?

Well, not the same... but a blank screen and no visible function.

[TheInvisible]

I've tested some older builds. The latest .bin which works on my Quicko STM32F072 ist the one from Jun 2 2022.

[M-Reimer]

I've received my station some days ago and to my surprise it has a STM32 inside.

There is no guarantee, but I've ordered this one: https://de.aliexpress.com/item/4000055007842.html in the variant without any handle (I don't like that "screw on" handle and ordered another handle separately). Mine came with a "real" STM32 MCU.

[DavidAlfa]

Is it working for everyone with F103 mcus? Ksger, Quicko, etc?

Edit: Mein bad! It seems I miss clicked the wrong folder und uploaded den Quicko F103 build.
Please re-download the zip file and try again!

[bozo]

It works ok.

[ygi]

Works great for my Ksger 1.5 with F103.

BTW, assuming HAS_BATTERY is set, is the selected tip also saved in backup registers or still written in flash? I remember KocsisV mentioning he could do that when you were discussing flash wear and now I'm wondering if the idea's been scrapped or implemented (or just on the todo list).

[KocsisV]

is the selected tip also saved in backup registers

Yes, the selected tip, last temperature and profile is saved to the backup registers. You have to enable the "remember x" options in the System settings (by default its disabled): https://github.com/KocsisV/stm32_soldering_iron_controller/blob/updateProjectStructure/Readme_files/Operation.md#system, scroll down to the "Remember last profile/tip/temp" description.

[ygi]

Nice, thanks

[TheInvisible]

Edit: Mein bad! It seems I miss clicked the wrong folder und uploaded den Quicko F103 build.
Please re-download the zip file and try again!

Ok, now there's the "HARD FAULT SYSTEM HALTET..." message again.

[KocsisV]

Can you set up the development environment and debug the code by placing a breakpoint to the fault handler and providing a stack trace?

[DavidAlfa]

Pretty sure it's related to the tip number and settings partition increase, will make some tests later...

Edit: Try this

[TheInvisible]

Sorry, but i get the error message again.

[TheInvisible]

Can you set up the development environment and debug the code by placing a breakpoint to the fault handler and providing a stack trace?

Ok, i've setup the build environment and i'm be able to compile the code without errors[1]. For debuging, compiler optimization needs be turned on, but ist too late now... I'll take a look at it tomorrow.

[1] in "addon_switch_off_reminder_settings_screen.c" "#include "addon_SWITCH_OFF_REMINDER_settings_screen.h"" should be "#include "addon_switch_off_reminder_settings_screen.h"" otherwise the compiler didn't find that header file on my linux machine...

[vqtrong]

I've received my station some days ago and to my surprise it has a STM32 inside.

There is no guarantee, but I've ordered this one: https://de.aliexpress.com/item/4000055007842.html in the variant without any handle (I don't like that "screw on" handle and ordered another handle separately). Mine came with a "real" STM32 MCU.

That's surprising with a "real" STM32 !? a CKS under STM32 label?

[wickated]

I've received my station some days ago and to my surprise it has a STM32 inside.

There is no guarantee, but I've ordered this one: https://de.aliexpress.com/item/4000055007842.html in the variant without any handle (I don't like that "screw on" handle and ordered another handle separately). Mine came with a "real" STM32 MCU.

That's surprising with a "real" STM32 !? a CKS under STM32 label?

just a very old batch from dusty warehouse.

[sevgiduvari_7]

deividAlfa Delete old binaries ?

[DavidAlfa]

Why do you need them?

You still have the history:

ksger v1.5
ksger v2
ksger v3
quicko f072
quicko f103

[KocsisV]

Ups, I missed your post sorry.
Could be done, I added it to the todo list. Its not that "nice" if its an user selectable option during runtime, as it requires hardware initialization plus different behavior during startup. Plus if someone sets it to on but do not have a battery installed it will complain on every startup.

[DavidAlfa]

Is this F072 build still failing?

[DavidAlfa]

Well, as nobody is trying, I just added a link to the Jun 02 build, mentioning the issue in the Quicko F072 section of the Readme, use that for now.

[AndyC]

I had some time to check out some of the newer builds, the "Switch off reminder" was a nice addition.
I updated the Swedish translation and checked so everything looked good on screen.

During this I think I found a bug: under Calibration/Settings, I can't set the Zero if the language is set to Swedish or Russian.
When pressing the button the text just flashes briefly and the "zero" is not measured or updated.
This appear to have changed somewhere between the April 5 and April 30 builds. (April 5 build = OK, April 30 = NOT)

[DavidAlfa]

Thanks for reporting. The projects is almost stalled since I'm getting little to none feedback.
Testing every combination myself would take a lot of time, not realistic...
If anyone with a STM32F072 allows me to remotely debug the code, trying to find the current issue with it, would be nice!

AndyC, not a bug, it's intentional to make these people life's harder, that's my xenophobia kicking in  .
Confirmed here, so strange the language affects the program behaviour, shouldn't at all, it's just an array of text strings .
Will check it!

Edit:I think I got it. It worked removing optimizations, so it had to be some undefined behavior.
The reserved char array for the zero string was 16 bytes long because I thought is as normal ASCII, forgetting special chars use 2 bytes (unicode/UTF-8), so it was overflowing and writing over other variables.

Edit2: v1.02 Released. Should be working now.

[DavidAlfa]

Perhabs someone can help here.
I want to debug the stack when a hardfault happens, so I can show the program counter in the display.
That way I could check the map file disassembly and see where it's crashing, greatly easing the debugging process, like currently happenning with Quicko STM32F072.
I can also read SCB->BFAR, thus easily checking if an invalid address was accessed.

This seems interesting:
https://community.st.com/s/question/0D50X0000BxwhEhSQI/my-stm32h743vi-application-runs-to-a-debug-instruction-in-the-startup-code

However the startup file is not happy with PROC and EXPORT lines. Perhabs a Keil-specific syntax?

Code: [Select]

HardFault_Handler\
                PROC
                EXPORT  HardFault_Handler
 
                ; Determine correct stack
 
                TST     lr, #4
                ITE     EQ
                MRSEQ   R0, MSP         ; Read MSP (Main)
                MRSNE   R0, PSP         ; Read PSP (Process)
 
                MOV     R1, R4
                MOV     R2, R5
                MOV     R3, R6
 
                EXTERN  hard_fault_handler_c
                B       hard_fault_handler_c
                ENDP ; sourcer32@gmail.com

The rest is plain easy, the custom HardFault handler is called and then you get the values.