[REQUEST] DFRobot Beetle ESP32C3

[kbsriram]

Name of Board
DFRobot Beetle ESP32C3

Board Architecture (i.e: SAMD51, ESP32-S2, ESP32, ...)
ESP32C3

Hardware URL
https://www.dfrobot.com/product-2566.html

Pinout URL
https://dfimg.dfrobot.com/enshop/image/cache3/data/DFR0868/pin.jpg

Additional context
Just another board - I happen to have one, was interesting in running Wippersnapper on it.

[brentru]

@kbsriram It shows that had two commits that reference the issue, so I assume you're taking it on. Thanks! I do not have one handy but can work with you to get this into IO and WS.

Please let me know (@ me on this issue) if you are experiencing any issues during this process and I'll work it with you.

[tyeth]

Seen the discord messages. Just to reiterate here:
Looks good. For now to immediately see the board online I would try with the board name/id matching the qtpy c3, then your board will be allowed online.
Alternatively if you add a field to the board definition for "published": false,
then we can merge the definition without it showing up in the list (see xiao board definition). Urls for installer still work with unpublished boards, and board registration process will too].
We'll need to add a CI build target to Adafruit/ci-arduino#ci-wippersnapper [all_platforms.py] and the . generate and .skip files to example folders. It probably makes sense to not call the build target wippersnapper_dfrobot_blah... And remove the extra WipperSnapper prefix.

[tyeth]

@kbsriram I've ordered one, so I can help test/verify issues, should arrive Wednesday. I've added the dfrobot_beetle_esp32c3 build target to ci-arduino now, so we can execute the CI build when the pull request comes in.

There will need to be an additional entry here for the dfrobot_beetle_esp32c3 target:
https://github.com/adafruit/Adafruit_Wippersnapper_Arduino/blob/main/.github/workflows/build-clang-doxy.yml#L321

and then the a .generate and .test.skip file for the dfrobot_beetle_esp32c3 in the example sketch folders.

Once you submit the pull requests then we can push those extra files/changes to the PR branch (or you can make the changes yourself), along with getting the board definitions uploaded (but in an unpublished state).

[tyeth]

Just to note that although this board is merged to main it isn't yet part of a firmware release, due to use wanting to resolve the #define situation for boards sharing the same define.

A pull-request to resolve this (adding an extra board specific define) has been opened in the Continuous Integration tooling repo (adafruit/ci-arduino#217) and the firmware repo (adafruit/Adafruit_Wippersnapper_Arduino#784).
The plan is to discuss them this week, but there are significant tooling changes so expecting feedback and revisions.