Feature request for support for Milk-V Boards

[herbkonik]

What kind of issue is this?

• Question.
  This issue tracker is not the place for questions. If you want to ask how to do something,
  or to understand why something isn't working the way you expect it to,
  use Community Forums or Premium Support

• PlatformIO IDE.
  All issues related to PlatformIO IDE should be reported to the
  PlatformIO IDE for VSCode repository

• Development Platform or Board.
  All issues (building, uploading, adding new boards, etc.) related to PlatformIO development platforms
  should be reported to appropriate repository related to your hardware
  https://github.com/topics/platformio-platform

• [ x] Feature Request.
  Start by telling us what problem you’re trying to solve. Often a solution
  already exists! Don’t send pull requests to implement new features without first getting our
  support. Sometimes we leave features out on purpose to keep the project small.

• PlatformIO Core.
  If you’ve found a bug, please provide an information below.

You can erase any parts of this template not applicable to your Issue.

---

Configuration

Operating system:

PlatformIO Version (platformio --version):

Description of problem

Steps to Reproduce

Actual Results

Expected Results

If problems with PlatformIO Build System:

The content of platformio.ini:

Insert here...

Source file to reproduce issue:

Insert here...

Additional info

[robertlipe]

Just to help others, a clarification might be in order. "Milk-V" is a company, not a product. This is like asking for support for "Adafruit" boards. Milk-V is dominantly built around RISC-V products, with some ARM cores added to help bring-up of RISC-V devices. As of this writing, my understanding is that they have approximately the following products:

Duo (CVITEK CV1800B) , Duo-256M(SG2002), Duo-S(SG2000), Duo: https://milkv.io/duo - the latter two SOCs have both ARM and RISC-V cores, so separating peripheral development and core development might be practical. These are low-cost DIP boards of physical size of approximately a Pico Pi or a (large) ESP32-S3 board like the 44-pin YD-ESP32-S3 variants of DevKitC or so. The SG parts have up to four independent CPU arches (Cortex-A53, C906, 8051, plus a TPU.) This family ranges from 64K-512K depending upon price. These are embedded parts that match sensibly to Platformio targets.

Pioneer (SG2042 - https://milkv.io/pioneer ) is a 64-core C920 workstation class system. C920 has some overlap with Platformio targets, but this is probably largely out of scope.

Mars and Mars-CM (base + compute module - https://milkv.io/mars and https://milkv.io/mars-cm) boards are built with JH-7110. They're approximately the size and power of a Pi 3b or so. They stand a good chance of being largely compatible with any support deceloped for StarFive VisionFive R2 and Pine64's Star64 or mabe OK7110 from https://www.forlinx.net/. This chip is pretty well supported by Linux upstream; see https://rvspace.org/en/project/JH7110_Upstream_Plan.

Meles (TH1520 https://milkv.io/meles) is likely quite similiar to boards like the Sipeed Lichee Pi4A and about the size (I/O, computationally, price, fit into market, etc.) of a Pi4 or maybe a Pi5. This board will be similar to a BeagleV-Ahead, a Sipeed Lichee Pi, or a couple of boards from Alibaba used for Android bring-up.

Some of these make sense for Platformio's embedded development (starting under $9, Duo would be a contender for a variety of embedded or sensor projects, even if they run a really chopped downLinux) and Meles and Mars teeter on that edge between FreeRTOS/Nuttx/Zephyr and a "normal" Linux distribution with real video and such. At 64 cores, Pioneer would be a lovely build system, but probably not much of a conventional Platformio build target.

I'm not involved with the company or the products. Any mistakes or omissions here are my own and are unintentional. I don't intend to maintain this entry as a PR listing for them. I'm just offering the clarification that Milk-V is a company, not a board or even a chip. I'm not lobbying for support. :-)