Tech Explained: eFPGAs

I’ve been exploring a few SoCs for a new project, and I ran across QuickLogic’s QuickFeather board with the EOS S3. It has an Arm Cortex M4F processor with an embedded FPGA. That made me realize many folks would benefit from a quick explainer on what an embedded FPGA is. Here it goes.

An eFPGA is reconfigurable hardware inside the chip. Think LEGO you can rearrange. You load a bitstream from flash at boot, control it like any other peripheral, and it runs next to the CPU with very low delay. You can keep it internal for accelerators or route its signals to pins through the normal pinmux.

eFPGA

Why this helps you? It gives you hardware speed for the complex parts of your design that keep changing. Think custom sensor timing, packet parsing, digital filters, cryptography, or tiny ML components. You move those time-consuming parts into hardware, and you free up clock cycles on your main processor firmware. Since it’s in hardware, responses come in deterministic time, it makes firmware less messy. Think of it as a programmable coprocessor which you can change into anything. You use it when you need tight timing, or for features you plan to revise after launch or potentially upgrades to certain algorithm blocks. It also helps when you want to try new ideas in the field without a new chip spin without massively worrying about what it does to your firmware.

Please don’t use it for simple projects. Your normal MCU with firmware changes, as we have all done till now, will work. If you are planning on using it, please make sure you have a plan to update devices safely, as it will definitely be needed.

Need to buy a EOS S3 board to try these out in detail. Anyone with practical experience with these chips/boards? How were they?

If you liked the post, Share it with your friends!

Back to Basics: eSIMs in Vehicles

Most of you who have used an EV or any connected vehicle already know it talks to the cloud. In our cars and scooters, the internet usually comes from an embedded eSIM inside a telematics box. A tiny chip that is usually soldered. Let’s discuss that today.

This is not a personal SIM like your phone. In India, it is an M2M(Machine to Machine) eSIM managed by the manufacturer or its M2M service provider. They buy data in bulk and bundle it in your plan. Technically, no separate Jio/Airtel bill you pay monthly. Your app works because the eSIM authenticates with a telecom profile that the backend pushes over the air.

Who controls those profiles? Not you. The OEM or its M2M provider does. They talk to two GSMA defined servers. One prepares operator profiles. Another installs and activates them on the eSIM. The big 2025 change launched by Govt is the interop. If an OEM asks, its server must integrate with any Indian operator’s profile server within three months. If needed, the OEM can move control of your eSIM to a different server within six months. That gives OEMs leverage.

What does this mean in practice? Owners benefit from fewer long lock ins. If coverage is weak in a region, the OEM has a formal path to add a new operator profile at scale. If an eSIM platform underperforms, the OEM can migrate. You still cannot pop in your own SIM. That is by design. It keeps security and KYC consistent with machine tracking and logs. If your connected pack lapses, you usually keep local features like Bluetooth. Just the cloud features die. I really hope Govt comes up with some data privacy standards for this communication. Because currently you don’t know what data from your vehicle is sent back to OEM servers with data traceable back to you.

BTW: The SIM inside many connected vehicles in India does not use the usual 10 digit format, they follow a dedicated 13 digit numbering scheme for traceability and scale. Pretty neat for something you never see while using your vehicle.

If you liked the post, Share it with your friends!
1 2 3 90