Ease integration of RTOS, we need cmsis-compatible exceptional handler naming or API to install exceptional handler in RAM #211
Labels
No labels
bazel
bluetooth
board settings
boot_stage2
bug
build
c++
can't reproduce
clang
clib-interface
cmsis
code cleanliness
code size
compiler version issues
cyw43_driver
debug
discussion
documentation
duplicate
dynamic_clock
elf2uf2
enhancement
errata
filesystem
flash layout
floating point
FreeRTOS
hardware_adc
hardware_claim
hardware_clocks
hardware_dma
hardware_exception
hardware_flash
hardware_gpio
hardware_i2c
hardware_irq
hardware_pio
hardware_pwm
hardware_rcp
hardware_rtc
hardware_spi
hardware_sync
hardware_uart
hardware_vreg
hardware_watchdog
hardware_xosc
help wanted
host
IAR
installation
invalid
linker scripts
lto
lwip
mbedtls
missing API
needs reporter detail
networking
newlib
newlib-multicore
non-c
non-cmake
non-gcc
openocd
orphan PR
OS integration
pico_async_context
pico_base
pico_binary_info
pico_flash
picolibc
pico_lwip
pico_malloc
pico_multicore
pico_printf
pico_runtime
pico_stdio
pico_stdio_usb
pico_sync
pico_time
pico_util
pioasm
port
question
review
review2
rtos interop
runtime init
static library
svd
test
tinyusb
vscode
wifi integration
wontfix
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-raspberrypi/pico-sdk#211
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm porting Azure RTOS threadx to PICO and I can't submodule the threadx repo because I need to hook the pendsv and systick exceptional handlers.
In crt0.S, the SDK declare as isr_pendsv and isr_systick which are private and not conform to CMSIS standard, so the cm0 processor port of Azure RTOS need to be modified.
Or if you can provide a API similar to
irq_set_exclusive_handlerbut work for all entries include 0-15 exceptional handlers. Then I can install by user code after main. This is also good.Now, I can only modify the source of threadx to align with SDK naming, which is not flexible
yes we plan to add ability to set exception handlers (an omission)
also we can make these public; we may not rename them, but at that point you can inject a header via cmake to rename them via #define.
Links to #21 and #127
Where can I put my vote that at least the cortex specific handlers get proper CMSIS names?
Actually since these were private, we can likely rename them.
That would be really great! https://github.com/raspberrypi/pico-sdk/issues/21 has all necessary links to cmsis docs.
So your suggestion is to add below global macro definition in CMakeLists.txt to replace the symbol, right?
that was an option that would have workedd - albeit ugly-ly - but i've decided to add the real names now
(setting variables yes, via global CMake add_defitions - which is eveil - no!)
at least it works and I can now submodule my threadx repo without any change. I left this ticket open and let you decide when a better solution is ready
Could this be a candidate for Release 1.2?
#127 seems to be so this one will propably make sense to have in, too
merged
closing this for the ability to set exception handlers, see #21 if you want the CMSIS exception handler naming instead