|
I absolutely agree! I tried using STM32CubeIDE while working with a custom board using the STM32 processor. The libraries were either horrible or non-existent. We ended up hiring an electronics engineer to develop a specific framework to use with the design of the board from scratch. I don't see how this IDE and framework are used in a professional setting. It's like it's designed to teach rather than produce.
"When you are dead, you won't even know that you are dead. It's a pain only felt by others; same thing when you are stupid."
Ignorant - An individual without knowledge, but is willing to learn.
Stupid - An individual without knowledge and is incapable of learning.
Idiot - An individual without knowledge and allows social media to do the thinking for them.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
Hello,
I am using the MS visual studio (2019) with some external tools for compiling and linking. The tools are the .bat file invoking the GNU compiler. I am using the same construction also for the AVR processor. It is working good enough (after my opinion). The main reason to implement this system was to keep the same development tool for any application.
If you need more details, contact me.
Emil Motolici
|
|
|
|
|
Are you using Azure Resource Manager scripts?
I found the Azure CLI to be a lot shorter and more readable 
Seriously though, we're running out of abbreviations and this one always gets me 
|
|
|
|
|
Oh heck no. ARM processors. 
Real programmers use butterflies
|
|
|
|
|
I know 
|
|
|
|
|
I always assume you're messing with me, but I reply as though you're not just to mess with you.
Real programmers use butterflies
|
|
|
|
|
The first problem is frameworks that are cluttered with crap that hardly anyone uses. Why? Because its architects are either clueless or actually think they're doing users a favor.
There has to be a use case for everything in a framework. If it isn't going to be used as soon as it's added, it should only go in if there are likely-to-occur scenarios where it would clearly be useful.
The other problem affects the whole industry. The hardware weenies do too good a job delivering faster processors, more memory, and more disk space. Thoughtless developers then piss it away because it's all good if it runs in less than an hour.
|
|
|
|
|
In their defense a lot of the crap is for supporting hardware that the device has, even if you won't be using most of it (they don't know in advance what you will use) - but the ESP-IDF has a "menuconfig" script that will remove headers for components you aren't using to shorten the compile times.
IoT doesn't suffer from the "free lunch problem" you describe. Every cycle and byte counts. You're dealing with 80kB of RAM and 256kB of non-volatile flash program space and that's being generous. Some have far less.
Real programmers use butterflies
|
|
|
|
|
Maybe that'll be the blessing of IOT, that those who work on it will learn to think about performance.
|
|
|
|
|
Its because we have to think of performance, cycles, milliamp hours, that I choose to play with uControllers.
Protected mode made the x86 landscape considerably less fun. Pre-emptive multi-tasking? Meh, why even bother anymore! I'll just play games on it.
|
|
|
|
|
I don't want to worry about cycles or milliamp hours. But I'm pretty much with you on the rest.
Well, except that I rarely play games.
|
|
|
|
|
I completely agree. 25% of the framework probably suffices for the bulk of the problems we're trying to solve. It's literally as if the framework architects don't understand SOLID.
Developer: "I'm going to Antarctica on a scientific expedition."
Framework (a.k.a. 'Mom'): "I've packed you some shorts and tee-shirts, in case you get some warm weather."
|
|
|
|
|
Another problem with frameworks is that their surface-to-volume ratio keeps getting worse because of the unwillingness to deprecate anything, let alone make "breaking changes" that force users to update their code.
|
|
|
|
|
Never thought C++ was usable for developing UI's.
I use C# and VS compiles my packages to ARM, ARM64, x86 and x64.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
I seriously doubt it runs on an Arm Cortex-M0 with 80kb of RAM and 256kB of flash.
ARM Cortex-As are a much different animal. They're basically fancy smartphone or surface PC CPUs.
Real programmers use butterflies
|
|
|
|
|
Building ships in bottles.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
My smart watch is a ship in a bottle?
Real programmers use butterflies
|
|
|
|
|
People still use C++?
*ducks*
|
|
|
|
|
*sideeyes you*
Real programmers use butterflies
|
|
|
|
|
|
Yes, of course. I will never try to write firmware in JavaScript... Actually, I prefer C.
|
|
|
|
|
Yeah, I know. I'm just messing. TBH I thought a lot of that is Java now though. Goodness knows why
|
|
|
|
|
I am working with STM32 for several years. Looks like every new release has more and more bugs, which are never fixed.
On the other hand, new CubeIDE version has super-ugly new look. Probably they have too much UI programmers, but not enough hadrware programmers.
CubeMX code generator produces non-working code. But if you don't want code generator, you can write everything from scratch. All code samples are written from scratch without CubeMX.
CubeIDE itself is OK, it is Eclipse-based and makes its work.
Starting a new project now, I think I will look for another options. If looks like STM moves in wrong direction.
|
|
|
|
|
I really like the ESP32s. The ESP-IDF is nice to code in - you can use fopen() and printf() and such, though I've had some issues with the SPI, but SPI works great under the Arduino framework with it.
The achilles heel is it's kind of quirky and draws more power than some other offerings. However, again, coding with it is just great compared to the STM32, IMO.
They are also powerful for an IoT device. The minimum configuration is single core, 360k or so of RAM and 4MB of NVS flash. A typical configuration has 520k of RAM and two cores. They have generous IO, with multiple SPI and I2C controllers, a ton of built in widgets including bluetooth and wifi, touch sensors, a magnetic field detector, ADCs (though a bit dodgy) and DACs, and all the pins are remappable in software.
They really are fantastic little machines.
Real programmers use butterflies
|
|
|
|
|
It could be worse. It could support only C with a disastrous code editor. Cypress, can you hear me?
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
