-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Comparing changes
Open a pull request
base repository: micropython/micropython
base: master
head repository: micropython/micropython
compare: v1.26-release
- 7 commits
- 17 files changed
- 2 contributors
Commits on Sep 11, 2025
-
esp32: Update esp_tinyusb component to v1.7.6.
Reported to fix issues reported with serial corruption when interacting with MicroPython from macOS hosts. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 02b5d42 - Browse repository at this point
Copy the full SHA 02b5d42View commit details -
tools: Add an environment variable MICROPY_MAINTAINER_BUILD.
This allows us to have some things which are fatal errors in CI or nightly builds, but warnings in normal developer builds. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for ad22089 - Browse repository at this point
Copy the full SHA ad22089View commit details -
esp32: Add IDF Component Lockfiles to git repo.
This is recommended by Espressif, and it's the only way to ensure everyone builds the same set of component versions. The awkward part is that updating the ESP-IDF version will churn a line in each of these files (and possibly other changes). Adds a build-time check for lock file changes, which is either a warning or a hard error depending on the value of MICROPY_MAINTAINER_BUILD flag (introduced in previous commit). This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 1abbdba - Browse repository at this point
Copy the full SHA 1abbdbaView commit details -
shared/tinyusb: Fix hang from new tx_overwritabe_if_not_connected flag.
This flag is in the main branch of TinyUSB, included in Espressif since their v0.18.0~3 component release (but it's not actually in TinyUSB v0.18.0 release). Setting the flag is needed for the USB device not to block waiting for space in the FIFO if the host is disconnected. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 7512ad6 - Browse repository at this point
Copy the full SHA 7512ad6View commit details -
shared/tinyusb/mp_usbd_cdc: Rewrite USB CDC TX loop.
This is related to the previous commit (where due to the new config flag this loop could end up stuck indefinitely if the USB host was disconnected). The previous loop could maybe still get stuck if the low-level USB state and the high-level USB state got out of sync. (Not clearly possible, but hard to say definitely not possible.) To be "belts and braces" careful: - Always run mp_usbd_task() each time around the loop to progress the state. - Always evaluate the timeout if we fail to write anything to the FIFO. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 6940845 - Browse repository at this point
Copy the full SHA 6940845View commit details -
tools/mpremote: Don't apply Espressif DTR/RTS quirk to TinyUSB CDC dev.
The DTR quirk workaround from dea949e is needed for the Espressif Serial/JTAG device, but not for TinyUSB - in fact DTR must be set for TinyUSB to correctly determine if the serial port is open (and leads to issues with lost bytes otherwise). See discussion in PR #17999. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 0edead4 - Browse repository at this point
Copy the full SHA 0edead4View commit details -
Signed-off-by: Damien George <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 647c8b9 - Browse repository at this point
Copy the full SHA 647c8b9View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...v1.26-release