Delete post
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-19 1:55 AM - edited ‎2024-04-25 4:29 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-19 1:59 AM
@Bonnie wrote:I'm a beginner in doing embedded coding and I don't want to use STM32cubeMX for code generation ?
Why not?
It's exactly things like this where CubeMX really shines!
The graphic interface is probably the clearest way to see all the timing options, and how they interact.
Even if you're not actually going to use the code that it generates, you could use the generated code as the basis for your own code ...
A complex system designed from scratch never works and cannot be patched up to make it work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-19 2:04 AM
I went on the assumption that it'll be better for me to learn how the firmware works through going through each line rather than have a program that generates the code for me to give me a better understanding on how to program the chips better.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-19 2:14 AM
That might be true on a simple 8-bit microcontroller, but I think, at the level of STM32 chips, there is so much complexity that it's going to be more a hindrance than a help.
eg, just getting the clocks set up involves writing dozens of registers, checking statuses, etc ...
This is exactly why all the Cortex-class chipmakers now have something like CubeMX
A complex system designed from scratch never works and cannot be patched up to make it work.
