Update dependencies rebased

[calamity10110]

CircuitPython Board Configuration System

This system allows board configurations to be defined using a single board_setting.toml file,
which is then automatically converted into the required C and Makefile configurations.

File Structure

• board_setting.toml - Main configuration file
• generate_board_config.py - Generator script
• test_board_config.py - Test script
• board_template.toml - Template with all available options

Usage

1. Create a board_setting.toml in your board directory following the template
2. Run the generator:

   python tools/generate_board_config.py ports/<port>/boards/<board_name>

3. The following files will be generated/updated:
   • mpconfigboard.h
   • mpconfigboard.mk
   • pins.c
   • board.c

GitHub Integration

The .github/workflows/board_builder.yml workflow will automatically:

• Detect changes to board_setting.toml files
• Generate the configuration files
• Build the firmware
• Run tests
• Upload artifacts

Testing

To test the configuration generator:

python tools/test_board_config.py

CXX coveragecpp.cpp
LINK build-coverage/micropython
   text    data     bss     dec     hex filename
1501735  319984  199040 2020759  1ed597 build-coverage/micropython

Adding a New Board

1. Copy board_template.toml to ports/<port>/boards/<new_board>/board_setting.toml
2. Fill in the configuration values
3. Run the generator script
4. Commit both the TOML and generated files

Best Practices

• Keep the TOML file well-commented
• Test configurations locally before committing
• Verify all pin definitions match the board schematic
• Update the configuration when making hardware changes

[dhalbert]

This is an interesting idea: a single config file that is a board definition.

However, there are many cases in current board definitions that are not covered in the board definitions or the script to generate the board definition. As an example, there are no provisions for pin aliases, special naming conventions, etc. For example, all GPIO pins are named GPIO<n> which is not always the case at all. Also, for example, board.I2C() is always included, even if there are no I2C pins.

The .mpy files in shared-module should not be there.

I don't think TOML is a good choice for a single board definition file. Using Python or some more powerful language that could do conditionals would make more sense.

It appears that this code was generated by AI, without good review.

We would not be able to accept this PR in its current form.

[dhalbert]

Closing for now.

[tannewt]

Note, the Zephyr port has more minimal TOML board definitions by relying mostly on zephyr's own board definitions. See https://github.com/adafruit/circuitpython/blob/main/ports/zephyr-cp/boards/nordic/nrf5340dk/circuitpython.toml as an example.