-
Notifications
You must be signed in to change notification settings - Fork 7
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
Ax88772a not work #1
Comments
On my chip the VID/PID appeared multiple times and all instances had to be changed. Can you find any remaining copies of the PID bytes in the image? |
It appeared on my chip twice |
I checked mine and had two instances as well at 0x48 and 0x88, after modifying them and reconnecting the VID/PID changed accordingly. Maybe there's a bit that controls whether the EEPROM based VID/PID is used and it's disabled on yours but that's just a guess. I'll keep this open for comments. The EEPROM dump from my B chip for comparison:
|
hi this is my code,i modify it from 772A to 7720 Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000000 5A 15 71 ED 12 20 27 29 0E 00 00 AA 72 A4 04 09 Z.qí. ')...ªr¤.. 00000010 22 60 12 71 0E 19 04 3D 04 3D 04 3D 04 3D 05 9C "`.q...=.=.=.=.œ 00000020 06 00 E0 10 24 54 12 40 27 49 FF FF 00 00 FF FF ..à.$T.@'Iÿÿ..ÿÿ 00000030 FF FF 03 0E 00 30 00 30 00 30 00 30 00 30 00 32 ÿÿ...0.0.0.0.0.2 00000040 01 12 02 00 FF FF 40 00 0B 95 77 20 00 01 02 01 ....ÿÿ@..•w .... 00000050 01 03 02 09 00 27 01 01 E0 04 09 7D 00 04 03 00 .....'..à..}.... 00000060 FF FF 07 00 05 07 03 81 00 08 07 0B 82 05 00 02 ÿÿ..........‚... 00000070 00 02 05 07 02 03 02 00 FF 00 03 04 00 30 FF FF ........ÿ....0ÿÿ 00000080 01 12 02 00 FF FF 08 00 0B 95 77 20 00 01 02 01 ....ÿÿ...•w .... 00000090 01 03 02 09 00 27 01 01 E0 04 09 7D 00 04 03 00 .....'..à..}.... 000000A0 FF FF 07 00 05 07 03 81 00 08 07 A0 82 05 40 02 ÿÿ......... ‚.@. 000000B0 00 00 05 07 02 03 00 40 DD 00 FF FF AA AA BB BB .......@Ý.ÿÿªª»» 000000C0 03 22 00 41 00 53 00 49 00 58 00 20 00 45 00 6C .".A.S.I.X. .E.l 000000D0 00 65 00 63 00 2E 00 20 00 43 00 6F 00 72 00 70 .e.c... .C.o.r.p 000000E0 00 2E 03 12 00 41 00 58 00 38 00 38 00 78 00 37 .....A.X.8.8.x.7 000000F0 00 32 00 41 FF FF FF FF FF FF FF FF FF FF FF FF .2.Aÿÿÿÿÿÿÿÿÿÿÿÿ Generated by HxD ` |
Hi, Someone tested this with an AX88772A last month and it worked for them: https://mastodon.online/@gcc_addict/104683023150830769 Could you read the eeprom from your device and double-check that your modifications were written properly and it's still coming up with the old VID/PID regardless? |
If anyone is still having this issue leave a comment and I'll reopen. Closing for now. |
i'm unable to modify the pid on a sabrent usb adapter from 772b to 7720. 0b95:772b shows up twice in my dump, but modifying both or 1 or the other has no effect. 0b95:802b also shows up and i once saw the adapter identified with this vid:pid (after writing new eeprom), but only that single time and never since. i have re-read the eeprom from the adapter so i know my changes were committed. any ideas why this isn't working? do you think i could flash a donor eeprom from a different ax88772b adapter? `Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000000 00 15 1D F8 12 20 35 29 00 00 00 00 B5 51 04 09 ...ø. 5)....µQ.. |
Thanks for confirming that this isn't an eeprom write problem. I tried looking into it but couldn't find anything conclusive. Some ASIX chips have this feature but it's not specifically mentioned for the AX88772A so it could be the cause but it could also be something in the eeprom disabling the use of the ID, no clue. No idea what the A chip would do with the B chip's eeprom contents either, unfortunately. Try at your own risk. I've reopened this, hopefully someone who managed to mod the A chip can chime in at some point. |
sorry for the confusion--my adapter is a ax88772B, not A. since your readme.md indicated you tested with a 2B i was hoping you might have some additional insight. incidentally, i also tried this with an ax881720 adapter and the pid change worked, but the device didn't completely function with the ax887720 drivers. |
Oh, I see the B in the dump now. I guess that means this isn't specific to the A chips. I just flashed it to my device to test. Strange. But even with your eeprom contents if I change the appropriate bytes my vid/pid changes: Bus 001 Device 046: ID 0b95:77aa ASIX Electronics Corp. So I think my theory above about permanent eFuse VID/PID configuration on some adapters is unfortunately correct and whether changing eeprom content does anything for VID/PID/MAC will depend on how the manufacturer decided to configure the device. |
Exchanged some emails and it was confirmed that even with my eeprom contents the chip's VID/PID could not be changed so there are definitely chips with permanently set VID/PID that ignore eeprom contents. Info added to repo readme. |
I test ax88772a Modify pid from 772a to 7720 Not working
Eeprom size 256
The eeprom Has been modified
There is no change in the device id in the device manager
The text was updated successfully, but these errors were encountered: