NewMCU

Introduction

This page will explain how to add a new microcontroller to the bootloader

Client

The following additions must be made on the client side

JSON

All json files which contain infromation about a microcontroller must be saved under "config/Devices". The name of the json file will be the identifier for the newly added mcu. It should be unique across all microcontrollers. You can use subfolders to organize your json files, but these will be ignored for identification of a microcontroller.

Structure

The following table will use a hierarchy format to identify json values. The following example will explain the structure:

{
  "device": {
    "general": {
      "id":   "atmega328p",
      "vendor": "Microchip",
      "arch": "AVR",
      "subarch": "ATMega",
      "name": "Atmega328p"
    }
  }
}

The arch value will be identified by the string "/device/general/arch"

Value	Description	Example Value
/device/general/id	A unique identifier for the microcontroller. It is recommended to use the same value as the filename	atmega328p
/device/general/vendor	Device Vendor of the Microcontroller	Microchip
/device/general/arch	The Architecture of the Microcontroller	AVR
/device/general/subarch	The Sub Category of the Microcontroller, can be empty if non-existent	ATmega
/device/general/name	The full Name of the microcontroller in "human readable form"	Atmega328p
/device/flash/total	Total flash space of the device	1KB
/device/flash/available	Available flash of the device. This value must be the flash size which the bootloader can access and write to.	2GB
/device/eeprom/total	Total EEPROM size of the Microcontroller (can be 0 if there is none)	0B
/device/eeprom/available	Available EEPROM size of the Microcontroller (can be 0 if there is none)	42KB

|