ESP stuff is so damn cheap and capable now I'm not sure what you would use Arduino for these days.
Don't look at just the specs. You also need to look at the board design and programming environment. I've used the ESP32 native tools and they are a lot more complex than Arduino. But I'm an embedded firmware developer, so it's kind of what I expect. But I used an Arduino, with 5V tolerant outputs, to light up Halloween costumes for years. I do it in 1 page of code that's I write in their IDE. I don't have to set up…
Qualcomm to acquire Arduino
481–490 of 553 posts
Re: Qualcomm to acquire Arduino
#482Earlier quoted context omitted.
People are making so much of this when it seems so much simpler. Qualcomm likes buying high-margin businesses, and Arduino is a high-margin business. Gross margin on their boards is over 90% (hence why you can buy a Chinese clone of a $30 board for $3) and this trend shows no signs of slowing down. The TI equivalent of the $30 Arduino Uno is $5, and it's a true gateway product.
What's the TI equivalent?
Re: Qualcomm to acquire Arduino
#483Earlier quoted context omitted.
> A competent engineer designing a devkit as simple as an arduino needs about 1 day of work. Hah! I like to underestimate scope as well, but this is really something else. Definitely a competent engineer could make something like this. But a couple of months maybe. You won't even read the documentation for the chip in a day.
Have you seen the schematics for these boards? They are exceptionally simple. Many devkits are much more complicated. I have actually done embedded engineering in the past and I was being generous with "a day." Skimming a datasheet is a skill and it certainly will not take a day to get the information you need off of it.
Even the simplest peripherals can bite back if you are not careful and you don't test the edge cases. AVR's are indeed quite simple, but if you try to build stuff other people will use, things need to be polished.
I actually do embedded engineering. I'm doing it right now! More on the SW side than the PCB design side, and, again, this is quite an exaggeration from your side, saying you could do it in a day.
Re: Qualcomm to acquire Arduino
#484Re: Qualcomm to acquire Arduino
#485Earlier quoted context omitted.
It’s unlikely that Qualcomm purchased them for their revenue or margins, which to Qualcomm’s scale are basically irrelevant.
So it sounds like again, this purchase makes no sense from anyone's perspective unless arduino are suckers.
Re: Qualcomm to acquire Arduino
#486Re: Qualcomm to acquire Arduino
#487Re: Qualcomm to acquire Arduino
#488Earlier quoted context omitted.
Have you seen the schematics for these boards? They are exceptionally simple. Many devkits are much more complicated. I have actually done embedded engineering in the past and I was being generous with "a day." Skimming a datasheet is a skill and it certainly will not take a day to get the information you need off of it.
If you mean the HW alone... Still over a day. If you mean the software to go along it, a couple orders of magnitude more. Even the simplest peripherals can bite back if you are not careful and you don't test the edge cases. AVR's are indeed quite simple, but if you try to build stuff other people will use, things need to be polished. I actually do embedded engineering. I'm doing it right now! More on the SW side than…
Re: Qualcomm to acquire Arduino
#489I'm not sure how it is possible to compete against the RP2040/RP2050 at this point: quality, great programming environment, awesome hardware specs, cheap.
Yeah, I just did a project at work with an RP2040 and was really impressed with the Pico SDK. It hits a sweet spot in between ST’s insanity and Arduino’s easy-but-not-powerful tradeoff. No crazy code generation, going from 0 to blinky is quick, but also going from blinky to DMA’s and interrupts is also a breeze. I will say that I think the hardware peripherals in STM32’s are miles ahead, and PIO’s don’t necessarily m…