this post was submitted on 09 Sep 2023
4 points (75.0% liked)

Electronics

1991 readers
1 users here now

Projects, pictures, industry discussions and news about electronic engineering & component-level electronic circuits.

Rules

1: Be nice.

2: Be on-topic (eg: Electronic, not electrical).

3: No commercial stuff, buying, selling or valuations.

4: No circuit design or repair, tools or component questions.

5: No excessively promoting your own sites, social media, videos etc.

Ask questions in https://discuss.tchncs.de/c/askelectronics

founded 1 year ago
MODERATORS
DavideAndrea@discuss.tchncs.de
linker3000@discuss.tchncs.de
4
Use Cases And Value Proposition Of eFPGA (Embedded FPGA) (semiengineering.com)
submitted 1 year ago by hardware26@discuss.tchncs.de to c/electronics@discuss.tchncs.de
1 comments fedilink hide all child comments
 

cross-posted from: https://discuss.tchncs.de/post/3011500

Many volume applications use FPGA because they need in-field reconfigurability (changing standards, changing algorithms, etc) but they want to improve their system’s competitiveness (power, size, cost). FPGAs are bulky, expensive and power hungry. Integrating eFPGA can greatly improve the economics while maintaining full reconfigurability and performance.

We’ve found with customers that a significant portion of the LUTs in their designs don’t change with reconfigurations: they are fixed buses to bring data to and from the reconfigurable core. This can be hardwired so the number of LUTs needed in the SoC is typically half of what’s in the FPGA. There is also a lot of cost of voltage regulators for an FPGA that disappear with integration.

Typically, the cost of eFPGA is 1/10th the cost of the FPGA it replaces but with the same speed and programmability. Power can also be cut to 1/10th because most of the power in an FPGA is the power-hungry PHYs that are mostly not needed when using eFPGA in the SoC.

top 1 comments
sorted by: hot top controversial new old
[–] al177@lemmy.sdf.org 2 points 1 year ago

This makes sense only if you're rolling your own silicon, and it depends on the application. I could see this as an alternative to a scalar DSP core or to provide more flexible high speed interfaces. The unspoken cost is going to be adding another proprietary set of tooling in the BSP for your chip.