I am unable to run MCUXpresso Secure Provisioning Tool v10 or v9 AARCH version on macOS Sequoia 15.2 on a new M4 MacBook Pro.
The app won't start.
Any suggestion?
Thank you!
David
解決済! 解決策の投稿を見る。
Hi David,
the dyioib file paths are cryptic, but from the stack the I suspect the issue is with Segger J-Link.
Could you confirm you have installed J-Link. Have you used the Universal (I guess so) installer, or the Apple Silicon Installer?
No, SEC tool does not need Rosetta, but it might happen that if the PyOCD python finds library that is for different architecture and then it emits the messages that it has Intel architecture and it requires Arm.
If you have the Segger installed, I'd
Please let me know your findings.
Regards,
Libor
P.S. I tried SEC tool on almost clean 15.1.1 and then upgraded to 15.2 Sequoia (M1) - in both cases the SEC tool runs there.
I have run the app in the verbose mode and it seems that a file packed by PyInstaller is using wrong architecture because I am getting this error:
have 'x86_64', need 'arm64e' or 'arm64'
It might mean that the issue is not related to my Sequoia macOS but your securep package.
You can find the log attached bellow.
Should the securep app work without Rosetta 2 installed? I don't have Rosetta 2 installed.
David
Hi David,
the dyioib file paths are cryptic, but from the stack the I suspect the issue is with Segger J-Link.
Could you confirm you have installed J-Link. Have you used the Universal (I guess so) installer, or the Apple Silicon Installer?
No, SEC tool does not need Rosetta, but it might happen that if the PyOCD python finds library that is for different architecture and then it emits the messages that it has Intel architecture and it requires Arm.
If you have the Segger installed, I'd
Please let me know your findings.
Regards,
Libor
P.S. I tried SEC tool on almost clean 15.1.1 and then upgraded to 15.2 Sequoia (M1) - in both cases the SEC tool runs there.
Hi Libor,
removing the Segger J-Link helped.
Thank you!
David
Hi David,
MCUXpresso Secure Provisioning Tool v10 supports macOS 14, see Release Notes. It is expected that newer macOS version will be supported in upcoming tool versions later this year.
You can try to run securep with "-v" (verbose mode) to understand, where is a problem and try to fix yourself.