Customize USB-UART Interface with KRAKE name
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
_A clear and concise description of what the problem is. Ex.
I'm always frustrated when I cannot identify which device is mapped to which COM port.
It would be nice if the device identified with a serial number in the DeviceManager.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Learn to use the "The Windows system USB configuration tool for CH340/CH342/CH343/CH344/CH347/CH348/CH9101/CH9102/CH9103/CH9104 can configure parameters such as chip VID, PID, maximum current value, manufacturer and product information strings."
Link:
https://www.wch.cn/downloads/CH34xSerCfg_ZIP.html
! Caution, It may be possible to brick devices if programed incorrectly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files, tests, or entry points are identified. Start by confirming which USB-UART chip and device identity settings are used, then review the linked CH34xSerCfg tool and its cautions; done should mean a defined, safe way for the device to identify itself as KRAKE without risking incorrect programming.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100