Maximilian Gerhardt

We're working on it in https://github.com/Community-PIO-CH32V/platform-ch32v.

I haven't reached out about this to anyone at least.

If https://github.com/volumit/package_940 doesn't infringe on any copyrights from HighTec or another company, I would deem it usable. I don't however know how well "chip is used in professional, safety-critical automotive...

At least I have not further worked on this due to lack of time and other projects. The repos are completely open for forking + development though.

No the VSCode extension stays constant. It's all handled dynamically by pointing PlatformIO to use a new platform url. Easiest is to just download https://github.com/Community-BL-IOT/pio-bl602-boufallo-arduino-test and open it in VSCode.

Pushing this again, for the raspberrypi Platform, the RP2040.svd file throws an error when loading too: See https://github.com/earlephilhower/arduino-pico/discussions/1579#discussioncomment-6642452 and [rp2040.svd](https://github.com/maxgerhardt/platform-raspberrypi/blob/develop/misc/svd/rp2040.svd).

Might just be some error caused by a weird / older package state. Since you've got platform + framework in github repos already, I think you should be able to...

Also: Your changes can be automatically verified to be compiling successfully on all architectures if you add an environment for your board in one of the examples, e.g., to `examples/arduino-blink/platformio.ini`...

Can you go in your repo's https://github.com/patrickwasp/platform-atmelsam/actions and click activate? You should get compile feedback then (because CI will only run here after someone approves it)

It should automatically triger in each commit (after it's been enabled), so the next commit will trigger it. Something that'll come up in review is also that last empty line...