qmk chibios-confmigrate: Make -i and -r required

[fauxpark]

Description

This command stacktraces without both of these.

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[myst729]

Excuse me if this is an off-topic question here.

I usually use AVR chips, until recently I got one STM32F103 and tried with QMK. I was confused by these chconf.h, halconf.h, mcuconf.h files. From the QMK command line help, it says chibios-confmigrate is to Generates a migrated ChibiOS configuration file, as a result of comparing the input against a reference. Also -r for REFERENCE, -i for INPUT. And it's not furtherly explained on docs.qmk.fm. Since STM32 series is not an option of qmk new-keyboard command. I had to copy from another keyboard uses the same MCU, and start my own modification.

Luckily I got my chip up and run. But I still don't figure out, where do those files come from. Or, in other words, what is the standard firmware template for an STM32 series chip?