History

fangxinyong c479ccb8aa sched: move etc romfs mount from nsh to sched/init

Usually the startup script is placed under /etc. The contents of the etc directory
are compiled and linked with Nuttx binary in the form of romfs. After startup,
it will be mounted by Nsh.

etc is generated by the different boards, that use genromfs and xxd tools to generate
and compile it into the Nuttx, for example: boards/arm/at32/at32f437-mini/tool/mkromfs.sh
The more common method is etc image generated from the content in the corresponding
board/arch/board/board/src/etc directory, and added by Makefile for example:
boards/sim/sim/sim/src/etc.

But in kernel/protected mode, Nuttx kernel and apps are run in different privileged/
non-privileged mode or the isolated binarys, so as that nsh should use syscall to
access Nuttx kernel by exported API. In this scenario, nsh can not mount the etc image
content, because that is generated in board and as a part of Nuttx kernel.

changes:

- move etc romfs mount from nsh to Nuttx, but keep the script to parse and execute.
- move and rename the related CONFIG, move customized nsh_romfsimg.h to etc_romfs.c
in boards, and no need declaration for romfs_img/romfs_img_len.

This commit changes and updates all configurations in Nuttx arch/board as much as possible,
but if any missing, please refer to the following simple guide:

- rename CONFIG_NSH_ROMFSETC to CONFIG_ETC_ROMFS, and delete CONFIG_NSH_ARCHROMFS in defconfig
- rename the etc romfs mount configs, for example CONFIG_NSH_FATDEVNO to CONFIG_ETC_FATDEVNO
- move customized nsh_romfsimg.h to etc_romfs.c in board/arch/board/board/src and no need
declaration for romfs_img/romfs_img_len.
- delete default nsh_romfsimg.h, if ROMFSETC is enabled, should generate and compile etc_romfs.c
in board/arch/board/board/src.

Signed-off-by: fangxinyong <fangxinyong@xiaomi.com>

2024-01-09 21:29:46 -03:00

env

…

script

sched: move etc romfs mount from nsh to sched/init

2024-01-09 21:29:46 -03:00

utils

Updated python scripts interpreter invocation in tools/.

2023-02-19 14:15:27 +08:00

pytest.ini

…

README.md

…

README.md

Requirements

Python 3.6 or above
pexpect + minicom
pytest

sudo apt-get install minicom
cd env
pip3 install -r requirements.txt

Pytest Original Parameter useage refer to help

Customized Parameters

pytest
    -D  specify device, for example: /dev/ttyUSB0
    -B  specify board, for example: sim,best1600_ep
    -P  specify nuttx path
    -F  specify filesystem, for example: /data
    -L  specify log path
    -O  specify ota version, for example: VELA-2.0
    -S  enable sudo as run sim
    -C  enable pre-checkin run
    -U  specify core: ap, audio, cp, sensor, tee
    -M  serial or minicom
    -R  specify target type: target|sim|qemu|module

Example

cd script
# testsuite
pytest test_[testsuite].py -D /dev/ttyUSBx -B <board> -L <logpath> -F <filesystem folder> -P <nuttx path> -R <target|sim|qemu|module>
# mark
pytest -m <mark_name> ./ -D /dev/ttyUSBx -B <board> -L <logpath> -F <filesystem folder> -P <nuttx path> -R <target|sim|qemu|module> --json=<logpath>/pytest.json
# sim
pytest -m sim ./ -B sim -P <nuttx path> -L <logpath> -F <filesystem folder> -P <nuttx path> -R <target|sim|qemu|module> --json=<logpath>/pytest.json
# stress test
pytest -m miwear ./ -B miwear -P <nuttx path> -L <logpath> -F <filesystem path> --json=<logpath>/pytest.json --count=100 --repeat-scope=session

Generate Report

cd utils/report
python3 report_gen.py -l <json log path> -b <branch>