raiden00pl opened a new issue, #15432: URL: https://github.com/apache/nuttx/issues/15432
### Description It's been quite some time since `CONFIG_STM32xx_USE_LEGACY_PINMAP` was introduced. Some upstream boards have already migrated to the new pinmap, but for many there is no progress. There was enough time for users to migrate their boards. Steps to fix this issue: - [ ] migrate `stm32f1` boards to new pinmap - [ ] migrate `stm32f2` boards to new pinmap - [ ] migrate `stm32f3` boards to new pinmap - [ ] migrate `stm32f4` boards to new pinmap - [ ] migrate `stm32l1` boards to new pinmap - [ ] migrate `stm32l4` boards to new pinmap - [ ] migrate `stm32l5` board to new pinmap - [ ] migrate `stm32wb` board to new pinmap - [ ] remove legacy pinmap from `stm32h7` - boards already migrated to new pinmap - [ ] remove legacy pinmap from `stm32f7` - boards already migrated to new pinmap - [ ] remove legacy pinmap from `stm32f0l0g0` - boards already migrated to new pinmap The biggest problem here is the port of `board/stm32` boards to the new pinmap, the number of stm32 boards is quite large, so practical there is no person who can test all modified board on real HW. In this case, we must accept the risk that part of the configuration will be broken, since compiling the code without errors doesn't provide certainty that the port is still working. Here is an example of me accidentally messing up the stm32f7 configuration while migrating the pinmap: https://github.com/apache/nuttx/pull/13915. We definitely need to watch out for similar cases. Is anyone willing to help with this issue? Maybe someone from px4 team is interested in helping? This issue is basically a result of fixes needed for your project and it was left in "half done" state with absolutely no progress for over a year. So sad... ### Verification - [X] I have verified before submitting the report. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
