Skip to content
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

The interrupt vector table offset register should not be set. #370

Open
SeeDeer opened this issue Mar 8, 2024 · 1 comment
Open

The interrupt vector table offset register should not be set. #370

SeeDeer opened this issue Mar 8, 2024 · 1 comment
Labels
bug Something isn't working discussion Flagged for discussion during the weekly team meeting hardware New hardware or architecture support request

Comments

@SeeDeer
Copy link

SeeDeer commented Mar 8, 2024

/* Setup Vector Table Offset Register. */
MOV r0, #0xE000E000 // Build address of NVIC registers
LDR r1, =_vectors // Pickup address of vector table
STR r1, [r0, #0xD08] // Set vector table address

/* Set system stack pointer from vector value. */
LDR r0, =_tx_thread_system_stack_ptr // Build address of system stack pointer
LDR r1, =_vectors // Pickup address of vector table
LDR r1, [r1] // Pickup reset stack pointer
STR r1, [r0] // Save system stack pointer

in ports/cortex_m7/gnu/example_build/tx_initialize_low_level.S file, the interrupt vector table offset register is set, which will cause trouble for users. The interrupt vector table is generally set before RTOS starts, such as in the startup.s file, or when performing an upgrade jump.

If the above code operation is intended to set the following variable '_tx_thread_system_stack_ptr'. It is recommended to let '_tx_thread_system_stack_ptr' be set by the user.

Also the variable '_tx_thread_system_stack_ptr' is not used to reset the interrupt stack.

@SeeDeer SeeDeer added bug Something isn't working hardware New hardware or architecture support request labels Mar 8, 2024
@fdesbiens fdesbiens added the discussion Flagged for discussion during the weekly team meeting label Feb 27, 2025
@fdesbiens
Copy link
Contributor

My apologies for the long delay. I will flag this issue for discussion with the group of committers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working discussion Flagged for discussion during the weekly team meeting hardware New hardware or architecture support request
Projects
None yet
Development

No branches or pull requests

2 participants