i.MX RT700 DSP support

[iuliana-prodan]

The i.MX RT700 has a Compute Subsystem which includes a primary ARM Cortex-M33 running at 325 MHz and Cadence Tensilica HiFi 4 DSP.
It also features an ultra-low power Sense Subsystem which includes a second ARM Cortex-M33 and Cadence Tensilica HiFi 1 DSP.

This pull request adds the soc and board support for the two HiFi cores.

[zephyrbot]

The following west manifest projects have changed revision in this Pull Request:

Name	Old Revision	New Revision	Diff
hal_xtensa	zephyrproject-rtos/hal_xtensa@baa56aa	zephyrproject-rtos/hal_xtensa@b38620c	zephyrproject-rtos/hal_xtensa@baa56aa3..b38620c7

✅ All manifest checks OK

Note: This message is automatically posted and updated by the Manifest GitHub Action.

[iuliana-prodan]

The twister tests are failing because the CI is using zephyr_sdk 0.16.8 which doesn't include the hifi1 and hifi4 toolchain for imxrt700.

Configuration saved to '/__w/zephyr/zephyr/twister-out/mimxrt700_evk_mimxrt798s_hifi1/samples/kernel/condition_variables/simple/sample.kernel.cond_var.simple/zephyr/.config'
Kconfig header saved to '/__w/zephyr/zephyr/twister-out/mimxrt700_evk_mimxrt798s_hifi1/samples/kernel/condition_variables/simple/sample.kernel.cond_var.simple/zephyr/include/generated/zephyr/autoconf.h'
CMake Error at /__w/zephyr/zephyr/cmake/compiler/gcc/target.cmake:12 (message):
  C compiler
  /opt/toolchains/zephyr-sdk-0.16.8/xtensa-nxp_rt700_hifi1_zephyr-elf/bin/xtensa-nxp_rt700_hifi1_zephyr-elf-gcc
  not found - Please check your toolchain installation

Locally I used zephyr-sdk-0.16.9-rc2 which had the 2 toolchain.

I see now that 0.17.0 was released.
@stephanosio when will the new toolchain be included in the CI?
Can I do the update?

[dcpleung]

Waiting for hal_nxp to be updated.

[github-actions]

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

[dleach02]

@iuliana-prodan the RT700 HAL PR merged. Can you update this PR to move the NXP HAL SHA to the tip and then resolve the merge conflicts? We can get this ready to merge quickly after the upstream v4.1 release

[iuliana-prodan]

@iuliana-prodan the RT700 HAL PR merged. Can you update this PR to move the NXP HAL SHA to the tip and then resolve the merge conflicts? We can get this ready to merge quickly after the upstream v4.1 release

Yes, I have this on my list :)
I'll do it this week!

[iuliana-prodan]

Changes since previous version:

• rebase and resolve conflicts with the M33 Core 0 and Core1 support for i.MXRT700;
• update west.yml only with commit id for Xtensa HAL (NXP hal was merged and updated in west.yml);