I couldn't even get a basic task done with it in 5 minutes. At this point I don't want to learn it, because it broke my 5 minute rule in terms of usability.
KEIL 5 FRAMEWORK CUBEMX.PDSC IS MISSING CODE
Maybe you had too many components configured into your build (were you paring down with menuconfig?)Īs far as my expertise, I know nothing about Stm32CubeIDE except for after like 5-10 minutes of getting absolutely nowhere with it just trying to interface with an ST7735 (where do I even drop the code for the library i download from github?) I just got sick of it. It has its problems but compile times are better for me than they are with the ARM toolchains I've (tried to) used. That's funny that you say that about the ESP-IDF. It's a great learning experience, but it's not maintainable and it's really inefficient. If you really want to code bare-metal, go for it. But, if you do the work for a living, the emphasis is never on being "hardcore." It's on getting the work out quickly and fixing it when it breaks. You'll see a lot of people in this sub who like to claim that they do all their dev in Vim and all their compiling with GCC and homespun makefiles. And god help you if you change anything, because it takes 2 or 3 minutes to rebuild the build scripts, and then another 2 or 3 minutes for a clean build. You end up 3 layers deep in their curses app trying to turn things on and off. And the access it provides is generally extremely high level, with a very serious amount of abstraction between you and the chip.ĮSP-IDF, which I used extensively at my last job for about 2 years, is a shit-show. Now, though, in ARM-Cortex, that stuff is extremely cumbersome.Īrduino really only lets you scratch the surface of what's possible with STM32. In PIC, it was actually pretty reasonable to configure the chip in assembly, because it was so straightforward. Manually doing those things was pretty manageable in older architectures. After the first twenty minutes of messing around with the pinout tool, you're stuck in a text editor like everybody else. There's no code-by-gui, and there's no drag-and-pray. There's a pin configurator, a visual clock configurator, and a couple of tools to help you set up things like timers and interrupts.
I just feel like some of your criticisms of programming environments are a bit off the mark.įirst, there's really not much "visual coding" in STM32CubeIDE. It's hard to respond to this, because I don't want to come across as hostile or condescending, and I don't know your level of expertise. Is there some kind of documentation for actual coding against the framework that doesn't require me to use ridiculous drag and drop code generators or is there a framework I should be using for ARM devices like this that *will* allow me to code? I don't want to use any silly visual "coding", or be stuck with some craptastic IDE. I want to code STM32's with just C++, preferably under PlatformIO or just VS Code with some scripts.
KEIL 5 FRAMEWORK CUBEMX.PDSC IS MISSING HOW TO
I've looked on their forums for how to do this and the only tutorial requires you to launch STM32CubeIDE and generate code for it and then copy that code into PlatformIO.Īnd I'm not willing to use STM32CubeIDE to write code in, because the workflow is unacceptable to me.
I want something I can import a library from github into, and code a main.cpp against.
0 kommentar(er)
