How to migrate custom logic from an FPGA to MCUs

10th January 2020

Sponsored Post

0 0

Just like a CPLD or FPGA, CLB is composed of programmable logic primitives that can be configured in many ways to implement custom blocks of logic. Instead of using VHDL or Verilog to configure these logic primitives, CLB is programmed with a GUI-based SysConfig tool and function calls. Since the configuration method is different, the CLB is technically not a CPLD or FPGA, but it can be used to achieve identical results.

The CLB holds certain advantages over external CPLDs and FPGAs. Because it resides inside the C2000 device, CLB has direct access to key CPU and peripheral signals without having to account for pin delays. Additionally, a simple built-in HLC processor facilitates data transfer between CLB and C2000 memory allowing the CLB to work hand-in-hand with software running on the C2000 processor(s).

With CLB it is now possible to absorb external custom logic into the C2000 device, create custom peripherals inside the C2000, and modify existing C2000 control peripherals at input stage, output stage or at many pre-defined sites inside the peripheral.

The following sections contain step-by-step instructions how to implement the most common use cases, plus low-level functional schematics of CLB building blocks to aid the process of mapping logic from VHDL or Verilog into CLB. Many powerful and flexible CLB features provide you with substantial benefits including reduction in system component count, added flexibility to differentiate products and ability to update custom logic in the field via software after parts have shipped.

To read the full paper from Texas Instruments, click here.