Conductor Tool demo application

Conductor Tool demo application

Conductor Tool demo application is an application which is used for demonstrating the Conductor Tool. Also referred to as the Device Configuration Tool or DCT. Application blinks two LEDs and writes output to UART. Check more information about the application and the Conductor tool from the Conductor-Tool demo application guide.

Building Conductor Tool demo application

git clone https://github.com/alifsemi/alif_conductor-demo.git
cd alif_conductor-demo
git submodule init
git submodule update

Build Conductor Tool demo for High-Performance M55 (M55_HP)

mkdir build_hp
cd build_hp

Linux and macOS with Apple M Chip

cmake .. -DALIF_CORE=M55_HP -DCMAKE_TOOLCHAIN_FILE=../toolchain-gnu.cmake -DCMAKE_BUILD_TYPE=Release
make

Build for Windows

In order to successfully build in Windows, you need Ninja build system. You can install it from here

You will also need gcc compiler. You can install it from here. Choose 13.2.Rel1 and Windows AArch32 bare-metal target (arm-none-eabi). Remember to add to path.

Install CMake from here

Now you can use CMake and generator Ninja

NOTE Make sure to call in clean build folder

Configure build using CMake

cmake .. -DALIF_CORE=M55_HP -DCMAKE_TOOLCHAIN_FILE="..\toolchain-gnu.cmake" -DCMAKE_BUILD_TYPE=Release -G "Ninja"

Then build with Ninja by typing ninja

Build Conductor Tool demo for High-Efficiency M55 (M55_HE)

mkdir build_he
cd build_he

Linux and macOS with Apple M Chip

cmake .. -DALIF_CORE=M55_HE -DCMAKE_TOOLCHAIN_FILE=../toolchain-gnu.cmake -DCMAKE_BUILD_TYPE=Release
make

Windows

cmake .. -DALIF_CORE=M55_HE -DCMAKE_TOOLCHAIN_FILE="..\toolchain-gnu.cmake" -DCMAKE_BUILD_TYPE=Release -G "Ninja"
ninja

Build Conductor demo with memory stitching

Memory stitching is valid only with AppKit-e7 and DevKit-e7. DevKit-e4 and DevKit-e8 already has the linear SRAMs. Build similar as above, but use CMake option -DMEMORY_STITCHING=ON Example:

mkdir build_he
cd build_he

Linux and macOS with Apple M Chip

cmake .. -DALIF_CORE=M55_HE -DCMAKE_TOOLCHAIN_FILE=../toolchain-gnu.cmake -DCMAKE_BUILD_TYPE=Release -DMEMORY_STITCHING=ON
make

Windows

cmake .. -DALIF_CORE=M55_HE -DCMAKE_TOOLCHAIN_FILE="..\toolchain-gnu.cmake" -DCMAKE_BUILD_TYPE=Release -DMEMORY_STITCHING=ON -G "Ninja"
make

Generate ATOC with command:

./app-gen-toc --filename build/config/conductor_tool_demo_mram_memory_stitching.json

Building for different board variants

By default, the application is built for DevKit-e7 (Gen 2). To build the application for different boards, define TARGET_BOARD variable for cmake.

-DTARGET_BOARD=DevKit-e8

Possible options: AppKit-e7, DevKit-e4, DevKit-e7 and DevKit-e8 Use conductor_tool_demo_mram.json for AppKit-e7 and DevKit-e7. Use conductor_tool_demo_mram_e8.json for DevKit-e4 and DevKit-e8.

Note

Needs SETOOLS v1.110.0 or later for flashing the application to DevKit-e4 and DevKit-e8.

Flashing the test application

In the root there is SETOOLS config file sfor this application conductor_tool_demo_mram.json and conductor_tool_demo_mram_e8.json which can be used for ISP with the Alif Security Toolkit. In root, there are two binaries sram0 and sram1, they need to be copied to same folder as demo binaries when using SE tools for flashing. conductor_tool_demo_mram.json and conductor_tool_demo_mram_e8.json do 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.