Allwinner T113 dual-core heterogeneous processor based on Tina Linux5.0 - RTOS compilation and development instructions

aleksib

Allwinner T113 dual-core heterogeneous processor based on Tina Linux5.0 - RTOS compilation and development instructions [Copy link]

 

**3. RTOS compilation and development instructions** **3.1. RTOS SDK and TinaLinux development environment** RTOS SDK related codes have been integrated into the Tina Linux development environment. The rtos subdirectory in the Tina Linux development environment is the RTOS development environment. ``` ├──brandy ├──bsp ├──build ├──buildroot ├──build.sh >build/top_build.sh ├──device ├──kernel ├──openwrt ├──out ├──platform ├──prebuilt ├──rtos #RTOS environment├──tee_kit ├──test └──tools ``` **3.2. RTOS compilation** Tina integrates the compilation and packaging functions of RTOS, and is suitable for file systems such as openwrt and buildroot. Here, the T113 S4 platform is used as an example to illustrate. **3.2.1. Associated RTOS solution** In TinaLinux SDK, there is a device directory under the SDK root directory. This directory stores the configurations of different processor platforms and motherboards. Take SBC-T113S4_NAND as an example. It uses T113_S4 as the main controller, and its configuration files are stored in the device/config/chips/t113_s4/configs/sbc_t113s4_nand directory. So how to associate the motherboard with the RTOS solution? ``` xxx@xxx:~/workspace/t113_tina5.0/t113_tinasdk5.0-v1/device/config/chips/t113_s4/configs/sbc_t113s4_nand$ tree -l . ├── bin │ ├── amp_dsp0.bin │ └── amp_rv0.bin ├── BoardConfig.mk //Key to associated RTOS project├── board.dts -> linux-5.4/board.dts ├── bsp │ ├── env.cfg │ └── sys_partition.fex ├── buildroot │ ├── BoardConfig.mk │ ├── BoardConfig_nor.mk │ ├── bootlogo.bmp │ ├── env_nor.cfg │ ├── swupdate │ │ ├── env_ab.cfg │ │ ├── sw-description-ab │ │ ├── sw-description-ab-rdiff │ │ ├── sw-description-recovery │ │ ├── sw-description-recovery-sign │ │ ├── sw-subimgs-ab.cfg │ │ ├── sw-subimgs-ab-rdiff.cfg │ │ ├── sw-subimgs-recovery.cfg │ │ ├── sw-subimgs-recovery-secure.cfg │ │ ├── sw-subimgs-recovery-sign.cfg │ │ ├── sys_partition_ab.fex │ │ └── sys_partition_recovery.fex │ ├── sys_partition.fex │ └── sys_partition_nor.fex ├── linux-5.4 │ ├── board_backup.dts │ ├── board.dts │ ├── board_lvds1024x600.dts │ ├── board_lvds1024x768.dts │ ├── board_old.dts │ ├── board_spi4bit_drv30.dts │ ├── board_spi4bit.dts │ ├── board_spi_sbc-t113s_v1p0.dts │ ├── board_tft1024x600.dts │ ├── board_uart3.dts │ ├── board_xr829_sbc-t113s_v1p1.dts │ ├── config-5.4 │ ├── config-5.4-recovery │ ├── config_uart3-5.4 │ ├── env.cfg │ ├── env_uart3.cfg │ └── sys_partition.fex ├── openwrt │ ├── bootlogo.bmp │ ├── sys_partition.fex │ └── sys_partition_nor.fex ├── sys_config.fex ├── sys_config_old.fex ├── sys_config_uart3.fex ├── uboot-board_backup.dts ├── uboot-board.dts ├── uboot-board-lvds-lcd1024x600.dts ├── uboot-board_spi0_1wire.dts ├── uboot-board_spi_sbc-t113s_v1p0.dts ├── uboot-board_spi_sbc-t113s_v1p1.dts └── uboot-board-tft-lcd1024x600.dts ``` Among these configuration files, there is a file BoardConfig.mk, which is the key to associating RTOS applications. The content of this file is as follows:  Configure the key field LICHEE_RTOS_PROJECT_NAME:=xxxxx of the RTOS solution name. Taking our company's SBC-T113S motherboard as an example, the t113_s4_c906_evb1_auto RTOS solution is configured in BoardConfig.mk. Developers can change the build RTOS solution by modifying the LICHEE_RTOS_PROJECT_NAME field. First enter Tina's rtos directory. The contents of the rtos directory are as follows: ``` ├──board ├──envsetup.sh >tools/scripts/source_envsetup.sh ├──lichee ├──out └──tools ``` Execute the following instructions to configure the RTOS environment ``` source envsetup.sh #Configure environment variables``` We can see that the RTOS scheme that can be selected is the RTOS scheme that can be configured in the LICHEE_RTOS_PROJECT_NAME field. ``` last=t113_s4_c906_evb1_auto You're building on Linux Lunch menu... pick a combo: 1. t113_i_c906_evb1_auto 2. t113_s3p_c906_evb1_auto 3. t113_s3p_c906_evb1_auto_fastboot 4. t113_s3 p_c906_evb1_auto_fastboot_video 5. t113_s3p_c906_evb1_auto_non_os 6. t113_s3p_c906_example_demo 7. t113_s4_c906_evb1_auto 8. t113_s4_c906_evb1_auto_fastboot_video 9. t113_s4p_c906_evb1_auto Which would you like? [Default t113_s4_c906_evb1_auto]: ``` From the above RTOS solutions, we can see that there are solutions that support t113-i processors and t113_s4 processors. The current default is t113_s4_c906_evb1_auto, which is a solution based on t113_s4 processors. In addition, this solution can be added. If the motherboard is based on T113I, you can use t113_i_c906_evb1_auto as a blueprint to add your own solution. If the motherboard is based on T113-S4, you can use t113_i_c906_evb1_auto as a blueprint to add your own solution. Please see Chapter 6 of this manual for how to add a solution. **3.2.2. Compile RTOS solution separately** After executing lunch_rtos to select the compilation solution, you can configure the solution through mrtos_menuconfig. After the configuration is completed, you can compile the RTOS through m or mrtos instructions. ``` xxx@xxx:~/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos$ lunch_rtos last=t113_s4_c906_evb1_auto You're building on Linux Lunch menu... pick a combo: 1. t113_i_c906_evb1_auto 2. t113_s3p_c906_ev b1_auto 3. t113_s3p_c906_evb1_auto_fastboot 4. t113_s3p_c906_evb1_auto_fastboot_video 5. t113_s3p_c906_evb1_auto_non_os 6. t113_s3p_c906_example_demo 7. t113_s4_c906_evb1_auto 8. t113_s4_c906_evb1_auto_fastboot_video 9. t113_s4p_c906_evb1_auto Which would you like? [Default t113_s4_c906_evb1_auto]: 7 select=7... t113_s4_c906 /evb1_auto '/home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos/lichee/rtos/projects/t113_s4_c906/evb1_auto/defconfig' -> '/home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos/lichee/rtos /.config' ========================================== RTOS_BUILD_TOP=/home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos RTOS_TARGET_ARCH=riscv RTOS_TARGET_CHIP=sun8iw20p1 RTOS_TARGET_DEVICE=t113_s4_c906 RTOS_PROJECT_NAME=t113_s4_c906_evb1_auto ============================================ Run mrtos_menuconfig to config rtos Run m or mrtos to build rtos ``` The above prompts us that we can configure the application through mrtos_menuconfig. The execution results are as follows:  From the configuration, it is similar to the Linux kernel configuration, and various driver peripherals can also be configured, as shown in the figure below:  The T113 series has a dual-core Cortex-A7 core and a RV64-C906 core. The peripherals used by these two cores are common. Therefore, when choosing peripherals for C906, avoid the peripherals already used by Cortex-A7. For example: the Cortex-A7 core has already used the two GPIOs PE2/PE3 as UART, and C906 can no longer use PE2/PE3. In addition, one thing that should be made clear here is that each RTOS application also has a corresponding configuration file. The configuration file for the t113_s4_c906_evb1_auto project is in the following directory: ``` TinaSDK directory/rtos/lichee/rtos/projects/t113_s4_c906/evb1_auto/defconfig ``` After the configuration is completed, you can execute m or mrtos to compile. The command execution results are as follows: ``` xxx@xxx:~/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos$ mrtos build rtos ... ===There isn't tina environment.=== Note: will use shell command origin rather than the functon. Dark Builder Version (1.6.0 - BiCEP2 (Gravitational Waves)) *[CC] [SCRIPT] build/t113_s4_c906_evb1_auto/img/sys_config.fex [CONF] [Tina-RT-Builder] .dbuild/..//include/generated/t113_s4_c906_evb1_aut o/autoconf. h [LDS] [Linker] projects/t113_s4_c906/evb1_auto/freertos.lds CC build/t113_s4_c906_evb1_auto/arch/common/version.o LD build/t113_s4_c906_evb1_auto/arch/common/obj-in.o LD build/t113_s4_c906_evb1 _auto/arch/obj -in.o [LD] [Tina-RT-Builder] build/t113_s4_c906_evb1_auto/img/rt_system.elf if [ -n /home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos/lichee/rtos/bu ild/t113_s4_c906_evb1_auto/img/ ]; then mkdir -p /home/ping/workspace/t113_tina 5.0/t113_tinasdk5.0-v1/rtos/lichee/rtos/build/t113_s4_c906_evb1_auto/img; fi Memory region Used Size Region Size %age Used RAM: 214096 B 6 MB 3.40% *[SYMS][Tina-RT-Builder] build/t113_s4_c906_evb1_auto/img/rt_system.syms *[IMAGE] [Tina-RT-Builder] build/t113_s4_c906_evb1_auto/img/rt_system.bin text data bss dec hex filename 134576 69048 10472 214096 34450 build/t1 13_s4_c906_evb1_auto/img/rt_syst em.elf copying /home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos/lichee/rtos/bu ild/t113_s4_c906_evb1_auto/img/rt_system.bin to /home/ping/workspace/t113_tina5. 0/t113_tinasdk5.0-v1/rtos/board/t113_s4_c906/evb1_auto/bin/freertos.fex #### make completed successfully '/home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos/lichee/ rtos/build/t11 3_s4_c906_evb1_auto/img/rt_system.bin' -> '/home/ping/workspace/t113_tina5.0/t11 3_tinasdk5.0-v1/rtos/board/t113_s4_c906/evb1_auto/bin/rtos_riscv_sun8iw20p1.fex' ping@ embedall:~/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos$ ``` From the above information, we can get some information. The name of the compiled firmware is freertos.fex/rtos_riscv_sun8iw20p1.fex. In fact, the two firmwares are the same. The firmware is compiled, but how to package this firmware into the root file system generated by Tina? Please see the next chapter. **3.2.3. Compile the RTOS solution under Tina** In the root directory of TinaSDK, first select the overall platform solution, as shown below: * buildroot solution 1. First use the following command to select the overall platform solution``` ./build.sh config ``` 2. Then the RTOS related operation commands are as follows``` ./build.sh rtos #Compile the RTOS solution separately./build.sh rtos menuconfig #Modify the RTOS configuration file./build.sh rtos clean #Clear RTOS compilation intermediate files``` Note: executing ./build.sh will not compile RTOS * openwrt solution 1. First use the following command to select the overall platform solution``` source build/envsetup.sh #Effective environment variables lunch #Select openwrt solution``` 2. Executing make will compile RTOS first, and then compile Tina * Quick commands In the root directory of Tina, after executing source build/envsetup.sh to configure the environment, you can use the RTOS shortcut commands to configure and compile RTOS.  **3.3, RTOS firmware packaging** Let's take the compilation of the openwrt solution as an example. In the process of compiling openwrt, the RTOS will be compiled first, and then the generated image file will be automatically copied to the corresponding platform solution, and rt_system.elf will be renamed to amp_rv0.bin, see the following information: ``` xxx@xxx:~/workspace/t113_tina5.0/t113_tinasdk5.0-v1$ make -j32 ===There is tina environment.=== Note: make is the shell functon in envsetup.sh. == action: openwrt_build, action_args: -j32 == ========ACTION List: build_rtos ;======== options : INFO: build rtos ... Setup env done! Run lunch_rtos to select project last=t113_s4_c906_evb1_auto select=t113_s4_c906_evb1_auto... t113_s4_c906/evb1_auto '/home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos/lichee/rtos/projects/t113_s4_c906/evb1_auto/defconfig' -> '/home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos/lichee/rtos/.config' ================================================ RTOS_BUILD_TOP=/home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos RTOS_TARGET_ARCH=riscv RTOS_TARGET_CHIP=sun8iw20p1 RTOS_TARGET_DEVICE=t113_s4_c906 RTOS_PROJECT_NAME=t113_s4_c906_evb1_auto ============================================ Run mrtos_menuconfig to config rtos Run m or mrtos to build rtos build rtos ... Dark Builder Version (1.6.0 - BiCEP2 (Gravitational Waves)) *[CC] [SCRIPT] build/t113_s4_c906_evb1_auto/img/sys_config.fex [CONF] [Tina-RT-Builder] .dbuild/..//include/generated/t113_s4_c906_evb1_auto/autoconf.h [LDS] [Linker] projects/t113_s4_c906/evb1_auto/freertos.lds CC build/t113_s4_c906_evb1_auto/arch/common/version.o LD build/t113_s4_c906_evb1_auto/arch/common/obj-in.o LD build/t113_s4_c906_evb1_auto/arch/obj-in.o [LD] [Tina-RT-Builder] build/t113_s4_c906_evb1_auto/img/rt_system.elf if [ -n /home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos/lichee/rtos/build/t113_s4_c906_evb1_auto/img/ ]; then mkdir -p /home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos/lichee/rtos/build/t113_s4_c906_evb1_auto/img; fi Memory region Used Size Region Size %age Used RAM: 214096 B 6 MB 3.40% *[IMAGE] [Tina-RT-Builder] build/t113_s4_c906_evb1_auto/img/rt_system.bin *[SYMS] [Tina-RT-Builder] build/t113_s4_c906_evb1_auto/img/rt_system.syms text data bss dec hex filename 134576 69048 10472 214096 34450 build/t113_s4_c906_evb1_auto/img/rt_system.elf copying /home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos/lichee/rtos/ build/t113_s4_c906_evb1_auto/img /rt_system.bin to /home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos/board/t113_s4_c906/evb1_auto/bin/freertos.fex #### make completed successfully '/home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos/lichee/rtos/build/t113_s4_c906_evb1_auto/img/rt_system.bin' -> '/home/ping/workspace/t113_tina5.0/t113_tinasdk5. 0-v1/rtos/board/t113_s4_c906/evb1_auto/bin/rtos_riscv_sun8iw20p1.fex' '/home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/rtos/lichee/rtos/build/t113_s4_c906_evb1_auto/img/ rt_system. elf' -> '/home/ping/workspace/t113_tina5.0/t113_tinasdk5.0-v1/device/config/chips/t113_s4/configs/sbc_t113s4_nand/bin/amp_rv0.bin' ``` Then package it in the Tina environment and make sure the RTOS compiles the firmware amp_rv0.bin is packaged into the root file system. Note: 1) buildroot needs to execute the ./build.sh&&./build.sh pack command 2) openwrt needs to execute the make&&pack command After packaging, the produced firmware is located in tina5.0/out/ t113_s4_linux_sbc_t113s4_uart0.img, can be burned to the motherboard using PhoenixSuit tool. **3.4, RISC-V core startup** After entering the main core Linux console, execute the following command to complete the initialization of the RV core heterogeneous communication framework: ``` echo start>/sys/class/remoteproc/remoteproc1/state ``` Note: The T113-S4 processor includes a DSP HIFI core and a RISC-V core, so it should have two nodes, remoteproc0/remoteproc1 (these two nodes are configurable in the kernel's DTS and can be Delete any node). If both nodes are present, then the remoteproc0 node is the DSP core and the remoteproc1 node is the RISC-V core. **3.5, RTOS image file update** There are two ways to update the RTOS image file: 1 , Tina Linux environment, recompile the firmware according to the RTOS compilation and RTOS firmware packaging steps, burn it into the development board, and then start the RV core. 2. Use adb push to push the newly generated image file amp_rv0.bin to the /lib/firmware directory. Execute the following command in the Linux console: ``` echo stop>/sys/class/remoteproc/remoteproc1/state #Close RV. echo amp_rv0.bin>/sys/class/remoteproc/remoteproc1/firmware echo start>/sys/class/remoteproc/remoteproc1/state #Start RV ```4. RISC-V core startup** After entering the main core Linux console, execute the following command to complete the initialization of the RV core heterogeneous communication framework: ``` echo start>/sys/class/remoteproc/remoteproc1/state ``` Note: The T113-S4 processor includes a DSP HIFI core and a RISC-V core, so it should have two nodes, remoteproc0/remoteproc1 (these two nodes are configurable in the kernel's DTS, and any node can be deleted). If both nodes are present, the remoteproc0 node is the DSP core and the remoteproc1 node is the RISC-V core. **3.5. RTOS image file update** There are two ways to update the RTOS image file: 1. In the Tina Linux environment, recompile the firmware according to the RTOS compilation and RTOS firmware packaging steps, and burn it into the development board, and then start the RV core. 2. Use adb push to push the newly generated image file amp_rv0.bin to the /lib/firmware directory, and execute the following commands in the Linux console: ``` echo stop>/sys/class/remoteproc/remoteproc1/state #Shut down RV. echo amp_rv0.bin>/sys/class/remoteproc/remoteproc1/firmware echo start>/sys/class/remoteproc/remoteproc1/state #Start RV ```4. RISC-V core startup** After entering the main core Linux console, execute the following command to complete the initialization of the RV core heterogeneous communication framework: ``` echo start>/sys/class/remoteproc/remoteproc1/state ``` Note: The T113-S4 processor includes a DSP HIFI core and a RISC-V core, so it should have two nodes, remoteproc0/remoteproc1 (these two nodes are configurable in the kernel's DTS, and any node can be deleted). If both nodes are present, the remoteproc0 node is the DSP core and the remoteproc1 node is the RISC-V core. **3.5. RTOS image file update** There are two ways to update the RTOS image file: 1. In the Tina Linux environment, recompile the firmware according to the RTOS compilation and RTOS firmware packaging steps, and burn it into the development board, and then start the RV core. 2. Use adb push to push the newly generated image file amp_rv0.bin to the /lib/firmware directory, and execute the following commands in the Linux console: ``` echo stop>/sys/class/remoteproc/remoteproc1/state #Shut down RV. echo amp_rv0.bin>/sys/class/remoteproc/remoteproc1/firmware echo start>/sys/class/remoteproc/remoteproc1/state #Start RV ```