You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now the M33s are more and more common. Any plans for Armv8-M?
We will try with the Armv7-M config, but would you have some advice that might be useful? I hope that if we won't use the secure modes, it could be the same.
The text was updated successfully, but these errors were encountered:
I don't currently have any plans to implement ARMv8-M support but I would be happy to review and merge a PR for such support.
It would be cool to start with just the non-secure stuff and see if it just works as is. A person could then invest the time in reading the ARMv8-M documentation to see exactly what changes they would need to make to have it work in the secure mode as well. If it ends up adding registers to cover the additional secure mode then CrashDebug would probably need to be modified as well to expose the additional registers on such ARMv8-M dumps and not expose them on all other types of dumps (ARMv6/7-M, etc).
Now the M33s are more and more common. Any plans for Armv8-M?
We will try with the Armv7-M config, but would you have some advice that might be useful? I hope that if we won't use the secure modes, it could be the same.
The text was updated successfully, but these errors were encountered: