Enjia Mai ef3e7a5fa6 soc: xtensa: cavstool: add support for logs coming from HDA logging ... 1) HDA logging seems to be using some padding like '\x00'. Such string can print well on a terminal but corrupt the string match. And this can cause false failure if RunID matching is affected. Remove such padding before checking RunID. An affected RunID example: '7aa9ba3c6db12\x00\...\x00\x00\x00\x00d0c7fcf382a4af40ec6' Expected: '7aa9ba3c6db12d0c7fcf382a4af40ec6' 2) Use non-displayable chars for live connection check. Otherwise the log output will have subtle garbage like extra spaces which locate randomly. This solution comes from the PR #50071, the author is smrtos. Signed-off-by: Ming Shao <ming.shao@intel.com> Signed-off-by: Enjia Mai <enjia.mai@intel.com>		2022-09-16 13:34:05 -04:00
..
esp32	soc: esp32: Switch from FLASH_AREA_ to FIXED_PARTITION_	2022-09-06 09:56:37 +02:00
esp32_net	soc: esp32: remove Kconfig.defconfig* setting of clock control drivers	2022-09-01 10:26:30 +02:00
esp32s2	soc: esp32s2: Switch from FLASH_AREA_ to FIXED_PARTITION_	2022-09-06 09:56:37 +02:00
intel_adsp	soc: xtensa: cavstool: add support for logs coming from HDA logging	2022-09-16 13:34:05 -04:00
nxp_adsp	linker: update files with <zephyr/...> include prefix	2022-05-09 12:45:29 -04:00
sample_controller	linker: update files with <zephyr/...> include prefix	2022-05-09 12:45:29 -04:00
CMakeLists.txt	…