Hi guys.

with this guide you can update your Renesas/NEC USB 3.0 uPD720200AF1/uPD720200A Firmware.

====

Needed Softwares:

-AIDA 64 ( For finding your USB 3.0 hardware address ) Download: http://download.aida64.com/aida64extreme450.exe

-Renesas/NEC Firmware Flasher with latest Firmware version 4.0.2.1.0.3: Download from Here: http://och.boxup.ir/fileup/uploads/14029903551.rar

====

Finding your USB 3.0 hardware address:

-install AIDA64 and run it
-go to Devices then click on PCI Devices
-click on your NEC usb 3.0



Note: if you have two USB 3.0 controller you must find secondary USB 3.0 hardware address



OK in my motherboard Primary USB 3.0 controller hardware address is 3/0/0 and secondary is 4/0/0 ( this is maybe different in your motherboard )

====

Lets Flashing:

-download and extract Renesas/NEC Firmware Flasher
-in the free space windows page hold shift and press right click and click on Open coomand window here



-now in command windows type this commands to flashing your USB 3.0 Firmware:

w200fw35 /srom 0 /address 03-00-00 /write F402003.mem cfg.ini

Note: 03-00-00 is your hardware address you find in AIDA64 and you must translate your usb 3.0 hardware address. for example: if your usb 3.0 hardware address is 3/0/0 you must convert it to 03-00-00



-after writing coomand in CMD press enter too Flashing/Updateing your USB 3.0

Flashing in progres:



Flash completed:



After flashing restart your computer

And here Video Tuturial by me: http://och.boxup.ir/fileup/uploads/13786557971.rar

====

good luck

This link has a newer flasher in x86 and x64 flavours. But the cfg.ini is different and anyone should input their true ID of the controller.

I have 2 chipsets on the motherboard but they are uPD720200F1, one says version 4.0.0 while the other one I have shows version 6.0.0 for the firmware, any ideas?

I fixed the problem, didn't read properly. :)

Is this procedure the same for the new firmware released for uPD720201/uPD720202? It was posted on Station Drivers on April 28th, 2015. I tried the new firmware 2026 but it killed my device. When I flashed back to the 2024 firmware it was immediately fixed, yay.

Now I got to figure out why the new firmware did not take.

EDIT: OK, I figured it out. I had to remove the Microsoft installed driver, by simply uninstalling the device. When I scanned system to have it find the device again I just installed the latest Renesas-NEC provided driver. Then I tried the new firmware again and it worked perfectly this time. However, after inspecting the newer firmware it appears it was built just 5 months after the last one. So, its not really that much newer. But newer is newer.... lol, after that all I did is search for drivers and it found the new April 24th 2015 driver from Microsoft. So all is well again...

Zitat von SkOrPn im Beitrag #5

---

Is this procedure the same for the new firmware released for uPD720201/uPD720202? It was posted on Station Drivers on April 28th, 2015. I tried the new firmware 2026 but it killed my device. When I flashed back to the 2024 firmware it was immediately fixed, yay.

Now I got to figure out why the new firmware did not take.

EDIT: OK, I figured it out. I had to remove the Microsoft installed driver, by simply uninstalling the device. When I scanned system to have it find the device again I just installed the latest Renesas-NEC provided driver. Then I tried the new firmware again and it worked perfectly this time. However, after inspecting the newer firmware it appears it was built just 5 months after the last one. So, its not really that much newer. But newer is newer.... lol, after that all I did is search for drivers and it found the new April 24th 2015 driver from Microsoft. So all is well again...

---

Zitat von ErfanDL im Beitrag #1

---

Hi guys.

with this guide you can update your Renesas/NEC USB 3.0 uPD720200AF1/uPD720200A Firmware.

good luck

---

Hi

try flashing manually from CMD. don't use execupdater.

Zitat von ErfanDL im Beitrag #8

---

Hi

try flashing manually from CMD. don't use execupdater.

---

OK well, I think these PCIe Renesas uPD720201 cards can't be updated. I have now tried three different computers and two different Operating Systems. On all three machines and both OS's I get the exact same thing, it acts like it has updated and then tells me to restart. Even in the CMD prompt it still loads the GUI updated, even though the ExecUpdater file has been deleted or renamed, it just doesn't matter what so ever. However, the Device Manager still ALWAYS shows Firmware Version 2020. So that's it. No updating the firmware for me I guess.

The only thing I have not tried is the x86 version of the OS's. So maybe these only work on the on-board Motherboard Renesas chips? Hmm, I wonder if the uPD720200 firmware flashing files can somehow work on the newer chips? LOL

I give up.....

Well I have some news. ONLY the Intel firmware flasher works on my 720201 device. This is a positive sign and is very telling for several reasons.

201_Rear.zip works ---> https://downloadcenter.intel.com/downloa...irmware-Updates

1. This tells me that my device is OK and that it is definitely flashable.
2. It also tells me that I have to figure out why the Intel provided flasher works, but all the others do not.

Sadly, the Intel flasher flashes firmware 2020, which was already on the device, lol. But hey at least it successfully flashes it, so now I just have to figure out what settings, addresses etc it is using that the others are not.

-https://en.sharkoon.com/product/1688/09909#download

try the above from sharkoon.

Zitat von boombastik im Beitrag #12

---

-https://en.sharkoon.com/product/1688/09909#download

try the above from sharkoon.

---

Bus:0x03 Device:0x00 Function:0x00
This Device is uPD720201(Revision 3).
     FW Version : 2.0.1.8
     PCI Subsystem Vendor ID : 0xFFFF
     PCI Subsystem ID : 0xFFFF
 

But when I type this directly from the admin command prompt I get this:

C:\fw\2024\x64>w201fw20 /srom ?
Bus:0x03 Device:0x00 Function:0x00
This Device is uPD720201(Revision 3).
 W25XxxV series(Winbond), Product ID = 0x00EF3012
 

When I go into my device manager and look at the Hardware Ids, I get this info:

Renesas Electronics USB 3.0 Host Controller
Hardware ID:
PCI\VEN_1912&DEV_0014&SUBSYS_00000000&REV_03
PCI\VEN_1912&DEV_0014&SUBSYS_00000000
PCI\VEN_1912&DEV_0014&REV_03
PCI\VEN_1912&DEV_0014
PCI\VEN_1912&DEV_0014&CC_0C0330
PCI\VEN_1912&DEV_0014&CC_0C03
 
Device instance path:
PCI\VEN_1912&DEV_0014&SUBSYS_00000000&REV_03\4&17A365D1&0&00E2
 

Here is USB Viewer's output from Microsoft for Windows 10.



And here is AIDA64's output for the Renesas controller.




And the Madnex provided Renesas flashing program (which has been very successful by others) gives me this result:

Die Datei CFG.INI wurde erstellt.
 
Das Update wird gestartet...
 
[Target Device]Bus:0x03 Device:0x00 Function:0x00
This Device is uPD720201(Revision 3).
HW Revision error
 

Any more ideas anyone??? Please

@SkOrPn

Try this one that i modified a little for you:

Firmware flasher for uPD720201/uPD720202 with firmware K2024 and K2020090 included

You will have to try to flash the K2024.mem file with one of the 2 configuration file included (.ini), cfg201v3.ini (prefered, try this one first) or W201FWup.ini.

Always best to use the flasher in command prompt. Type W201FW21.exe /? for all the command. Don't use the .bat file, i didn't modified it for you. Use /srom ? to get some usefull info

Also, if it works, don't forget to use the /verify command after to be sure all is fine (i assume this command still exist in this flasher). You must use it in a format similar to this: "W201FW21.exe /srom 0 /verify K2024.mem cfg201v3.ini". Most people forget to add the cfg.ini file after the firmware file in the command and wonder why the verification fail.

Last advice, before flashing, don't forget to use the /dump backup.mem command to make a backup file in case anything go wrong.

As for the revision rules that i warned you about. I know for sure that they apply to uPD720200AF1/uPD720200A. But if a 2020 firmware is in your revision 3 chip, then it means the rules are different for uPD720201/uPD720202. Unless the 3 is implied and simply not written everywhere. (meaning K2024 is in fact K32024 by the old conventions).

Yeah, WOW, thanks for all the great information. I had to do a lot of reading from docs found at Renesas, and as far as I can tell the 201/202 chip got up to rev 6 before they finished it. I found much help days ago, for example here at this LINK. BUT, the site is VERY difficult for me since its in Russian, and when I post replies the websites software greatly damages my englishe structured writing and whole sections of what I was trying to say are just missing, so I simply gave up trying to find help from there. Even his Russian language Renesas flashing software I have to translate for every question it asks me. However that guy Madnex knows his stuff with making flashers, but it just isn't working for me for some reason. It keeps spitting out what I perceive to be incorrect data, such as my firmware being at 2018, when device manager clearly shows it at 2020. Also his flasher tells me my VEN ID is FFFF and Subsystem ID is FFFF. This simply can't be right when I already know the vendor ID is 1912. And no matter what I edit with Notepad++ it ALWAYS tells me "HW Revision Error" in the end, even when I am 100% sure I entered the correct information.

So thank you VERY much for this info. It is greatly appreciated. And yes I agree I ALWAYS prefer flashing from command prompt or even from DOS (freedos) for that matter. All the Station Drivers Renesas firmware files REFUSE to run from the CMD even when I launch them from an admin CMD prompt and I can't figure out why. Those ALWAYS launch the windows GUI flasher program, so those aren't really command prompt files I assume. I like the older flashers that could run from DOS such as W200FW20.exe.

Anyway, thanks again I will give this another go soon now that I am armed with more info. Even if the Rev of my chip is somehow newer, that doesn't really matter as they should still take the newer firmware so long the srom is the correct ones. Right? you would think anyway, lol.

Thanks again bud. I will let you know what I figure out. Oh, and I assume if I am successful with 2024, I can then try 2026 firmware, correct? Thanks