-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix RAM vector table for NCS36510 #4310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
/morph test |
retest uvisor |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The NCS36510 has 35 vectors, not 36.
The NCS36510 has 35 interrupts with
16 levels of programmable priority
Could you reflect this in the PR ?
@pan- Good catch! This came most probably from https://github.com/c1728p9/mbed-os/blob/d74e219685f1e55a6a01eb4bb7d4f0e3e46759da/targets/TARGET_ONSEMI/TARGET_NCS36510/device/NCS36510.h#L76 (it was set to 36) . As you quoted, the reference manual defines 35. |
Fix the ram address of the vector table on the NCS36510. Also reserve space for it in the linker scripts.
d74e219
to
5cf2255
Compare
Good catch @pan-. I updated the comment to reflect the correct number of interrupt vectors. I kept the size the same to keep 8 byte alignment. |
/morph test |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
Fix the ram address of the vector table on the NCS36510. Also reserve space for it in the linker scripts.
This is based on 94a0256 from the CMSIS_5 branch.