Xps 15 9570 Thunderbolt 3 Firmware Update

Xps 15 9570 Thunderbolt 3 Firmware Update


Xps 15 9570 Thunderbolt 3 Firmware Update

(@tompouce)

Active Member

Joined: 4 years ago

Howdy there,

I just acquired a new XPS 13 (9370) with 2 thunderbolt 3 ports pcie x4 and OPI GT4. I was eager to exam my External GPU (Mantiz venus
+
GTX 1050 Ti
+ SSD 250) enclosure through Thunderbolt iii. Merely to obtain the full speed of this enclosure connected to the thunderbolt iii I needed to have the last version of the TB3 Firmware  installed (version 25).

I started by updating all my drivers and bios by connecting on dell support with my service tag. After installing all this i installed the thunderbolt 3 controller commuter (Intel-Thunderbolt-Controller-Driver_39G55_WIN_17.1.64.250_A04.EXE)from dell support. Then I tried to update the Thunderbolt 3 firmware from dell support (Intel_TBT3_FW_UPDATE_NVM28_3H3DP_A01_4.28.06.001.exe). Unfortunatly I obtain this error :



Therefore I reinstalled the dell Thunderbolt controller driver and retried to update the firmware. Only I obtained the same mistake.

When I check the current driver and firmware version of the thunderbolt 3 program i obtain the post-obit.



And if I try to connect my egpu enclosure I got an fault seing that my external device may non piece of work correctly.



And indeed when I launch a test of the Egpu, I only obtain half of the expected bandwidth in wrinting speed.



Here is a mail of a similar configuration (XPS 9370 +
akitio node
+
1070) showing what i should obtain in term of performance.


eGPU Community



Does anyone accept a hint for my problem on the update of the TB3 firmware?

Thank you past advance for your help.

Best Regards.


To do
:

Create my signature

with
system
and expected
eGPU configuration
information to
give context
to my posts. I have
no
builds
.

.




tanantish

(@tanantish)

Active Member

Joined: iv years agone





FJFG84

(@fjfg84)

Active Member

Joined: 4 years ago

I had exactly the same issue on a DELL Latitude 7285… Even worse, my NVM version is 16… I’ve tried everything with no luck, always is the same equally you post:



My eGPU enclosure is
MANTIZ Venus, purchased after January 2018, so it comes with the updated firmware. Glad i works and only fails when starting a game, that it works for a few seconds and the crash… but for piece of work information technology works fine, even my
CUDA-Z
shows full speed:



Perchance ane day DELL update their Thunderbolt drivers on the support web, then we have a correspondent drivers and firmware utility.




karatekid430

(@karatekid430)

Estimable Member

Joined: v years ago

If anybody is interested, I merely updated my Dell 9370 NVM with the Dell 9575 NVM and zippo exploded or bricked.
It went from NVM28->NVM30 and External GPUs Supported: No->Yes
Non that the External GPUs Supported flag ever seems to matter. My eGPU worked with Dell 9365 with NVM09 and “No”.


2018 04 24


2018 04 24 (1)

Flash at your ain risk, use common sense and remember that if y’all flash an incompatible firmware, it could brick the Thunderbolt controller.

I was brave plenty to try with mine because I had done the same in the past when I had the Dell 9365, and it successfully accepted firmwares from any Dell laptop with the same Thunderbolt controller model.

You lot will need Linux with a recent kernel. 4.thirteen or 4.14 is the minimum, but ideally simply install 4.sixteen.2 for now.

If no Thunderbolt devices are fastened, you will demand to wake the controller:
repeat one | sudo tee /sys/bus/wmi/devices/86CCFD48-205E-4A77-9C48-2021CBEDE341/force_power

Read:  Lg Aristo 2 Lmx210ma Flash International Firmware

Then observe out current NVM version:
true cat /sys/coach/thunderbolt/devices/0-0/nvm_version

If 23, then we should back upwards – the 23 comes from manufactory, but but 28 is available for download. We volition need to support should we ever wish to revert. To back up, practice:

sudo dd if=/sys/bus/thunderbolt/devices/0-0/nvm_active0/nvmem of=/path/to/backup/destination/file

Now we demand to download the exe file from here:
http://world wide web.dell.com/support/abode/us/en/19/drivers/driversdetails?driverId=TRC47
– or but exercise:

cd ~/Downloads
mkdir harambe && cd harambe
wget
https://downloads.dell.com/FOLDER04765332M/1/Intel_TBT3_FW_UPDATE_NVM30_TRC47_4.30.02.002.exe

7z e *

Which should produce 0x080D_secure.bin within a subdirectory. Y’all can verify it uses the same Thunderbolt controller as the Dell 9370 by:

hexdump -s19472 -n4 0x080D_secure.bin

Now to flash:

sudo dd if=0x080D_secure.bin
of=/sys/jitney/thunderbolt/devices/0-0/nvm_non_active0/nvmem
echo 1 | sudo tee /sys/coach/thunderbolt/devices/0-0/nvm_authenticate

If no Thunderbolt devices attached, wake it once again:

echo i | sudo tee /sys/autobus/wmi/devices/86CCFD48-205E-4A77-9C48-2021CBEDE341/force_power

Verify new NVM:

cat /sys/bus/thunderbolt/devices/0-0/nvm_version


To do
:

Create my signature

with
organisation
and expected
eGPU configuration
information to
give context
to my posts. I have
no
builds
.

.




karatekid430

(@karatekid430)

Estimable Member

Joined: 5 years ago

You guys didn’t know that Windows NVM flashing simply seems to work for 16.2 Thunderbolt driver or like? It has been an issue for a long time.

It is more of an upshot for flashing peripherals, only it could be an result for flashing host firmware, particularly when using the Intel tool.

You tin try using the Dell tool – download a firmware NVM exe, extract the exe using 7z and detect packed inside the fwupdatetool.exe. Ignore the bin file that comes with the Dell annal unless it is actually the one you want.

The command is:

fwupdatetool.exe /up1 /path/to/nvm.bin

Or without the frontwards-slash in front end of up1? Cannot remember. It’s been a while.
Can add /f to downgrade or wink incompatible firmware – but only do and so at your ain risk and only if you are sure the file is compatible.
If you lot don’t take a Thunderbolt device and then you will need to discover a way to force the Thunderbolt controller power. On Linux that is petty regardless of vendor. On Windows, it depends on vendor. The unextracted Dell NVM exe files force the power, just just on Dell systems, afaik.


To do
:

Create my signature

with
organisation
and expected
eGPU configuration
information to
give context
to my posts. I have
no
builds
.

.




Xps 15 9570 Thunderbolt 3 Firmware Update

(@tompouce)

Active Member

Joined: 4 years ago

Hi karatekid430,
But saw your respond on my subject.
So do you call back that under windows by unzipping the NVM thirty and using the cmd
FwUpdateCmd.exe Up1 /f firmware_file.bin
I could patch my firmware from NVM 23 to NVM 30 if I take 16.two or 16.3 trhunderbolt commuter installed without risks?

Thank in advance


To do
:

Create my signature

with
system
and expected
eGPU configuration
data to
requite context
to my posts. I have
no
builds
.

.




Xps 15 9570 Thunderbolt 3 Firmware Update

(@tompouce)

Active Fellow member

Joined: 4 years ago

Posted past: karatekid430

You guys didn’t know that Windows NVM flashing only seems to work for 16.2 Thunderbolt driver or similar? It has been an effect for a long time.

It is more of an issue for flashing peripherals, merely it could be an upshot for flashing host firmware, especially when using the Intel tool.

Yous can endeavour using the Dell tool – download a firmware NVM exe, extract the exe using 7z and detect packed within the fwupdatetool.exe. Ignore the bin file that comes with the Dell archive unless it is actually the one you want.

The command is:

fwupdatetool.exe /up1 /path/to/nvm.bin

Or without the forward-slash in front of up1? Cannot remember. It’s been a while.
Tin can add /f to downgrade or flash incompatible firmware – but simply do so at your own gamble and only if you are sure the file is compatible.
If you don’t have a Thunderbolt device so you will need to discover a way to force the Thunderbolt controller power. On Linux that is trivial regardless of vendor. On Windows, it depends on vendor. The unextracted Dell NVM exe files force the power, but only on Dell systems, afaik.

By using the command y’all suggested on windows 10 with xvi.2 thunderbolt driver, I was able to update the controler firmware to version 28 with the XPS 9370 file from dell back up. And then I was able to update to version xxx by using the XPS 9575 file from dell support. Everything works fine and i now also have the egpu enabled support option enabled now on the thunderbolt properties.

Read:  Ipod Classic Firmware File Could Not Be Found

However I accept something weird that happened : On my thunderbolt properties windows i at present take two controlers that announced! One with version 23 and the other i with version xxx.
Is it normal?




To do
:

Create my signature

with
organisation
and expected
eGPU configuration
information to
give context
to my posts. I have
no
builds
.

.




karatekid430

(@karatekid430)

Estimable Fellow member

Joined: five years ago

Distressing, the forum does not notify me properly when there are replies. Information technology was simply a coincidence I happened to stumble across this thread again.

Yes, that is normal. Those details are only cached (tin can find / alter in regedit). Sometimes the NVM updates modify the PCI Subsystem ID of the controller, and hence it is registered as a new controller.

Tin clear listing by uninstalling and reinstalling Thunderbolt commuter. Use latest 17.4.77.400 WHQL Thunderbolt commuter (I use necacom.net).

I might not have mentioned on this thread how easily Linux manages firmware. Information technology does not do any checks, though, so make sure you feed it the right file for the exact model from the manufacturer, or else it could brick (for case, flashing a peripheral firmware to a host controller, despite them beingness the aforementioned silicon). It should be completely safe, if and simply if you provide the correct file. Linux can also backup the current firmware (although needs 8192 or 16384 bytes of /dev/naught prepended to reflash, headers not included when extracted).

https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/thunderbolt.rst

Best wishes!


To practice
:

Create my signature

with
system
and expected
eGPU configuration
information to
give context
to my posts. I accept
no
builds
.

.




Xps 15 9570 Thunderbolt 3 Firmware Update

(@tompouce)

Active Member

Joined: four years agone




Wzza

(@wzza)

Active Member

Joined: 2 years ago

If 23, then we should back up – the 23 comes from mill, but only 28 is available for download. We will demand to back up should we ever wish to revert. To back upward, do:

sudo dd if=/sys/motorbus/thunderbolt/devices/0-0/nvm_active0/nvmem of=/path/to/fill-in/destination/file

Howdy,

Would you lot be then kind as to explain how one can wink a firmware backup that was fabricated post-obit your instructions? I understand the raw dump cannot exist reflashed as is. Yet, I did not quite get this comment from your most recent post:

(although needs 8192 or 16384 bytes of /dev/zero prepended to reflash, headers non included when extracted)

Does that mean adding 8192 or 16384 bytes of zeros to the kickoff of the dump with dd? My dump is already larger than firmware binaries. What command would I have to use to and then reflash? Thanks!

I have a Dell Latitude 7380 and was running into the same issue regarding the TB firmware upgrade. Could non get the Dell update tool to work at all and couldn’t find whatever firmware file in
its annal
(NVM40). Turns out the resource files are sent to the ‘User\AppData\Local\Temp\Dell’ directory. I was and so able to flash i of the provided bin files with FwUpdateTool. What’s odd is that the only firmware (079F) I was able to wink corresponds to the Latitude 7280 TB controller…  Would it make sense to try and force wink the firmware intended (07F3) for my model (Latitude 7380)? How tin I brand sure that the 2 models share the same controller?

The main reason I would similar to revert to the original firmware I backed up (NVM23) is to check how it registers. Although I did hex the backed binary and saw mention of ‘7280’… How is that possible? What difference could in that location be between the two firmwares, given that the two models do share the same TB controller, other than registering information technology to a given model?

Any help or insight on this would be profoundly appreciated 😉

EDIT

So I made some progress:

one) Adding the header to my firmware dump, I institute that it corresponds exactly to the 079F NVM23 firmware (Latitude 7280,
not
my model).

ii) I hex compared the firmwares from the two models (079F and 07F3) and, apart from a string specifying the laptop model, they are exactly the aforementioned for NVM23 and NVM33. Looking at the nigh recent NVM40, there is more than difference which I could not interpret.

three) Regardless of the subid (079F and 07F3), I was unable to downgrade the NVM below NVM40. I tried both the windows (‘Mistake: 0x1 AUTHENTICATION_FAILED_RESPONSE_CODE’) and linux (‘invalid statement’) methods and both fail subsequently the firmware is sent to the controller. Information technology seems the device itself refuses to authenticate a lower NVM version binary… Does that brand sense? Is there a workaround?

iv) I was able to flash the 07F3 NVM40 firmware successfully through FwUpdateTool. So now the TB3 controller displays the proper model (Latitude 7380).

Was all of this useless? Probably
Smile

This mail service was modified ii years ago



Xps 15 9570 Thunderbolt 3 Firmware Update

Check Also

How to Update Firmware on a Samsung Hd204ui

How to Update Firmware on a Samsung Hd204ui

How to Update Firmware on a Samsung Hd204ui #i What the heck…I just got a …