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

Figure out USB VID and PID for non-GHI devices #27

Closed
Arke64 opened this Issue Aug 29, 2017 · 2 comments

Comments

Projects
None yet
1 participant
@Arke64
Member

Arke64 commented Aug 29, 2017

No description provided.

@Arke64 Arke64 added this to the v0.7.0 milestone Aug 29, 2017

@Arke64 Arke64 self-assigned this Aug 29, 2017

@Arke64

This comment has been minimized.

Show comment
Hide comment
@Arke64

Arke64 Sep 8, 2017

Member

Will likely use our VID but all 3rd party devices will use the same PID with name "TinyCLR Device". Of course, forks and clones can do whatever they want. This is just for the official port repo.

Member

Arke64 commented Sep 8, 2017

Will likely use our VID but all 3rd party devices will use the same PID with name "TinyCLR Device". Of course, forks and clones can do whatever they want. This is just for the official port repo.

@Arke64

This comment has been minimized.

Show comment
Hide comment
@Arke64

Arke64 Sep 27, 2017

Member

Done. 0x5000 under our PID is available general use for the TinyCLR USB debugger interface on non-GHI devices. 3rd parties remain free to use their own VID and PID if they have one.

Member

Arke64 commented Sep 27, 2017

Done. 0x5000 under our PID is available general use for the TinyCLR USB debugger interface on non-GHI devices. 3rd parties remain free to use their own VID and PID if they have one.

@Arke64 Arke64 closed this Sep 27, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment