forked from mfulz_github/qmk_firmware
Minor documentation fixes - change \note entries to \warning where appropriate and remove/update old documentation.
This commit is contained in:
parent
e406140f11
commit
63a65a9598
|
@ -94,7 +94,7 @@
|
|||
* Several user application functions for FLASH and other special memory area manipulations are exposed by the bootloader,
|
||||
* allowing the user application to call into the bootloader at runtime to read and write FLASH data.
|
||||
*
|
||||
* \note The APIs exposed by the DFU class bootloader are \b NOT compatible with the API exposed by the official Atmel DFU bootloader.
|
||||
* \warning The APIs exposed by the DFU class bootloader are \b NOT compatible with the API exposed by the official Atmel DFU bootloader.
|
||||
*
|
||||
* By default, the bootloader API jump table is located 32 bytes from the end of the device's FLASH memory, and follows the
|
||||
* following layout:
|
||||
|
|
|
@ -76,7 +76,7 @@
|
|||
/** Structure for the association of attribute ID values to an attribute value in FLASH. A table of these
|
||||
* structures can then be built up for each supported UUID service within the device.
|
||||
*
|
||||
* \note This table must be terminated with a \ref SERVICE_ATTRIBUTE_TABLE_TERMINATOR element.
|
||||
* \attention This table must be terminated with a \ref SERVICE_ATTRIBUTE_TABLE_TERMINATOR element.
|
||||
*/
|
||||
typedef struct
|
||||
{
|
||||
|
|
Loading…
Reference in New Issue