91–100 of 119 posts
Earlier quoted context omitted.
Queued for later.
Obviously with a certain max depth, most probably of 1, meaning you're still missing repeated interrupts.
It lists `USB Device` as well. This could be a really accessible device for building hybrid usb/bt devices, like wireless keyboards.
It seems it only supports CDC and some JTAG mode. For keyboards and such, the USB stack should support HID which doesn't seem to be the case here. In other words, they've implemented a USB 1.1 FS stack just so far to make intermediary USB2UART chips like FTDI and CP2102 redundant.
Earlier quoted context omitted.
That is going to put a dent in ARMs revenue. Even if that particular chip isn't a big seller, it means ST now has a drop-in replacement for ARM in their other SoCs. Soon people will realize that ISA is often irrelevant, but the peripherals, libraries, and tools are.
I'm not so sure. About ISA there is this : https://news.ycombinator.com/item?id=24958423
Earlier quoted context omitted.
I2S is also handy for bit-banging protocols without using CPU time—it's popular to use it on the ESP* chips to drive WS2812B and similar strips without hassle.
Curious question, is it just I2S that is used for this purpose? I'd assume you could use any serial protocol for bit banging purposes right?
Earlier quoted context omitted.
It’s all about the software & documentation. There’s lots of “competitors” to esp32, pretty much none of them except STM have the software for developers, which makes their offerings close to useless. The only way to gain critical mass is relentless deep commitment to developer tools/libraries and documentation. In many cases these competitors actually try to hide their documentation and keep secret how their chips w…
Bouffalo apparently has been giving Pine64 the necessary documentation access to make their initiative for a full open software stack workable: https://www.pine64.org/2020/10/28/nutcracker-challenge-blob-... Edit: a better reference is Bouffalo’s GitHub org showing the docs and mostly open code: https://github.com/bouffalolab
Earlier quoted context omitted.
It’s all about the software & documentation. There’s lots of “competitors” to esp32, pretty much none of them except STM have the software for developers, which makes their offerings close to useless. The only way to gain critical mass is relentless deep commitment to developer tools/libraries and documentation. In many cases these competitors actually try to hide their documentation and keep secret how their chips w…
> gain critical mass is relentless deep commitment to developer tools/libraries and documentation Which seems (IMHO) why the likes of Texas Instruments has failed. They've made a few attempts at jumping on the IoT bandwagon over the last decade and should have been in a perfect position to capitalize on the huge uptake but it just didn't fit their profit margin goals I'm guessing.
Rust is much easier to use on RISC-V [1] than on ESP32 [2]. I'm looking forward to making some small projects with this chip, assuming the software is usable. [1] https://doc.rust-lang.org/nightly/rustc/platform-support.htm... [2] https://github.com/MabezDev/xtensa-rust-quickstart
Eicks! 10GB of disk space and 6GB+ RAM for the compiler? That’s seems crazy. No compiling that on most RPi’s. Maybe the cranelift project will help over time.
> Pricing will also be similar to ESP8266. How can they possibly sell these chips at these prices? This is impossibly cheap. You can’t even accuse them of trying to flood and control the market because they already own the market!
Earlier quoted context omitted.
Eicks! 10GB of disk space and 6GB+ RAM for the compiler? That’s seems crazy. No compiling that on most RPi’s. Maybe the cranelift project will help over time.
That's for compiling the compiler.
Earlier quoted context omitted.
Wow, that's a much bigger differential than my experience. Are you comfortable sharing the general region so I can avoid it?
I have been involved in embedded systems for more than 25 years now, and I barely do "pure" embedded development these days. That is projects that comprise only designing a specific PCB hardware, or writing the firmware drivers and top level application for them. Except for a couple of years I have resided mostly outside of California, but when doing consulting I have mostly engaged with companies in the Bay area. In…