Software signoff again
What do you think the dominant design paradigm for electronic systems is going to be going forward?
As I’ve said before, I believe that it is going to be taking software, probably written in C and C++, and synthesizing parts of it into FPGAs and compiling the rest into binary to run on processors in the FPGA. This is what I’ve been calling software signoff for a long time. It’s more than just the software necessary to run on the FPGA or SoC. It is signing off hardware that co-optimizes the software. The idea that conceptually we need to get the software that specifies the system right, and then hardware design is just creating a silicon fabric (SoC or FPGA) which is able to run the software high enough performance and at low enough power (because otherwise why bother to do anything other than simply execute it). Power, performance and price, the 3Ps again.
Related Semiconductor IP
- AES GCM IP Core
- High Speed Ethernet Quad 10G to 100G PCS
- High Speed Ethernet Gen-2 Quad 100G PCS IP
- High Speed Ethernet 4/2/1-Lane 100G PCS
- High Speed Ethernet 2/4/8-Lane 200G/400G PCS
Related Blogs
- Exploring the Xilinx Zynq: software platform, or complex FPGA?
- Open ARM-wrestling in FPGAs
- Why FPGA startups keep failing
- Over-interpreting the extended ARM
Latest Blogs
- Why Choose Hard IP for Embedded FPGA in Aerospace and Defense Applications
- Migrating the CPU IP Development from MIPS to RISC-V Instruction Set Architecture
- Quintauris: Accelerating RISC-V Innovation for next-gen Hardware
- Say Goodbye to Limits and Hello to Freedom of Scalability in the MIPS P8700
- Why is Hard IP a Better Solution for Embedded FPGA (eFPGA) Technology?