{"arduino": {"arduino-due-blinky": {"chip": "atsam3x8e", "board": "arduino-due", "boardfamily": "arduino", "path": "arduino/arduino/arduino-due-blinky.7z", "icon": null, "info": "microcontroller: atsam3x8e\nboard: arduino-due\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/due\n\n\ninfo:\nNo readme file found in original project."}, "arduino-due-serial": {"chip": "atsam3x8e", "board": "arduino-due", "boardfamily": "arduino", "path": "arduino/arduino/arduino-due-serial.7z", "icon": null, "info": "microcontroller: atsam3x8e\nboard: arduino-due\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/due\n\n\ninfo:\nNo readme file found in original project."}, "arduino-mega-2560-r3-blinky": {"chip": "atmega2560", "board": "arduino-mega-2560-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-mega-2560-r3-blinky.7z", "icon": null, "info": "microcontroller: atmega2560\nboard: arduino-mega-2560-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/mega-2560-r3\n\n\ninfo:\nNo readme file found in original project."}, "arduino-mega-2560-r3-serial": {"chip": "atmega2560", "board": "arduino-mega-2560-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-mega-2560-r3-serial.7z", "icon": null, "info": "microcontroller: atmega2560\nboard: arduino-mega-2560-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/mega-2560-r3\n\n\ninfo:\nNo readme file found in original project."}, "arduino-nano-blinky": {"chip": "atmega328p-mu", "board": "arduino-nano", "boardfamily": "arduino", "path": "arduino/arduino/arduino-nano-blinky.7z", "icon": null, "info": "microcontroller: atmega328p-mu\nboard: arduino-nano\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/nano\n\n\ninfo:\nNo readme file found in original project."}, "arduino-nano-every-blinky": {"chip": "atmega4809", "board": "arduino-nano-every", "boardfamily": "arduino", "path": "arduino/arduino/arduino-nano-every-blinky.7z", "icon": null, "info": "microcontroller: atmega4809\nboard: arduino-nano-every\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/nano-every\n\n\ninfo:\nNo readme file found in original project."}, "arduino-nano-every-serial": {"chip": "atmega4809", "board": "arduino-nano-every", "boardfamily": "arduino", "path": "arduino/arduino/arduino-nano-every-serial.7z", "icon": null, "info": "microcontroller: atmega4809\nboard: arduino-nano-every\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/nano-every\n\n\ninfo:\nNo readme file found in original project."}, "arduino-nano-serial": {"chip": "atmega328p-mu", "board": "arduino-nano", "boardfamily": "arduino", "path": "arduino/arduino/arduino-nano-serial.7z", "icon": null, "info": "microcontroller: atmega328p-mu\nboard: arduino-nano\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/nano\n\n\ninfo:\nNo readme file found in original project."}, "arduino-uno-blaster-2022": {"chip": "atmega328p-pu", "board": "arduino-uno-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-blaster-2022.7z", "icon": null, "info": "microcontroller: atmega328p-pu\nboard: arduino-uno-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-r3\n\n\ninfo:\n"}, "arduino-uno-r3-blinky": {"chip": "atmega328p-pu", "board": "arduino-uno-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-r3-blinky.7z", "icon": null, "info": "microcontroller: atmega328p-pu\nboard: arduino-uno-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-r3\n\n\ninfo:\nNo readme file found in original project."}, "arduino-uno-r3-serial": {"chip": "atmega328p-pu", "board": "arduino-uno-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-r3-serial.7z", "icon": null, "info": "microcontroller: atmega328p-pu\nboard: arduino-uno-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-r3\n\n\ninfo:\nNo readme file found in original project."}, "arduino-uno-smd-r3-blinky": {"chip": "atmega328p-mu", "board": "arduino-uno-smd-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-smd-r3-blinky.7z", "icon": null, "info": "microcontroller: atmega328p-mu\nboard: arduino-uno-smd-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-smd-r3\n\n\ninfo:\nNo readme file found in original project."}, "arduino-uno-smd-r3-serial": {"chip": "atmega328p-mu", "board": "arduino-uno-smd-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-smd-r3-serial.7z", "icon": null, "info": "microcontroller: atmega328p-mu\nboard: arduino-uno-smd-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-smd-r3\n\n\ninfo:\nNo readme file found in original project."}, "arduino-uno-ssd1306-oled128x32-i2c": {"chip": "atmega328p-pu", "board": "arduino-uno-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-ssd1306-oled128x32-i2c.7z", "icon": null, "info": "microcontroller: atmega328p-pu\nboard: arduino-uno-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-r3\n\n\ninfo:\n"}, "arduino-uno-ssd1306-oled128x64-i2c": {"chip": "atmega328p-pu", "board": "arduino-uno-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-ssd1306-oled128x64-i2c.7z", "icon": null, "info": "microcontroller: atmega328p-pu\nboard: arduino-uno-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-r3\n\n\ninfo:\nmicrocontroller: atmega328p-pu\nboard: arduino-uno-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nicon: icons/folder/closed/blinky.png\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-r3\n\n\ninfo:\nNo readme file found in original project."}}, "demsay": {"demedukit-accelerometer-oled-ntc-example": {"chip": "stm32g030c8", "board": "demedukit-stm32g030", "boardfamily": "demedukit", "path": "demsay/demedukit/demedukit-accelerometer-oled-ntc-example.7z", "icon": null, "info": "microcontroller: stm32g030c8\nboard: demedukit-stm32g030\nmicrocontroller manufacturer: stmicro\nboard manufacturer: demsay\nlink: https://embeetle.com/#supported-hardware/demsay/boards/demedukit-stm32g030\n\n\ninfo:\nhttps://gitlab.com/demedukit/demedukit-accelerometer-oled-ntc-example"}, "demedukit-button-control-example": {"chip": "stm32g030c8", "board": "demedukit-stm32g030", "boardfamily": "demedukit", "path": "demsay/demedukit/demedukit-button-control-example.7z", "icon": null, "info": "microcontroller: stm32g030c8\nboard: demedukit-stm32g030\nmicrocontroller manufacturer: stmicro\nboard manufacturer: demsay\nlink: https://embeetle.com/#supported-hardware/demsay/boards/demedukit-stm32g030\n\n\ninfo:\nhttps://gitlab.com/demedukit/demedukit-buton-control-example"}, "demedukit-led-control-example": {"chip": "stm32g030c8", "board": "demedukit-stm32g030", "boardfamily": "demedukit", "path": "demsay/demedukit/demedukit-led-control-example.7z", "icon": null, "info": "microcontroller: stm32g030c8\nboard: demedukit-stm32g030\nmicrocontroller manufacturer: stmicro\nboard manufacturer: demsay\nlink: https://embeetle.com/#supported-hardware/demsay/boards/demedukit-stm32g030\n\n\ninfo:\nhttps://gitlab.com/demedukit/demedukit-led-control-example"}}, "fermionic": {"fd5mlm0-devkit-03": {"chip": "fd5mlm01032n", "board": "fd5mlm0-devkit-03", "boardfamily": "devkit", "path": "fermionic/devkit/fd5mlm0-devkit-03.7z", "icon": null, "info": "microcontroller: fd5mlm01032n\nboard: fd5mlm0-devkit-03\nmicrocontroller manufacturer: fermionic\nboard manufacturer: fermionic\nlink: https://embeetle.com/#supported-hardware/fermionic/boards/fd5mlm0-devkit-03\n\n\ninfo:\nREADME CONTENT"}}, "geehy": {"apm32e103ze-mini": {"chip": "apm32e103zet6", "board": "apm32e103ze-mini", "boardfamily": "apm32-mini", "path": "geehy/apm32-mini/apm32e103ze-mini.7z", "icon": null, "info": "microcontroller: apm32e103ze\nboard: apm32e103ze-mini\nmicrocontroller manufacturer: geehy\nboard manufacturer: geehy\nlink: https://embeetle.com/#supported-hardware/geehy/boards/apm32e103ze-mini\n\n\ninfo:\nThis project was originally a Geehy Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "apm32f003f6p6-mini-baremetal": {"chip": "apm32f003f6p6", "board": "apm32f003f6p6-mini", "boardfamily": "apm32-mini", "path": "geehy/apm32-mini/apm32f003f6p6-mini-baremetal.7z", "icon": null, "info": "microcontroller: apm32f003f6p6\nboard: apm32f003f6p6-mini\nmicrocontroller manufacturer: geehy\nboard manufacturer: geehy\nlink: https://embeetle.com/#supported-hardware/geehy/boards/apm32f003f6p6-mini\n\n\ninfo:\nThis is a baremetal project for the APM32F003F6P6-MINI board."}, "apm32f003f6p6-mini": {"chip": "apm32f003f6p6", "board": "apm32f003f6p6-mini", "boardfamily": "apm32-mini", "path": "geehy/apm32-mini/apm32f003f6p6-mini.7z", "icon": null, "info": "microcontroller: apm32f003f6p6\nboard: apm32f003f6p6-mini\nmicrocontroller manufacturer: geehy\nboard manufacturer: geehy\nlink: https://embeetle.com/#supported-hardware/geehy/boards/apm32f003f6p6-mini\n\n\ninfo:\nThis project was originally a Geehy Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure.\n\nThe project files are identical for the APM32F0-MINI boards.\nThe heuristics in the chip files lead to the selection of the\ncorrect files for the build."}, "apm32f030r8-mini": {"chip": "apm32f030r8t6", "board": "apm32f030r8-mini", "boardfamily": "apm32-mini", "path": "geehy/apm32-mini/apm32f030r8-mini.7z", "icon": null, "info": "microcontroller: apm32f030r8\nboard: apm32f030r8-mini\nmicrocontroller manufacturer: geehy\nboard manufacturer: geehy\nlink: https://embeetle.com/#supported-hardware/geehy/boards/apm32f030r8-mini\n\n\ninfo:\nThis project was originally a Geehy Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure.\n\nThe project files are identical for the APM32F0-MINI boards.\nThe heuristics in the chip files lead to the selection of the\ncorrect files for the build."}, "apm32f030rc-mini": {"chip": "apm32f030rct6", "board": "apm32f030rc-mini", "boardfamily": "apm32-mini", "path": "geehy/apm32-mini/apm32f030rc-mini.7z", "icon": null, "info": "microcontroller: apm32f030rc\nboard: apm32f030rc-mini\nmicrocontroller manufacturer: geehy\nboard manufacturer: geehy\nlink: https://embeetle.com/#supported-hardware/geehy/boards/apm32f030rc-mini\n\n\ninfo:\nThis project was originally a Geehy Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure.\n\nThe project files are identical for the APM32F0-MINI boards.\nThe heuristics in the chip files lead to the selection of the\ncorrect files for the build."}, "apm32f072vb-mini": {"chip": "apm32f072vbt6", "board": "apm32f072vb-mini", "boardfamily": "apm32-mini", "path": "geehy/apm32-mini/apm32f072vb-mini.7z", "icon": null, "info": "microcontroller: apm32f072vb\nboard: apm32f072vb-mini\nmicrocontroller manufacturer: geehy\nboard manufacturer: geehy\nlink: https://embeetle.com/#supported-hardware/geehy/boards/apm32f072vb-mini\n\n\ninfo:\nThis project was originally a Geehy Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure.\n\nThe project files are identical for the APM32F0-MINI boards.\nThe heuristics in the chip files lead to the selection of the\ncorrect files for the build."}, "apm32f407vg-mini": {"chip": "apm32f407vgt6", "board": "apm32f407vg-mini", "boardfamily": "apm32-mini", "path": "geehy/apm32-mini/apm32f407vg-mini.7z", "icon": null, "info": "microcontroller: apm32f407vg\nboard: apm32f407vg-mini\nmicrocontroller manufacturer: geehy\nboard manufacturer: geehy\nlink: https://embeetle.com/#supported-hardware/geehy/boards/apm32f407vg-mini\n\n\ninfo:\nThis project was originally a Geehy Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "apm32f407ig-tiny": {"chip": "apm32f407igt6", "board": "apm32f407ig-tiny", "boardfamily": "apm32-tiny", "path": "geehy/apm32-tiny/apm32f407ig-tiny.7z", "icon": null, "info": "microcontroller: apm32f407ig\nboard: apm32f407ig-tiny\nmicrocontroller manufacturer: geehy\nboard manufacturer: geehy\nlink: https://embeetle.com/#supported-hardware/geehy/boards/apm32f407ig-tiny\n\n\ninfo:\nThis project was originally a Geehy Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "apm32f411vc-tiny-baremetal": {"chip": "apm32f411vet6", "board": "apm32f411vc-tiny", "boardfamily": "apm32-tiny", "path": "geehy/apm32-tiny/apm32f411vc-tiny-baremetal.7z", "icon": null, "info": "microcontroller: apm32f411vet6\nboard: apm32f411vc-tiny\nmicrocontroller manufacturer: geehy\nboard manufacturer: geehy\nlink: https://embeetle.com/#supported-hardware/geehy/boards/apm32f411vc-tiny\n\n\ninfo:\nThis is a baremetal project for the APM32F411VC-TINY board."}, "apm32f411vc-tiny-chipconfig": {"chip": "apm32f411vet6", "board": "apm32f411vc-tiny", "boardfamily": "apm32-tiny", "path": "geehy/apm32-tiny/apm32f411vc-tiny-chipconfig.7z", "icon": null, "info": "microcontroller: apm32f411vet6\nboard: apm32f411vc-tiny\nmicrocontroller manufacturer: geehy\nboard manufacturer: geehy\nlink: https://embeetle.com/#supported-hardware/geehy/boards/apm32f411vc-tiny\n\n\ninfo:\nThis is a baremetal project for the APM32F411VC-TINY board."}, "apm32f411vc-tiny-dal": {"chip": "apm32f411vet6", "board": "apm32f411vc-tiny", "boardfamily": "apm32-tiny", "path": "geehy/apm32-tiny/apm32f411vc-tiny-dal.7z", "icon": null, "info": "microcontroller: apm32f411ve\nboard: apm32f411vc-tiny\nmicrocontroller manufacturer: geehy\nboard manufacturer: geehy\nlink: https://embeetle.com/#supported-hardware/geehy/boards/apm32f411vc-tiny\n\n\ninfo:\nThis project was originally a Geehy Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "apm32f411vc-tiny": {"chip": "apm32f411vet6", "board": "apm32f411vc-tiny", "boardfamily": "apm32-tiny", "path": "geehy/apm32-tiny/apm32f411vc-tiny.7z", "icon": null, "info": "microcontroller: apm32f411ve\nboard: apm32f411vc-tiny\nmicrocontroller manufacturer: geehy\nboard manufacturer: geehy\nlink: https://embeetle.com/#supported-hardware/geehy/boards/apm32f411vc-tiny\n\n\ninfo:\nThis project was originally a Geehy Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}}, "giga": {"gd32e230c-eval": {"chip": "gd32e230c8t6", "board": "gd32e230c-eval", "boardfamily": "gd32-eval", "path": "giga/gd32-eval/gd32e230c-eval.7z", "icon": null, "info": "microcontroller: gd32e230c8t6\nboard: gd32e230c-eval\nmicrocontroller manufacturer: giga\nboard manufacturer: giga\nlink: https://embeetle.com/#supported-hardware/giga/boards/gd32e230c_eval\n\n\ninfo:\nThis project was originally a Giga Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "gd32e231c-start": {"chip": "gd32e231c8t6", "board": "gd32e231c-start", "boardfamily": "gd32-start", "path": "giga/gd32-start/gd32e231c-start.7z", "icon": null, "info": "microcontroller: gd32e231c8t6\nboard: gd32e231c-start\nmicrocontroller manufacturer: giga\nboard manufacturer: giga\nlink: https://embeetle.com/#supported-hardware/giga/boards/gd32e231c_start\n\n\ninfo:\nThis project was originally a Giga Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "gd32e232k-start": {"chip": "gd32e232k8q7", "board": "gd32e232k-start", "boardfamily": "gd32-start", "path": "giga/gd32-start/gd32e232k-start.7z", "icon": null, "info": "microcontroller: gd32e232k8q7\nboard: gd32e232k-start\nmicrocontroller manufacturer: giga\nboard manufacturer: giga\nlink: https://embeetle.com/#supported-hardware/giga/boards/gd32e232k_start\n\n\ninfo:\nThis project was originally a Giga Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "gd32f303r-start": {"chip": "gd32f303rgt6", "board": "gd32f303r-start", "boardfamily": "gd32-start", "path": "giga/gd32-start/gd32f303r-start.7z", "icon": null, "info": "microcontroller: gd32f303rgt6\nboard: gd32f303r-start\nmicrocontroller manufacturer: giga\nboard manufacturer: giga\nlink: https://embeetle.com/#supported-hardware/giga/boards/gd32f303r-start\n\n\ninfo:\nThis project was originally a Giga Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "gd32vf103c-start": {"chip": "gd32vf103cbt6", "board": "gd32vf103c-start", "boardfamily": "gd32-start", "path": "giga/gd32-start/gd32vf103c-start.7z", "icon": null, "info": "microcontroller: gd32vf103cbt6\nboard: gd32vf103c-start\nmicrocontroller manufacturer: giga\nboard manufacturer: giga\nlink: https://embeetle.com/#supported-hardware/giga/boards/gd32vf103c_start\n\n\ninfo:\nThis project was originally a Giga Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}}, "hpmicro": {"hpm6200evk-revb": {"chip": "hpm6280", "board": "hpm6200evk-revb", "boardfamily": "hpm-evk", "path": "hpmicro/hpm-evk/hpm6200evk-revb.7z", "icon": null, "info": "microcontroller: hpm6280\nboard: hpm6200evk-revb\nmicrocontroller manufacturer: hpmicro\nboard manufacturer: hpmicro\nlink: https://embeetle.com/#supported-hardware/hpmicro/boards/hpm6200evk-revb\n\n\ninfo:\nThis project was originally a CMake-based HPMicro sample project which we've slightly\nmodified to fit the typical Embeetle project structure."}, "hpm6750evkmini": {"chip": "hpm6750ivm", "board": "hpm6750evkmini", "boardfamily": "hpm-evk", "path": "hpmicro/hpm-evk/hpm6750evkmini.7z", "icon": null, "info": "microcontroller: hpm6750ivm\nboard: hpm6750evkmini\nmicrocontroller manufacturer: hpmicro\nboard manufacturer: hpmicro\nlink: https://embeetle.com/#supported-hardware/hpmicro/boards/hpm6750evkmini\n\n\ninfo:\nThis project was originally a CMake-based HPMicro sample project which we've slightly\nmodified to fit the typical Embeetle project structure.\n\nWARNING:\nadded hpm_sdk_version.h"}}, "microchip-atmel": {"arduino-due-blinky": {"chip": "atsam3x8e", "board": "arduino-due", "boardfamily": "arduino", "path": "arduino/arduino/arduino-due-blinky.7z", "icon": null, "info": "microcontroller: atsam3x8e\nboard: arduino-due\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/due\n\n\ninfo:\nNo readme file found in original project."}, "arduino-due-serial": {"chip": "atsam3x8e", "board": "arduino-due", "boardfamily": "arduino", "path": "arduino/arduino/arduino-due-serial.7z", "icon": null, "info": "microcontroller: atsam3x8e\nboard: arduino-due\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/due\n\n\ninfo:\nNo readme file found in original project."}, "arduino-mega-2560-r3-blinky": {"chip": "atmega2560", "board": "arduino-mega-2560-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-mega-2560-r3-blinky.7z", "icon": null, "info": "microcontroller: atmega2560\nboard: arduino-mega-2560-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/mega-2560-r3\n\n\ninfo:\nNo readme file found in original project."}, "arduino-mega-2560-r3-serial": {"chip": "atmega2560", "board": "arduino-mega-2560-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-mega-2560-r3-serial.7z", "icon": null, "info": "microcontroller: atmega2560\nboard: arduino-mega-2560-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/mega-2560-r3\n\n\ninfo:\nNo readme file found in original project."}, "arduino-nano-blinky": {"chip": "atmega328p-mu", "board": "arduino-nano", "boardfamily": "arduino", "path": "arduino/arduino/arduino-nano-blinky.7z", "icon": null, "info": "microcontroller: atmega328p-mu\nboard: arduino-nano\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/nano\n\n\ninfo:\nNo readme file found in original project."}, "arduino-nano-every-blinky": {"chip": "atmega4809", "board": "arduino-nano-every", "boardfamily": "arduino", "path": "arduino/arduino/arduino-nano-every-blinky.7z", "icon": null, "info": "microcontroller: atmega4809\nboard: arduino-nano-every\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/nano-every\n\n\ninfo:\nNo readme file found in original project."}, "arduino-nano-every-serial": {"chip": "atmega4809", "board": "arduino-nano-every", "boardfamily": "arduino", "path": "arduino/arduino/arduino-nano-every-serial.7z", "icon": null, "info": "microcontroller: atmega4809\nboard: arduino-nano-every\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/nano-every\n\n\ninfo:\nNo readme file found in original project."}, "arduino-nano-serial": {"chip": "atmega328p-mu", "board": "arduino-nano", "boardfamily": "arduino", "path": "arduino/arduino/arduino-nano-serial.7z", "icon": null, "info": "microcontroller: atmega328p-mu\nboard: arduino-nano\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/nano\n\n\ninfo:\nNo readme file found in original project."}, "arduino-uno-blaster-2022": {"chip": "atmega328p-pu", "board": "arduino-uno-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-blaster-2022.7z", "icon": null, "info": "microcontroller: atmega328p-pu\nboard: arduino-uno-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-r3\n\n\ninfo:\n"}, "arduino-uno-r3-blinky": {"chip": "atmega328p-pu", "board": "arduino-uno-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-r3-blinky.7z", "icon": null, "info": "microcontroller: atmega328p-pu\nboard: arduino-uno-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-r3\n\n\ninfo:\nNo readme file found in original project."}, "arduino-uno-r3-serial": {"chip": "atmega328p-pu", "board": "arduino-uno-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-r3-serial.7z", "icon": null, "info": "microcontroller: atmega328p-pu\nboard: arduino-uno-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-r3\n\n\ninfo:\nNo readme file found in original project."}, "arduino-uno-smd-r3-blinky": {"chip": "atmega328p-mu", "board": "arduino-uno-smd-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-smd-r3-blinky.7z", "icon": null, "info": "microcontroller: atmega328p-mu\nboard: arduino-uno-smd-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-smd-r3\n\n\ninfo:\nNo readme file found in original project."}, "arduino-uno-smd-r3-serial": {"chip": "atmega328p-mu", "board": "arduino-uno-smd-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-smd-r3-serial.7z", "icon": null, "info": "microcontroller: atmega328p-mu\nboard: arduino-uno-smd-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-smd-r3\n\n\ninfo:\nNo readme file found in original project."}, "arduino-uno-ssd1306-oled128x32-i2c": {"chip": "atmega328p-pu", "board": "arduino-uno-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-ssd1306-oled128x32-i2c.7z", "icon": null, "info": "microcontroller: atmega328p-pu\nboard: arduino-uno-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-r3\n\n\ninfo:\n"}, "arduino-uno-ssd1306-oled128x64-i2c": {"chip": "atmega328p-pu", "board": "arduino-uno-r3", "boardfamily": "arduino", "path": "arduino/arduino/arduino-uno-ssd1306-oled128x64-i2c.7z", "icon": null, "info": "microcontroller: atmega328p-pu\nboard: arduino-uno-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-r3\n\n\ninfo:\nmicrocontroller: atmega328p-pu\nboard: arduino-uno-r3\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: arduino\nicon: icons/folder/closed/blinky.png\nlink: https://embeetle.com/#supported-hardware/arduino/boards/uno-r3\n\n\ninfo:\nNo readme file found in original project."}, "cip-united-pic32mz1024efg144": {"chip": "pic32mz1024efg144", "board": "cip-united-pic32mz1024efg144", "boardfamily": "cip-united", "path": "microchip-atmel/cip-united/cip-united-pic32mz1024efg144.7z", "icon": null, "info": "microcontroller: pic32mz1024efg144\nboard: cip-united-pic32mz1024efg144\nmicrocontroller manufacturer: microchip-atmel\nboard manufacturer: microchip-atmel\nlink: \n\n\ninfo:\nThis project was originally a CIP United project."}}, "nordic": {"pca10056-freertos": {"chip": "nrf52840", "board": "pca10056", "boardfamily": "pca", "path": "nordic/pca/pca10056-freertos.7z", "icon": null, "info": "microcontroller: nrf52840\nboard: pca10056\nmicrocontroller manufacturer: nordic\nboard manufacturer: nordic\nlink: https://embeetle.com/#supported-hardware/nordic/boards/pca10056\n\n\ninfo:\nThis project was originally a Nordic Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "pca10056": {"chip": "nrf52840", "board": "pca10056", "boardfamily": "pca", "path": "nordic/pca/pca10056.7z", "icon": null, "info": "microcontroller: nrf52840\nboard: pca10056\nmicrocontroller manufacturer: nordic\nboard manufacturer: nordic\nlink: https://embeetle.com/#supported-hardware/nordic/boards/pca10056\n\n\ninfo:\nThis project was originally a Nordic Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "pca10100-freertos": {"chip": "nrf52833", "board": "pca10100", "boardfamily": "pca", "path": "nordic/pca/pca10100-freertos.7z", "icon": null, "info": "microcontroller: nrf52833\nboard: pca10100\nmicrocontroller manufacturer: nordic\nboard manufacturer: nordic\nlink: https://embeetle.com/#supported-hardware/nordic/boards/pca10100\n\n\ninfo:\nThis project was originally a Nordic Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}}, "nuvoton": {"numaker-m031sd-v1-2": {"chip": "m031sd2ae", "board": "numaker-m031sd-v1-2", "boardfamily": "numaker", "path": "nuvoton/numaker/numaker-m031sd-v1-2.7z", "icon": null, "info": "microcontroller: m031sd2ae\nboard: numaker-m031sd-v1-2\nmicrocontroller manufacturer: nuvoton\nboard manufacturer: nuvoton\nlink: https://embeetle.com/#supported-hardware/nuvoton/boards/numaker_m031sd_v1_2\n\n\ninfo:\nThis project was originally a Nuvoton Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "numaker-m031se-v1-1": {"chip": "m031se3ae", "board": "numaker-m031se-v1-1", "boardfamily": "numaker", "path": "nuvoton/numaker/numaker-m031se-v1-1.7z", "icon": null, "info": "microcontroller: m031se3ae\nboard: numaker-m031se-v1-1\nmicrocontroller manufacturer: nuvoton\nboard manufacturer: nuvoton\nlink: https://embeetle.com/#supported-hardware/nuvoton/boards/numaker_m031se_v1_1\n\n\ninfo:\nThis project was originally a Nuvoton Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "numaker-m031tb-v1-1": {"chip": "m031tb0ae", "board": "numaker-m031tb-v1-1", "boardfamily": "numaker", "path": "nuvoton/numaker/numaker-m031tb-v1-1.7z", "icon": null, "info": "microcontroller: m031tb0ae\nboard: numaker-m031tb-v1-1\nmicrocontroller manufacturer: nuvoton\nboard manufacturer: nuvoton\nlink: https://embeetle.com/#supported-hardware/nuvoton/boards/numaker_m031tb_v1_1\n\n\ninfo:\nThis project was originally a Nuvoton Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "numaker-m031tc-v1-1": {"chip": "m031tc1ae", "board": "numaker-m031tc-v1-1", "boardfamily": "numaker", "path": "nuvoton/numaker/numaker-m031tc-v1-1.7z", "icon": null, "info": "microcontroller: m031tc1ae\nboard: numaker-m031tc-v1-1\nmicrocontroller manufacturer: nuvoton\nboard manufacturer: nuvoton\nlink: https://embeetle.com/#supported-hardware/nuvoton/boards/numaker_m031tc_v1_1\n\n\ninfo:\nThis project was originally a Nuvoton Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "numaker-m032se-v1-3": {"chip": "m032se3ae", "board": "numaker-m032se-v1-3", "boardfamily": "numaker", "path": "nuvoton/numaker/numaker-m032se-v1-3.7z", "icon": null, "info": "microcontroller: m032se3ae\nboard: numaker-m032se-v1-3\nmicrocontroller manufacturer: nuvoton\nboard manufacturer: nuvoton\nlink: https://embeetle.com/#supported-hardware/nuvoton/boards/numaker_m032se_v1_3\n\n\ninfo:\nThis project was originally a Nuvoton Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "numaker-m263ki-v1-2": {"chip": "m263kiaae", "board": "numaker-m263ki-v1-2", "boardfamily": "numaker", "path": "nuvoton/numaker/numaker-m263ki-v1-2.7z", "icon": null, "info": "microcontroller: m263kiaae\nboard: numaker-m263ki-v1-2\nmicrocontroller manufacturer: nuvoton\nboard manufacturer: nuvoton\nlink: https://embeetle.com/#supported-hardware/nuvoton/boards/numaker_m263ki_v1_2\n\n\ninfo:\nThis project was originally a Nuvoton Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "numaker-m483kg-v1-1": {"chip": "m483kgcae2a", "board": "numaker-m483kg-v1-1", "boardfamily": "numaker", "path": "nuvoton/numaker/numaker-m483kg-v1-1.7z", "icon": null, "info": "microcontroller: m483kgcae2a\nboard: numaker-m483kg-v1-1\nmicrocontroller manufacturer: nuvoton\nboard manufacturer: nuvoton\nlink: https://embeetle.com/#supported-hardware/nuvoton/boards/numaker_m483kg_v1_1\n\n\ninfo:\nThis project was originally a Nuvoton Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}, "nutiny-nuc029sde-v1-0": {"chip": "nuc029sde", "board": "nutiny-nuc029sde-v1-0", "boardfamily": "nutiny", "path": "nuvoton/nutiny/nutiny-nuc029sde-v1-0.7z", "icon": null, "info": "microcontroller: nuc029sde\nboard: nutiny-nuc029sde-v1-0\nmicrocontroller manufacturer: nuvoton\nboard manufacturer: nuvoton\nlink: https://embeetle.com/#supported-hardware/nuvoton/boards/nutiny_nuc029sde_v1_0\n\n\ninfo:\nThis project was originally a Nuvoton Eclipse sample project\nwhich we've slightly modified to fit the typical Embeetle project\nstructure."}}, "nxp": {"frdm-k22f": {"chip": "mk22fn512vlh12", "board": "frdm-k22f", "boardfamily": "frdm", "path": "nxp/frdm/frdm-k22f.7z", "icon": null, "info": "microcontroller: mk22fn512vlh12\nboard: frdm-k22f\nmicrocontroller manufacturer: nxp\nboard manufacturer: nxp\nlink: https://embeetle.com/#supported-hardware/nxp/boards/frdm-k22f\n\n\ninfo:\nThis project was originally an NXP sample project which we've\nslightly modified to fit the typical Embeetle project structure."}, "frdm-k32l2b3": {"chip": "k32l2b31vlh0a", "board": "frdm-k32l2b3", "boardfamily": "frdm", "path": "nxp/frdm/frdm-k32l2b3.7z", "icon": null, "info": "microcontroller: k32l2b31vlh0a\nboard: frdm-k32l2b3\nmicrocontroller manufacturer: nxp\nboard manufacturer: nxp\nlink: https://embeetle.com/#supported-hardware/nxp/boards/frdm-k32l2b3\n\n\ninfo:\nThis project was originally an NXP sample project which we've\nslightly modified to fit the typical Embeetle project structure."}, "frdm-k64f": {"chip": "mk64fn1m0vll12", "board": "frdm-k64f", "boardfamily": "frdm", "path": "nxp/frdm/frdm-k64f.7z", "icon": null, "info": "microcontroller: mk64fn1m0vll12\nboard: frdm-k64f\nmicrocontroller manufacturer: nxp\nboard manufacturer: nxp\nlink: https://embeetle.com/#supported-hardware/nxp/boards/frdm-k64f\n\n\ninfo:\nThis project was originally an NXP sample project which we've\nslightly modified to fit the typical Embeetle project structure."}, "frdm-kl27z": {"chip": "mkl27z64vlh4", "board": "frdm-kl27z", "boardfamily": "frdm", "path": "nxp/frdm/frdm-kl27z.7z", "icon": null, "info": "microcontroller: mkl27z64vlh4\nboard: frdm-kl27z\nmicrocontroller manufacturer: nxp\nboard manufacturer: nxp\nlink: https://embeetle.com/#supported-hardware/nxp/boards/frdm-kl27z\n\n\ninfo:\nThis project was originally an NXP sample project which we've\nslightly modified to fit the typical Embeetle project structure."}, "frdm-kl46z-baremetal": {"chip": "mkl46z256vll4", "board": "frdm-kl46z", "boardfamily": "frdm", "path": "nxp/frdm/frdm-kl46z-baremetal.7z", "icon": null, "info": "microcontroller: mkl46z256vll4\nboard: frdm-kl46z\nmicrocontroller manufacturer: nxp\nboard manufacturer: nxp\nlink: https://embeetle.com/#supported-hardware/nxp/boards/frdm-kl46z\n\n\ninfo:\nThis project was created by Sergio Prado and published on GitHub:\nhttps://github.com/sergioprado/bare-metal-arm\n\nIt's a minimalistic blinky sample project for the FRDM-KL46Z board. We've\nreplaced Sergio's makefile with the default one from Embeetle, such that the\nproject is fully integrated in Embeetle.\n\nThank you Sergio!"}, "frdm-kl46z": {"chip": "mkl46z256vll4", "board": "frdm-kl46z", "boardfamily": "frdm", "path": "nxp/frdm/frdm-kl46z.7z", "icon": null, "info": "microcontroller: mkl46z256vll4\nboard: frdm-kl46z\nmicrocontroller manufacturer: nxp\nboard manufacturer: nxp\nlink: https://embeetle.com/#supported-hardware/nxp/boards/frdm-kl46z\n\n\ninfo:\nThis project was originally an NXP sample project which we've\nslightly modified to fit the typical Embeetle project structure."}}, "raspberry-pi": {"rpi-pico": {"chip": "rp2040", "board": "rpi-pico", "boardfamily": "rpi-pico", "path": "raspberry-pi/rpi-pico/rpi-pico.7z", "icon": null, "info": "microcontroller: rp2040\nboard: rpi-pico\nmicrocontroller manufacturer: raspberry-pi\nboard manufacturer: raspberry-pi\nlink: https://embeetle.com/#supported-hardware/raspberry-pi/boards/rpi-pico\n\n\ninfo:\n"}}, "stmicro": {"demedukit-accelerometer-oled-ntc-example": {"chip": "stm32g030c8", "board": "demedukit-stm32g030", "boardfamily": "demedukit", "path": "demsay/demedukit/demedukit-accelerometer-oled-ntc-example.7z", "icon": null, "info": "microcontroller: stm32g030c8\nboard: demedukit-stm32g030\nmicrocontroller manufacturer: stmicro\nboard manufacturer: demsay\nlink: https://embeetle.com/#supported-hardware/demsay/boards/demedukit-stm32g030\n\n\ninfo:\nhttps://gitlab.com/demedukit/demedukit-accelerometer-oled-ntc-example"}, "demedukit-button-control-example": {"chip": "stm32g030c8", "board": "demedukit-stm32g030", "boardfamily": "demedukit", "path": "demsay/demedukit/demedukit-button-control-example.7z", "icon": null, "info": "microcontroller: stm32g030c8\nboard: demedukit-stm32g030\nmicrocontroller manufacturer: stmicro\nboard manufacturer: demsay\nlink: https://embeetle.com/#supported-hardware/demsay/boards/demedukit-stm32g030\n\n\ninfo:\nhttps://gitlab.com/demedukit/demedukit-buton-control-example"}, "demedukit-led-control-example": {"chip": "stm32g030c8", "board": "demedukit-stm32g030", "boardfamily": "demedukit", "path": "demsay/demedukit/demedukit-led-control-example.7z", "icon": null, "info": "microcontroller: stm32g030c8\nboard: demedukit-stm32g030\nmicrocontroller manufacturer: stmicro\nboard manufacturer: demsay\nlink: https://embeetle.com/#supported-hardware/demsay/boards/demedukit-stm32g030\n\n\ninfo:\nhttps://gitlab.com/demedukit/demedukit-led-control-example"}, "stm32f3-disco-freertos": {"chip": "stm32f303vc", "board": "stm32f3-disco", "boardfamily": "disco", "path": "stmicro/disco/stm32f3-disco-freertos.7z", "icon": null, "info": "microcontroller: stm32f303vc\nboard: stm32f3-disco\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/disco-stm32f3\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "stm32f3-disco": {"chip": "stm32f303vc", "board": "stm32f3-disco", "boardfamily": "disco", "path": "stmicro/disco/stm32f3-disco.7z", "icon": null, "info": "microcontroller: stm32f303vc\nboard: stm32f3-disco\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/disco-stm32f3\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "stm32f4-disco-freertos": {"chip": "stm32f407vg", "board": "stm32f4-disco", "boardfamily": "disco", "path": "stmicro/disco/stm32f4-disco-freertos.7z", "icon": null, "info": "microcontroller: stm32f407vg\nboard: stm32f4-disco\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/disco-stm32f4\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "stm32f4-disco": {"chip": "stm32f407vg", "board": "stm32f4-disco", "boardfamily": "disco", "path": "stmicro/disco/stm32f4-disco.7z", "icon": null, "info": "microcontroller: stm32f407vg\nboard: stm32f4-disco\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/disco-stm32f4\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "stm32f429i-disco-freertos": {"chip": "stm32f429zi", "board": "stm32f429i-disco", "boardfamily": "disco", "path": "stmicro/disco/stm32f429i-disco-freertos.7z", "icon": null, "info": "microcontroller: stm32f429zi\nboard: stm32f429i-disco\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/disco-stm32f429i\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "stm32f429i-disco-lcd": {"chip": "stm32f429zi", "board": "stm32f429i-disco", "boardfamily": "disco", "path": "stmicro/disco/stm32f429i-disco-lcd.7z", "icon": null, "info": "microcontroller: stm32f429zi\nboard: stm32f429i-disco\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/disco-stm32f429i\n\n\ninfo:\nThis project was created by Aleksei Prokopov (see https://github.com/roboter)."}, "stm32f429i-disco-lvgl": {"chip": "stm32f429zi", "board": "stm32f429i-disco", "boardfamily": "disco", "path": "stmicro/disco/stm32f429i-disco-lvgl.7z", "icon": null, "info": "microcontroller: stm32f429zi\nboard: stm32f429i-disco\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/disco-stm32f429i\n\n\ninfo:\nThis LVGL demo project is created by G\u00e1bor Kiss-V\u00e1mosi\n(https://github.com/lvgl/lv_port_stm32f429_disco) and ported to Embeetle IDE by Aleksei\nProkopov (https://github.com/roboter and\nhttps://github.com/roboter/Hardware/tree/main/STM32/STM32F429-Discovery/embeetle/lv_port_stm32f429_disco)\n\nNote:\nIt's important to add the -DSTM32F4 flag to the TARGET_CFLAGS and\nTARGET_CXXFLAGS in '/config/dashboard.mk' such that LVGL\nworks properly."}, "stm32f429i-disco": {"chip": "stm32f429zi", "board": "stm32f429i-disco", "boardfamily": "disco", "path": "stmicro/disco/stm32f429i-disco.7z", "icon": null, "info": "microcontroller: stm32f429zi\nboard: stm32f429i-disco\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/disco-stm32f429i\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "stm32f746g-disco-freertos": {"chip": "stm32f746ng", "board": "stm32f746g-disco", "boardfamily": "disco", "path": "stmicro/disco/stm32f746g-disco-freertos.7z", "icon": null, "info": "microcontroller: stm32f746ng\nboard: stm32f746g-disco\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/disco-stm32f746g\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "stm32f746g-disco-lvgl": {"chip": "stm32f746ng", "board": "stm32f746g-disco", "boardfamily": "disco", "path": "stmicro/disco/stm32f746g-disco-lvgl.7z", "icon": null, "info": "microcontroller: stm32f746ng\nboard: stm32f746g-disco\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/disco-stm32f746g\n\n\ninfo:\nThis LVGL demo project is created by G\u00e1bor Kiss-V\u00e1mosi\n(https://github.com/lvgl/lv_port_stm32f746_disco) and ported to Embeetle IDE by Aleksei\nProkopov (https://github.com/roboter and\nhttps://github.com/roboter/Hardware/tree/main/STM32/32F746GDISCOVERY/embeetle/lv_port_stm32f746_disco)\n\nNote:\nIt's important to add the -DSTM32F7 flag to the TARGET_CFLAGS and\nTARGET_CXXFLAGS in '/config/dashboard.mk' such that LVGL\nworks properly."}, "stm32f746g-disco": {"chip": "stm32f746ng", "board": "stm32f746g-disco", "boardfamily": "disco", "path": "stmicro/disco/stm32f746g-disco.7z", "icon": null, "info": "microcontroller: stm32f746ng\nboard: stm32f746g-disco\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/disco-stm32f746g\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f030r8-freertos": {"chip": "stm32f030r8", "board": "nucleo-f030r8", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f030r8-freertos.7z", "icon": null, "info": "microcontroller: stm32f030r8\nboard: nucleo-f030r8\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f030r8\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f030r8": {"chip": "stm32f030r8", "board": "nucleo-f030r8", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f030r8.7z", "icon": null, "info": "microcontroller: stm32f030r8\nboard: nucleo-f030r8\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f030r8\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f031k6-freertos": {"chip": "stm32f031k6", "board": "nucleo-f031k6", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f031k6-freertos.7z", "icon": null, "info": "microcontroller: stm32f031k6\nboard: nucleo-f031k6\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f031k6\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f031k6": {"chip": "stm32f031k6", "board": "nucleo-f031k6", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f031k6.7z", "icon": null, "info": "microcontroller: stm32f031k6\nboard: nucleo-f031k6\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f031k6\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f072rb-freertos": {"chip": "stm32f072rb", "board": "nucleo-f072rb", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f072rb-freertos.7z", "icon": null, "info": "microcontroller: stm32f072rb\nboard: nucleo-f072rb\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f072rb\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f072rb": {"chip": "stm32f072rb", "board": "nucleo-f072rb", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f072rb.7z", "icon": null, "info": "microcontroller: stm32f072rb\nboard: nucleo-f072rb\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f072rb\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f303k8-freertos": {"chip": "stm32f303k8", "board": "nucleo-f303k8", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f303k8-freertos.7z", "icon": null, "info": "microcontroller: stm32f303k8\nboard: nucleo-f303k8\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f303k8\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f303k8": {"chip": "stm32f303k8", "board": "nucleo-f303k8", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f303k8.7z", "icon": null, "info": "microcontroller: stm32f303k8\nboard: nucleo-f303k8\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f303k8\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f401re-freertos": {"chip": "stm32f401re", "board": "nucleo-f401re", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f401re-freertos.7z", "icon": null, "info": "microcontroller: stm32f401re\nboard: nucleo-f401re\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f401re\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f401re": {"chip": "stm32f401re", "board": "nucleo-f401re", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f401re.7z", "icon": null, "info": "microcontroller: stm32f401re\nboard: nucleo-f401re\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f401re\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f446re-freertos": {"chip": "stm32f446re", "board": "nucleo-f446re", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f446re-freertos.7z", "icon": null, "info": "microcontroller: stm32f446re\nboard: nucleo-f446re\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f446re\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f446re-oled": {"chip": "stm32f446re", "board": "nucleo-f446re", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f446re-oled.7z", "icon": null, "info": "microcontroller: stm32f446re\nboard: nucleo-f446re\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f446re\n\n\ninfo:\nAuthor: Husamuldeen Al-daffaie\nGithub: https://github.com/hussamaldean\n\nThis project is about interfacing 0.96\" 128*64 OLED Display with SSD1306 Driver \nwith STM32F446RE-Nucleo64.\nThe connection as following:\n\n\n * This SSD1306 LCD uses I2C for communication\n *\n * Library features functions for drawing lines, rectangles and circles.\n *\n * It also allows you to draw texts and characters using appropriate functions\n * provided in library.\n *\n * Default pinout\n *\nSSD1306 |STM32F446RE |DESCRIPTION\n--------------------------------------\nVCC |3.3V |\nGND |GND |\nSCL |PB8 |Serial clock line\nSDA |PB9 |Serial data line"}, "nucleo-f446re": {"chip": "stm32f446re", "board": "nucleo-f446re", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f446re.7z", "icon": null, "info": "microcontroller: stm32f446re\nboard: nucleo-f446re\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f446re\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f722ze-freertos": {"chip": "stm32f722ze", "board": "nucleo-f722ze", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f722ze-freertos.7z", "icon": null, "info": "microcontroller: stm32f722ze\nboard: nucleo-f722ze\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f722ze\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f722ze": {"chip": "stm32f722ze", "board": "nucleo-f722ze", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f722ze.7z", "icon": null, "info": "microcontroller: stm32f722ze\nboard: nucleo-f722ze\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f722ze\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f746zg-freertos": {"chip": "stm32f746zg", "board": "nucleo-f746zg", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f746zg-freertos.7z", "icon": null, "info": "microcontroller: stm32f746zg\nboard: nucleo-f746zg\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f746zg\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f746zg": {"chip": "stm32f746zg", "board": "nucleo-f746zg", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f746zg.7z", "icon": null, "info": "microcontroller: stm32f746zg\nboard: nucleo-f746zg\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f746zg\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f767zi-freertos": {"chip": "stm32f767zi", "board": "nucleo-f767zi", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f767zi-freertos.7z", "icon": null, "info": "microcontroller: stm32f767zi\nboard: nucleo-f767zi\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f767zi\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-f767zi": {"chip": "stm32f767zi", "board": "nucleo-f767zi", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-f767zi.7z", "icon": null, "info": "microcontroller: stm32f767zi\nboard: nucleo-f767zi\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-f767zi\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-g031k8-freertos": {"chip": "stm32g031k8", "board": "nucleo-g031k8", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-g031k8-freertos.7z", "icon": null, "info": "microcontroller: stm32g031k8\nboard: nucleo-g031k8\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-g031k8\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-g031k8": {"chip": "stm32g031k8", "board": "nucleo-g031k8", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-g031k8.7z", "icon": null, "info": "microcontroller: stm32g031k8\nboard: nucleo-g031k8\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-g031k8\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-g070rb-freertos": {"chip": "stm32g070rb", "board": "nucleo-g070rb", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-g070rb-freertos.7z", "icon": null, "info": "microcontroller: stm32g070rb\nboard: nucleo-g070rb\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-g070rb\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-g070rb": {"chip": "stm32g070rb", "board": "nucleo-g070rb", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-g070rb.7z", "icon": null, "info": "microcontroller: stm32g070rb\nboard: nucleo-g070rb\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-g070rb\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-g0b1re-freertos": {"chip": "stm32g0b1re", "board": "nucleo-g0b1re", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-g0b1re-freertos.7z", "icon": null, "info": "microcontroller: stm32g0b1re\nboard: nucleo-g0b1re\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-g0b1re\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-g0b1re": {"chip": "stm32g0b1re", "board": "nucleo-g0b1re", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-g0b1re.7z", "icon": null, "info": "microcontroller: stm32g0b1re\nboard: nucleo-g0b1re\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-g0b1re\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-h723zg-freertos": {"chip": "stm32h723zg", "board": "nucleo-h723zg", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-h723zg-freertos.7z", "icon": null, "info": "microcontroller: stm32h723zg\nboard: nucleo-h723zg\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-h723zg\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-h723zg": {"chip": "stm32h723zg", "board": "nucleo-h723zg", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-h723zg.7z", "icon": null, "info": "microcontroller: stm32h723zg\nboard: nucleo-h723zg\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-h723zg\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-h743zi-freertos": {"chip": "stm32h743zi", "board": "nucleo-h743zi", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-h743zi-freertos.7z", "icon": null, "info": "microcontroller: stm32h743zi\nboard: nucleo-h743zi\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-h743zi\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-h743zi": {"chip": "stm32h743zi", "board": "nucleo-h743zi", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-h743zi.7z", "icon": null, "info": "microcontroller: stm32h743zi\nboard: nucleo-h743zi\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-h743zi\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-l053r8-freertos": {"chip": "stm32l053r8", "board": "nucleo-l053r8", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-l053r8-freertos.7z", "icon": null, "info": "microcontroller: stm32l053r8\nboard: nucleo-l053r8\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-l053r8\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-l053r8": {"chip": "stm32l053r8", "board": "nucleo-l053r8", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-l053r8.7z", "icon": null, "info": "microcontroller: stm32l053r8\nboard: nucleo-l053r8\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-l053r8\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-l412kb-freertos": {"chip": "stm32l412kb", "board": "nucleo-l412kb", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-l412kb-freertos.7z", "icon": null, "info": "microcontroller: stm32l412kb\nboard: nucleo-l412kb\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-l412kb\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-l412kb": {"chip": "stm32l412kb", "board": "nucleo-l412kb", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-l412kb.7z", "icon": null, "info": "microcontroller: stm32l412kb\nboard: nucleo-l412kb\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-l412kb\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-l476rg-freertos": {"chip": "stm32l476rg", "board": "nucleo-l476rg", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-l476rg-freertos.7z", "icon": null, "info": "microcontroller: stm32l476rg\nboard: nucleo-l476rg\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-l476rg\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-l476rg": {"chip": "stm32l476rg", "board": "nucleo-l476rg", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-l476rg.7z", "icon": null, "info": "microcontroller: stm32l476rg\nboard: nucleo-l476rg\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-l476rg\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "nucleo-wb55rg": {"chip": "stm32wb55rg", "board": "nucleo-wb55rg", "boardfamily": "nucleo", "path": "stmicro/nucleo/nucleo-wb55rg.7z", "icon": null, "info": "microcontroller: stm32wb55rg\nboard: nucleo-wb55rg\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-wb55rg\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "p-nucleo-wb55-nucleo": {"chip": "stm32wb55rg", "board": "nucleo-wb55rg", "boardfamily": "nucleo", "path": "stmicro/nucleo/p-nucleo-wb55-nucleo.7z", "icon": null, "info": "microcontroller: stm32wb55rg\nboard: nucleo-wb55rg\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/nucleo-wb55rg\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "p-nucleo-wb55-usbdongle": {"chip": "stm32wb55cg", "board": "p-nucleo-wb55-usbdongle", "boardfamily": "nucleo", "path": "stmicro/nucleo/p-nucleo-wb55-usbdongle.7z", "icon": null, "info": "microcontroller: stm32wb55cg\nboard: p-nucleo-wb55-usbdongle\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/p-nucleo-wb55-usbdongle\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure."}, "blue-pill": {"chip": "stm32f103c8", "board": "blue-pill", "boardfamily": "pill", "path": "stmicro/pill/blue-pill.7z", "icon": null, "info": "microcontroller: stm32f103c8\nboard: blue-pill\nmicrocontroller manufacturer: stmicro\nboard manufacturer: stmicro\nlink: https://embeetle.com/#supported-hardware/stmicro/boards/blue-pill\n\n\ninfo:\nThis project is generated from CubeMX (with default settings)\nand modified slightly to fit the typical Embeetle project\nstructure.\n\nWARNING:\nIn Makefile-mode, CubeMX generates a startup file named 'startup_stm32f103xb.s'\nfor this chip. In STM32CubeIDE-mode, it generates 'startup_stm32f103c8tx.s'\ninstead. Both files have the same content though.\n\nWARNING:\nThe '-fcyclomatic-complexity' flag doesn't work in our GCC versions."}}, "wch": {"tiny-scarab-baremetal": {"chip": "ch32v003f4p6", "board": "tiny-scarab", "boardfamily": "beetle", "path": "wch/beetle/tiny-scarab-baremetal.7z", "icon": null, "info": "microcontroller: ch32v003f4p6\nboard: tiny-scarab\nmicrocontroller manufacturer: wch\nboard manufacturer: embeetle\nlink: https://embeetle.com/#supported-hardware/beetle-boards/boards/tiny-scarab\n\n\ninfo:\nThis is a minimalistic project for the CH32V003F4P6 microcontroller, with only three files:\n - main.c\n - registers.h\n - startup.S\n\nThe 'registers.h' file contains bitfield definitions for all registers in the chip. It is auto-\ngenerated from the svd file (see /config/ch32v00xxx.svd) with a python script (see\n/config/svd_parser.py)."}, "tiny-scarab-oled-128x32": {"chip": "ch32v003f4p6", "board": "tiny-scarab", "boardfamily": "beetle", "path": "wch/beetle/tiny-scarab-oled-128x32.7z", "icon": null, "info": "microcontroller: ch32v003f4p6\nboard: tiny-scarab\nmicrocontroller manufacturer: wch\nboard manufacturer: embeetle\nlink: https://embeetle.com/#supported-hardware/beetle-boards/boards/tiny-scarab\n\n\ninfo:\nAuthor: Aleksei Prokopov\nSource: https://github.com/roboter/Hardware/tree/main/WCH/ch32v003f4p6-evt-r0-1v1-i2c\nWebsite: https://begemotik.ee/blog/20231203-wch-ssd1306-oled-display/"}, "tiny-scarab-oled-128x64": {"chip": "ch32v003f4p6", "board": "tiny-scarab", "boardfamily": "beetle", "path": "wch/beetle/tiny-scarab-oled-128x64.7z", "icon": null, "info": "microcontroller: ch32v003f4p6\nboard: tiny-scarab\nmicrocontroller manufacturer: wch\nboard manufacturer: embeetle\nlink: https://embeetle.com/#supported-hardware/beetle-boards/boards/tiny-scarab\n\n\ninfo:\nAuthor: Aleksei Prokopov\nSource: https://github.com/roboter/Hardware/tree/main/WCH/ch32v003f4p6-evt-r0-1v1-i2c\nWebsite: https://begemotik.ee/blog/20231203-wch-ssd1306-oled-display/"}, "tiny-scarab": {"chip": "ch32v003f4p6", "board": "tiny-scarab", "boardfamily": "beetle", "path": "wch/beetle/tiny-scarab.7z", "icon": null, "info": "microcontroller: ch32v003f4p6\nboard: tiny-scarab\nmicrocontroller manufacturer: wch\nboard manufacturer: embeetle\nlink: https://embeetle.com/#supported-hardware/beetle-boards/boards/tiny-scarab\n\n\ninfo:\nThis project was originally a WCH Eclipse sample project which we've slightly\nmodified to fit the typical Embeetle project structure.\n\nThe original resources can be found on:\nhttp://www.wch-ic.com/products/CH32V003.html\n\nAfter unzipping this ZIP-folder:\n - The general source code is copied from: 'CH32V003EVT/EVT/EXAM/SRC/'.\n - The sample projects can be found in folders like: 'CH32V003EVT/EVT/EXAM/GPIO/GPIO_Toggle/User/'.\n - The linkerscript is found at: 'CH32V003EVT/EVT/EXAM/SRC/Ld/Link.ld'.\n\nSAMPLE PROJECTS\n---------------\n\nSamples\n |-- ADC\n | |-- ADC_DMA: ADC DMA sampling routines\n | |-- AnalogWatchdog: analog watchdog routine\n | |-- Auto_Injection: automatic injection mode routine\n | |-- Discontinuous_mode: discontinuous mode routine\n | |-- ExtLines_Trigger: external lines trigger ADC conversion routine\n |-- DMA\n | |-- DMA_MEM2MEM: Memory to memory mode routine\n | |-- DMA_MEM2PERIP: Memory to peripheral mode, and peripheral to memory mode routine, see peripheral sub-routines\n |-- EXTI\n | |-- EXTI0: external interrupt line routine\n |-- FLASH\n | |-- FLASH_Program: FLASH erase/read/write, and fast programming \n |-- GPIO \n | |-- GPIO_Toggle: GPIO routine \n |-- I2C\n | |-- I2C_7bit_Mode: 7-bit addressing mode, master/slave mode, transceiver routine\n | |-- I2C_10bit_Mode: 10-bit addressing mode, master/slave mode transceiver routine\n | |-- I2C_DMA: I2C DMA, master/slave mode transceiver routine\n | |-- I2C_EEPROM: I2C interface routine to operate EEPROM peripheral \n | |-- I2C_PEC: PEC error check, master/slave mode transceiver routine \n |-- IAP\n | |-- V00x_APP: APP go to IAP routine \n |-- IWDG\n | |-- IWDG: independent watchdog routine\n |-- OPA \n | |-- OPA: OPA as voltage follower output routine \n |-- PWR\n | |-- Sleep_Mode: low power, sleep mode routine\n | |-- Standby_Mode: low power, standby mode routine\n |-- RCC\n | |-- Get_CLK: Get system-HCLK-AHB1-AHB2 clock routine \n | |-- MCO: MCO pin clock output routine \n |-- SPI\n | |-- 1Lines_half-duplex: single wire half duplex mode, master/slave mode, data transceiver\n | |-- 2Lines_FullDuplex: two-wire full duplex mode, master/slave mode, data transceiver\n | |-- FullDuplex_HardNSS: Hardware NSS mode, master/slave mode, data transceiver\n | |-- SPI_CRC: CRC error check and master/slave mode transceiver routine\n | |-- SPI_DMA: SPI DMA, master/slave mode transceiver routine\n |-- SYSTICK\n | |-- SYSTICK_Interrupt: systick interrupt routine \n |-- TIM\n | |-- Clock_Select: clock source selection routine\n | |-- ComplementaryOutput_DeadTime: complementary output and deadband insertion mode routines\n | |-- ExtTrigger_Start_Two_Timer: external trigger routines to start two timers synchronously\n | |-- Input_Capture: input capture routine\n | |-- One_Pulse: single pulse output routine\n | |-- Output_Compare_Mode: output comparison mode routine\n | |-- PWM_Output: PWM output routine\n | |-- Synchro_ExtTrigger: slave mode routine, including reset mode, gating mode and trigger mode\n | |-- Synchro_Timer: timer synchronization mode\n | |-- TIM_DMA: timer DMA routines\n |-- USART\n | |-- USART_DMA: USART DMA, master/slave mode transceiver routine\n | |-- USART_HalfDuplex: single wire half duplex mode, master/slave mode transceiver routine\n | |-- USART_HardwareFlowControl: hardware flow control mode, master/slave mode, transceiver routine\n | |-- USART_Interrupt: USART interrupt routine, master/slave mode transceiver routine\n | |-- USART_MultiProcessorCommunication: multiprocessor communication mode routine\n | |-- USART_Polling: polling transceiver mode, master/slave transceiver routine\n | |-- USART_Printf: USART Print debugging routine\n | |-- USART_SynchronousMode: synchronous mode, master/slave mode, transceiver routine \n |-- USART-IAP: IAP Upgrade Routine - Built-in Hex to Bin Tool and IAP Upgrade Tool \n |-- WWDG: \n |-- WWDG: window watchdog routine"}, "ch32v003f4p6-evt-r0-1v1-baremetal": {"chip": "ch32v003f4p6", "board": "ch32v003f4p6-evt-r0-1v1", "boardfamily": "ch32v00x", "path": "wch/ch32v00x/ch32v003f4p6-evt-r0-1v1-baremetal.7z", "icon": null, "info": "microcontroller: ch32v003f4p6\nboard: ch32v003f4p6-evt-r0-1v1\nmicrocontroller manufacturer: wch\nboard manufacturer: wch\nlink: https://embeetle.com/#supported-hardware/wch/boards/ch32v003f4p6-evt-r0-1v1\n\n\ninfo:\nThis is a minimalistic project for the CH32V003F4P6 microcontroller, with only three files:\n - main.c\n - registers.h\n - startup.S\n\nThe 'registers.h' file contains bitfield definitions for all registers in the chip. It is auto-\ngenerated from the svd file (see /config/ch32v00xxx.svd) with a python script (see\n/config/svd_parser.py)."}, "ch32v003f4p6-evt-r0-1v1-oled-128x32": {"chip": "ch32v003f4p6", "board": "ch32v003f4p6-evt-r0-1v1", "boardfamily": "ch32v00x", "path": "wch/ch32v00x/ch32v003f4p6-evt-r0-1v1-oled-128x32.7z", "icon": null, "info": "microcontroller: ch32v003f4p6\nboard: ch32v003f4p6-evt-r0-1v1\nmicrocontroller manufacturer: wch\nboard manufacturer: wch\nlink: https://embeetle.com/#supported-hardware/wch/boards/ch32v003f4p6-evt-r0-1v1\n\n\ninfo:\nAuthor: Aleksei Prokopov\nSource: https://github.com/roboter/Hardware/tree/main/WCH/ch32v003f4p6-evt-r0-1v1-i2c\nWebsite: https://begemotik.ee/blog/20231203-wch-ssd1306-oled-display/"}, "ch32v003f4p6-evt-r0-1v1-oled-128x64": {"chip": "ch32v003f4p6", "board": "ch32v003f4p6-evt-r0-1v1", "boardfamily": "ch32v00x", "path": "wch/ch32v00x/ch32v003f4p6-evt-r0-1v1-oled-128x64.7z", "icon": null, "info": "microcontroller: ch32v003f4p6\nboard: ch32v003f4p6-evt-r0-1v1\nmicrocontroller manufacturer: wch\nboard manufacturer: wch\nlink: https://embeetle.com/#supported-hardware/wch/boards/ch32v003f4p6-evt-r0-1v1\n\n\ninfo:\nAuthor: Aleksei Prokopov\nSource: https://github.com/roboter/Hardware/tree/main/WCH/ch32v003f4p6-evt-r0-1v1-i2c\nWebsite: https://begemotik.ee/blog/20231203-wch-ssd1306-oled-display/"}, "ch32v003f4p6-evt-r0-1v1": {"chip": "ch32v003f4p6", "board": "ch32v003f4p6-evt-r0-1v1", "boardfamily": "ch32v00x", "path": "wch/ch32v00x/ch32v003f4p6-evt-r0-1v1.7z", "icon": null, "info": "microcontroller: ch32v003f4p6\nboard: ch32v003f4p6-evt-r0-1v1\nmicrocontroller manufacturer: wch\nboard manufacturer: wch\nlink: https://embeetle.com/#supported-hardware/wch/boards/ch32v003f4p6-evt-r0-1v1\n\n\ninfo:\nThis project was originally a WCH Eclipse sample project which we've slightly\nmodified to fit the typical Embeetle project structure.\n\nThe original resources can be found on:\nhttp://www.wch-ic.com/products/CH32V003.html\n\nAfter unzipping this ZIP-folder:\n - The general source code is copied from: 'CH32V003EVT/EVT/EXAM/SRC/'.\n - The sample projects can be found in folders like: 'CH32V003EVT/EVT/EXAM/GPIO/GPIO_Toggle/User/'.\n - The linkerscript is found at: 'CH32V003EVT/EVT/EXAM/SRC/Ld/Link.ld'.\n\nSAMPLE PROJECTS\n---------------\n\nSamples\n |-- ADC\n | |-- ADC_DMA: ADC DMA sampling routines\n | |-- AnalogWatchdog: analog watchdog routine\n | |-- Auto_Injection: automatic injection mode routine\n | |-- Discontinuous_mode: discontinuous mode routine\n | |-- ExtLines_Trigger: external lines trigger ADC conversion routine\n |-- DMA\n | |-- DMA_MEM2MEM: Memory to memory mode routine\n | |-- DMA_MEM2PERIP: Memory to peripheral mode, and peripheral to memory mode routine, see peripheral sub-routines\n |-- EXTI\n | |-- EXTI0: external interrupt line routine\n |-- FLASH\n | |-- FLASH_Program: FLASH erase/read/write, and fast programming \n |-- GPIO \n | |-- GPIO_Toggle: GPIO routine \n |-- I2C\n | |-- I2C_7bit_Mode: 7-bit addressing mode, master/slave mode, transceiver routine\n | |-- I2C_10bit_Mode: 10-bit addressing mode, master/slave mode transceiver routine\n | |-- I2C_DMA: I2C DMA, master/slave mode transceiver routine\n | |-- I2C_EEPROM: I2C interface routine to operate EEPROM peripheral \n | |-- I2C_PEC: PEC error check, master/slave mode transceiver routine \n |-- IAP\n | |-- V00x_APP: APP go to IAP routine \n |-- IWDG\n | |-- IWDG: independent watchdog routine\n |-- OPA \n | |-- OPA: OPA as voltage follower output routine \n |-- PWR\n | |-- Sleep_Mode: low power, sleep mode routine\n | |-- Standby_Mode: low power, standby mode routine\n |-- RCC\n | |-- Get_CLK: Get system-HCLK-AHB1-AHB2 clock routine \n | |-- MCO: MCO pin clock output routine \n |-- SPI\n | |-- 1Lines_half-duplex: single wire half duplex mode, master/slave mode, data transceiver\n | |-- 2Lines_FullDuplex: two-wire full duplex mode, master/slave mode, data transceiver\n | |-- FullDuplex_HardNSS: Hardware NSS mode, master/slave mode, data transceiver\n | |-- SPI_CRC: CRC error check and master/slave mode transceiver routine\n | |-- SPI_DMA: SPI DMA, master/slave mode transceiver routine\n |-- SYSTICK\n | |-- SYSTICK_Interrupt: systick interrupt routine \n |-- TIM\n | |-- Clock_Select: clock source selection routine\n | |-- ComplementaryOutput_DeadTime: complementary output and deadband insertion mode routines\n | |-- ExtTrigger_Start_Two_Timer: external trigger routines to start two timers synchronously\n | |-- Input_Capture: input capture routine\n | |-- One_Pulse: single pulse output routine\n | |-- Output_Compare_Mode: output comparison mode routine\n | |-- PWM_Output: PWM output routine\n | |-- Synchro_ExtTrigger: slave mode routine, including reset mode, gating mode and trigger mode\n | |-- Synchro_Timer: timer synchronization mode\n | |-- TIM_DMA: timer DMA routines\n |-- USART\n | |-- USART_DMA: USART DMA, master/slave mode transceiver routine\n | |-- USART_HalfDuplex: single wire half duplex mode, master/slave mode transceiver routine\n | |-- USART_HardwareFlowControl: hardware flow control mode, master/slave mode, transceiver routine\n | |-- USART_Interrupt: USART interrupt routine, master/slave mode transceiver routine\n | |-- USART_MultiProcessorCommunication: multiprocessor communication mode routine\n | |-- USART_Polling: polling transceiver mode, master/slave transceiver routine\n | |-- USART_Printf: USART Print debugging routine\n | |-- USART_SynchronousMode: synchronous mode, master/slave mode, transceiver routine \n |-- USART-IAP: IAP Upgrade Routine - Built-in Hex to Bin Tool and IAP Upgrade Tool \n |-- WWDG: \n |-- WWDG: window watchdog routine"}, "ch32v103r8t6-evt-r0-1v3": {"chip": "ch32v103r8t6", "board": "ch32v103r8t6-evt-r0-1v3", "boardfamily": "ch32v10x", "path": "wch/ch32v10x/ch32v103r8t6-evt-r0-1v3.7z", "icon": null, "info": "microcontroller: ch32v103r8t6\nboard: ch32v103r8t6-evt-r0-1v3\nmicrocontroller manufacturer: wch\nboard manufacturer: wch\nlink: https://embeetle.com/#supported-hardware/wch/boards/ch32v103r8t6-evt-r0-1v3\n\n\ninfo:\nThis project was originally a WCH Eclipse sample project which we've slightly\nmodified to fit the typical Embeetle project structure.\n\nThe original resources can be found on:\nhttps://www.wch-ic.com/products/CH32V103.html\n\nThe ZIP-folder is not downloadable on that page. Refer to:\nhttps://www.wch.cn/downloads/CH32V103EVT_ZIP.html\n\nAfter unzipping this ZIP-folder:\n - The general source code is copied from: 'CH32V103EVT/EVT/EXAM/SRC/'.\n - Sample projects are in folders like: 'CH32V103EVT/EVT/EXAM/GPIO/GPIO_Toggle/User/'.\n - The linkerscript is found at: 'CH32V103EVT/EVT/EXAM/SRC/Ld/Link.ld'.\n\nThe original sources provide two startup assembly files:\n- startup_ch32v10x_3v3.S\n- startup_ch32v10x_5v.S\nThe 3v3 version is selected through our heuristics.\n\nSAMPLE PROJECTS\n---------------\n\nSamples\n |-- ADC\n | |-- ADC_DMA:ADC uses DMA sampling routines\n | |-- AnalogWatchdog:analog watchdog routine\n | |-- Auto_Injection:automatic injection mode routine\n | |-- Discontinuous_mode:discontinuous mode routine\n | |-- ExtLines_Trigger:external lines trigger ADC conversion routine\n | |-- Internal_Temperature:internal temperature sensor routine \n | |-- TIM Trigger:TIM trigger ADC conversion routine \n | |-- Temperature-External channel:Temperature-External channel Injection alternating inversion routine \n |-- BKP:BKP routine\n |-- CRC:CRC routine\n |-- DMA\n | |-- DMA_MEM2MEM:memory to memory mode routine\n | |-- DMA_MEM2PERIP:see each peripheral subroutine for memory to peripheral mode and peripheral to memory mode routines\n |-- EXTI:external interrupt line routine\n |-- FLASH:FLASH erase / read / write, and fast programming\n |-- FreeRTOS:FreeRTOS migration routine \n |-- GPIO:GPIO routine\n |-- HarmonyOS:HarmonyOS migration routine \n |-- I2C\n | |-- I2C_7bit_Mode:7-bit address mode, master / slave mode, transceiver routine\n | |-- I2C_10bit_Mode:10 bit address mode, master / slave mode transceiver routine\n | |-- I2C_DMA:I2C uses DMA, master / slave mode transceiver routine\n | |-- I2C_EEPROM:I2C interface operation EEPROM peripheral routine\n | |-- I2C_PEC:use PEC error check and master / slave mode transceiver routine\n |-- IWDG:independent watchdog routine\n |-- PWR\n | |-- Sleep_Mode:low power consumption, sleep mode routine\n | |-- Standby_Mode:low power consumption, standby mode routine\n | |-- Stop_Mode:low power consumption, stop mode routine\n |-- RCC\n | |-- MCO:MCO pin clock output routine\n | |-- HSI_PLL_Source:HSI or HSI/2 as PLL input clock routine\n | |-- HSE_CLK:HSE frequency check routine \n |-- RTC:calendar routine\n |-- RT-Thread:RT thread migration routine \n |-- SPI\n | |-- 1Lines_half-duplex:single wire half duplex mode, master / slave mode, data transceiver\n | |-- 2Lines_FullDuplex:two-wire full duplex mode, master / slave mode, data transceiver\n | |-- FullDuplex_HardNSS:Hardware NSS mode, master / slave mode, data transceiver\n | |-- SPI_CRC:use CRC error check and master / slave mode transceiver routine\n | |-- SPI_DMA:SPI uses DMA, master / slave mode transceiver routine\n | |-- SPI_FLASH:SPI interface operation flash peripheral routine\n |-- TencentOS:TencentOS migration routine \n |-- TIM\n | |-- Clock_Select:clock source selection routine\n | |-- ComplementaryOutput_DeadTime:complementary output and deadband insertion mode routines\n | |-- ExtTrigger_Start_Two_Timer:external trigger starts two timer routines synchronously\n | |-- Input_Capture:input capture routine\n | |-- One_Pulse:single pulse output routine\n | |-- Output_Compare_Mode:output comparison mode routine\n | |-- PWM_Output:PWM output routine\n | |-- Synchro_ExtTrigger:slave mode routine, including reset mode, gating mode and trigger mode\n | |-- Synchro_Timer:timer synchronization mode\n | |-- TIM_DMA:the timer uses DMA routines\n |-- TOUCHKEY:touchkey detection routine\n |-- USART\n | |-- USART_DMA:USART uses DMA, master / slave mode transceiver routine\n | |-- USART_HalfDuplex:single wire half duplex mode, master / slave mode transceiver routine\n | |-- USART_HardwareFlowControl:hardware flow control mode, master / slave mode, transceiver routine\n | |-- USART_Interrupt:USART interrupt routine, master / slave mode transceiver routine\n | |-- USART_MultiProcessorCommunication:multiprocessor communication mode routine\n | |-- USART_Polling:polling transceiver mode, master / slave transceiver routine\n | |-- USART_Printf:USART Print debugging routine\n | |-- USART_SynchronousMode:synchronous mode, master / slave mode, transceiver routine\n |-- USB\n | |-- USBHD\n | |-- DEVICE\n | | |-- CH372:Simulates a custom USB device (CH372 device) with endpoints 1, 3 down and 2, 4 up. Data down from endpoint 1 is uploaded from endpoint 3 and not reversed, and data down from endpoint 2 is uploaded from endpoint 4 and reversed.\n | | |-- Compatibility_HID:Simulates HID devices, with data transmitted up and down through the serial port.\n | | |-- CompositeKM:Simulate keyboard and mouse, use IO to simulate keystrokes, while simulated data can be uploaded through serial port 2.\n | | |-- CompositeKM_LowSpeed:Simulate low speed keyboard and mouse, use IO to simulate keystrokes, while simulated data can be uploaded through serial port 2.\n | | |-- MSC_U-Disk: Smulates a simple USB flash drive, optionally using on-chip Flash or external SPI-Flash\n | | |-- SimulateCDC:Simulate a CDC serial port and use serial port 2 to send and receive.\n | | |-- MSC_CD-ROM: Simulate CDROM, need external SPI-Flash\n | |-- HOST_IAP\n | | |-- APP: APP used with HOST_IAP, the project has modified the starting location of the program, after compilation, you need to convert the file into a bin file and rename it to APP.bin\n | | |-- HOST_IAP: The host U disk IAP routine based on the U disk read file routine finishing, read the file with the name bit APP.bin from the U disk, write it to the internal flash, check it and jump automatically.\n | |-- HOST_KM: The host operates the keypad, gets the data of the endpoints uploaded by the keypad and prints it, supports U-port under level 1 hub\n | |-- HOST_MTP_FileSystem:Enumeration process of a USB host to a device that supports MTP and PTP protocols, supports MTP and PTP protocols, and reads its files\n | |-- Udisk_Lib:U disk file system library file \n | |-- Host_Udisk:USB host operation USB disk routine \n |-- WWDG:window watchdog routine"}, "ch32v203c8t6-evt-r0-1v0": {"chip": "ch32v203c8t6", "board": "ch32v203c8t6-evt-r0-1v0", "boardfamily": "ch32v20x", "path": "wch/ch32v20x/ch32v203c8t6-evt-r0-1v0.7z", "icon": null, "info": "microcontroller: ch32v203c8t6\nboard: ch32v203c8t6-evt-r0-1v0\nmicrocontroller manufacturer: wch\nboard manufacturer: wch\nlink: https://embeetle.com/#supported-hardware/wch/boards/ch32v203c8t6-evt-r0-1v0\n\n\ninfo:\nThis project was originally a WCH Eclipse sample project which we've slightly\nmodified to fit the typical Embeetle project structure.\n\nThe original resources can be found on:\nhttp://www.wch-ic.com/products/CH32V203.html\n\nThe ZIP-folder is not downloadable on that page. Refer to:\nhttps://www.wch.cn/downloads/CH32V20xEVT_ZIP.html\n\nAfter unzipping this ZIP-folder:\n - The general source code is copied from: 'CH32V20xEVT/EVT/EXAM/SRC/'.\n - The sample projects are in folders like: 'CH32V20xEVT/EVT/EXAM/GPIO/GPIO_Toggle/User/'.\n - The linkerscript is found at: 'CH32V20xEVT/EVT/EXAM/SRC/Ld/Link.ld'.\n\nSAMPLE PROJECTS\n---------------\nSamples\n |-- ADC\n | |-- ADC_DMA: ADC DMA sampling routines\n | |-- AnalogWatchdog: analog watchdog routine\n | |-- Auto_Injection: automatic injection mode routine\n | |-- Discontinuous_mode: discontinuous mode routine\n | |-- DualADC_AlternateTrigger: dual ADC alternate trigger sampling routine, only applied to CH32V20x_D6 \n | |-- DualADC_Combined_RegInjectionSimul: dual ADC combined regular + injection + simultaneous sampling routine, only applied to CH32V20x_D6\n | |-- DualADC_FastInterleaved: dual ADC fast interleaved sampling routine, only applied to CH32V20x_D6\n | |-- DualADC_InjectionSimul: dual ADC injection simultaneous sampling routine, only applied to CH32V20x_D6 \n | |-- DualADC_RegSimul: dual ADC regular simultaneous sampling routine, only applied to CH32V20x_D6\n | |-- DualADC_SlowInterleaved: dual ADC slow interleaved sampling routine, only applied to CH32V20x_D6\n | |-- ExtLines_Trigger: external lines trigger ADC conversion routine\n | |-- Internal_Temperature: internal temperature sensor routine \n |-- BLE: only for CH32V20x_D8W \n | |-- BackupUpgrade_IAP: backup wireless upgrade IAP routine. Detect the current code flag, determine whether to move the code from the backup area to the user area, and run the code in the user area \n | |-- BackupUpgrade_OTA: backup wireless upgrade user routine. Add OTA function to peripheral slave routines, save the upgrade firmware to the backup area and jump to the IAP program to upgrade \n | |-- BLE_UART: BLE and UART transparent transmission routine, for detailed instructions, please refer to the document in the root directory\n | |-- BLE_USB: BLE with USB routine, USB emulation 340 device forwards BLE data \n | |-- Broadcaster: broadcaster routine, always broadcast when in broadcast status\n | |-- CentPeri: central-peripheral routine, integrate the function of central routine and peripheral routine and run simultaneously\n | |-- Central: central routine, actively scan surrounding devices, conect to the specified peripheral address, search custom service and characteristic, execute read/write commands, peripheral routine is needed, and modify the peripheral address to the routine target address, (84:C2:E4:03:02:02) by default\n | |-- CyclingSensor: cycling sensor routine, upload speed and cadence regularly after connected to the host\n | |-- DirectTest: direct test routine, test data packets sent by specified communication channel\n | |-- HAL: Hardware-related files shared by routines\n | |-- HeartRate: heart rate routine, upload heart rate regularly after connected to the central\n | |-- HID_Consumer: BLE consumer routine, simulate user control device, upload volume key down key regularly after connected to the central\n | |-- HID_Keyboard: BLE keyboard routine, simulate a keyboard device, upload key value regularly after connected to the central\n | |-- HID_Mouse: BLE mouse routine, simulate a mouse device, upload key value regularly after connected to the central\n | |-- HID_Touch: BLE touch routine, simulate a touch pencil device, upload touch value regularly after connected to the central\n | |-- LIB: BLE protocol stack library file and header file\n | |-- LWNS: LWNS wireless networking routine,including broadcast, unicast, netflood, mesh.\n | |-- MultiCentPeri: Multi-central and multi-peripheral routines, support connecting three masters and three slaves at the same time\n | |-- MultiCentral: multicentral routine, actively scan surrounding devices, conect to the specified three peripheral addresses, search custom services and characteristics, execute read/write commands, peripheral routine is needed, and modify the peripheral address to this routine target address, the addresses of these peripherals are (84:C2:E4:03:02:02), (84:C2:E4:03:02:03) and (84:C2:E4:03:02:04) by default\n | |-- Observer: observer routine, scan regularly, print the scanned broadcast address if the scanning result is not empty\n | |-- OnlyUpdateApp_IAP: the only library wireless upgrade IAP routine, with OTA function, upgrade the user area code after receiving the upgraded firmware\n | |-- OnlyUpdateApp_Peripheral: the only library wireless upgrade user routine, on the basis of peripheral routine, the jumping to IAP program is added for subsequent upgrades\n | |-- Peripheral: peripheral role routine, custom including five services with different attributes, including read attribute, write attribute, notify attribute, read/write attribute, and safe and readable attribute\n | |-- peripheral_ancs_client: peripheral slave role routine, including Apple Notification Center service\n | |-- peripheral_ETH: Bluetooth ETH routines\n | |-- RF_PHY: non-standard wireless transceiver routines\n | |-- RF_PHY_Hop: non-standard wireless frequency hopping transceiver routine\n | |-- RunningSensor: running sensor routine,upload rate regularly after connected to the central \n | |-- SpeedTest_Central: Bluetooth speed test central routine\n | |-- SpeedTest_Peripheral: Bluetooth speed test peripheral routine\n | |-- SYNC_ADV: cycle synchronization advertising routine\n | |-- SYNC_SCAN: cycle synchronization scanning routine\n | |-- WCH BLE Software Developers Guide.pdf\n | |-- BLE Certification: Product: WCH CH32V208 QDID: 179771 \n | |-- MESH\n | |-- adv_ali_light: Tmall Genie light routine, devices can be found and provisioned network via Tmall Genie, to control the switch state. By default, only switch attribute can be controlled. If other attributes (brightness, power, temperature, etc.) are needed, add the corresponding processing function and status report function according to the attribute description of the Alibaba Cloud product configuration.\n | |-- adv_ali_light_add_lightness: MESH general attribute adding routine. On the basis of the Tmall Genie light routine, the brightness attribute is added, which is used to compare the original Tmall Genie light routine to quickly become familiar with the method of adding other MESH general attributes.\n | |-- adv_ali_light_add_windspeed: Tmall definition attribute adding routine. On the basis of the Tmall Genie light routine, the wind speed attribute is added, which is used to compare the original Tmall Genie light routine to quickly become familiar with the method of adding other Tmall definition attributes.\n | |-- adv_ali_light_multi_element: Multi-element fan lamp, which is used to compare the original Tmall Genie light routine to quickly become familiar with the method of adding multi-element Tmall definition attributes.\n | |-- adv_ali_light_with_peripheral: Based on the Tmall Genie light routine, add brightness and color temperature controls, it supports the connection control of BLE debugging tool on the mobile phone.\n | |-- adv_proxy: proxy node routine, which can be used to provision network through the PV_GATT layer (BLE connection).\n | |-- adv_vendor: vendor-defined model routine, used with self_provisioner_vendor, supports two communication attributes of response transmission and non-response transparent transmission, and develops the communication protocol by yourself.\n | |-- adv_vendor_friend: based on vendor-defined model routine, support friend node function\n | |-- adv_vendor_low_power: On the basis of the vendor custom model routine, support low-power node functions and should be used with friend nodes\n | |-- adv_vendor_self_provision: On the basis of the vendor custom model routine, support local provision\n | |-- adv_vendor_self_provision_IAP: MESH backup wireless upgrade IAP routine, detect the current code flag, judge whether to move the backup area code to the user area and run the user area code\n | |-- adv_vendor_self_provision_with_peripheral: MESH backup wireless upgrade user routine, On the basis of the vendor custom model routine, supports the connection control of the mobile phone BLE debugging assistant, receives the distribution network information through BLE and distributes the network itself. It is suitable for terminal control networking applications. It can formulate the communication protocol by itself to realize the mobile phone control all devices in the mesh network.\n | |-- self_provisioner_vendor: vendor-defined model self-provisioning network initiator routine, used with adv_vendor, automatically provision network to the surrounding devices without network, and add it to its own mesh network, support provision network to six devices by default . The default configuration device is bound with single APPKEY, which is used for response transmission and non-response transparent transmission, and the configuration device is bound with single subscription address, which is used for mass sending of unanswered messages\n | |-- self_provisioner_vendor_with_peripheral: Based on the vendor-defined model self-provisioning network initiator routine, can be connected and controlled by BLE debugging tool on the mobile phone, transfer the communication between the mobile phone and the mesh network, and can draw up the communication protocol to implement that all devices in mesh network can be controlled the mobile phone.\n | |-- MESH_LIB: MESH protocol stack library file and header file\n | |-- Qinheng MESH APP Management Distribution Network Application Manual.pdf\n | |-- Qinheng Low Energy Bluetooth MESH Software Development Reference Manual.pdf\n |-- BKP: BKP routine\n |-- CAN: only for CH32V20x_D6-CH32V20x_D8W \n | |-- Networking: CAN routine: normal mode, standard frame and expanded frame data transceiver\n | |-- TestMode: test mode, including silent mode, loopback mode and loopback silent mode\n | |-- Time-triggered: time triggered communication mode \n |-- CRC: CRC routine\n |-- DMA\n | |-- DMA_MEM2MEM: Memory to memory mode routine\n | |-- DMA_MEM2PERIP: Memory to peripheral mode, and peripheral to memory mode routine, see peripheral sub-routines\n |-- ETH: only for CH32V20x_D8-CH32V20x_D8W\n | |-- 1_Tool_Doc: routine-related documents and configuration software\n | |-- DHCP: DHCP demonstration routine to obtain IP automatically, and establish TCP connection for data return\n | |-- DNS: DHCP demonstration routine to obtain IP automatically and then request domain name resolution \n | |-- ETH_CFG: ETH_CFG routine. Create a UDP Server to communicate with upper computer, to configure WCHNET functions, including configuring various parameters and creating a new communication. \n | |-- ETH_IAP: ETH IAP routine\n | |-- ETH_UART: ETH_UART routine, to demonstrate data transparent transfer between Ethernet and UART. By default, the 1000000 baud rate (can be modified in bsp_uart.h) is selected for serial port data transmission\n | |-- IPRaw_PING: PING function demonstration routine\n | |-- Mail: to demonstrate reception and transmission of SMTP and POP3 mails \n | |-- MQTT: MQTT routine, to demonstrate MQTT protocol communication based on TCP/IP \n | |-- NetLib: Network protocol stack library file\n | |-- TcpClient: demonstration routine that TCP client receives data after connected to the server and then returns data \n | |-- TcpServer: demonstration routine that TCP server receives data after connected to the client and then returns data\n | |-- UdpClient: demonstration routine that Udp Client receives data and returns data\n | |-- UdpServer: demonstration routine that Udp Server receives data and returns data\n | |-- WebServer: Web Server routine, to demonstrate the configuration of WCHNET device functions through Web browser. As the WCHNET devices have built-in web server, the network parameter configuration and password management of WCHNET can be implemented on the web page. \n |-- EXTI: external interrupt line routine\n |-- FLASH: FLASH erase/read/write, and fast programming\n |-- FreeRTOS: FreeRTOS migration routine \n |-- GPIO: GPIO routine\n |-- HarmonyOS: HarmonyOS migration routine \n |-- I2C\n | |-- I2C_7bit_Mode: 7-bit addressing mode, master/slave mode, transceiver routine\n | |-- I2C_10bit_Mode: 10-bit addressing mode, master/slave mode transceiver routine\n | |-- I2C_DMA: I2C DMA, master/slave mode transceiver routine\n | |-- I2C_EEPROM: I2C interface routine to operate EEPROM peripheral \n | |-- I2C_PEC: PEC error check, master/slave mode transceiver routine\n |-- INT\n | |-- Interrupt_VTF: VTF IRQ interrupt routine \n |-- IAP: IAP upgrade routine, including the Hex to Bin tool and IAP upgrade tool \n | |-- USB_UART: USB+UART IAP routine \n |-- IWDG: independent watchdog routine\n |-- OPA: OPA4 as voltage follower output routine\n |-- PWR\n | |-- Sleep_Mode: low power, sleep mode routine\n | |-- Standby_Mode: low power, standby mode routine\n | |-- Stop_Mode: low power, stop mode routine\n | |-- Standby_RAM_LV_Mode: when LV is enabled in standby mode, RAM 2k and 30K low-power data holding routines\n | |-- Standby_RAM_Mode: when LV is not enabled in standby mode, RAM 2k and 30K low-power data holding routines\n |-- RCC\n | |-- Get_CLK: Get system-HCLK-AHB1-AHB2 clock routine \n | |-- MCO: MCO pin clock output routine\n | |-- HSI_PLL_Source: HSI or HSI/2 as PLL input clock routine \n |-- RT-Thread: RT thread migration routine \n |-- RTC: calendar routine\n |-- SPI\n | |-- 1Lines_half-duplex: single wire half duplex mode, master/slave mode, data transceiver\n | |-- 2Lines_FullDuplex: two-wire full duplex mode, master/slave mode, data transceiver\n | |-- FullDuplex_HardNSS: Hardware NSS mode, master/slave mode, data transceiver\n | |-- SPI_CRC: CRC error check and master/slave mode transceiver routine\n | |-- SPI_DMA: SPI DMA, master/slave mode transceiver routine\n | |-- SPI_FLASH: SPI interface operation flash peripheral routine\n |-- TencentOS: TencentOS migration routine \n |-- TIM\n | |-- Clock_Select: clock source selection routine\n | |-- ComplementaryOutput_DeadTime: complementary output and deadband insertion mode routines\n | |-- ExtTrigger_Start_Two_Timer: external trigger routines to start two timers synchronously\n | |-- Input_Capture: input capture routine\n | |-- One_Pulse: single pulse output routine\n | |-- Output_Compare_Mode: output comparison mode routine\n | |-- PWM_Output: PWM output routine\n | |-- Synchro_ExtTrigger: slave mode routine, including reset mode, gating mode and trigger mode\n | |-- Synchro_Timer: timer synchronization mode\n | |-- TIM_DMA: timer DMA routines\n |-- TOUCHKEY: touchkey detection routine\n |-- USART\n | |-- USART_DMA: USART DMA, master/slave mode transceiver routine\n | |-- USART_HalfDuplex: single wire half duplex mode, master/slave mode transceiver routine\n | |-- USART_HardwareFlowControl: hardware flow control mode, master/slave mode, transceiver routine\n | |-- USART_Interrupt: USART interrupt routine, master/slave mode transceiver routine\n | |-- USART_MultiProcessorCommunication: multiprocessor communication mode routine\n | |-- USART_Polling: polling transceiver mode, master/slave transceiver routine\n | |-- USART_Printf: USART Print debugging routine\n | |-- USART_SynchronousMode: synchronous mode, master/slave mode, transceiver routine\n |-- USB\n | |-- USBD\n | | |-- CH372: Simulates a custom USB device (CH372 device) with endpoints 1, 3 down and 2, 4 up. Data down from endpoint 1 is uploaded from endpoint 3 and not reversed, and data down from endpoint 2 is uploaded from endpoint 4 and reversed.\n | | |-- Compatibility_HID: Simulates HID devices, with data transmitted up and down through the serial port.\n | | |-- CompositeKM: Simulate keyboard and mouse, use IO to simulate keystrokes, while simulated data can be uploaded through serial port 2.\n | | |-- MSC_U-Disk: Smulates a simple USB flash drive, optionally using on-chip Flash or external SPI-Flash\n | | |-- MSC_CD-ROM: Simulate CDROM, need external SPI-Flash\n | | |-- SimulateCDC: Simulate a CDC serial port and use serial port 2 to send and receive.\n | | |-- SimulateCDC-HID: Simulate a CDC serial port, use serial port 2 to send and receive, HID interrupt endpoints to send and receive data to reverse and upload. \n | |-- USBFS\n | |-- DEVICE\n | | |-- CH372: Simulates a custom USB device (CH372 device) with endpoints 1, 3 down and 2, 4 up. Data down from endpoint 1 is uploaded from endpoint 3 and not reversed, and data down from endpoint 2 is uploaded from endpoint 4 and reversed.\n | | |-- Compatibility_HID: Simulates HID devices, with data transmitted up and down through the serial port.\n | | |-- CompositeKM: Simulate keyboard and mouse, use IO to simulate keystrokes, while simulated data can be uploaded through serial port 2.\n | | |-- MSC_U-Disk: Smulates a simple USB flash drive, optionally using on-chip Flash or external SPI-Flash\n | | |-- MSC_CD-ROM: Simulate CDROM, need external SPI-Flash\n | | |-- SimulateCDC: Simulate a CDC serial port and use serial port 2 to send and receive.\n | | |-- SimulateCDC-HID: Simulate a CDC serial port, use serial port 2 to send and receive, HID interrupt endpoints to send and receive data to reverse and upload. \n | |-- HOST_IAP\n | | |-- APP: APP used with HOST_IAP, the project has modified the starting location of the program, after compilation, you need to convert the file into a bin file and rename it to APP.bin\n | | |-- HOST_IAP: The host U disk IAP routine based on the U disk read file routine finishing, read the file with the name bit APP.bin from the U disk, write it to the internal flash, check it and jump automatically.\n | |-- HOST_KM: The host operates the keypad, gets the data of the endpoints uploaded by the keypad and prints it, supports U-port under level 1 hub\n | |-- HOST_MTP_FileSystem: Enumeration process of a USB host to a device that supports MTP and PTP protocols, supports MTP and PTP protocols, and reads its files\n | |-- Host_Udisk: USB host operation USB disk routine \n | |-- Udisk_Lib: U disk file system library file \n |-- WWDG: window watchdog routine"}, "lana-tny-01-blaster-2024": {"chip": "ch32v203g6u6", "board": "lana-tny-01", "boardfamily": "ch32v20x", "path": "wch/ch32v20x/lana-tny-01-blaster-2024.7z", "icon": null, "info": "microcontroller: ch32v203g6u6\nboard: lana-tny-01\nmicrocontroller manufacturer: wch\nboard manufacturer: wch\nlink: https://embeetle.com/#supported-hardware/wch/boards/lana-tny-01\n\n\ninfo:\nThis project was originally a WCH Eclipse sample project which we've slightly\nmodified to fit the typical Embeetle project structure.\n\nThe original resources can be found on:\nhttp://www.wch-ic.com/products/CH32V203.html\n\nThe ZIP-folder is not downloadable on that page. Refer to:\nhttps://www.wch.cn/downloads/CH32V20xEVT_ZIP.html\n\nAfter unzipping this ZIP-folder:\n - The general source code is copied from: 'CH32V20xEVT/EVT/EXAM/SRC/'.\n - The sample projects are in folders like: 'CH32V20xEVT/EVT/EXAM/GPIO/GPIO_Toggle/User/'.\n - The linkerscript is found at: 'CH32V20xEVT/EVT/EXAM/SRC/Ld/Link.ld'.\n\n\nSAMPLE PROJECTS\n---------------\nSamples\n |-- ADC\n | |-- ADC_DMA: ADC DMA sampling routines\n | |-- AnalogWatchdog: analog watchdog routine\n | |-- Auto_Injection: automatic injection mode routine\n | |-- Discontinuous_mode: discontinuous mode routine\n | |-- DualADC_AlternateTrigger: dual ADC alternate trigger sampling routine, only applied to CH32V20x_D6 \n | |-- DualADC_Combined_RegInjectionSimul: dual ADC combined regular + injection + simultaneous sampling routine, only applied to CH32V20x_D6\n | |-- DualADC_FastInterleaved: dual ADC fast interleaved sampling routine, only applied to CH32V20x_D6\n | |-- DualADC_InjectionSimul: dual ADC injection simultaneous sampling routine, only applied to CH32V20x_D6 \n | |-- DualADC_RegSimul: dual ADC regular simultaneous sampling routine, only applied to CH32V20x_D6\n | |-- DualADC_SlowInterleaved: dual ADC slow interleaved sampling routine, only applied to CH32V20x_D6\n | |-- ExtLines_Trigger: external lines trigger ADC conversion routine\n | |-- Internal_Temperature: internal temperature sensor routine \n |-- BLE: only for CH32V20x_D8W \n | |-- BackupUpgrade_IAP: backup wireless upgrade IAP routine. Detect the current code flag, determine whether to move the code from the backup area to the user area, and run the code in the user area \n | |-- BackupUpgrade_OTA: backup wireless upgrade user routine. Add OTA function to peripheral slave routines, save the upgrade firmware to the backup area and jump to the IAP program to upgrade \n | |-- BLE_UART: BLE and UART transparent transmission routine, for detailed instructions, please refer to the document in the root directory\n | |-- BLE_USB: BLE with USB routine, USB emulation 340 device forwards BLE data \n | |-- Broadcaster: broadcaster routine, always broadcast when in broadcast status\n | |-- CentPeri: central-peripheral routine, integrate the function of central routine and peripheral routine and run simultaneously\n | |-- Central: central routine, actively scan surrounding devices, conect to the specified peripheral address, search custom service and characteristic, execute read/write commands, peripheral routine is needed, and modify the peripheral address to the routine target address, (84:C2:E4:03:02:02) by default\n | |-- CyclingSensor: cycling sensor routine, upload speed and cadence regularly after connected to the host\n | |-- DirectTest: direct test routine, test data packets sent by specified communication channel\n | |-- HAL: Hardware-related files shared by routines\n | |-- HeartRate: heart rate routine, upload heart rate regularly after connected to the central\n | |-- HID_Consumer: BLE consumer routine, simulate user control device, upload volume key down key regularly after connected to the central\n | |-- HID_Keyboard: BLE keyboard routine, simulate a keyboard device, upload key value regularly after connected to the central\n | |-- HID_Mouse: BLE mouse routine, simulate a mouse device, upload key value regularly after connected to the central\n | |-- HID_Touch: BLE touch routine, simulate a touch pencil device, upload touch value regularly after connected to the central\n | |-- LIB: BLE protocol stack library file and header file\n | |-- LWNS: LWNS wireless networking routine,including broadcast, unicast, netflood, mesh.\n | |-- MultiCentPeri: Multi-central and multi-peripheral routines, support connecting three masters and three slaves at the same time\n | |-- MultiCentral: multicentral routine, actively scan surrounding devices, conect to the specified three peripheral addresses, search custom services and characteristics, execute read/write commands, peripheral routine is needed, and modify the peripheral address to this routine target address, the addresses of these peripherals are (84:C2:E4:03:02:02), (84:C2:E4:03:02:03) and (84:C2:E4:03:02:04) by default\n | |-- Observer: observer routine, scan regularly, print the scanned broadcast address if the scanning result is not empty\n | |-- OnlyUpdateApp_IAP: the only library wireless upgrade IAP routine, with OTA function, upgrade the user area code after receiving the upgraded firmware\n | |-- OnlyUpdateApp_Peripheral: the only library wireless upgrade user routine, on the basis of peripheral routine, the jumping to IAP program is added for subsequent upgrades\n | |-- Peripheral: peripheral role routine, custom including five services with different attributes, including read attribute, write attribute, notify attribute, read/write attribute, and safe and readable attribute\n | |-- peripheral_ancs_client: peripheral slave role routine, including Apple Notification Center service\n | |-- peripheral_ETH: Bluetooth ETH routines\n | |-- RF_PHY: non-standard wireless transceiver routines\n | |-- RF_PHY_Hop: non-standard wireless frequency hopping transceiver routine\n | |-- RunningSensor: running sensor routine,upload rate regularly after connected to the central \n | |-- SpeedTest_Central: Bluetooth speed test central routine\n | |-- SpeedTest_Peripheral: Bluetooth speed test peripheral routine\n | |-- SYNC_ADV: cycle synchronization advertising routine\n | |-- SYNC_SCAN: cycle synchronization scanning routine\n | |-- WCH BLE Software Developers Guide.pdf\n | |-- BLE Certification: Product: WCH CH32V208 QDID: 179771 \n | |-- MESH\n | |-- adv_ali_light: Tmall Genie light routine, devices can be found and provisioned network via Tmall Genie, to control the switch state. By default, only switch attribute can be controlled. If other attributes (brightness, power, temperature, etc.) are needed, add the corresponding processing function and status report function according to the attribute description of the Alibaba Cloud product configuration.\n | |-- adv_ali_light_add_lightness: MESH general attribute adding routine. On the basis of the Tmall Genie light routine, the brightness attribute is added, which is used to compare the original Tmall Genie light routine to quickly become familiar with the method of adding other MESH general attributes.\n | |-- adv_ali_light_add_windspeed: Tmall definition attribute adding routine. On the basis of the Tmall Genie light routine, the wind speed attribute is added, which is used to compare the original Tmall Genie light routine to quickly become familiar with the method of adding other Tmall definition attributes.\n | |-- adv_ali_light_multi_element: Multi-element fan lamp, which is used to compare the original Tmall Genie light routine to quickly become familiar with the method of adding multi-element Tmall definition attributes.\n | |-- adv_ali_light_with_peripheral: Based on the Tmall Genie light routine, add brightness and color temperature controls, it supports the connection control of BLE debugging tool on the mobile phone.\n | |-- adv_proxy: proxy node routine, which can be used to provision network through the PV_GATT layer (BLE connection).\n | |-- adv_vendor: vendor-defined model routine, used with self_provisioner_vendor, supports two communication attributes of response transmission and non-response transparent transmission, and develops the communication protocol by yourself.\n | |-- adv_vendor_friend: based on vendor-defined model routine, support friend node function\n | |-- adv_vendor_low_power: On the basis of the vendor custom model routine, support low-power node functions and should be used with friend nodes\n | |-- adv_vendor_self_provision: On the basis of the vendor custom model routine, support local provision\n | |-- adv_vendor_self_provision_IAP: MESH backup wireless upgrade IAP routine, detect the current code flag, judge whether to move the backup area code to the user area and run the user area code\n | |-- adv_vendor_self_provision_with_peripheral: MESH backup wireless upgrade user routine, On the basis of the vendor custom model routine, supports the connection control of the mobile phone BLE debugging assistant, receives the distribution network information through BLE and distributes the network itself. It is suitable for terminal control networking applications. It can formulate the communication protocol by itself to realize the mobile phone control all devices in the mesh network.\n | |-- self_provisioner_vendor: vendor-defined model self-provisioning network initiator routine, used with adv_vendor, automatically provision network to the surrounding devices without network, and add it to its own mesh network, support provision network to six devices by default . The default configuration device is bound with single APPKEY, which is used for response transmission and non-response transparent transmission, and the configuration device is bound with single subscription address, which is used for mass sending of unanswered messages\n | |-- self_provisioner_vendor_with_peripheral: Based on the vendor-defined model self-provisioning network initiator routine, can be connected and controlled by BLE debugging tool on the mobile phone, transfer the communication between the mobile phone and the mesh network, and can draw up the communication protocol to implement that all devices in mesh network can be controlled the mobile phone.\n | |-- MESH_LIB: MESH protocol stack library file and header file\n | |-- Qinheng MESH APP Management Distribution Network Application Manual.pdf\n | |-- Qinheng Low Energy Bluetooth MESH Software Development Reference Manual.pdf\n |-- BKP: BKP routine\n |-- CAN: only for CH32V20x_D6-CH32V20x_D8W \n | |-- Networking: CAN routine: normal mode, standard frame and expanded frame data transceiver\n | |-- TestMode: test mode, including silent mode, loopback mode and loopback silent mode\n | |-- Time-triggered: time triggered communication mode \n |-- CRC: CRC routine\n |-- DMA\n | |-- DMA_MEM2MEM: Memory to memory mode routine\n | |-- DMA_MEM2PERIP: Memory to peripheral mode, and peripheral to memory mode routine, see peripheral sub-routines\n |-- ETH: only for CH32V20x_D8-CH32V20x_D8W\n | |-- 1_Tool_Doc: routine-related documents and configuration software\n | |-- DHCP: DHCP demonstration routine to obtain IP automatically, and establish TCP connection for data return\n | |-- DNS: DHCP demonstration routine to obtain IP automatically and then request domain name resolution \n | |-- ETH_CFG: ETH_CFG routine. Create a UDP Server to communicate with upper computer, to configure WCHNET functions, including configuring various parameters and creating a new communication. \n | |-- ETH_IAP: ETH IAP routine\n | |-- ETH_UART: ETH_UART routine, to demonstrate data transparent transfer between Ethernet and UART. By default, the 1000000 baud rate (can be modified in bsp_uart.h) is selected for serial port data transmission\n | |-- IPRaw_PING: PING function demonstration routine\n | |-- Mail: to demonstrate reception and transmission of SMTP and POP3 mails \n | |-- MQTT: MQTT routine, to demonstrate MQTT protocol communication based on TCP/IP \n | |-- NetLib: Network protocol stack library file\n | |-- TcpClient: demonstration routine that TCP client receives data after connected to the server and then returns data \n | |-- TcpServer: demonstration routine that TCP server receives data after connected to the client and then returns data\n | |-- UdpClient: demonstration routine that Udp Client receives data and returns data\n | |-- UdpServer: demonstration routine that Udp Server receives data and returns data\n | |-- WebServer: Web Server routine, to demonstrate the configuration of WCHNET device functions through Web browser. As the WCHNET devices have built-in web server, the network parameter configuration and password management of WCHNET can be implemented on the web page. \n |-- EXTI: external interrupt line routine\n |-- FLASH: FLASH erase/read/write, and fast programming\n |-- FreeRTOS: FreeRTOS migration routine \n |-- GPIO: GPIO routine\n |-- HarmonyOS: HarmonyOS migration routine \n |-- I2C\n | |-- I2C_7bit_Mode: 7-bit addressing mode, master/slave mode, transceiver routine\n | |-- I2C_10bit_Mode: 10-bit addressing mode, master/slave mode transceiver routine\n | |-- I2C_DMA: I2C DMA, master/slave mode transceiver routine\n | |-- I2C_EEPROM: I2C interface routine to operate EEPROM peripheral \n | |-- I2C_PEC: PEC error check, master/slave mode transceiver routine\n |-- INT\n | |-- Interrupt_VTF: VTF IRQ interrupt routine \n |-- IAP: IAP upgrade routine, including the Hex to Bin tool and IAP upgrade tool \n | |-- USB_UART: USB+UART IAP routine \n |-- IWDG: independent watchdog routine\n |-- OPA: OPA4 as voltage follower output routine\n |-- PWR\n | |-- Sleep_Mode: low power, sleep mode routine\n | |-- Standby_Mode: low power, standby mode routine\n | |-- Stop_Mode: low power, stop mode routine\n | |-- Standby_RAM_LV_Mode: when LV is enabled in standby mode, RAM 2k and 30K low-power data holding routines\n | |-- Standby_RAM_Mode: when LV is not enabled in standby mode, RAM 2k and 30K low-power data holding routines\n |-- RCC\n | |-- Get_CLK: Get system-HCLK-AHB1-AHB2 clock routine \n | |-- MCO: MCO pin clock output routine\n | |-- HSI_PLL_Source: HSI or HSI/2 as PLL input clock routine \n |-- RT-Thread: RT thread migration routine \n |-- RTC: calendar routine\n |-- SPI\n | |-- 1Lines_half-duplex: single wire half duplex mode, master/slave mode, data transceiver\n | |-- 2Lines_FullDuplex: two-wire full duplex mode, master/slave mode, data transceiver\n | |-- FullDuplex_HardNSS: Hardware NSS mode, master/slave mode, data transceiver\n | |-- SPI_CRC: CRC error check and master/slave mode transceiver routine\n | |-- SPI_DMA: SPI DMA, master/slave mode transceiver routine\n | |-- SPI_FLASH: SPI interface operation flash peripheral routine\n |-- TencentOS: TencentOS migration routine \n |-- TIM\n | |-- Clock_Select: clock source selection routine\n | |-- ComplementaryOutput_DeadTime: complementary output and deadband insertion mode routines\n | |-- ExtTrigger_Start_Two_Timer: external trigger routines to start two timers synchronously\n | |-- Input_Capture: input capture routine\n | |-- One_Pulse: single pulse output routine\n | |-- Output_Compare_Mode: output comparison mode routine\n | |-- PWM_Output: PWM output routine\n | |-- Synchro_ExtTrigger: slave mode routine, including reset mode, gating mode and trigger mode\n | |-- Synchro_Timer: timer synchronization mode\n | |-- TIM_DMA: timer DMA routines\n |-- TOUCHKEY: touchkey detection routine\n |-- USART\n | |-- USART_DMA: USART DMA, master/slave mode transceiver routine\n | |-- USART_HalfDuplex: single wire half duplex mode, master/slave mode transceiver routine\n | |-- USART_HardwareFlowControl: hardware flow control mode, master/slave mode, transceiver routine\n | |-- USART_Interrupt: USART interrupt routine, master/slave mode transceiver routine\n | |-- USART_MultiProcessorCommunication: multiprocessor communication mode routine\n | |-- USART_Polling: polling transceiver mode, master/slave transceiver routine\n | |-- USART_Printf: USART Print debugging routine\n | |-- USART_SynchronousMode: synchronous mode, master/slave mode, transceiver routine\n |-- USB\n | |-- USBD\n | | |-- CH372: Simulates a custom USB device (CH372 device) with endpoints 1, 3 down and 2, 4 up. Data down from endpoint 1 is uploaded from endpoint 3 and not reversed, and data down from endpoint 2 is uploaded from endpoint 4 and reversed.\n | | |-- Compatibility_HID: Simulates HID devices, with data transmitted up and down through the serial port.\n | | |-- CompositeKM: Simulate keyboard and mouse, use IO to simulate keystrokes, while simulated data can be uploaded through serial port 2.\n | | |-- MSC_U-Disk: Smulates a simple USB flash drive, optionally using on-chip Flash or external SPI-Flash\n | | |-- MSC_CD-ROM: Simulate CDROM, need external SPI-Flash\n | | |-- SimulateCDC: Simulate a CDC serial port and use serial port 2 to send and receive.\n | | |-- SimulateCDC-HID: Simulate a CDC serial port, use serial port 2 to send and receive, HID interrupt endpoints to send and receive data to reverse and upload. \n | |-- USBFS\n | |-- DEVICE\n | | |-- CH372: Simulates a custom USB device (CH372 device) with endpoints 1, 3 down and 2, 4 up. Data down from endpoint 1 is uploaded from endpoint 3 and not reversed, and data down from endpoint 2 is uploaded from endpoint 4 and reversed.\n | | |-- Compatibility_HID: Simulates HID devices, with data transmitted up and down through the serial port.\n | | |-- CompositeKM: Simulate keyboard and mouse, use IO to simulate keystrokes, while simulated data can be uploaded through serial port 2.\n | | |-- MSC_U-Disk: Smulates a simple USB flash drive, optionally using on-chip Flash or external SPI-Flash\n | | |-- MSC_CD-ROM: Simulate CDROM, need external SPI-Flash\n | | |-- SimulateCDC: Simulate a CDC serial port and use serial port 2 to send and receive.\n | | |-- SimulateCDC-HID: Simulate a CDC serial port, use serial port 2 to send and receive, HID interrupt endpoints to send and receive data to reverse and upload. \n | |-- HOST_IAP\n | | |-- APP: APP used with HOST_IAP, the project has modified the starting location of the program, after compilation, you need to convert the file into a bin file and rename it to APP.bin\n | | |-- HOST_IAP: The host U disk IAP routine based on the U disk read file routine finishing, read the file with the name bit APP.bin from the U disk, write it to the internal flash, check it and jump automatically.\n | |-- HOST_KM: The host operates the keypad, gets the data of the endpoints uploaded by the keypad and prints it, supports U-port under level 1 hub\n | |-- HOST_MTP_FileSystem: Enumeration process of a USB host to a device that supports MTP and PTP protocols, supports MTP and PTP protocols, and reads its files\n | |-- Host_Udisk: USB host operation USB disk routine \n | |-- Udisk_Lib: U disk file system library file \n |-- WWDG: window watchdog routine"}, "lana-tny-01-communicator-2024": {"chip": "ch32v203g6u6", "board": "lana-tny-01", "boardfamily": "ch32v20x", "path": "wch/ch32v20x/lana-tny-01-communicator-2024.7z", "icon": null, "info": "microcontroller: ch32v203g6u6\nboard: lana-tny-01\nmicrocontroller manufacturer: wch\nboard manufacturer: wch\nlink: https://embeetle.com/#supported-hardware/wch/boards/lana-tny-01\n\n\ninfo:\nThis project was originally a WCH Eclipse sample project which we've slightly\nmodified to fit the typical Embeetle project structure.\n\nThe original resources can be found on:\nhttp://www.wch-ic.com/products/CH32V203.html\n\nThe ZIP-folder is not downloadable on that page. Refer to:\nhttps://www.wch.cn/downloads/CH32V20xEVT_ZIP.html\n\nAfter unzipping this ZIP-folder:\n - The general source code is copied from: 'CH32V20xEVT/EVT/EXAM/SRC/'.\n - The sample projects are in folders like: 'CH32V20xEVT/EVT/EXAM/GPIO/GPIO_Toggle/User/'.\n - The linkerscript is found at: 'CH32V20xEVT/EVT/EXAM/SRC/Ld/Link.ld'.\n\n\nSAMPLE PROJECTS\n---------------\nSamples\n |-- ADC\n | |-- ADC_DMA: ADC DMA sampling routines\n | |-- AnalogWatchdog: analog watchdog routine\n | |-- Auto_Injection: automatic injection mode routine\n | |-- Discontinuous_mode: discontinuous mode routine\n | |-- DualADC_AlternateTrigger: dual ADC alternate trigger sampling routine, only applied to CH32V20x_D6 \n | |-- DualADC_Combined_RegInjectionSimul: dual ADC combined regular + injection + simultaneous sampling routine, only applied to CH32V20x_D6\n | |-- DualADC_FastInterleaved: dual ADC fast interleaved sampling routine, only applied to CH32V20x_D6\n | |-- DualADC_InjectionSimul: dual ADC injection simultaneous sampling routine, only applied to CH32V20x_D6 \n | |-- DualADC_RegSimul: dual ADC regular simultaneous sampling routine, only applied to CH32V20x_D6\n | |-- DualADC_SlowInterleaved: dual ADC slow interleaved sampling routine, only applied to CH32V20x_D6\n | |-- ExtLines_Trigger: external lines trigger ADC conversion routine\n | |-- Internal_Temperature: internal temperature sensor routine \n |-- BLE: only for CH32V20x_D8W \n | |-- BackupUpgrade_IAP: backup wireless upgrade IAP routine. Detect the current code flag, determine whether to move the code from the backup area to the user area, and run the code in the user area \n | |-- BackupUpgrade_OTA: backup wireless upgrade user routine. Add OTA function to peripheral slave routines, save the upgrade firmware to the backup area and jump to the IAP program to upgrade \n | |-- BLE_UART: BLE and UART transparent transmission routine, for detailed instructions, please refer to the document in the root directory\n | |-- BLE_USB: BLE with USB routine, USB emulation 340 device forwards BLE data \n | |-- Broadcaster: broadcaster routine, always broadcast when in broadcast status\n | |-- CentPeri: central-peripheral routine, integrate the function of central routine and peripheral routine and run simultaneously\n | |-- Central: central routine, actively scan surrounding devices, conect to the specified peripheral address, search custom service and characteristic, execute read/write commands, peripheral routine is needed, and modify the peripheral address to the routine target address, (84:C2:E4:03:02:02) by default\n | |-- CyclingSensor: cycling sensor routine, upload speed and cadence regularly after connected to the host\n | |-- DirectTest: direct test routine, test data packets sent by specified communication channel\n | |-- HAL: Hardware-related files shared by routines\n | |-- HeartRate: heart rate routine, upload heart rate regularly after connected to the central\n | |-- HID_Consumer: BLE consumer routine, simulate user control device, upload volume key down key regularly after connected to the central\n | |-- HID_Keyboard: BLE keyboard routine, simulate a keyboard device, upload key value regularly after connected to the central\n | |-- HID_Mouse: BLE mouse routine, simulate a mouse device, upload key value regularly after connected to the central\n | |-- HID_Touch: BLE touch routine, simulate a touch pencil device, upload touch value regularly after connected to the central\n | |-- LIB: BLE protocol stack library file and header file\n | |-- LWNS: LWNS wireless networking routine,including broadcast, unicast, netflood, mesh.\n | |-- MultiCentPeri: Multi-central and multi-peripheral routines, support connecting three masters and three slaves at the same time\n | |-- MultiCentral: multicentral routine, actively scan surrounding devices, conect to the specified three peripheral addresses, search custom services and characteristics, execute read/write commands, peripheral routine is needed, and modify the peripheral address to this routine target address, the addresses of these peripherals are (84:C2:E4:03:02:02), (84:C2:E4:03:02:03) and (84:C2:E4:03:02:04) by default\n | |-- Observer: observer routine, scan regularly, print the scanned broadcast address if the scanning result is not empty\n | |-- OnlyUpdateApp_IAP: the only library wireless upgrade IAP routine, with OTA function, upgrade the user area code after receiving the upgraded firmware\n | |-- OnlyUpdateApp_Peripheral: the only library wireless upgrade user routine, on the basis of peripheral routine, the jumping to IAP program is added for subsequent upgrades\n | |-- Peripheral: peripheral role routine, custom including five services with different attributes, including read attribute, write attribute, notify attribute, read/write attribute, and safe and readable attribute\n | |-- peripheral_ancs_client: peripheral slave role routine, including Apple Notification Center service\n | |-- peripheral_ETH: Bluetooth ETH routines\n | |-- RF_PHY: non-standard wireless transceiver routines\n | |-- RF_PHY_Hop: non-standard wireless frequency hopping transceiver routine\n | |-- RunningSensor: running sensor routine,upload rate regularly after connected to the central \n | |-- SpeedTest_Central: Bluetooth speed test central routine\n | |-- SpeedTest_Peripheral: Bluetooth speed test peripheral routine\n | |-- SYNC_ADV: cycle synchronization advertising routine\n | |-- SYNC_SCAN: cycle synchronization scanning routine\n | |-- WCH BLE Software Developers Guide.pdf\n | |-- BLE Certification: Product: WCH CH32V208 QDID: 179771 \n | |-- MESH\n | |-- adv_ali_light: Tmall Genie light routine, devices can be found and provisioned network via Tmall Genie, to control the switch state. By default, only switch attribute can be controlled. If other attributes (brightness, power, temperature, etc.) are needed, add the corresponding processing function and status report function according to the attribute description of the Alibaba Cloud product configuration.\n | |-- adv_ali_light_add_lightness: MESH general attribute adding routine. On the basis of the Tmall Genie light routine, the brightness attribute is added, which is used to compare the original Tmall Genie light routine to quickly become familiar with the method of adding other MESH general attributes.\n | |-- adv_ali_light_add_windspeed: Tmall definition attribute adding routine. On the basis of the Tmall Genie light routine, the wind speed attribute is added, which is used to compare the original Tmall Genie light routine to quickly become familiar with the method of adding other Tmall definition attributes.\n | |-- adv_ali_light_multi_element: Multi-element fan lamp, which is used to compare the original Tmall Genie light routine to quickly become familiar with the method of adding multi-element Tmall definition attributes.\n | |-- adv_ali_light_with_peripheral: Based on the Tmall Genie light routine, add brightness and color temperature controls, it supports the connection control of BLE debugging tool on the mobile phone.\n | |-- adv_proxy: proxy node routine, which can be used to provision network through the PV_GATT layer (BLE connection).\n | |-- adv_vendor: vendor-defined model routine, used with self_provisioner_vendor, supports two communication attributes of response transmission and non-response transparent transmission, and develops the communication protocol by yourself.\n | |-- adv_vendor_friend: based on vendor-defined model routine, support friend node function\n | |-- adv_vendor_low_power: On the basis of the vendor custom model routine, support low-power node functions and should be used with friend nodes\n | |-- adv_vendor_self_provision: On the basis of the vendor custom model routine, support local provision\n | |-- adv_vendor_self_provision_IAP: MESH backup wireless upgrade IAP routine, detect the current code flag, judge whether to move the backup area code to the user area and run the user area code\n | |-- adv_vendor_self_provision_with_peripheral: MESH backup wireless upgrade user routine, On the basis of the vendor custom model routine, supports the connection control of the mobile phone BLE debugging assistant, receives the distribution network information through BLE and distributes the network itself. It is suitable for terminal control networking applications. It can formulate the communication protocol by itself to realize the mobile phone control all devices in the mesh network.\n | |-- self_provisioner_vendor: vendor-defined model self-provisioning network initiator routine, used with adv_vendor, automatically provision network to the surrounding devices without network, and add it to its own mesh network, support provision network to six devices by default . The default configuration device is bound with single APPKEY, which is used for response transmission and non-response transparent transmission, and the configuration device is bound with single subscription address, which is used for mass sending of unanswered messages\n | |-- self_provisioner_vendor_with_peripheral: Based on the vendor-defined model self-provisioning network initiator routine, can be connected and controlled by BLE debugging tool on the mobile phone, transfer the communication between the mobile phone and the mesh network, and can draw up the communication protocol to implement that all devices in mesh network can be controlled the mobile phone.\n | |-- MESH_LIB: MESH protocol stack library file and header file\n | |-- Qinheng MESH APP Management Distribution Network Application Manual.pdf\n | |-- Qinheng Low Energy Bluetooth MESH Software Development Reference Manual.pdf\n |-- BKP: BKP routine\n |-- CAN: only for CH32V20x_D6-CH32V20x_D8W \n | |-- Networking: CAN routine: normal mode, standard frame and expanded frame data transceiver\n | |-- TestMode: test mode, including silent mode, loopback mode and loopback silent mode\n | |-- Time-triggered: time triggered communication mode \n |-- CRC: CRC routine\n |-- DMA\n | |-- DMA_MEM2MEM: Memory to memory mode routine\n | |-- DMA_MEM2PERIP: Memory to peripheral mode, and peripheral to memory mode routine, see peripheral sub-routines\n |-- ETH: only for CH32V20x_D8-CH32V20x_D8W\n | |-- 1_Tool_Doc: routine-related documents and configuration software\n | |-- DHCP: DHCP demonstration routine to obtain IP automatically, and establish TCP connection for data return\n | |-- DNS: DHCP demonstration routine to obtain IP automatically and then request domain name resolution \n | |-- ETH_CFG: ETH_CFG routine. Create a UDP Server to communicate with upper computer, to configure WCHNET functions, including configuring various parameters and creating a new communication. \n | |-- ETH_IAP: ETH IAP routine\n | |-- ETH_UART: ETH_UART routine, to demonstrate data transparent transfer between Ethernet and UART. By default, the 1000000 baud rate (can be modified in bsp_uart.h) is selected for serial port data transmission\n | |-- IPRaw_PING: PING function demonstration routine\n | |-- Mail: to demonstrate reception and transmission of SMTP and POP3 mails \n | |-- MQTT: MQTT routine, to demonstrate MQTT protocol communication based on TCP/IP \n | |-- NetLib: Network protocol stack library file\n | |-- TcpClient: demonstration routine that TCP client receives data after connected to the server and then returns data \n | |-- TcpServer: demonstration routine that TCP server receives data after connected to the client and then returns data\n | |-- UdpClient: demonstration routine that Udp Client receives data and returns data\n | |-- UdpServer: demonstration routine that Udp Server receives data and returns data\n | |-- WebServer: Web Server routine, to demonstrate the configuration of WCHNET device functions through Web browser. As the WCHNET devices have built-in web server, the network parameter configuration and password management of WCHNET can be implemented on the web page. \n |-- EXTI: external interrupt line routine\n |-- FLASH: FLASH erase/read/write, and fast programming\n |-- FreeRTOS: FreeRTOS migration routine \n |-- GPIO: GPIO routine\n |-- HarmonyOS: HarmonyOS migration routine \n |-- I2C\n | |-- I2C_7bit_Mode: 7-bit addressing mode, master/slave mode, transceiver routine\n | |-- I2C_10bit_Mode: 10-bit addressing mode, master/slave mode transceiver routine\n | |-- I2C_DMA: I2C DMA, master/slave mode transceiver routine\n | |-- I2C_EEPROM: I2C interface routine to operate EEPROM peripheral \n | |-- I2C_PEC: PEC error check, master/slave mode transceiver routine\n |-- INT\n | |-- Interrupt_VTF: VTF IRQ interrupt routine \n |-- IAP: IAP upgrade routine, including the Hex to Bin tool and IAP upgrade tool \n | |-- USB_UART: USB+UART IAP routine \n |-- IWDG: independent watchdog routine\n |-- OPA: OPA4 as voltage follower output routine\n |-- PWR\n | |-- Sleep_Mode: low power, sleep mode routine\n | |-- Standby_Mode: low power, standby mode routine\n | |-- Stop_Mode: low power, stop mode routine\n | |-- Standby_RAM_LV_Mode: when LV is enabled in standby mode, RAM 2k and 30K low-power data holding routines\n | |-- Standby_RAM_Mode: when LV is not enabled in standby mode, RAM 2k and 30K low-power data holding routines\n |-- RCC\n | |-- Get_CLK: Get system-HCLK-AHB1-AHB2 clock routine \n | |-- MCO: MCO pin clock output routine\n | |-- HSI_PLL_Source: HSI or HSI/2 as PLL input clock routine \n |-- RT-Thread: RT thread migration routine \n |-- RTC: calendar routine\n |-- SPI\n | |-- 1Lines_half-duplex: single wire half duplex mode, master/slave mode, data transceiver\n | |-- 2Lines_FullDuplex: two-wire full duplex mode, master/slave mode, data transceiver\n | |-- FullDuplex_HardNSS: Hardware NSS mode, master/slave mode, data transceiver\n | |-- SPI_CRC: CRC error check and master/slave mode transceiver routine\n | |-- SPI_DMA: SPI DMA, master/slave mode transceiver routine\n | |-- SPI_FLASH: SPI interface operation flash peripheral routine\n |-- TencentOS: TencentOS migration routine \n |-- TIM\n | |-- Clock_Select: clock source selection routine\n | |-- ComplementaryOutput_DeadTime: complementary output and deadband insertion mode routines\n | |-- ExtTrigger_Start_Two_Timer: external trigger routines to start two timers synchronously\n | |-- Input_Capture: input capture routine\n | |-- One_Pulse: single pulse output routine\n | |-- Output_Compare_Mode: output comparison mode routine\n | |-- PWM_Output: PWM output routine\n | |-- Synchro_ExtTrigger: slave mode routine, including reset mode, gating mode and trigger mode\n | |-- Synchro_Timer: timer synchronization mode\n | |-- TIM_DMA: timer DMA routines\n |-- TOUCHKEY: touchkey detection routine\n |-- USART\n | |-- USART_DMA: USART DMA, master/slave mode transceiver routine\n | |-- USART_HalfDuplex: single wire half duplex mode, master/slave mode transceiver routine\n | |-- USART_HardwareFlowControl: hardware flow control mode, master/slave mode, transceiver routine\n | |-- USART_Interrupt: USART interrupt routine, master/slave mode transceiver routine\n | |-- USART_MultiProcessorCommunication: multiprocessor communication mode routine\n | |-- USART_Polling: polling transceiver mode, master/slave transceiver routine\n | |-- USART_Printf: USART Print debugging routine\n | |-- USART_SynchronousMode: synchronous mode, master/slave mode, transceiver routine\n |-- USB\n | |-- USBD\n | | |-- CH372: Simulates a custom USB device (CH372 device) with endpoints 1, 3 down and 2, 4 up. Data down from endpoint 1 is uploaded from endpoint 3 and not reversed, and data down from endpoint 2 is uploaded from endpoint 4 and reversed.\n | | |-- Compatibility_HID: Simulates HID devices, with data transmitted up and down through the serial port.\n | | |-- CompositeKM: Simulate keyboard and mouse, use IO to simulate keystrokes, while simulated data can be uploaded through serial port 2.\n | | |-- MSC_U-Disk: Smulates a simple USB flash drive, optionally using on-chip Flash or external SPI-Flash\n | | |-- MSC_CD-ROM: Simulate CDROM, need external SPI-Flash\n | | |-- SimulateCDC: Simulate a CDC serial port and use serial port 2 to send and receive.\n | | |-- SimulateCDC-HID: Simulate a CDC serial port, use serial port 2 to send and receive, HID interrupt endpoints to send and receive data to reverse and upload. \n | |-- USBFS\n | |-- DEVICE\n | | |-- CH372: Simulates a custom USB device (CH372 device) with endpoints 1, 3 down and 2, 4 up. Data down from endpoint 1 is uploaded from endpoint 3 and not reversed, and data down from endpoint 2 is uploaded from endpoint 4 and reversed.\n | | |-- Compatibility_HID: Simulates HID devices, with data transmitted up and down through the serial port.\n | | |-- CompositeKM: Simulate keyboard and mouse, use IO to simulate keystrokes, while simulated data can be uploaded through serial port 2.\n | | |-- MSC_U-Disk: Smulates a simple USB flash drive, optionally using on-chip Flash or external SPI-Flash\n | | |-- MSC_CD-ROM: Simulate CDROM, need external SPI-Flash\n | | |-- SimulateCDC: Simulate a CDC serial port and use serial port 2 to send and receive.\n | | |-- SimulateCDC-HID: Simulate a CDC serial port, use serial port 2 to send and receive, HID interrupt endpoints to send and receive data to reverse and upload. \n | |-- HOST_IAP\n | | |-- APP: APP used with HOST_IAP, the project has modified the starting location of the program, after compilation, you need to convert the file into a bin file and rename it to APP.bin\n | | |-- HOST_IAP: The host U disk IAP routine based on the U disk read file routine finishing, read the file with the name bit APP.bin from the U disk, write it to the internal flash, check it and jump automatically.\n | |-- HOST_KM: The host operates the keypad, gets the data of the endpoints uploaded by the keypad and prints it, supports U-port under level 1 hub\n | |-- HOST_MTP_FileSystem: Enumeration process of a USB host to a device that supports MTP and PTP protocols, supports MTP and PTP protocols, and reads its files\n | |-- Host_Udisk: USB host operation USB disk routine \n | |-- Udisk_Lib: U disk file system library file \n |-- WWDG: window watchdog routine"}, "lana-tny-01": {"chip": "ch32v203g6u6", "board": "lana-tny-01", "boardfamily": "ch32v20x", "path": "wch/ch32v20x/lana-tny-01.7z", "icon": null, "info": "microcontroller: ch32v203g6u6\nboard: lana-tny-01\nmicrocontroller manufacturer: wch\nboard manufacturer: wch\nlink: https://embeetle.com/#supported-hardware/wch/boards/lana-tny-01\n\n\ninfo:\nThis project was originally a WCH Eclipse sample project which we've slightly\nmodified to fit the typical Embeetle project structure.\n\nThe original resources can be found on:\nhttp://www.wch-ic.com/products/CH32V203.html\n\nThe ZIP-folder is not downloadable on that page. Refer to:\nhttps://www.wch.cn/downloads/CH32V20xEVT_ZIP.html\n\nAfter unzipping this ZIP-folder:\n - The general source code is copied from: 'CH32V20xEVT/EVT/EXAM/SRC/'.\n - The sample projects are in folders like: 'CH32V20xEVT/EVT/EXAM/GPIO/GPIO_Toggle/User/'.\n - The linkerscript is found at: 'CH32V20xEVT/EVT/EXAM/SRC/Ld/Link.ld'.\n\n\nSAMPLE PROJECTS\n---------------\nSamples\n |-- ADC\n | |-- ADC_DMA: ADC DMA sampling routines\n | |-- AnalogWatchdog: analog watchdog routine\n | |-- Auto_Injection: automatic injection mode routine\n | |-- Discontinuous_mode: discontinuous mode routine\n | |-- DualADC_AlternateTrigger: dual ADC alternate trigger sampling routine, only applied to CH32V20x_D6 \n | |-- DualADC_Combined_RegInjectionSimul: dual ADC combined regular + injection + simultaneous sampling routine, only applied to CH32V20x_D6\n | |-- DualADC_FastInterleaved: dual ADC fast interleaved sampling routine, only applied to CH32V20x_D6\n | |-- DualADC_InjectionSimul: dual ADC injection simultaneous sampling routine, only applied to CH32V20x_D6 \n | |-- DualADC_RegSimul: dual ADC regular simultaneous sampling routine, only applied to CH32V20x_D6\n | |-- DualADC_SlowInterleaved: dual ADC slow interleaved sampling routine, only applied to CH32V20x_D6\n | |-- ExtLines_Trigger: external lines trigger ADC conversion routine\n | |-- Internal_Temperature: internal temperature sensor routine \n |-- BLE: only for CH32V20x_D8W \n | |-- BackupUpgrade_IAP: backup wireless upgrade IAP routine. Detect the current code flag, determine whether to move the code from the backup area to the user area, and run the code in the user area \n | |-- BackupUpgrade_OTA: backup wireless upgrade user routine. Add OTA function to peripheral slave routines, save the upgrade firmware to the backup area and jump to the IAP program to upgrade \n | |-- BLE_UART: BLE and UART transparent transmission routine, for detailed instructions, please refer to the document in the root directory\n | |-- BLE_USB: BLE with USB routine, USB emulation 340 device forwards BLE data \n | |-- Broadcaster: broadcaster routine, always broadcast when in broadcast status\n | |-- CentPeri: central-peripheral routine, integrate the function of central routine and peripheral routine and run simultaneously\n | |-- Central: central routine, actively scan surrounding devices, conect to the specified peripheral address, search custom service and characteristic, execute read/write commands, peripheral routine is needed, and modify the peripheral address to the routine target address, (84:C2:E4:03:02:02) by default\n | |-- CyclingSensor: cycling sensor routine, upload speed and cadence regularly after connected to the host\n | |-- DirectTest: direct test routine, test data packets sent by specified communication channel\n | |-- HAL: Hardware-related files shared by routines\n | |-- HeartRate: heart rate routine, upload heart rate regularly after connected to the central\n | |-- HID_Consumer: BLE consumer routine, simulate user control device, upload volume key down key regularly after connected to the central\n | |-- HID_Keyboard: BLE keyboard routine, simulate a keyboard device, upload key value regularly after connected to the central\n | |-- HID_Mouse: BLE mouse routine, simulate a mouse device, upload key value regularly after connected to the central\n | |-- HID_Touch: BLE touch routine, simulate a touch pencil device, upload touch value regularly after connected to the central\n | |-- LIB: BLE protocol stack library file and header file\n | |-- LWNS: LWNS wireless networking routine,including broadcast, unicast, netflood, mesh.\n | |-- MultiCentPeri: Multi-central and multi-peripheral routines, support connecting three masters and three slaves at the same time\n | |-- MultiCentral: multicentral routine, actively scan surrounding devices, conect to the specified three peripheral addresses, search custom services and characteristics, execute read/write commands, peripheral routine is needed, and modify the peripheral address to this routine target address, the addresses of these peripherals are (84:C2:E4:03:02:02), (84:C2:E4:03:02:03) and (84:C2:E4:03:02:04) by default\n | |-- Observer: observer routine, scan regularly, print the scanned broadcast address if the scanning result is not empty\n | |-- OnlyUpdateApp_IAP: the only library wireless upgrade IAP routine, with OTA function, upgrade the user area code after receiving the upgraded firmware\n | |-- OnlyUpdateApp_Peripheral: the only library wireless upgrade user routine, on the basis of peripheral routine, the jumping to IAP program is added for subsequent upgrades\n | |-- Peripheral: peripheral role routine, custom including five services with different attributes, including read attribute, write attribute, notify attribute, read/write attribute, and safe and readable attribute\n | |-- peripheral_ancs_client: peripheral slave role routine, including Apple Notification Center service\n | |-- peripheral_ETH: Bluetooth ETH routines\n | |-- RF_PHY: non-standard wireless transceiver routines\n | |-- RF_PHY_Hop: non-standard wireless frequency hopping transceiver routine\n | |-- RunningSensor: running sensor routine,upload rate regularly after connected to the central \n | |-- SpeedTest_Central: Bluetooth speed test central routine\n | |-- SpeedTest_Peripheral: Bluetooth speed test peripheral routine\n | |-- SYNC_ADV: cycle synchronization advertising routine\n | |-- SYNC_SCAN: cycle synchronization scanning routine\n | |-- WCH BLE Software Developers Guide.pdf\n | |-- BLE Certification: Product: WCH CH32V208 QDID: 179771 \n | |-- MESH\n | |-- adv_ali_light: Tmall Genie light routine, devices can be found and provisioned network via Tmall Genie, to control the switch state. By default, only switch attribute can be controlled. If other attributes (brightness, power, temperature, etc.) are needed, add the corresponding processing function and status report function according to the attribute description of the Alibaba Cloud product configuration.\n | |-- adv_ali_light_add_lightness: MESH general attribute adding routine. On the basis of the Tmall Genie light routine, the brightness attribute is added, which is used to compare the original Tmall Genie light routine to quickly become familiar with the method of adding other MESH general attributes.\n | |-- adv_ali_light_add_windspeed: Tmall definition attribute adding routine. On the basis of the Tmall Genie light routine, the wind speed attribute is added, which is used to compare the original Tmall Genie light routine to quickly become familiar with the method of adding other Tmall definition attributes.\n | |-- adv_ali_light_multi_element: Multi-element fan lamp, which is used to compare the original Tmall Genie light routine to quickly become familiar with the method of adding multi-element Tmall definition attributes.\n | |-- adv_ali_light_with_peripheral: Based on the Tmall Genie light routine, add brightness and color temperature controls, it supports the connection control of BLE debugging tool on the mobile phone.\n | |-- adv_proxy: proxy node routine, which can be used to provision network through the PV_GATT layer (BLE connection).\n | |-- adv_vendor: vendor-defined model routine, used with self_provisioner_vendor, supports two communication attributes of response transmission and non-response transparent transmission, and develops the communication protocol by yourself.\n | |-- adv_vendor_friend: based on vendor-defined model routine, support friend node function\n | |-- adv_vendor_low_power: On the basis of the vendor custom model routine, support low-power node functions and should be used with friend nodes\n | |-- adv_vendor_self_provision: On the basis of the vendor custom model routine, support local provision\n | |-- adv_vendor_self_provision_IAP: MESH backup wireless upgrade IAP routine, detect the current code flag, judge whether to move the backup area code to the user area and run the user area code\n | |-- adv_vendor_self_provision_with_peripheral: MESH backup wireless upgrade user routine, On the basis of the vendor custom model routine, supports the connection control of the mobile phone BLE debugging assistant, receives the distribution network information through BLE and distributes the network itself. It is suitable for terminal control networking applications. It can formulate the communication protocol by itself to realize the mobile phone control all devices in the mesh network.\n | |-- self_provisioner_vendor: vendor-defined model self-provisioning network initiator routine, used with adv_vendor, automatically provision network to the surrounding devices without network, and add it to its own mesh network, support provision network to six devices by default . The default configuration device is bound with single APPKEY, which is used for response transmission and non-response transparent transmission, and the configuration device is bound with single subscription address, which is used for mass sending of unanswered messages\n | |-- self_provisioner_vendor_with_peripheral: Based on the vendor-defined model self-provisioning network initiator routine, can be connected and controlled by BLE debugging tool on the mobile phone, transfer the communication between the mobile phone and the mesh network, and can draw up the communication protocol to implement that all devices in mesh network can be controlled the mobile phone.\n | |-- MESH_LIB: MESH protocol stack library file and header file\n | |-- Qinheng MESH APP Management Distribution Network Application Manual.pdf\n | |-- Qinheng Low Energy Bluetooth MESH Software Development Reference Manual.pdf\n |-- BKP: BKP routine\n |-- CAN: only for CH32V20x_D6-CH32V20x_D8W \n | |-- Networking: CAN routine: normal mode, standard frame and expanded frame data transceiver\n | |-- TestMode: test mode, including silent mode, loopback mode and loopback silent mode\n | |-- Time-triggered: time triggered communication mode \n |-- CRC: CRC routine\n |-- DMA\n | |-- DMA_MEM2MEM: Memory to memory mode routine\n | |-- DMA_MEM2PERIP: Memory to peripheral mode, and peripheral to memory mode routine, see peripheral sub-routines\n |-- ETH: only for CH32V20x_D8-CH32V20x_D8W\n | |-- 1_Tool_Doc: routine-related documents and configuration software\n | |-- DHCP: DHCP demonstration routine to obtain IP automatically, and establish TCP connection for data return\n | |-- DNS: DHCP demonstration routine to obtain IP automatically and then request domain name resolution \n | |-- ETH_CFG: ETH_CFG routine. Create a UDP Server to communicate with upper computer, to configure WCHNET functions, including configuring various parameters and creating a new communication. \n | |-- ETH_IAP: ETH IAP routine\n | |-- ETH_UART: ETH_UART routine, to demonstrate data transparent transfer between Ethernet and UART. By default, the 1000000 baud rate (can be modified in bsp_uart.h) is selected for serial port data transmission\n | |-- IPRaw_PING: PING function demonstration routine\n | |-- Mail: to demonstrate reception and transmission of SMTP and POP3 mails \n | |-- MQTT: MQTT routine, to demonstrate MQTT protocol communication based on TCP/IP \n | |-- NetLib: Network protocol stack library file\n | |-- TcpClient: demonstration routine that TCP client receives data after connected to the server and then returns data \n | |-- TcpServer: demonstration routine that TCP server receives data after connected to the client and then returns data\n | |-- UdpClient: demonstration routine that Udp Client receives data and returns data\n | |-- UdpServer: demonstration routine that Udp Server receives data and returns data\n | |-- WebServer: Web Server routine, to demonstrate the configuration of WCHNET device functions through Web browser. As the WCHNET devices have built-in web server, the network parameter configuration and password management of WCHNET can be implemented on the web page. \n |-- EXTI: external interrupt line routine\n |-- FLASH: FLASH erase/read/write, and fast programming\n |-- FreeRTOS: FreeRTOS migration routine \n |-- GPIO: GPIO routine\n |-- HarmonyOS: HarmonyOS migration routine \n |-- I2C\n | |-- I2C_7bit_Mode: 7-bit addressing mode, master/slave mode, transceiver routine\n | |-- I2C_10bit_Mode: 10-bit addressing mode, master/slave mode transceiver routine\n | |-- I2C_DMA: I2C DMA, master/slave mode transceiver routine\n | |-- I2C_EEPROM: I2C interface routine to operate EEPROM peripheral \n | |-- I2C_PEC: PEC error check, master/slave mode transceiver routine\n |-- INT\n | |-- Interrupt_VTF: VTF IRQ interrupt routine \n |-- IAP: IAP upgrade routine, including the Hex to Bin tool and IAP upgrade tool \n | |-- USB_UART: USB+UART IAP routine \n |-- IWDG: independent watchdog routine\n |-- OPA: OPA4 as voltage follower output routine\n |-- PWR\n | |-- Sleep_Mode: low power, sleep mode routine\n | |-- Standby_Mode: low power, standby mode routine\n | |-- Stop_Mode: low power, stop mode routine\n | |-- Standby_RAM_LV_Mode: when LV is enabled in standby mode, RAM 2k and 30K low-power data holding routines\n | |-- Standby_RAM_Mode: when LV is not enabled in standby mode, RAM 2k and 30K low-power data holding routines\n |-- RCC\n | |-- Get_CLK: Get system-HCLK-AHB1-AHB2 clock routine \n | |-- MCO: MCO pin clock output routine\n | |-- HSI_PLL_Source: HSI or HSI/2 as PLL input clock routine \n |-- RT-Thread: RT thread migration routine \n |-- RTC: calendar routine\n |-- SPI\n | |-- 1Lines_half-duplex: single wire half duplex mode, master/slave mode, data transceiver\n | |-- 2Lines_FullDuplex: two-wire full duplex mode, master/slave mode, data transceiver\n | |-- FullDuplex_HardNSS: Hardware NSS mode, master/slave mode, data transceiver\n | |-- SPI_CRC: CRC error check and master/slave mode transceiver routine\n | |-- SPI_DMA: SPI DMA, master/slave mode transceiver routine\n | |-- SPI_FLASH: SPI interface operation flash peripheral routine\n |-- TencentOS: TencentOS migration routine \n |-- TIM\n | |-- Clock_Select: clock source selection routine\n | |-- ComplementaryOutput_DeadTime: complementary output and deadband insertion mode routines\n | |-- ExtTrigger_Start_Two_Timer: external trigger routines to start two timers synchronously\n | |-- Input_Capture: input capture routine\n | |-- One_Pulse: single pulse output routine\n | |-- Output_Compare_Mode: output comparison mode routine\n | |-- PWM_Output: PWM output routine\n | |-- Synchro_ExtTrigger: slave mode routine, including reset mode, gating mode and trigger mode\n | |-- Synchro_Timer: timer synchronization mode\n | |-- TIM_DMA: timer DMA routines\n |-- TOUCHKEY: touchkey detection routine\n |-- USART\n | |-- USART_DMA: USART DMA, master/slave mode transceiver routine\n | |-- USART_HalfDuplex: single wire half duplex mode, master/slave mode transceiver routine\n | |-- USART_HardwareFlowControl: hardware flow control mode, master/slave mode, transceiver routine\n | |-- USART_Interrupt: USART interrupt routine, master/slave mode transceiver routine\n | |-- USART_MultiProcessorCommunication: multiprocessor communication mode routine\n | |-- USART_Polling: polling transceiver mode, master/slave transceiver routine\n | |-- USART_Printf: USART Print debugging routine\n | |-- USART_SynchronousMode: synchronous mode, master/slave mode, transceiver routine\n |-- USB\n | |-- USBD\n | | |-- CH372: Simulates a custom USB device (CH372 device) with endpoints 1, 3 down and 2, 4 up. Data down from endpoint 1 is uploaded from endpoint 3 and not reversed, and data down from endpoint 2 is uploaded from endpoint 4 and reversed.\n | | |-- Compatibility_HID: Simulates HID devices, with data transmitted up and down through the serial port.\n | | |-- CompositeKM: Simulate keyboard and mouse, use IO to simulate keystrokes, while simulated data can be uploaded through serial port 2.\n | | |-- MSC_U-Disk: Smulates a simple USB flash drive, optionally using on-chip Flash or external SPI-Flash\n | | |-- MSC_CD-ROM: Simulate CDROM, need external SPI-Flash\n | | |-- SimulateCDC: Simulate a CDC serial port and use serial port 2 to send and receive.\n | | |-- SimulateCDC-HID: Simulate a CDC serial port, use serial port 2 to send and receive, HID interrupt endpoints to send and receive data to reverse and upload. \n | |-- USBFS\n | |-- DEVICE\n | | |-- CH372: Simulates a custom USB device (CH372 device) with endpoints 1, 3 down and 2, 4 up. Data down from endpoint 1 is uploaded from endpoint 3 and not reversed, and data down from endpoint 2 is uploaded from endpoint 4 and reversed.\n | | |-- Compatibility_HID: Simulates HID devices, with data transmitted up and down through the serial port.\n | | |-- CompositeKM: Simulate keyboard and mouse, use IO to simulate keystrokes, while simulated data can be uploaded through serial port 2.\n | | |-- MSC_U-Disk: Smulates a simple USB flash drive, optionally using on-chip Flash or external SPI-Flash\n | | |-- MSC_CD-ROM: Simulate CDROM, need external SPI-Flash\n | | |-- SimulateCDC: Simulate a CDC serial port and use serial port 2 to send and receive.\n | | |-- SimulateCDC-HID: Simulate a CDC serial port, use serial port 2 to send and receive, HID interrupt endpoints to send and receive data to reverse and upload. \n | |-- HOST_IAP\n | | |-- APP: APP used with HOST_IAP, the project has modified the starting location of the program, after compilation, you need to convert the file into a bin file and rename it to APP.bin\n | | |-- HOST_IAP: The host U disk IAP routine based on the U disk read file routine finishing, read the file with the name bit APP.bin from the U disk, write it to the internal flash, check it and jump automatically.\n | |-- HOST_KM: The host operates the keypad, gets the data of the endpoints uploaded by the keypad and prints it, supports U-port under level 1 hub\n | |-- HOST_MTP_FileSystem: Enumeration process of a USB host to a device that supports MTP and PTP protocols, supports MTP and PTP protocols, and reads its files\n | |-- Host_Udisk: USB host operation USB disk routine \n | |-- Udisk_Lib: U disk file system library file \n |-- WWDG: window watchdog routine"}, "ch32v307vct6-evt-r1-1v1": {"chip": "ch32v307vct6", "board": "ch32v307vct6-evt-r1-1v1", "boardfamily": "ch32v30x", "path": "wch/ch32v30x/ch32v307vct6-evt-r1-1v1.7z", "icon": null, "info": "microcontroller: ch32v307vct6\nboard: ch32v307vct6-evt-r1-1v1\nmicrocontroller manufacturer: wch\nboard manufacturer: wch\nlink: https://embeetle.com/#supported-hardware/wch/boards/ch32v307vct6-evt-r1-1v1\n\n\ninfo:\nThis project was originally a WCH Eclipse sample project which we've slightly\nmodified to fit the typical Embeetle project structure.\n\nThe original resources can be found on:\nhttp://www.wch-ic.com/products/CH32V307.html\n\nThe ZIP-folder is not downloadable on that page. Refer to:\nhttps://www.wch.cn/downloads/CH32V307EVT_ZIP.html\n\nAfter unzipping this ZIP-folder:\n - The general source code is copied from: 'CH32V307EVT/EVT/EXAM/SRC/'.\n - The GPIO toggle code is copied from: 'CH32V307EVT/EVT/EXAM/GPIO/GPIO_Toggle/User/'.\n - The linkerscript is found at: 'CH32V307EVT/EVT/EXAM/SRC/Ld/Link.ld'.\n\nThe original sources provide three startup assembly files:\n- startup_ch32v30x_D8.S\n- startup_ch32v30x_D8C.S\nOnly the second one is correct for this particular board.\n\nSAMPLE PROJECTS\n---------------\n\nSamples\n |-- ADC\n | |-- ADC_DMA: ADC DMA sampling routines\n | |-- AnalogWatchdog: analog watchdog routine\n | |-- Auto_Injection: automatic injection mode routine\n | |-- Discontinuous_mode: discontinuous mode routine\n | |-- DualADC_AlternateTrigger: dual ADC alternate trigger sampling routine \n | |-- DualADC_Combined_RegInjectionSimul: dual ADC combined regular + injection + simultaneous sampling routine\n | |-- DualADC_FastInterleaved: dual ADC fast interleaved sampling routine\n | |-- DualADC_InjectionSimul: dual ADC injection simultaneous sampling routine\n | |-- DualADC_RegSimul: dual ADC regular simultaneous sampling routine\n | |-- DualADC_SlowInterleaved: dual ADC slow interleaved sampling routine \n | |-- ExtLines_Trigger: external lines trigger ADC conversion routine\n | |-- Internal_Temperature: internal temperature sensor routine \n |-- BKP: BKP routine\n |-- CAN\n | |-- Networking: CAN routine: normal mode, standard frame and expanded frame data transceiver\n | |-- TestMode: test mode, including silent mode, loopback mode and loopback silent mode\n | |-- Time-triggered: time triggered communication mode \n |-- CRC: CRC routine\n |-- DAC \n | |-- DAC_DMA: DAC DMA conversion routines\n | |-- DAC_Exit_9_Trig: external trigger DAC conversion routine\n | |-- DAC_Noise_Generation: noise waveform generation routine\n | |-- DAC_Normal_OUT: normal output routine\n | |-- DAC_Timer_Trig: timer trigger DAC conversion routine\n | |-- DAC_Triangle_Generation: triangular waveform generation routine\n | |-- DualDAC_SineWave: dual DAC output sine wave routine\n | |-- DualDAC_Triangle: dual DAC output triangular wave routine \n |-- DMA\n | |-- DMA_MEM2MEM: memory to memory mode routine\n | |-- DMA_MEM2PERIP: see each peripheral subroutine for memory to peripheral mode and peripheral to memory mode routines\n |-- DVP ----only for CH32V30x_D8C\n | |-- DVP_TFTLCD: DVP routine to operate OV2640 camera video mode to display image on LCD\n | |-- DVP_UART: DVP routine to operate OV2640 camera JPEG mode\n |-- ETH ----only for CH32V30x_D8C\n | |-- 1_Tool_Doc:ETH routine related documents and tools \n | |-- 8_UART_Server: demonstration routine of 8 UART network server \n | |-- DHCP: DHCP demonstration routine to obtain IP automatically\n | |-- DNS: DHCP demonstration routine to obtain IP automatically and then request domain name resolution \n | |-- ETH_CFG: ETH_CFG routine. Create a UDP Server to communicate with upper computer, to configure WCHNET functions, including configuring various parameters and creating a new communication. \n | |-- ETH_IAP: ETH IAP routine\n | |-- ETH_UART: ETH_UART routine, to demonstrate data transparent transfer between Ethernet and UART \n | |-- IPRaw_PING: IP_RAW routine, to demonstrate that the TCP client receives data after connecting to the server and then sends it back\n | |-- Mail: mail routine, to demonstrate reception and transmission of SMTP and POP3 mails \n | |-- MQTT: MQTT routine, to demonstrate MQTT protocol communication based on TCP/IP \n | |-- NetLib: Network protocol stack library file\n | |-- TcpClient: demonstration routine that TCP client receives data after connecting to the server and then returns data \n | |-- TcpServer: demonstration routine that TCP server receives data after connecting to the client and then returns data\n | |-- UdpClient: demonstration routine that Udp Client receives data and returns data\n | |-- UdpServer: demonstration routine that Udp Server receives data and returns data\n | |-- ETH_Filter_Multicast:demonstrate filtering and multicast sending functions\n | |-- WebServer: Web Server routine, to demonstrate the configuration of WCHNET device functions through Web browser. As the WCHNET devices have built-in web server, the network parameter configuration and password management of WCHNET can be implemented on the web page. \n |-- EXTI: external interrupt line routine\n |-- FLASH: FLASH erase/read/write, and fast programming\n |-- FPU: FPU hardware floating point operation routine\n |-- FreeRTOS: FreeRTOS migration routine \n |-- FSMC \n | |-- LCD: FSMC routine to operate TFTLCD\n | |-- NANDFLASH: FSMC routine to operate NANDFLASH \n | |-- SRAM: FSMC routine to operate NOR_ SRAM \n |-- GPIO: GPIO routine\n |-- HarmonyOS:HarmonyOS migration routine \n |-- I2C\n | |-- I2C_7bit_Mode: 7-bit address mode, master/slave mode, transceiver routine\n | |-- I2C_10bit_Mode: 10 bit address mode, master/slave mode transceiver routine\n | |-- I2C_DMA: I2C DMA, master/slave mode transceiver routine\n | |-- I2C_EEPROM: I2C interface routine to operate EEPROM peripheral \n | |-- I2C_PEC: PEC error check, master/slave mode transceiver routine\n |-- I2S \n | |-- HostRx_SlaveTx: I2S master receiver slave transmitter routine\n | |-- I2S_DMA: I2S master transmitter slave receiver DMA routine\n | |-- I2S_Interupt: I2S master transmitter slave receiver interrupt routine\n |-- IAP: IAP upgrade routine, including the Hex to Bin tool and IAP upgrade tool \n | |-- USB+UART: USB+UART IAP routine \n |-- INT\n | |-- Interrupt_Nest: interrupt nested routine\n | |-- Interrupt_VTF: VTF IRQ interrupt routine \n |-- IWDG: independent watchdog routine\n |-- OPA: OPA4 as voltage follower output routine\n |-- PWR\n | |-- Sleep_Mode: low power, sleep mode routine\n | |-- Standby_Mode: low power, standby mode routine\n | |-- Stop_Mode: low power, stop mode routine\n | |-- Standby_RAM_LV_Mode: when LV is enabled in standby mode, RAM 2k and 30K low-power data holding routines\n | |-- Standby_RAM_Mode:when LV is not enabled in standby mode, RAM 2k and 30K low-power data holding routines\n |-- RCC\n | |-- Get_CLK:Get system-HCLK-AHB1-AHB2 clock routine \n | |-- MCO: MCO pin clock output routine\n | |-- HSI_PLL_Source:HSI or HSI/2 as PLL input clock routine \n |-- RNG: Random number generator routine \n |-- RTC: calendar routine\n |-- RT-Thread:RT thread migration routine \n |-- SDIO:SDIO routine to operate SD card\n |-- SPI\n | |-- 1Lines_half-duplex: single wire half duplex mode, master/slave mode, data transceiver\n | |-- 2Lines_FullDuplex: two-wire full duplex mode, master/slave mode, data transceiver\n | |-- FullDuplex_HardNSS: Hardware NSS mode, master/slave mode, data transceiver\n | |-- SPI_CRC: CRC error check and master/slave mode transceiver routine\n | |-- SPI_DMA: SPI uses DMA, master/slave mode transceiver routine\n | |-- SPI_FLASH: SPI interface operation flash peripheral routine\n |-- TencentOS: TencentOS migration routine \n |-- TIM\n | |-- Clock_Select: clock source selection routine\n | |-- ComplementaryOutput_DeadTime: complementary output and deadband insertion mode routines\n | |-- ExtTrigger_Start_Two_Timer: external trigger routines to start two timers synchronously\n | |-- Input_Capture: input capture routine\n | |-- One_Pulse: single pulse output routine\n | |-- Output_Compare_Mode: output comparison mode routine\n | |-- PWM_Output: PWM output routine\n | |-- Synchro_ExtTrigger:slave mode routine, including reset mode, gating mode and trigger mode\n | |-- Synchro_Timer:timer synchronization mode\n | |-- TIM_DMA: timer DMA routines\n |-- TOUCHKEY:touchkey detection routine\n |-- USART\n | |-- USART_DMA: USART DMA, master/slave mode transceiver routine\n | |-- USART_HalfDuplex: single wire half duplex mode, master/slave mode transceiver routine\n | |-- USART_HardwareFlowControl: hardware flow control mode, master/slave mode, transceiver routine\n | |-- USART_Interrupt: USART interrupt routine, master/slave mode transceiver routine\n | |-- USART_MultiProcessorCommunication: multiprocessor communication mode routine\n | |-- USART_Polling: polling transceiver mode, master/slave transceiver routine\n | |-- USART_Printf: USART Print debugging routine\n | |-- USART_SynchronousMode: synchronous mode, master/slave mode, transceiver routine\n |-- USB\n | |-- USBFS\n | | |-- DEVICE\n | | | |-- CH372:Simulates a custom USB device (CH372 device) with endpoints 1, 3 down and 2, 4 up. Data down from endpoint 1 is uploaded from endpoint 3 and not reversed, and data down from endpoint 2 is uploaded from endpoint 4 and reversed.\n | | | |-- Compatibility_HID:Simulates HID devices, with data transmitted up and down through the serial port.\n | | | |-- CompositeKM:Simulate keyboard and mouse, use IO to simulate keystrokes, while simulated data can be uploaded through serial port 2.\n | | | |-- MSC_U-Disk: Smulates a simple USB flash drive, optionally using on-chip Flash or external SPI-Flash\n | | | |-- MSC_CD-ROM: Simulate CDROM, need external SPI-Flash\n | | | |-- SimulateCDC:Simulate a CDC serial port and use serial port 2 to send and receive.\n | | | |-- SimulateCDC-HID:Simulate a CDC serial port, use serial port 2 to send and receive, HID interrupt endpoints to send and receive data to reverse and upload. \n | | |-- HOST_IAP\n | | | |-- APP: APP used with HOST_IAP, the project has modified the starting location of the program, after compilation, you need to convert the file into a bin file and rename it to APP.bin\n | | | |-- HOST_IAP: The host U disk IAP routine based on the U disk read file routine finishing, read the file with the name bit APP.bin from the U disk, write it to the internal flash, check it and jump automatically.\n | | |-- HOST_KM: The host operates the keypad, gets the data of the endpoints uploaded by the keypad and prints it, supports U-port under level 1 hub\n | | |-- HOST_MTP_FileSystem:Enumeration process of a USB host to a device that supports MTP and PTP protocols, supports MTP and PTP protocols, and reads its files\n | | |-- Host_Udisk:USB host operation USB disk routine \n | | |-- Udisk_Lib:U disk file system library file \n | |-- USBHS \n | |-- DEVICE\n | | |-- CH372:Simulates a custom USB device (CH372 device) with endpoints 1, 3 down and 2, 4 up. Data down from endpoint 1 is uploaded from endpoint 3 and not reversed, and data down from endpoint 2 is uploaded from endpoint 4 and reversed.\n | | |-- Compatibility_HID:Simulates HID devices, with data transmitted up and down through the serial port.\n | | |-- CompositeKM:Simulate keyboard and mouse, use IO to simulate keystrokes, while simulated data can be uploaded through serial port 2.\n | | |-- MSC_U-Disk: Smulates a simple USB flash drive, optionally using on-chip Flash or external SPI-Flash\n | | |-- MSC_CD-ROM: Simulate CDROM, need external SPI-Flash\n | | |--USB_ECM-NetWorkAdaptor: USB ECM routines\n | | |-- SimulateCDC:Simulate a CDC serial port and use serial port 2 to send and receive.\n | | |-- SimulateCDC-HID:Simulate a CDC serial port, use serial port 2 to send and receive, HID interrupt endpoints to send and receive data to reverse and upload. \n | |-- HOST_IAP\n | | |-- APP: APP used with HOST_IAP, the project has modified the starting location of the program, after compilation, you need to convert the file into a bin file and rename it to APP.bin\n | | |-- HOST_IAP: The host U disk IAP routine based on the U disk read file routine finishing, read the file with the name bit APP.bin from the U disk, write it to the internal flash, check it and jump automatically.\n | |-- HOST_KM: The host operates the keypad, gets the data of the endpoints uploaded by the keypad and prints it, supports U-port under level 1 hub\n | |-- HOST_MTP_FileSystem:Enumeration process of a USB host to a device that supports MTP and PTP protocols, supports MTP and PTP protocols, and reads its files\n | |-- Host_Udisk:USB host operation USB disk routine \n | |-- Udisk_Lib:U disk file system library file \n |-- VoiceRcgExam: individual term voice recognition routine \n |-- WWDG: window watchdog routine"}}, "embeetle": {"tiny-scarab-baremetal": {"chip": "ch32v003f4p6", "board": "tiny-scarab", "boardfamily": "beetle", "path": "wch/beetle/tiny-scarab-baremetal.7z", "icon": null, "info": "microcontroller: ch32v003f4p6\nboard: tiny-scarab\nmicrocontroller manufacturer: wch\nboard manufacturer: embeetle\nlink: https://embeetle.com/#supported-hardware/beetle-boards/boards/tiny-scarab\n\n\ninfo:\nThis is a minimalistic project for the CH32V003F4P6 microcontroller, with only three files:\n - main.c\n - registers.h\n - startup.S\n\nThe 'registers.h' file contains bitfield definitions for all registers in the chip. It is auto-\ngenerated from the svd file (see /config/ch32v00xxx.svd) with a python script (see\n/config/svd_parser.py)."}, "tiny-scarab-oled-128x32": {"chip": "ch32v003f4p6", "board": "tiny-scarab", "boardfamily": "beetle", "path": "wch/beetle/tiny-scarab-oled-128x32.7z", "icon": null, "info": "microcontroller: ch32v003f4p6\nboard: tiny-scarab\nmicrocontroller manufacturer: wch\nboard manufacturer: embeetle\nlink: https://embeetle.com/#supported-hardware/beetle-boards/boards/tiny-scarab\n\n\ninfo:\nAuthor: Aleksei Prokopov\nSource: https://github.com/roboter/Hardware/tree/main/WCH/ch32v003f4p6-evt-r0-1v1-i2c\nWebsite: https://begemotik.ee/blog/20231203-wch-ssd1306-oled-display/"}, "tiny-scarab-oled-128x64": {"chip": "ch32v003f4p6", "board": "tiny-scarab", "boardfamily": "beetle", "path": "wch/beetle/tiny-scarab-oled-128x64.7z", "icon": null, "info": "microcontroller: ch32v003f4p6\nboard: tiny-scarab\nmicrocontroller manufacturer: wch\nboard manufacturer: embeetle\nlink: https://embeetle.com/#supported-hardware/beetle-boards/boards/tiny-scarab\n\n\ninfo:\nAuthor: Aleksei Prokopov\nSource: https://github.com/roboter/Hardware/tree/main/WCH/ch32v003f4p6-evt-r0-1v1-i2c\nWebsite: https://begemotik.ee/blog/20231203-wch-ssd1306-oled-display/"}, "tiny-scarab": {"chip": "ch32v003f4p6", "board": "tiny-scarab", "boardfamily": "beetle", "path": "wch/beetle/tiny-scarab.7z", "icon": null, "info": "microcontroller: ch32v003f4p6\nboard: tiny-scarab\nmicrocontroller manufacturer: wch\nboard manufacturer: embeetle\nlink: https://embeetle.com/#supported-hardware/beetle-boards/boards/tiny-scarab\n\n\ninfo:\nThis project was originally a WCH Eclipse sample project which we've slightly\nmodified to fit the typical Embeetle project structure.\n\nThe original resources can be found on:\nhttp://www.wch-ic.com/products/CH32V003.html\n\nAfter unzipping this ZIP-folder:\n - The general source code is copied from: 'CH32V003EVT/EVT/EXAM/SRC/'.\n - The sample projects can be found in folders like: 'CH32V003EVT/EVT/EXAM/GPIO/GPIO_Toggle/User/'.\n - The linkerscript is found at: 'CH32V003EVT/EVT/EXAM/SRC/Ld/Link.ld'.\n\nSAMPLE PROJECTS\n---------------\n\nSamples\n |-- ADC\n | |-- ADC_DMA: ADC DMA sampling routines\n | |-- AnalogWatchdog: analog watchdog routine\n | |-- Auto_Injection: automatic injection mode routine\n | |-- Discontinuous_mode: discontinuous mode routine\n | |-- ExtLines_Trigger: external lines trigger ADC conversion routine\n |-- DMA\n | |-- DMA_MEM2MEM: Memory to memory mode routine\n | |-- DMA_MEM2PERIP: Memory to peripheral mode, and peripheral to memory mode routine, see peripheral sub-routines\n |-- EXTI\n | |-- EXTI0: external interrupt line routine\n |-- FLASH\n | |-- FLASH_Program: FLASH erase/read/write, and fast programming \n |-- GPIO \n | |-- GPIO_Toggle: GPIO routine \n |-- I2C\n | |-- I2C_7bit_Mode: 7-bit addressing mode, master/slave mode, transceiver routine\n | |-- I2C_10bit_Mode: 10-bit addressing mode, master/slave mode transceiver routine\n | |-- I2C_DMA: I2C DMA, master/slave mode transceiver routine\n | |-- I2C_EEPROM: I2C interface routine to operate EEPROM peripheral \n | |-- I2C_PEC: PEC error check, master/slave mode transceiver routine \n |-- IAP\n | |-- V00x_APP: APP go to IAP routine \n |-- IWDG\n | |-- IWDG: independent watchdog routine\n |-- OPA \n | |-- OPA: OPA as voltage follower output routine \n |-- PWR\n | |-- Sleep_Mode: low power, sleep mode routine\n | |-- Standby_Mode: low power, standby mode routine\n |-- RCC\n | |-- Get_CLK: Get system-HCLK-AHB1-AHB2 clock routine \n | |-- MCO: MCO pin clock output routine \n |-- SPI\n | |-- 1Lines_half-duplex: single wire half duplex mode, master/slave mode, data transceiver\n | |-- 2Lines_FullDuplex: two-wire full duplex mode, master/slave mode, data transceiver\n | |-- FullDuplex_HardNSS: Hardware NSS mode, master/slave mode, data transceiver\n | |-- SPI_CRC: CRC error check and master/slave mode transceiver routine\n | |-- SPI_DMA: SPI DMA, master/slave mode transceiver routine\n |-- SYSTICK\n | |-- SYSTICK_Interrupt: systick interrupt routine \n |-- TIM\n | |-- Clock_Select: clock source selection routine\n | |-- ComplementaryOutput_DeadTime: complementary output and deadband insertion mode routines\n | |-- ExtTrigger_Start_Two_Timer: external trigger routines to start two timers synchronously\n | |-- Input_Capture: input capture routine\n | |-- One_Pulse: single pulse output routine\n | |-- Output_Compare_Mode: output comparison mode routine\n | |-- PWM_Output: PWM output routine\n | |-- Synchro_ExtTrigger: slave mode routine, including reset mode, gating mode and trigger mode\n | |-- Synchro_Timer: timer synchronization mode\n | |-- TIM_DMA: timer DMA routines\n |-- USART\n | |-- USART_DMA: USART DMA, master/slave mode transceiver routine\n | |-- USART_HalfDuplex: single wire half duplex mode, master/slave mode transceiver routine\n | |-- USART_HardwareFlowControl: hardware flow control mode, master/slave mode, transceiver routine\n | |-- USART_Interrupt: USART interrupt routine, master/slave mode transceiver routine\n | |-- USART_MultiProcessorCommunication: multiprocessor communication mode routine\n | |-- USART_Polling: polling transceiver mode, master/slave transceiver routine\n | |-- USART_Printf: USART Print debugging routine\n | |-- USART_SynchronousMode: synchronous mode, master/slave mode, transceiver routine \n |-- USART-IAP: IAP Upgrade Routine - Built-in Hex to Bin Tool and IAP Upgrade Tool \n |-- WWDG: \n |-- WWDG: window watchdog routine"}}}