Creating the Zynq Virtual Platform, Including Errata
Although I have never contributed any code to the Linux kernel, the headline We are all Linux developers now on linux today caught my eye. One of the things that amazes me is how many embedded products use Linux and how they deal with all of the complexity. Nearly every product has similar but different hardware, and keeping it all straight and shipping a product with working software in the dynamic world of Linux is impressive.
As a virtual platform developer these details hit me every so often, but I actually enjoy learning and finding connections to the greater software development world. This story is about creating a model of the PL310 L2 cache controller for the Zynq Virtual Platform I have previously described. At Cadence, we create Virtual Platform models from an IP-XACT description of each hardware block (I'll save the details of this flow for another day), but needless to say we sometimes encounter situations where gaps are revealed between the spec and what the Linux kernel actually does. Today, I hit one such situation.
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
- The Zynq Virtual Platform: Not Just for Pre-Silicon
- Using Physical USB Devices with the Xilinx Zynq-7000 Virtual Platform
- Using Scoreboards and Virtual Platforms for Software Verification
- Exploring the Xilinx Zynq: software platform, or complex FPGA?
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?