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

Remove STM32 legacy pinmap #15432

Open
1 of 12 tasks
raiden00pl opened this issue Jan 6, 2025 · 0 comments
Open
1 of 12 tasks

Remove STM32 legacy pinmap #15432

raiden00pl opened this issue Jan 6, 2025 · 0 comments
Labels
Arch: arm Issues related to ARM (32-bit) architecture Area: Board support Board support issues Type: Improvement

Comments

@raiden00pl
Copy link
Member

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: #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

  • I have verified before submitting the report.
@raiden00pl raiden00pl added Community: Question Further information is requested Type: Improvement Arch: arm Issues related to ARM (32-bit) architecture Area: Board support Board support issues and removed Community: Question Further information is requested labels Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Arch: arm Issues related to ARM (32-bit) architecture Area: Board support Board support issues Type: Improvement
Projects
None yet
Development

No branches or pull requests

1 participant