You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expand the instructions for building the repository's arduino-usbserial firmware to provide all information needed to ensure a successful build by anyone.
Describe the current behavior
I'm trying to build the arduino-usbserial firmware to include custom features. There are instructions for building the firmware:
It would be helpful if the specific version of LUFA verified to be compatible with the firmware code was specified.
Not directly related to the documentation request, but it would also be a good idea to set up a GitHub Actions workflow that builds the firmware on any change to the files, and periodically. This would validate the functionality of the intended build procedure, which might be broken by changes to the firmware or by external changes to the build dependencies.
The text was updated successfully, but these errors were encountered:
per1234
changed the title
need compile method or docker image for firmwares using lufa
Provide more comprehensive documentation for building arduino-usbserial firmware
Mar 8, 2025
Describe the request
Expand the instructions for building the repository's arduino-usbserial firmware to provide all information needed to ensure a successful build by anyone.
Describe the current behavior
I'm trying to build the arduino-usbserial firmware to include custom features. There are instructions for building the firmware:
https://github.com/arduino/ArduinoCore-avr/blob/master/firmwares/atmegaxxu2/arduino-usbserial/readme.txt
However, I find them to be somewhat vague and I have not had any success following them.
ArduinoCore-avr version
c8c514c
Additional context
It would be helpful if the specific version of LUFA verified to be compatible with the firmware code was specified.
Not directly related to the documentation request, but it would also be a good idea to set up a GitHub Actions workflow that builds the firmware on any change to the files, and periodically. This would validate the functionality of the intended build procedure, which might be broken by changes to the firmware or by external changes to the build dependencies.
Related
The text was updated successfully, but these errors were encountered: