stm32_soldering_iron_controller
mongoose-os
stm32_soldering_iron_controller | mongoose-os | |
---|---|---|
4 | 2 | |
374 | 2,473 | |
- | 0.4% | |
9.4 | 1.5 | |
26 days ago | 5 months ago | |
C | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
stm32_soldering_iron_controller
-
IronOS: Open-source soldering iron firmware
There's also an open-source firmware for STM32 based soldering irons like the T12 soldering stations that are pretty commonly cloned.
https://github.com/deividAlfa/stm32_soldering_iron_controlle...
I've had one of the KSGER units for a few years now that I absolutely love. Uses Hakko style tips, heats quickly, holds temp well.
-
Seeking advice on Quecoo t12-959
•Has anybody been able to flash the custom firmware?
-
How do i flash a firmware onto the Quicko soldering station?
I googled and found https://github.com/deividAlfa/stm32_soldering_iron_controller.
-
Identifying formatting and changing image of boot screen in CPP (I think CPP)
This file (https://github.com/deividAlfa/stm32_soldering_iron_controller/blob/master/Drivers/graphics/gui/screens/boot_screen.c) has an image in it, I'd like to replace it with one a little more appealing. I have the original image, and my replacement, I've been using CPP image converters (like https://javl.github.io/image2cpp/) and re-flashing the device but the image contains artifacts. Is there a way to identify how the original image is displayed and replace it?
mongoose-os
-
Toit – A Language Designed for Microcontrollers
As long as Toit is licensed under the GNU Lesser General Public License v2.1, I am unlikely to consider using it. By contrast, MicroPython is licensed under the MIT License (MIT).
As others have noted, Toit seems like a bad name. I suppose non-French speakers will tend to inadvertently mispronounce Toit.
Getting traction is hard. In my opinion, having a restrictive license and a bad name make it less likely Toit will gain traction. Finally, Toit licensing reminds me of Mongoose OS https://github.com/cesanta/mongoose-os#mongoose-os---an-iot-....
-
CISA Advisory (ICSA-21-119-04) - CyberHoot
Cesanta Software mongooses – Update available
What are some alternatives?
IronOS - Open Source Soldering Iron firmware
FreeRTOS-Kernel - FreeRTOS kernel files only, submoduled into https://github.com/FreeRTOS/FreeRTOS and various other repos.
stm32-bootloader - Customizable Bootloader for STM32 microcontrollers. This example demonstrates how to perform in-application-programming of a firmware located on an external SD card with FAT32 file system.
zephyr - Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
NanoVNA - Very Tiny Palmtop Vector Network Analyzer
RIOT - RIOT - The friendly OS for IoT
AxxSolder - STM32 Based soldering station for JBC cartridges
mbed-os - Arm Mbed OS is a platform operating system designed for the internet of things
flipperzero-firmware - Flipper Zero firmware source code
RFLink - RFLink for ESP, with MQTT client
stm32_soldering_iron_controlle
esp32-snippets - Sample ESP32 snippets and code fragments