gerwg 0.1.0

Краткое описание пустой библиотеки

I checked the link you shared — it’s the Elbear Arduino IDE Board Support Package (BSP) project on Gitflic, which is a Board Support Package for MIK32 “Амур”-based boards intended for use in Arduino IDE (not PlatformIO) — specifically supporting boards like ELBEAR ACE-UNO, ELBEAR ACE-NANO, ELSOMIK, and START-MIK32. (gitflic.ru)

This is not already a PlatformIO package — it’s written to integrate with Arduino’s Boards Manager via a JSON index in Arduino IDE. (gitflic.ru)

---

Can You Use This BSP in PlatformIO?

Yes — but you must manually import/adapt it, because PlatformIO does not automatically consume Arduino IDE board support packages distributed in this form.

What This BSP Contains

From the README:

• Arduino core and variant files for MIK32 (Amur CPU)-based boards
• Arduino-style libraries adapted for these MCUs
• Board descriptions and behavior tailored for Arduino IDE
• Instructions and special API behavior for GPIO, ADC, PWM, interrupts, etc. (gitflic.ru)

How to Import It into PlatformIO

There are two practical ways:

---

Option A — Create a Custom PlatformIO Platform

This is the cleanest way:

1. Clone the BSP locally from the repository.

2. Create a custom PlatformIO platform folder.

   Example structure inside your project:

   myproject/ platformio.ini custom_elbear_bsp/ platform.json boards/ elbear_ace_uno.json start_mik32.json framework-arduino-mik32/ cores/ variants/ libraries/

   Essentially transplant the Arduino IDE BSP into PlatformIO’s structure.

3. Write platform.json to define your platform:

   { "name": "elbear_mik32", "title": "Elbear MIK32 Custom Platform", "version": "0.1.0", "frameworks": { "arduino": {} }, "packages": { "framework-arduino-mik32": { "type": "framework", "path": "framework-arduino-mik32" } } }

4. Convert each board definition into PlatformIO JSON files in boards/.

   Example minimal:

   { "build": { "core": "mik32", "mcu": "mik32", "f_cpu": "80000000L", "variant": "ace_uno" }, "frameworks": ["arduino"], "name": "ELBEAR ACE-UNO", "upload": { "protocol": "serial", "speed": 115200 } }

5. Use it in your platformio.ini:

   [env:elbear_ace_uno] platform = ./custom_elbear_bsp board = elbear_ace_uno framework = arduino

6. Make sure to port any Arduino IDE build flags in the BSP’s platform.txt into PlatformIO’s build_flags.

---

Option B — Extend an Existing Platform

If the architecture of the MIK32 CPU is supported by an existing PlatformIO platform (e.g., if it’s GCC-ARM or another supported toolchain), you could:

1. Pick the closest existing PlatformIO platform (for example, ststm32 or atmelavr, but only if binary toolchain is compatible).

2. Add the core/variant files from the BSP manually via:

   • build_flags
   • board_build.core
   • board_build.variant
   • Custom include paths (-I)

3. Create a custom board JSON in $HOME/.platformio/boards/ defining MCU, frequency, etc.

This is usually more fragile and only recommended if you know the underlying toolchain works.

---

Practical Tips

• The BSP does not include a PlatformIO platform.json or board JSONs — you must add those yourself.
• Arduino IDE boards.txt and platform.txt contain build flags that must be translated to PlatformIO’s format (build_flags, upload.protocol, etc.).
• Upload protocol may need custom scripts if the BSP uses something non-standard.

---

Summary

• The Elbear BSP you linked is for Arduino IDE and supports specific MIK32 boards. (gitflic.ru)

• PlatformIO will not import it automatically — you must:

  1. Create a custom PlatformIO platform
  2. Or extend an existing platform by manually adding BSP files and board JSONs.

If you want, provide the specific board you’re targeting (e.g., ELBEAR ACE-UNO or START-MIK32) and I can help generate the necessary board JSON and platform.json boilerplate for PlatformIO.

Установка

pip install gerwg