You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by "raiden00pl (via GitHub)" <gi...@apache.org> on 2025/01/06 11:08:28 UTC
[I] Remove STM32 legacy pinmap [nuttx]
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: commits-unsubscribe@nuttx.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Remove STM32 legacy pinmap [nuttx]
Posted by "cederom (via GitHub)" <gi...@apache.org>.
cederom commented on issue #15432:
URL: https://github.com/apache/nuttx/issues/15432#issuecomment-2629531245
* I asked STM several times for NuttX RTOS contracting development support but they were not interested :-(
* We should not move with that subject forward, especially if with a big chance of breaking stuff, until we have an option to runtime validate all / most of the boards.
* Even simple build and runtime scripts can be made just to test changes and push the DRUNX forward. I have some boards and can help here :-) Will list the boards in a free moment.
* STM was always keen to share their devkits even for free so when we have a full list of boards I can requests free samples for me and for you @raiden00pl so we can move forward?
--
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-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Remove STM32 legacy pinmap [nuttx]
Posted by "cederom (via GitHub)" <gi...@apache.org>.
cederom commented on issue #15432:
URL: https://github.com/apache/nuttx/issues/15432#issuecomment-2629551786
Okay I have created list of hardware that I have at hand. Some modern devkits seems to have more powerful STLink MCU than the target MCU 🗡
@raiden00pl please mark the hardware that we need and I will try to ask STM for free samples so we could test changes in NuttX and add them all to DRUNX :-)
--
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-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Remove STM32 legacy pinmap [nuttx]
Posted by "raiden00pl (via GitHub)" <gi...@apache.org>.
raiden00pl commented on issue #15432:
URL: https://github.com/apache/nuttx/issues/15432#issuecomment-4306885982
testing on nucleo doesn't make much sense, because there's nothing that can break with these changes.
Boards worth checking:
stm32f429i-disco
stm32f4discovery
stm3240g-eval
stm3220g-eval
shenzhou
viewtool-stm32f107
nice-to-check boards (but most likely should be OK):
b-l475e-iot01a
stm32l476vg-disco
stm32l4r9ai-disco
fire-stm32v2
stm3210e-eval
--
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-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Remove STM32 legacy pinmap [nuttx]
Posted by "xiaoxiang781216 (via GitHub)" <gi...@apache.org>.
xiaoxiang781216 closed issue #15432: Remove STM32 legacy pinmap
URL: https://github.com/apache/nuttx/issues/15432
--
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-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Remove STM32 legacy pinmap [nuttx]
Posted by "raiden00pl (via GitHub)" <gi...@apache.org>.
raiden00pl commented on issue #15432:
URL: https://github.com/apache/nuttx/issues/15432#issuecomment-2630267626
@cederom changing most boars is easy and the risk of breaking something is marginal. Problematic are only boards with
peripherals that require complex pin configuration like displays or external memory.
And here comes the problem, because some of these boards are old and probably unavailable. Many boards are also from manufacturers other than ST.
--
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-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Remove STM32 legacy pinmap [nuttx]
Posted by "cederom (via GitHub)" <gi...@apache.org>.
cederom commented on issue #15432:
URL: https://github.com/apache/nuttx/issues/15432#issuecomment-4299661236
@raiden00pl big thank you for taking and leading this big task!
In the meantime I got NUCLEO-H755ZI-Q / MB1363-H755ZIQ-D01, it is not yet in the NuttX but seems compatible with existing configurations?
Regarding STM32F2, STM32F3, STM32WB I can ask my friends at www.arrow.com it should be get free samples or at least possible to borrow some devkits for testing.
Let me know how to migrate, lets split the job, so slowly in small steps but we move forward? You can create one migration that I will test on the hw, when I know how this works I can do some other migrations :-)
I understand your frustration, and I share it, vendors and users should be most interested in supporting this work. But vendors just want the money and users want the stuff for free :D
--
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-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Remove STM32 legacy pinmap [nuttx]
Posted by "raiden00pl (via GitHub)" <gi...@apache.org>.
raiden00pl commented on issue #15432:
URL: https://github.com/apache/nuttx/issues/15432#issuecomment-4298969853
The issue has been hanging here for over a year and there have been no offers of help except for Tomek.
Should I understand that no one uses STM32 with NuttX? So sad.
I can migrate the rest of the boards with some AI. This will require manual board-by-board review, but there's no other way.
There is no chance I will fix this issue manually (I value my time too much), and I see that no one else is interested in fixing it.
--
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-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Remove STM32 legacy pinmap [nuttx]
Posted by "linguini1 (via GitHub)" <gi...@apache.org>.
linguini1 commented on issue #15432:
URL: https://github.com/apache/nuttx/issues/15432#issuecomment-4380885073
Unfortunately I don't have any STM32 boards to test this against, but thanks for the hard work!
--
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-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org