linguini1 opened a new pull request, #16348:
URL: https://github.com/apache/nuttx/pull/16348
## Summary
The previous interrupt implementation allowed only one single interrupt mode
to be selected. The debug assertion is now updated to allow the entire range of
possible interrupt combinations (a 4-bit field), up to 0xf.
## Impact
The `DEBUGASSERT` will no longer fail for users who are making use of the
multiple interrupt mode selection.
This affects all RP2040 boards where code is using more than one interrupt
type (no such code exists in the kernel or apps yet, only for users). No other
systems affected.
## Testing
Successful build locally, verified that the assertion no longer fails when
`DEBUGASSERT` is enabled on a W5500-EVB Pico.
```console
$ ./tools/configure.sh w5500-evb-pico:usbnsh
$ make menuconfig
# Enable debug features and CONFIG_DEBUG_ASSERTIONS
# Enable CONFIG_DEV_GPIO and CONFIG_EXAMPLES_GPIO
$ make -j
/usr/lib/gcc/arm-none-eabi/14.2.0/../../../../arm-none-eabi/bin/ld: warning:
rp2040_boot_stage2.elf has a LOAD segment with RWX permissions
LD: nuttx
Memory region Used Size Region Size %age Used
flash: 244 KB 2 MB 11.91%
sram: 24120 B 264 KB 8.92%
Generating: nuttx.uf2
Done.
```
Previous behaviour: program would crash at the assert statement
Current behaviour: assertion passes
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
