Hi, On 04.08.2014 18:29, Chuck McManis wrote: > When you make the library it creates the nvic.h files for the various > parts. This is done because every part has a different set of > peripherals and associated interrupts. I know that the nvic.h files in the family subdirectories (e.g. libopencm3/stm32/f4/nvic.h) are autogenerated. What I meant to say is that there is no file that automatically pulls in the right header for the family (i.e. no libopencm3/stm32/nvic.h).
However, from looking at the examples, I just learned that I am supposed to include libopencm3/cm3/nvic.h, which then *does* pull in the right header for the specific chip. Thus, the issue is probably moot. Thanks, Norbert ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ libopencm3-devel mailing list libopencm3-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libopencm3-devel
