On Fri, Feb 5, 2021, 5:55 PM Grr <gebbe...@gmail.com> wrote: > > It absolutely is not including arch headers will break things. > > > > board.h: > > > > > https://www.github.com/apache/incubator-nuttx/tree/master/boards%2Farm%2Fstm32%2Fstm32f4discovery%2Finclude%2Fboard.h > > > > And the arch specific board configuration: > > > > > https://www.github.com/apache/incubator-nuttx/tree/master/boards%2Farm%2Fstm32%2Fstm32f4discovery%2Fsrc%2Fstm32f4discovery.h > > > > I'm thinking maybe the confusion is I said "arch specific" when I meant > "chip specific". I always talked about stm32 (which should be "subarch", > not "chip" to have "chip" referring to stm32f407|stm32f103|whatever. > Semantics) > > What I mean is there should be no problem at all calling STM32 header files > from a STM32 board (except for the fact they're not in include/ but in > src/) > > And for my purposes, it's needed
But there is a problem with it, which is why it's hard to do this. Please read the wiki page Greg posted which explains why you cannot include chip specific headers in board.h What is it that must go in there?
