manifest: update cmsis-nn to v6.0.0 & tflite-micro

[JordanYates]

Update cmsis-nn to version 6.0.0.
Revision history can be found at:
https://arm-software.github.io/CMSIS-NN/latest/rev_hist.html

New upstream revision is the v6.0.0 release tag + module.yml ARM-software/CMSIS-NN@6982301

[zephyrbot]

The following west manifest projects have been modified in this Pull Request:

Name	Old Revision	New Revision	Diff
cmsis-nn	zephyrproject-rtos/cmsis-nn@0c8669d (zephyr)	zephyrproject-rtos/cmsis-nn@ea987c1 (zephyr-v6.0.0)	zephyrproject-rtos/[email protected]
tflite-micro	zephyrproject-rtos/tflite-micro@1a34dca (main)	zephyrproject-rtos/tflite-micro@48613f7 (zephyr)	zephyrproject-rtos/[email protected]

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

[JordanYates]

Updating CMSIS-NN also requires updating tflite-micro.
@XenuIsWatching do you remember how you generated the third_party_static folders last time?

[XenuIsWatching]

Updating CMSIS-NN also requires updating tflite-micro. @XenuIsWatching do you remember how you generated the third_party_static folders last time?

Yes, I put the info on how those were obtain in the commit message such as here zephyrproject-rtos/tflite-micro@c331051

[JordanYates]

Updating CMSIS-NN also requires updating tflite-micro. @XenuIsWatching do you remember how you generated the third_party_static folders last time?

Yes, I put the info on how those were obtain in the commit message such as here zephyrproject-rtos/tflite-micro@c331051

Origin: kissfft
License: BSD-3-Clause
URL: https://github.com/mborgerding/kissfft/archive/refs/tags/v130.zip
Commit: 918336beac80868ad3011cb283063bb224e3e5da
Patch File: third_party/kissfft/kissfft.patch
Purpose: Used by TensorFlow Lite Micro
Maintained-by: External

Tells me what was imported, but not how. Did you build some sample application which pulled down all the sources which were then copied, or did you manually find git commit hashes and download sources from Github? Where did the patch files come from?

[XenuIsWatching]

Updating CMSIS-NN also requires updating tflite-micro. @XenuIsWatching do you remember how you generated the third_party_static folders last time?

Yes, I put the info on how those were obtain in the commit message such as here zephyrproject-rtos/tflite-micro@c331051

Origin: kissfft
License: BSD-3-Clause
URL: https://github.com/mborgerding/kissfft/archive/refs/tags/v130.zip
Commit: 918336beac80868ad3011cb283063bb224e3e5da
Patch File: third_party/kissfft/kissfft.patch
Purpose: Used by TensorFlow Lite Micro
Maintained-by: External

Tells me what was imported, but not how. Did you build some sample application which pulled down all the sources which were then copied, or did you manually find git commit hashes and download sources from Github? Where did the patch files come from?

These are the same files that are pulled in as apart of the tflite-micro build process.
https://github.com/tensorflow/tflite-micro/tree/main/tensorflow/lite/micro/tools/make

For example you can find the kissfft within here which is downloaded, unzipped, and had the patch file applied
https://github.com/tensorflow/tflite-micro/blob/71fba59b5bebfd64b48e167bfcb669fff568ec74/tensorflow/lite/micro/tools/make/kissfft_download.sh#L48

Skimming through the folder... I noticed that if you update tflite-micro, it looks like flatbuffers will need to be updated along with the patch file applied
https://github.com/tensorflow/tflite-micro/pull/2274/files#diff-c7caf59f2356917e38d2acda5785d137d47d5ec33302d219795efe88440b3b49

They were all manually pulled down from the download links

[XenuIsWatching]

As something I just found digging though... it looks like they pull a specific 'hash' of cmsis-nn which is this https://github.com/tensorflow/tflite-micro/blob/71fba59b5bebfd64b48e167bfcb669fff568ec74/tensorflow/lite/micro/tools/make/ext_libs/cmsis_download.sh#L50

It only looks like that hash is 2 commits behind the v6.0.0, so it 'may' still work with the v6.0.0

As I typed this... I noticed those 2 commits are only updates to pdsc files :/

[JordanYates]

Included the tflite-micro in this PR. I don't have permissions for the forked repo, and I don't think merging my commit into main or zephyr is the right approach. Would prefer a zephyr-v3.7 branch or similar.

Actual branch this is pointing at: https://github.com/JordanYates/tflite-micro/commits/zephyr-v3.7/

[XenuIsWatching]

Included the tflite-micro in this PR. I don't have permissions for the forked repo, and I don't think merging my commit into main or zephyr is the right approach. Would prefer a zephyr-v3.7 branch or similar.

Actual branch this is pointing at: https://github.com/JordanYates/tflite-micro/commits/zephyr-v3.7/

looks like all the CI is passing now 👍 but I don't have admin rights to create a branch for zephyr-3.7. We may have to poke around to get that created

[nashif]

Can we please get issues resolved before RC2 on Friday, this PR shall go in for 3.7 as per the TSC meeting today.

[nashif]

need to remove leading slash /

[nashif]

update to e1eecbee18aa8f7f0ad7e90f8b335564eb52c13f please

[ithinuel]

based on the reviews and updates in zephyrproject-rtos/tflite-micro#6,

the sha should be 48613f7ba1ffbda46ad771a77a35408f48f922e9 instead. (https://github.com/zephyrproject-rtos/tflite-micro’s zephyr branch should be updated accordingly)

[JordanYates]

@ithinuel is correct, the original export commit had some duplicated files, please repush the last commit @nashif

[nashif]

@JordanYates

done

revisit please