d809390405
The twister integration on this board is problematic: + It assumes that it will be building on the device's linux installation, which is often a somewhat slow Apollo Lake board (Up Squared) with extremely limited storage space (mine has only 5G left on the internal eMMC after Zephyr installation and can't fit a full twister build tree). + Reading the trace output before the firmware load will emit output from a previous test run. Twister isn't consistent about the order in which the --west-flash and --device-serial-pty scripts are started, which means that tests show spurious failures when the order changes or if the device started with a test in its trace buffer. This is an elaboration on the scripting I've been using. It's a single script that works as both the west-flash and device-serial-pty handlers (or as an all-in-one standalone if you pass it the path to the zephyr.elf file instead of running it under twister). It reaches the device host over ssh and runs the tools with sudo, minimizing administration overhead (the device does need a checked-out Zephyr tree and a built diag_driver kernel module though). Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
|---|---|---|
| .. | ||
| doc | ||
| tools | ||
| board.cmake | ||
| intel_adsp_cavs15_defconfig | ||
| intel_adsp_cavs15.dts | ||
| intel_adsp_cavs15.yaml | ||
| Kconfig.board | ||
| Kconfig.defconfig | ||