Hi,
it seems that the style of the output changes either if a variable or
function declaration is part of such group.
But this is not always the case. For example, even though there are such
declarations in
http://riot-os.org/api/boards_2native_2include_2board_8h.html
"LED handlers" and "MTD em
Hi,
finally, I'm trying to improve the doxygen documentation of
board*.h/periph*.h configuration files for my ESP8266 port.
I tried to use the @name command together with @{ and }@ , to group all
definitions that are related to a certain peripheral interface, e.g.,
I2C interface.
It seems that t
Hi!
I have to disagree here. While the peripherals belong to the MCU
hardware-wise, the actual board might limit the available
configurations, as pins might be used as GPIOs, and the peripherals
might not be available. Therefore it would also belong to the board.h.
IMO it is *possible* to merge in
Hi Gunar,
in `periph_conf.h` we configure all the MCU/CPU peripherals, i.e., SPI, I2C bus
and so on,
these are typically not bound to a board. On the other hand, in `board.h` we
configure all
board specific stuff, like for instance LEDs which are not part of the MCU.
While LEDs also
need a cert
Hi,
I'm trying again to sort the definitions of board configurations. I feel
like doing this for the tenth time.
I have taken a look at many board.h, periph_conf.h, board_common.h and
periph_conf_common.h files for different platforms, eg., Arduino*,
Nucleo*, IoTlab, ...
The difference between *
