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.

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

MCU dropdown should not affect dfu-programmer behavior #198

Open
1 of 3 tasks
skullydazed opened this issue May 15, 2020 · 2 comments
Open
1 of 3 tasks

MCU dropdown should not affect dfu-programmer behavior #198

skullydazed opened this issue May 15, 2020 · 2 comments

Comments

@skullydazed
Copy link
Member

When we're using dfu-programmer we know what kind of MCU is attached. The MCU dropdown should be ignored when building a dfu-programmer command, and we should always use the vid/pid detection to determine mcu.

Feature Request Type

  • Core functionality
  • Alteration (enhancement/optimization) of existing feature(s)
  • New behavior

Description

@nooges
Copy link
Member

nooges commented May 16, 2020

Some VID/PID pairs listed here: http://ww1.microchip.com/downloads/en/devicedoc/doc7618.pdf

@skullydazed
Copy link
Member Author

We had this functionality in the old qmk firmware flasher and the list of pid's that used is here: https://github.com/qmk/qmk_flasher/blob/master/src/MainWindow/app.js#L15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants