ARGB broke. ASRock Dynamic Lighting |
Post Reply | Page 123> |
Author | |||
dchang0
Newbie Joined: 02 Dec 2024 Status: Offline Points: 30 |
Post Options
Thanks(0)
Posted: 02 Dec 2024 at 8:24am |
||
Forgot to mention some important details to the post above.
The AsrISP.exe /I flag is really important. Normally /I 0 uses the USB interface to flash the controller. In my case, the USB interface was misbehaving, so I used the I2C interface via the /I 1 command. After the USB interface came back online (I think right after the overwriting of the LDROM and/or APROM), then it would have been possible to use the USB interface, but I kept using the I2C interface the whole time since that's what I am used to using with Arduino. I remember also trying a bunch of reboots of the controller with the /BS flag at the beginning and not having a whole lot of luck with it fixing anything, so I ended up moving on to overwriting the LDROM and APROM. Note that rebooting might be necessary in between the flashing steps, but I think it's included already. |
|||
dchang0
Newbie Joined: 02 Dec 2024 Status: Offline Points: 30 |
Post Options
Thanks(0)
|
||
If you haven't fixed this yet, here's what I had to do quite a while ago (07/2023). ALL OF THIS COULD BE DANGEROUS, SO DO THIS AT YOUR OWN RISK. I tried everything everyone else mentioned and then started digging into the actual WriteFW.BAT file that does the flashing. I realized that the WriteFW.BAT file was skipping doing anything in my case, so what I did was copy the actual flashing command out of the section of the .BAT file that it was skipping, and I ran it manually at the command prompt. The command is:
BUT!!!! This didn't work for me at all. It did for other people, but not me. I had to go further and start guessing at the other options for the AsrISP.exe command. Here is what the current version of AsrISP.exe has:
What I ended up doing was: 1) reboot the controller using the /BS 0 flag If the reboot with reset works to fix your ARGB LED controller, STOP HERE!!! 2) THIS IS DANGEROUS: erase all with the /E all flag 3) manually overwrite the LDROM with /UL flag, then 4) manually overwrite the APROM with /UA flag, then 5) manually overwrite the data file with /UD flag It's been so long ago I don't remember the exact flags/options I used, but it was probably exactly as shown in the AsrISP.exe /? above. Now, the hard part for me was figuring out which LDROM .bin file to use and which APROM .bin file to use after that and then which data file to use. (All these files are in the same directory as the AsrISP.exe file.) I didn't have a config file and was terrified about having screwed up by erasing it before finding out I didn't have one. I ended up using trial and error (there were only four or so LDROM and four or so APROM .bin files to try). I DO NOT RECOMMEND TRIAL AND ERROR FOR YOU. In my case, I had nothing else to lose, so I went ahead and did it. After I re-flashed the LDROM and APROM, I then deduced which .dat file to use for my motherboard model (there was some trial and error, but I was able to rule out most of the .dat files based on what appear to be dates and parts of model names). Finally, I was able to run the firmware update with the /AUTO /FORCE flags, and it worked. I now had the latest firmware, and the ARGB LED controller was working properly again. It was visible in both BIOS and PolyChrome app. I have not had any trouble since then. How did I know to do the above? I have some experience working on microcontrollers like Arduino and also flashing ROMs on Android phones, so I knew something about flashing bootloaders and OS images and digging out of a bricked situation. The big question that makes the above dangerous is what to do if you need to do a hardware reset and hardware flash of the ARGB LED controller chip on the motherboard. On an Arduino, it's possible to get at the hardware pins, so there's a kind of fearlessness. If you mess up you can always recover. Anyway, I don't remember much more about what I did, and I probably won't be back on this forum. Just posting it in case someone got stuck like I did. |
|||
Darkje
Senior Member Joined: 30 Dec 2022 Status: Offline Points: 1610 |
Post Options
Thanks(0)
|
||
If you also have an unknown device in windows device manager, this can usually be solved by unplugging the psu from the mains for a few minutes. |
|||
FLORRIDAMAN
Newbie Joined: 12 May 2024 Location: Florida Status: Offline Points: 15 |
Post Options
Thanks(0)
|
||
i have a problem where when ever i launch ASRRGBLED it says device not detected can anyone help me
|
|||
uyhh
|
|||
m00zis
Newbie Joined: 08 May 2024 Status: Offline Points: 15 |
Post Options
Thanks(0)
|
||
Unfortunately nothing of all of the above steps worked for me. I installed my new b650 Steel Legend yesterday and everything worked fine. Just after installing Polychrome (I had SignalRGB running in the Background) my PCH RGBs stopped working. I tried everything from flashing the RGB firmware, BIOS update, uninstalling SignalRGB, reinstalling Polychrome, unplugging pc for 10 minutes and run UpdateFW.cmd and whatsoever.
Nothing seems to work for me. Has anyone anymore tips for me? Thank you |
|||
oskar_1993
Newbie Joined: 03 May 2024 Status: Offline Points: 30 |
Post Options
Thanks(0)
|
||
thank you, kind man, because I thought that everything was broken, but it was your way that helped me)
|
|||
oskar_1993
Newbie Joined: 03 May 2024 Status: Offline Points: 30 |
Post Options
Thanks(0)
|
||
|
|||
Darkje
Senior Member Joined: 30 Dec 2022 Status: Offline Points: 1610 |
Post Options
Thanks(0)
|
||
oh well, i guessed it was worth a shot, pitty it didn't work.
|
|||
ard
Newbie Joined: 08 Oct 2023 Status: Offline Points: 125 |
Post Options
Thanks(0)
|
||
I didn't try that, as WriteFW.bat only does it if AsrISP fails twice, so I figured it was for other (older?) boards. The input file being only 13KB when one that I know works is 20KB is another sign I should not give it a go.
When I gave it a go it displayed the correct board type and BIOS version, so I guess it interrogated the board successfully. But it said no more, consuming a CPU until I killed it. The last thing it did was look for a file called SMBUS.ini, which is not there. |
|||
Darkje
Senior Member Joined: 30 Dec 2022 Status: Offline Points: 1610 |
Post Options
Thanks(0)
|
||
? Did you also try:
wICPFLASHADSBv2.exe /file=nu51_3.04 (it comes with Polychrome RGB ver:2.0.170) |
|||
Post Reply | Page 123> |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |