-
Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
Thunderbolt 1 Into deep. Notes, Boardviews etc.
- Thread starter bigguygeo
- Start date
- Joined
- May 22, 2020
- Messages
- 148 (0.09/day)
- Location
- Ukraine
DROM MODDING:
offset 0x4C0 = CRC-8 checksum of UUID, next 8 bytes
Calculate here <=
offset 0x4C9 = CRC-32C starting from next byte (0x01), with length through one byte (0x6E) !!!!!
(Keep in mind, that Generated CheckSum Should be converted from big endian to little endian )
Calculate here <=
RESULT AFTER PATCHING:
Drom Patched BIN added
UPD2.
After Flashing DROM From ThunderLink NS 1101, thunderbolt controller refuses to identify the Ethernet, because of some port info hardcoded there
UPD3. New rom offsets
tst06_SomeNewOffsets+.bin
It's just for better understanding of code parts
offset 0x4C0 = CRC-8 checksum of UUID, next 8 bytes
Calculate here <=
offset 0x4C9 = CRC-32C starting from next byte (0x01), with length through one byte (0x6E) !!!!!
(Keep in mind, that Generated CheckSum Should be converted from big endian to little endian )
Calculate here <=
RESULT AFTER PATCHING:
Drom Patched BIN added
UPD2.
After Flashing DROM From ThunderLink NS 1101, thunderbolt controller refuses to identify the Ethernet, because of some port info hardcoded there
UPD3. New rom offsets
tst06_SomeNewOffsets+.bin
It's just for better understanding of code parts
Last edited:
- Joined
- May 22, 2020
- Messages
- 148 (0.09/day)
- Location
- Ukraine
Ethernet EEPROM Win capture - Aligned
Ethernet EEPROM Mac capture - Aligned
- Joined
- May 22, 2020
- Messages
- 148 (0.09/day)
- Location
- Ukraine
I WAS READY TO CLOSE THE PROJECT AS I HAVE ALREADY DAMAGED 4x THUNDERBOLT DONGLES, TRYING TO ANALYZE DATA AND OTHER STUFF, WAS GATHERING THE REPORT ABOUT LAST FINDINGS AND DECIDED TO GATHER ALL DATA AT ONE PACK, AND... IT WAS AMAZING, WHAT I HAVE FOUND THERE!
I am not a professional engineer, but a hobbyist, like to modify everything that goes to my hands. So the reason why I have no success with Apple design thunderbolt dongle, is because of the special sauce by Apple. It was right in front of the eyes, so I missed it too many times. The answer is on image:
UPD1:
END OF PROJECT STATEMENT (First step):
I have successfully modified dongle and make it working with Broadcom Wifi by Apple. Working on manual for project legacy
I am not a professional engineer, but a hobbyist, like to modify everything that goes to my hands. So the reason why I have no success with Apple design thunderbolt dongle, is because of the special sauce by Apple. It was right in front of the eyes, so I missed it too many times. The answer is on image:
UPD1:
END OF PROJECT STATEMENT (First step):
I have successfully modified dongle and make it working with Broadcom Wifi by Apple. Working on manual for project legacy
Attachments
-
TWIK.jpg
Last edited:
- Joined
- May 22, 2020
- Messages
- 148 (0.09/day)
- Location
- Ukraine
END OF PROJECT
This story is about some researches and discoveries of Thunderbolt technology is ending. So that is results:
1. The connection of Apple Thunderbolt to Ethernet Dongle to Apple Wifi card from iMac:
2. Theory of how dongle caddy should look like:
3. How the rough soldering look like:
4. How PCI Config space look like when this setup is connected:
5. How Modification appears at MacOs System Information:
6. The same, but at windows:
7. Adding the first test PCB Prototype Caddy for adapter, 2400 dpi quality:
8. Adding firmware with 5 versions of UUID with DROM patching (actually cosmetics, but whatever)
DSL2210+LPC1112_ROMS.ZIP
Thanks for your attention!
If someone is planing to design a caddy PCB, please contact me for teamwork!
The legacy goal: make a PCB in which you can easily insert DSL2210 PCB via Thunderbolt connector to it and solder an FPC cable to create a simple bridge. This board will be a good option to connect sound cards or other interesting stuff
Last edited:
