DCT demo application is an application which is used for demonstrating the DCT tool. Application blinks two LEDs and writes output to UART.
git clone git@github.com:alifsemi/dct_demo.git
cd dct_demo
git submodule init
git submodule update
By default application code is executed from TCM. If you want to run code directly from MRAM (XIP), add parameter -DXIP=1
to your CMake command as seen below.
Both cores must use the same run mode.
mkdir build_hp
cd build_hp
cmake .. -DENSEMBLE_CORE=M55_HP -DCMAKE_TOOLCHAIN_FILE=../toolchain-gnu.cmake -DCMAKE_BUILD_TYPE=Release -DXIP=1
OR
cmake .. -DENSEMBLE_CORE=M55_HP -DCMAKE_TOOLCHAIN_FILE=../toolchain-gnu.cmake -DCMAKE_BUILD_TYPE=Release
make
mkdir build_he
cd build_he
cmake .. -DENSEMBLE_CORE=M55_HE -DCMAKE_TOOLCHAIN_FILE=../toolchain-gnu.cmake -DCMAKE_BUILD_TYPE=Release -DXIP=1
OR
cmake .. -DENSEMBLE_CORE=M55_HE -DCMAKE_TOOLCHAIN_FILE=../toolchain-gnu.cmake -DCMAKE_BUILD_TYPE=Release
make
By default, the application is built for DevKit-E7 (Gen 2). To build the application for different boards, define ENSEMBLE_BOARD variable for cmake.
-DENSEMBLE_BOARD="devkit_gen2"
Possible options: devkit_gen1/2, appkit_alpha1/2, appkit_gen2 or devkit_b0_cob0
In the root there are two SETOOLS config files for this application, dct_demo_tcm.json or dct_demo_mram.json which can be used for ISP with the Alif Security Toolkit. Use either one based on whether your compilation has XIP (MRAM) enabled or do you run code from TCM (default). In root, there is two binaries sram0 and sram1, they need to be copied to same folder as demo binaries when using SE tools for flashing. dct_demo_tcm.json or dct_demo_mram.json both require demo application for both cores and sram0/1-binaries.
M55_HE core uses UART2 and M55_HP core uses UART4 for printing the information to demonstrate how the application works.