I'm developing firmware for a UAVCAN proxy card that can fulfill multiple roles, which are selected via configuration parameters stored in an external EEPROM.
Many of these roles rely on libraries written years ago. I'm facing a conflict where one role uses USART2 with the SD driver, while another uses USART2 with the UART driver. Each driver is well-suited to its specific role.
I’ve already implemented a dynamic resource manager that guarantees no two roles using the same hardware resource can be selected at the same time. Because of that, I don’t need the static resource conflict checks enforced by ChibiOS.
Is there any way to bypass those checks — a sort of “trust me, I’m an engineer” mode?
If not, I guess I’ll need to migrate the legacy SD-based code to use UARTD... but I have better plans for this summer !
No "ask chatgpt to migrate the code" will be accepted
