Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate all Miniware devices to use Bit-Bang I2C #1838

Merged
merged 7 commits into from
Nov 16, 2023
Merged

Migrate all Miniware devices to use Bit-Bang I2C #1838

merged 7 commits into from
Nov 16, 2023

Conversation

Ralim
Copy link
Owner

@Ralim Ralim commented Nov 15, 2023 •
edited
Loading

  • Please check if the PR fulfills these requirements
  • The changes have been tested locally
  • There are no breaking changes
  • What kind of change does this PR introduce?
    Miniware has gone against their word and used clone chips for the MHP30.

At this point it just cant be trusted; so migrating all their devices to use I2C Bit-Banging

  • What is the current behavior?
    Sometimes broken I2C things on miniware devices, or slow OLED updates.

  • What is the new behavior (if this is a feature change)?
    Fix ^

  • Other information:
    Should cause no regressions. I've tested this on:

* S60
* TS101
* TS100
* TS80P
* TS100 GD32 chip

@Ralim Ralim force-pushed the miniware-cant-be-trusted branch from 1c78da7 to 3f797d3 Compare November 15, 2023 10:07
@Ralim Ralim merged commit e3bad2a into dev Nov 16, 2023
30 checks passed
@Ralim Ralim deleted the miniware-cant-be-trusted branch November 16, 2023 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Ralim