-
-
Notifications
You must be signed in to change notification settings - Fork 762
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
Thunderbolt issue #256
Comments
Thunderbolt is quite well secured by default. But you indicate that you changed some settings. Also, Windows 11 employs a few protection techniques when the computer is locked in addition to the ones you mention. On a freshly booted (not rebooted) and unlocked target system does the command below work and display some memory?
Also, if you run some custom firmware this may be causing issues. I don't think it should be an issue of it works thru PCIe ports tho. But you can also try (on a freshly booted system):
Please let me know how it goes, if you have any success or if you're still having issues. |
Hello, i have a leetdma but i have flashed the pcieSquirrel firmware . The thunderbolt adapter is a wikingoo egpu ( seen as TB4 Home in the thunderbolt app ) and the leetdma is shown as an ethernet adapter in the device tree ( just changed id in vivado before compiling ) On a fresh boot, after unlocking the session: ####################################################### pcileech.exe display -min 0x1000 -device fpga -v DEVICE: FPGA: ScreamerM2 PCIe gen2 x1 [300,25,500] [v4.12,0e00] [ASYNC,NORM] ####################################################### pcileech.exe display -min 0x1000 -device fpga://algo=1 -v DEVICE: FPGA: ScreamerM2 PCIe gen2 x1 [300,25,500] [v4.12,0e00] [ASYNC,TINY] |
It seems like communicating with the device works fine, but DMA is not working. Ensure Thunderbolt security mode is set to no security / legacy in BIOS settings. Also if you have some extra Thunderbolt controller software installed you may need to disable it here as well. On a freshly booted (and logged on unlocked state) try: |
Context: hp laptop with vt-d, vbs, kernel dma etc
I have successfully read dma through the pci, (a lot of unreadable pages which is normal with vt-d)
If I do the same thing with thunderbolt (no security at the thunderbolt level, my pci device is present once the session is open), If I read outside physical ranges, I get a blue screen or the pc freeze which is normal. But if i stay in the physical range 100% of the pages read fail and sometime the pc freez or get a bsod too .
It is normal ?
The text was updated successfully, but these errors were encountered: