41–50 of 151 posts
Oh neat. Zigbee support. I wonder if I at some point can create low power devices with EspHome for home assistant. I assume this should use less power than connecting to wifi?
Oh neat. Zigbee support. I wonder if I at some point can create low power devices with EspHome for home assistant. I assume this should use less power than connecting to wifi?
I believe this is the first ESP to gain Ethernet capability? I totally wish that a board would come with PoE… Because as it is right now, powering a fleet of those with USB power supplies is annoying as fsck…
Nah, ESP32's have had ethernet capability for a while and ESP-IDF supports it well. I've been using one I built for 5+ years now. Unfortunately RMII (ethernet phy) interface takes up a lot of the GPIO pins. This part looks like it'll remedy that issue. There's two ESP32 boards that have been around for a while with PoE: - https://www.tme.com/us/en-us/details/esp32-poe/development-k... - https://wesp32.com/ I'm more h…
I believe this is the first ESP to gain Ethernet capability? I totally wish that a board would come with PoE… Because as it is right now, powering a fleet of those with USB power supplies is annoying as fsck…
> Because as it is right now, powering a fleet of those with USB power supplies is annoying as fsck… Therefore, wifi is more convenient than ethernet. You don't need long cables, just a local power source.
Which means batteries that have to be replaced and maintained or cables... So ethernet with PoE or even better SPE (single pair Ethernet) with PoDL (power over data lines which is PoE for SPE) is the best from my point of view
I'm puzzled by Espressif's naming here. We had the ESP32-S3, so "S31" sounds like "S3, variant 1," but this part doesn't really look like a simple S3 variant. And then there's an ESP32-E22, but no E21 or even a plain E2 anywhere. Edit: found an article explaining some of their naming logic, and said that the SoC naming will get its follow-up article, but sadly it never happened. https://developer.espressif.com/blog/2…
> high-speed 250 MHz 8-bit DDR PSRAM with concurrent flash and PSRAM access This is perhaps lost in the noise but IMO a large deal. PSRAM starting to get serious bandwidth.
I wonder if it will be possible to (ab)use the faster PSRAM interface on the ESP32-S31 as a general purpose 8-bit parallel interface, eg. for ADCs...
Earlier quoted context omitted.
> Because as it is right now, powering a fleet of those with USB power supplies is annoying as fsck… Therefore, wifi is more convenient than ethernet. You don't need long cables, just a local power source.
> You don't need long cables, just a local power source Which means batteries that have to be replaced and maintained or cables... So ethernet with PoE or even better SPE (single pair Ethernet) with PoDL (power over data lines which is PoE for SPE) is the best from my point of view
Both solutions require 1 cable per device, but the first solution would require only short and thin cables, and the second solution would require very long cables which I don't know even how to do properly without milling my walls.
Although, I'd like to seem some non-paid blogger head-to-head reviews benchmarking instruction cycle efficiency per power of comparable Arm vs. ESP32 Xtensa LX6* and RISC-V parts.
* Metric crap tons of WROOM parts are still available and ancient ESP8266 probably too.
Since the Snowden leaks in 2013, it just doesn't make sense that *any* foreign customers would put US technology inside their firewall. But they do. It shocks me even more that any Western customer would do the same with network-connected Chinese chips. But we do. The Espressif chips are truly incredible value, but what are we doing here? Is there any doubt that these don't represent a major attack surface if a confl…
It’s not like creating a chip gives you unfettered access to it. You _can_ add 0-day flaws and backdoors, but these can be discovered, leaked, etc. Has there been any case of such a backdoor built in consumer chips like theses? I’m not talking about CIA ops like snowden described, that’s supply chain interception. I mean, has anybody ever found such a backdoor?
- Early (ESP8622) MCUs had weak security, implementation flaws, and a host of issues that meant an attacker could hijack and maintain control of devices via OTA updates.
- Their chosen way to implement these systems makes them more vulnerable. They explicitly reduce hardware footprint by moving functionality from hardware to software.
- More recently there was some controversy about hidden commands in the BT chain, which were claimed to be debug functionality. Even if you take them at their word, that speaks volumes about their practices and procedures.
That’s the main problem with these kinds of backdoors, you can never really prove they exist because there’s reasonable alternative explanations since bugs do happen.
What I can tell you is that every single company I’ve worked which took security seriously (medical implants, critical safety industry) not only banned their use on our designs, they banned the presence of ESP32 based devices on our networks.