For historical reasons (NuttX STM32 numbering) PX4 bus numbering is
1 based. All PX4 code, including, board code is written to assuming 1
based numbering. In the PX4 I2C driver the 1 is subtracted from the
buss number to address the freqency array. These macros are used to
allow the board config to define the bus numbers in terms of the NuttX
driver numbering. 1,2,3 for one based numbering (STM32) or 0,1,2
for zero based (Kinetis)
PX4_NUMBER_I2C_BUSES number of busses that the HW can support
not all of them my be usesd. I.E. The STM32F427 has 3 I2C
busses but only I2C1 and I2C3 are used.
Remove the notion of legacy from the api. The board level code
will perform the traslation to lecacy format on the STM32.
new targets will not need to do this as there is no case
where the serial number were used by mfg for tracking.
Extend board common api to get mfguid and mfguid formatted
This adds an api that return the MFGUID as an array of bytes
or a string.
The data is returned with the MSD at index 0 and the LSD at
index PX4_CPU_MFGUID_BYTE_LENGTH-1.
Removed all reodering defines from the api and hal
This abstraction will support mcu's with longer ID's then the
stm32 family.
It provids a common interface for byte and 32 bit word access
to the UUID data and a facility to reorder it.
David Sidrane