That is my card, its from a company called SEDNA and it has a built in bridge layout for eSATA. However, I am 100% sure that eSATA thing is just a trace through and has absolutely NOTHING to do with the uPD720201 chip. However, that chip does have a two port hub thing on the back of the card so that you can route a cable to the front of a chasis. Is that the Root HUB? Or is the ROOT HUB part of the chip itself?

I am not an expert in that but i think the chip control the USB hub. The rest (the SATA part) just pass through to the PCI-e.

Edit: i just looked at my own system with Hardware identify and i saw a LOT of SUBSYS 00000000 from other devices that i never modified so it may be as simple as because your chip is on an external card and not on the motherboard itself, it doesn't have a SUBSYS number and never will. That would also explain why the flasher is not able to change it.

Yeah agreed, I looked it up and SUBSYS 00000000 is perfectly normal for this chipset brand it appears, so no worries about that.

https://plugable.com/drivers/renesas/

and

https://www.driveridentifier.com//scan/d...DEV_0014&REV_03

EDIT: However, it does look like my chip was probably flashed with a mem that was originally meant for a Intel board, since the numbers keep coming up under Intel based motherboards. Weird...

Zitat von Phoenix48 im Beitrag #30

---

So your system is really reporting the SUBSYS as 00000000 and the SID as FFFFFFFF.

Now i wonder why the flasher don't change those when you use the cfg.ini file...

---

Your download link is not working because you didn't chose the "link with key" in mega.nz.

Zitat von Phoenix48 im Beitrag #35

---

Your download link is not working because you didn't chose the "link with key" in mega.nz.

---

I took a look at it.

Is this the backup.mem of your chip when you had only one firmware version reported or when you had two reported?

Zitat von Phoenix48 im Beitrag #37

---

I took a look at it.

Is this the backup.mem of your chip when you had only one firmware version reported or when you had two reported?

---

I just realized that I could be wrong on what version number was installed. It could have been 2018 by default. I just never seen 2018 in the device manager and now its been too much time to remember how events unfolded.

I do remember seeing 2020, and the russian software reporting 2018, which is one of the reasons that led me to win raid again. It "might" have been 2018, but the russian software ALWAYS reports 2018, even today I am sure it would report 2018. Lol

Actually your guess is as good as mine. I assume what you see is weirder than you thought it would be??? haha, thats funny...


EDIT: I just looked at the K2020090.mem from Intels site and it looks perfectly normal. Now I think that even though they say it would not flash if it was the wrong mem file, I think the W201FW21.exe file did in fact flash 2020 over top, or behind the 2018 firmware. Maybe this card came with 2018 and I just never seen it, although that feels unlikely to me. But it would explain the double firmwares. I bet the Intel board has a different srom chip with a much smaller size and thus the flasher just decided to put 2020 behind the 2018 firmware? Is that even possible?

I bet editing the 2026.mem file with lots of FF's for extra space would work just fine though. Why wouldnt it?

This is what the Russian software reported below (upper left corner it says 2018, but device manager below it says 2020), it's just a RUN.cmd that uses flasher W201FW20.exe and the mem files from Station Drivers (I assume). This software asks you question, and you answer them. It always ended with "HW Revision error" because, I assume, W201FW20 doesn't work with Revision 3 chips. https://www.computerbase.de/forum/showth...21#post21008021 (as you can see my English is broken at this website, because their software doesnt fully understand me so it has ommited lots of my words, so that's why some sentences dont make any sense)

The K2020090.mem and K2026.mem as well as K2024 seems fine because they all have the same structure. What does not seems fine is the double firmware in your backup.mem. After seeing all those, i don't think anymore that editing a file would do. The only editing that can be done is, maybe, extract the 2018 firmware that seems to be still intact in your backup file. But that would not help to update your chip.

The only thing that can be done at this point to ensure a clean flash with only one firmware on the chip is this: Do the /erase command, that will put FF everywhere in your chip. Then flash the update you wish. This will ensure that only one version is on the chip.

Zitat von Phoenix48 im Beitrag #40

---

The K2020090.mem and K2026.mem as well as K2024 seems fine because they all have the same structure. What does not seems fine is the double firmware in your backup.mem. After seeing all those, i don't think anymore that editing a file would do. The only editing that can be done is, maybe, extract the 2018 firmware that seems to be still intact in your backup file. But that would not help to update your chip.

The only thing that can be done at this point to ensure a clean flash with only one firmware on the chip is this: Do the /erase command, that will put FF everywhere in your chip. Then flash the update you wish. This will ensure that only one version is on the chip.

---

It seems that, contrary to the older flashers for 200/200A. The 201/202 flasher don't requires a specific size and just put the file there. Which means that /erase may sometimes be required. It is basically the same thing but different. Meaning in the old version it was the files that was putting FF everywhere that was needed. Now it seems the /erase has to do it (It is nothing more than putting FF everywhere) and only then the firmware will replace some FF as needed.

OK, I am genuinely confused now.

I did an erase using "W201FW21 /srom 0 /erase", and it verified the erase with no errors at all.

Then I did a write using "W201FW21 /srom 0 /log /writeall K2024.mem CFG_201.INI" and that completed without any errors.

Then I did a verify using "W201FW21 /srom 0 /verify K2024.mem" and that said "Verify Mismatch" yet again, as always.

I then tried everything above a second time, but changing it to "W201FW21 /srom 0 /log /write K2024.mem CFG_201.INI" and the exact same thing happens, it says it was completely and the verify succeeds. Then I did yet another verify using "W201FW21 /srom 0 /verify K2024.mem" and that said "Verify Mismatch" yet again.

All along in the Device Manager it still shows firmware 2020 and the device still works as if it was never touched.

So, I then did a mem dump using "W201FW21 /srom 0 /dump backup.mem", and then I opened it with a Hex editor and it is identical to my first backup.mem file. NOTHING has changed.

What is going on? lol, someone said they think it is not seated but then why can I use it with all my drives? I also tried this in another computer, my x58 and I was getting the same things last week.

I wonder if this W201FW21.exe will work in FreeDOS? Maybe Windows 10 is blocking something?

OK, I am now done trying. Even in DOS I can't get the known NEC DOS flasher tool to even launch. Keeps saying "This program does not work in DOS". BS

I guess my device has a write protect on it or something. The only other thing that comes to my mind is the x1 slot. Maybe the device needs an x16 slot, lol. But I digress as I am not willing to try it from different slots.

@Phoenix48, thanks man for all your help, it is highly appreciated. Maybe all this tons of extra data in this thread might one day help someone else. Lets hope it does.

Hey at least I didn't kill the card, its still working just fine. ;)

I can already tell you that it did helped me. Now at least i know my chip has the right SUBSYS number in it. That was not the case before.