Keith Packard

> And this allowed me to at least boot the PSA arch tests and run some crypto test cases. I am investigating more at the moment but in the mean...

I've pushed an update which omits the linker script changes as those aren't necessary unless something needs thread local storage (which doesn't appear to be true in the current code).

> @keith-packard I cannot build with it anymore because of the same issues as here: [#134 (comment)](https://github.com/zephyrproject-rtos/trusted-firmware-m/pull/134#issuecomment-3234808880) > > But as I said before the problem at least for Nordic...

Ok, I did a bunch more digging today and discovered that the existing patch didn't track picolibc 1.8.10 changes in initialization code. That version changed the symbols used as the...

Oh, as a bonus feature, I've also updated the llvm linker scripts -- those will also need the new constructor bounds symbols once ARM updates that toolchain to use picolibc...

and pushed another small set of changes that just stops using picolibc's crt0 entirely; we don't need any CPU initialization it might do, we just need memory set up and...

> Hey @keith-packard, thanks a lot for the detailed investigation! I tried the new version of this PR and I still could not boot TF-M in Nordic devices. I did...

> I'll certainly fix it; I'll go investigate and see if it seems like it will be easier to just add explicit code so that we don't end up with...

> Thanks again for the fix @keith-packard . I can now confirm that this patch works for Nordic devices :) > > Feel free to rework the history and let...

I don't know; I didn't try applying them to the development version.