Hi David, Hi Miguel, thanks for your feedback!
David wrote: > Are the L5 and U5 the same with different marketing names or are there underlying IP differences? What is the delta? To me the U5 seems to essentially be a re-spin of the L5 on a new technology node. However, the IP blocks have been updated considerably. I assume such subtle differences in the IP blocks have been the reason for the breakage problems you mentioned? I agree with you and will start a new stm32u5 arch. Thanks again Michael Am Do., 9. Dez. 2021 um 15:47 Uhr schrieb David Sidrane < david.sidr...@nscdg.com>: > Hi Michael, > > Of course you are much closer to the problem than I am. So here is just my > opinion based on the stm32, stm32f7, stm32h7 lessons. > > Are the L5 and U5 the same with different marketing names or are there > underlying IP differences? What is the delta? > > I would head the direction of splitting them up unless there are only minor > pin map differences and then do those as wrapped includes (see the > stm32F412). > > The decoupling adds maintenance overhead but prevents the breakage that we > endured in the stm32. > > > > David > > > On Wed, Dec 8, 2021 at 10:54 PM Michael Jung <mij...@gmx.net> wrote: > > > Hello everybody, > > > > I have started to work on STM32U5 support for Apache NuttX and would like > > to get some feedback on how this should be integrated. Realizing that > > support STM32F0, STM32L0 and STM32G0 is all handled within > > /arch/arm/src/stm32l0g0f0, I would like to rename /arch/arch/src/stm32l5 > to > > /arch/arm/src/stm32l5u5 and change filenames and literals accordingly. > > Would you please let me know whether corresponding changes will be > > acceptable? > > > > Thanks! > > Michael > > >
