Frequently Asked Questions#

Build#

Q1: `make` says to run `make xxx_defconfig` first. What should I do?#

Symptom: Running make directly before selecting a config produces an error asking you to choose a configuration first. Solution:

make list-def
make <your_board>_defconfig
make

Q2: My board only has a `k230_canmv_*_defconfig`. How do I build an RTOS image?#

Solution: Select the CanMV defconfig first, then switch to RTOS via menuconfig:

Run make k230_canmv_xxx_defconfig
Run make menuconfig
Disable CanMV Components Configuration
Enable RT-Smart Configuration > Enable build Rtsmart examples as needed
Enable MPP Configuration > Enable build MPP samples as needed
Run time make log

Q3: The toolchain is missing. How do I fix it?#

Symptom: make reports that the toolchain cannot be found. Solution:

make dl_toolchain

Run this once to download the toolchain, then build again.

Q4: I modified `src/rtsmart/mpp` but the changes don’t take effect after `make`?#

Symptom: The image builds, but the changes are not reflected. Solution: Clean the RT-Smart build artifacts first, then rebuild:

make rtsmart-clean
make

Flashing and Boot#

Q5: When should I use `.img` vs `.kdimg`?#

Guidelines:

USB GUI tool (K230BurningTool): prefer *.kdimg
SD card flashing: use *.img
Command-line flashing (k230-flash): typically use *.img

Q6: After running `reboot_to_upgrade`, the board doesn’t enter flashing mode?#

Solution:

Make sure the flashing tool is a recent version.
Follow the patch instructions in the flashing guide, apply the patch, and try again.
Alternatively, use the hardware method: hold the Boot button while powering on to enter flashing mode.

Reference: userguide/how_to_flash.md

Q7: Flashing succeeded but the device doesn’t boot normally?#

Troubleshooting steps:

Check that the image matches the board (is the defconfig correct?).
Check that the boot medium is correct (EMMC/SD).
Check the serial log to confirm whether boot is stuck at a particular stage.
Reflash once more to rule out file corruption or interrupted transfers.

Q8: How do I quickly get started with OTA?#

Follow this minimal flow:

Build to get the *.kdimg update package on your PC (located at output/<defconfig>/images/).
Transfer *.kdimg to the device filesystem (e.g. /data/update.kdimg).
Call the OTA interface on the board to perform the update (sample test command):

test_ota /data/update.kdimg

After a successful update log appears, reboot and confirm the new version is running.

Notes:

OTA requires *.kdimg, not *.img.
For production, it is recommended to add update package signature/source verification, power-loss recovery, and rollback policies at the application layer.

For the full mechanism and API description, see: advanced_development_guide/how_to_use_k230_ota.md

Samples and Applications#

Q9: Samples are not in `/sdcard/app`. Does that mean packaging failed?#

Not necessarily. RT-Smart samples are placed in:

/sdcard/app/examples/

Check with:

cd /sdcard/app/examples
find . -name "*.elf" | head

Q10: How do I configure a sample to auto-start on boot?#

There are two configuration options:

Runtime auto-start command (Startup command)

Configure in menuconfig:
```
RT-Smart Configuration > Startup command
```
This is a runtime command string (CONFIG_RTT_AUTO_EXEC_CMD). Use an absolute path, for example:
```
/sdcard/app/examples/integrated_poc/smart_ipc.elf
```
Fast Boot file path at image packaging time (supports variables)

To configure the Fast Boot source file path, go to:
```
Fast Boot Configuration > Fast boot file path
```
This field supports absolute paths or ${SDK_*} variables exported by tools/mkenv.mk (e.g. ${SDK_BUILD_IMAGES_DIR}), for example:
```
${SDK_BUILD_IMAGES_DIR}/sdcard/app/examples/integrated_poc/smart_ipc.elf
```

Q11: How do I check which sensors the current firmware supports?#

On the board, run:

list_sensor

If the target sensor is not listed, enable it in the Sensor-related options under menuconfig and rebuild and reflash.

Reference: userguide/sensor_list.md

Still not resolved?#

Post on the community forum for help.

Providing the following information will speed up troubleshooting:

The defconfig name you are using
The full error log (including 30 lines before and after)
The flashing method and image file name
Key sections of the serial boot log

Also include the commands you have already tried.

Frequently Asked Questions

Contents

Frequently Asked Questions#

Build#

Q1: make says to run make xxx_defconfig first. What should I do?#

Q2: My board only has a k230_canmv_*_defconfig. How do I build an RTOS image?#