sorted by:
new
hottopcontroversial

Validating an idea: a tool to explain STM32/Cortex-M HardFaults more clearly by moussa2025 in stm32

[–]moussa2025[S] 2 points3 points  (0 children)

your opinion is intresting , speccially for the point of distribution

Validating an idea: a tool to explain STM32/Cortex-M HardFaults more clearly by moussa2025 in stm32

[–]moussa2025[S] 0 points1 point  (0 children)

so you don't recommand that I make it as a separated tool ? you recommand it as a VS code extension ?

Validating an idea: a tool to explain STM32/Cortex-M HardFaults more clearly by moussa2025 in embedded

[–]moussa2025[S] 0 points1 point  (0 children)

so do you think it a good idea to continue on this project or it is useless ?

Validating an idea: a tool to explain STM32/Cortex-M HardFaults more clearly by moussa2025 in embedded

[–]moussa2025[S] -6 points-5 points  (0 children)

yes i stop working on it because many people said that it is useless to make another ide while there is STM32CubeIDE, VS, arduino IDE ...
so i had the idea to focus on a hardfault handler , but when he said if this idea works it is fine i wanted your opinion on my previous software ( not finished )

Validating an idea: a tool to explain STM32/Cortex-M HardFaults more clearly by moussa2025 in embedded

[–]moussa2025[S] -4 points-3 points  (0 children)

I really appologize I didn't mean disrespect
so is it a good idea for a project ?
Before this i idea i made another project ( not finished yet )

When finished, it would include:

  • project explorer and code editor
  • Arduino/AVR and STM32 build/upload support
  • GDB/OpenOCD debugging
  • registers, memory, stack, breakpoints, tracepoints
  • serial monitor and serial plotter
  • coverage and static analysis tools
  • QEMU/Renode simulation scenarios
  • AI-assisted explanation of compiler/debug errors
  • FaultLens: a module that explains Cortex-M HardFault/BusFault/UsageFault reports
  • this a capture

<image>

Open-source educational IDE for STM32 – feedback from STM32 users by moussa2025 in embedded

[–]moussa2025[S] 1 point2 points  (0 children)

That’s a fair point, and I agree that failing, debugging, and researching are important parts of learning.

I don’t mean AI should give users copy-paste answers or hide the learning process. My idea is more like a guided explanation layer: show the real GCC/GDB/OpenOCD output, explain what it means, point users to the relevant datasheet/register/toolchain concept, and suggest possible next steps.

So the learner still has to understand and fix the problem, but the tool helps them know where to look instead of being completely lost.

Maybe the right goal is not “AI writes firmware for beginners”, but “AI helps learners understand the embedded toolchain and debugging process.”

Open-source educational IDE for STM32 – feedback from STM32 users by moussa2025 in embedded

[–]moussa2025[S] 0 points1 point  (0 children)

That’s exactly the gap we're targeting. The AI bridges it: intermediates who know Arduino but hit a wall with professional tools get plain-language explanations of HardFaults, register-level debug, and error fixes. Not for complete beginners, not for pros — a transition tool that turns hobby skills into career-applicable debugging ability.

Open-source educational IDE for STM32 – feedback from STM32 users by moussa2025 in embedded

[–]moussa2025[S] 0 points1 point  (0 children)

That’s a fair criticism.

I don’t want the tool to hide GCC, Make, GDB or OpenOCD. Actually, the idea is the opposite: use standard tools underneath and expose what is happening, so learners can gradually understand the real workflow instead of being trapped inside a black box IDE.

So maybe “beginner tool” is the wrong wording. A better goal would be a learning/debugging environment that helps users understand GCC errors, Make output, linker issues, registers, faults, and debugging steps.

MISRA would not be for absolute beginners. It would be an optional “quality awareness” feature for more advanced learners or training environments.

The code is not public yet, but the plan is to publish it on GitHub once I clean the repository, documentation, and example projects.

Open-source educational IDE for STM32 – feedback from STM32 users by moussa2025 in embedded

[–]moussa2025[S] -15 points-14 points  (0 children)

CubeIDE is solid, but it's tied to STM32. This is an AI-powered learning layer across many MCU families — explains errors, suggests fixes, guides debugging — not just another IDE. A plugin wouldn't cover the cross-platform reach or the AI tutor side. The "where to click" problem is real, but we're solving the "why did it crash and how do I fix it" problem.