modules: Update trusted-firmware-m for picolibc

[keith-packard]

This adds linker script bits and compiler options so that trusted-firmware-m will build with picolibc.

This has not been merged to the Zephyr trusted-firmware-m repository yet, that PR is zephyrproject-rtos/trusted-firmware-m#134

[github-actions]

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

Name	Old Revision	New Revision	Diff
tf-m-tests	zephyrproject-rtos/tf-m-tests@a90702b (main,zephyr_tf-m-tests_v2.2.0)	zephyrproject-rtos/tf-m-tests#17	zephyrproject-rtos/tf-m-tests#17/files
trusted-firmware-m	zephyrproject-rtos/trusted-firmware-m@c2f9edc (main,zephyr_tf-m_v2.2.0)	zephyrproject-rtos/trusted-firmware-m#134	zephyrproject-rtos/trusted-firmware-m#134/files

⛔ DNM label due to: 2 projects with PR revision

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

[keith-packard]

This is waiting for zephyr SDK 0.17.4

[nandojve]

Hi @keith-packard ,

I would like to printout that #94470 shows that arm platform needs some fixes. I'm not sure if that affects your CI tests.

[keith-packard]

Hi @keith-packard ,

I would like to printout that #94470 shows that arm platform needs some fixes. I'm not sure if that affects your CI tests.

Thanks. It's also blocked on the SDK at present, so once that's merged I'll see what else is broken.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[keith-packard]

Hi @keith-packard ,
I would like to printout that #94470 shows that arm platform needs some fixes. I'm not sure if that affects your CI tests.

Thanks. It's also blocked on the SDK at present, so once that's merged I'll see what else is broken.

All seems to work fine with just this patch.

[tomi-font]

just need some competent people (not me) to review the TF-M changes

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[keith-packard]

I've restructured the tf-m patch a bunch, fixing all of the linker scripts instead of just those used by Zephyr CI and removing the TLS changes as they aren't required with current tf-m code. Overall, the changes are a whole lot cleaner now, I'm hoping they'll be easier to review as a result.

[keith-packard]

I added a PR for tf-m-tests to this as well; there were some minor picolibc compatibility changes needed once I discovered that the Zephyr build had disabled assert(0) when building these tests.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[keith-packard]

I added a PR for tf-m-tests to this as well; there were some minor picolibc compatibility changes needed once I discovered that the Zephyr build had disabled assert(0) when building these tests.

[keith-packard]

(sorry, must have clicked 'close' by mistake)

[keith-packard]

re-opening without the tf-m-tests change

[keith-packard]

Oof. I'm not sure what's up with github, but I can't get this PR re-opened. I've re-created it as #100544

[tomi-font]

Probably because you have force-pushed your branch since the close?

[keith-packard]

Probably because you have force-pushed your branch since the close?

Probably so. The ways of github are sometimes mysterious. In any case, thanks for the review of #100544.