zara/zephyr - zephyr - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Dmitrii Golovanov	fdc20fdff6	soc: xtensa: intel_adsp: move and convert to HWMv2 Move and convert soc/xtensa/intel_adsp SoC family configurations to HWMv2 with its SoC series: `ace` (INTEL_ACE) and `cavs` (INTEL_ADSP_CAVS). Signed-off-by: Dmitrii Golovanov <dmitrii.golovanov@intel.com>	1 year ago
Jamie McCrae	22c53e97b5	hwmv2: move all non-ported legacy boards and socs to legacy folders To un-block continuing of soc and board porting then move all socs and boards which have not yet been ported to boards_legacy / soc_legacy folders. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>	1 year ago
Jamie McCrae	ec7044437e	treewide: Disable automatic argparse argument shortening Disables allowing the python argparse library from automatically shortening command line arguments, this prevents issues whereby a new command is added and code that wrongly uses the shortened command of an existing argument which is the same as the new command being added will silently change script behaviour. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>	2 years ago
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>	3 years ago
Enjia Mai	5b5107090d	soc: xtensa: tools: add specifying log and request port for cavs client Besides in a form of {host}:{port} to specifying the port using, we also support specifying --log-port and --req-port parameters for the cavstool client. Signed-off-by: Enjia Mai <enjia.mai@intel.com>	3 years ago
Enjia Mai	e33fd73546	soc: xtensa: add support for specifying the service port Add specifying the port for the remote cavstool remote service. Ex. west flash --remote-host {host}:{port} \ --pty {host}:{port} Specify the port is optional when running west. And another major change is now we have to specify the remote log service by --pty to make it output the log message immediately. Previously it will output directly. Why we make this change is because this is more close to the behavior we use west flash. Fixes. #46865 Signed-off-by: Enjia Mai <enjia.mai@intel.com>	3 years ago
Enjia Mai	faff3f7ecc	soc: xtensa: partial fix of socket misuse and refine the code 1. Improve the firmware transfer reliability by fixing the misuse of the socket. Fix the most frequent occurence of the common `recv()` bug described here: https://docs.python.org/3/howto/sockets.html#using-a-socket The longer term fix is to switch to a higher level API like Python Remote Objects. 2. Not rely on the client's command to disconnect. Previously we rely on the SIGINT to send stop_command to the server, but it does not work well in some environments. Refine the whole logic and the sever disconnect service by checking if the client is alive or not. These changes make the client-server-based cavstool more stable. Fixes #46864 Signed-off-by: Enjia Mai <enjia.mai@intel.com>	3 years ago
Enjia Mai	01b0c73ece	soc: intel_adsp: add a client-server based cavstool tool The cavstool_client.py is a client use to communicate with the firmware loading and running server which dealing with the requests from the intel_adsp west runner. It supports: 1. Download firmware to remote ADSP host and running. 2. Send the ADSP log messages back to client. Signed-off-by: Enjia Mai <enjia.mai@intel.com>	3 years ago