these are settings on the top layer that effect the whole project.

Name of the company that sells the micro controller. As listed on https://chipselect.org

type: string

Model number of the micro controller. As listed on https://chipselect.org

type: string

Model number is truncated so that it only contains relevant differences for code generation: flash and ram sizes are relevant, temperature range or package are not.

what type of project to generate.

type: enum

default: “make”

Possible values are:

• “hal only” : only creates the hardware driver files (in the hal/ folder) and hardware definitions (in the hal/hw/ folder)
• “embeetle” : create an Embeetle IDE project
• “make” : creates a makefile based “blinky” project.

defines the comment at the top of each generated file.

type: enum

default: “created”

Possible values are:

• “created” : file comment list date and time of file creation as well as configuration file name.
• “minimal” : short comment only stating the file name and that it was automatically created.

defines the location of the firmware code when run.

type: enum

default: “flash”

Possible values are:

• “flash” : firmware is located and run from the flash memory.
• “ram” : firmware is located and run from the RAM.
• “flash2ram” : firmware is located in flash, copied to RAM on boot and then executed from RAM.

if you use a “hal only” MBSP project located in a sub folder of your project then the name of the sub folder goes here.

type: string

default: “”

if something unexpected (like a hard fault) happens this defines what should happen:

type: enum

default: “halt”

Possible values are:

• “halt” : firmware stops executing.
• “reset” : firmware resets.