Update custom name eeprom register #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changed the eeprom registers from 92:92 to 96:96 in order to get the device custom name
Owner
|
Unfortunately, it looks like both 92 and 96 are likely hacks; 92 was what worked for me on an MD-HX. It looks like there's a higher-level function we should be using instead: https://www.intra2net.com/en/developer/libftdi/documentation/ftdi_8c.html#aefc3d12f7421030c63ad77b9af1d4a83 Can you change it to use |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changed the eeprom registers from 92:92 to 96:96 in order to get the device custom name using the DMON-Quad device (MDA/MDB)