-
Notifications
You must be signed in to change notification settings - Fork 12
AS6602T sata LEDs not working #34
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
Comments
🤔️The method I can think of is to randomly set some GPIOs to output mode and pull up the voltage, hoping that the corresponding LED lights up. However, from what I remember, this operation carries the risk of permanently damaging the device. |
I try to set almost every GPIO to output, New
And I tried this comment #27. But there was no change. What should I do now? |
After the above tests, I returned to ADM, and was surprised to find that now sata LEDs do not blink in ADM either. Maybe this is the permanent device damage I have suffered. 😂😭️ |
It's weird that those LEDs wouldn't work, because I briefly had an AS6602T and IIRC all the LEDs worked with the code? And I think the AS6604T is also known to work? Maybe the LEDs were already broken before you started testing? While poking the GPIOs could maybe, theoretically damage your device, I don't think it should happen in practice. Shutting down the device (maybe disconnecting power for a minute) should reset whatever internal state might get confused by setting the pins wrong and on next boot they should work as usual again. As you wrote
I assume that SATA drives were installed during testing? Could be that the LEDs are disabled if the tray is empty |
Thank you very much for your reply! I am confident that all SATA LEDs were working normally under ADM before I started testing. Unfortunately, I no longer have any proof of this. I have tried shutting down the device. I disconnected the power adapter for several hours and then reconnected it, but sadly, the SATA LEDs did not work as expected. During this time, I also tried pressing the Reset button on the back of the device, but this did not help either. As for
Actually I installed one SATA HDD during the testing period in order to observe the status of the LED. However, after I finished testing and returned to ADM, both SATA HDDs stopped flashing. |
I just realized that the CMOS battery could also be storing some state. Let me try removing the CMOS battery to see if that makes any difference. |
Briefly: Removing both the CMOS battery and the power adapter also failed to restore functionality. After removing the CMOS battery, I attempted to speed up the reset process by shorting the two poles on the battery holder, but the SATA LEDs still did not resume flashing. Perhaps the removal time was too brief; I now plan to leave the device idle for several hours again with both the CMOS battery and power adapter removed. |
If all this didn't help then I guess that shutting down and/or clearing CMOS really doesn't help in your case. What is |
Thanks for your reply! Bad news for me: clearing CMOS doesn't work for my case. As for the root@fnos:/# cat /sys/class/leds/sata1\:green\:disk/trigger
none kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock [disk-activity] disk-read disk-write mtd nand-disk cpu cpu0 cpu1 cpu2 cpu3 panic usb-gadget usb-host mmc0 mmc1 rfkill-any rfkill-none r8169-0-300:00:link r8169-0-300:00:2.5Gbps r8169-0-300:00:1Gbps r8169-0-300:00:100Mbps r8169-0-300:00:10Mbps r8169-0-400:00:link r8169-0-400:00:2.5Gbps r8169-0-400:00:1Gbps r8169-0-400:00:100Mbps r8169-0-400:00:10Mbps and root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:49.551Z 1
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:49.746Z 0
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:49.955Z 1
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:50.139Z 1
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:50.338Z 0
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:50.551Z 0
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:50.744Z 0
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:50.955Z 0
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:51.166Z 1
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:51.377Z 0
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:51.615Z 0
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:51.810Z 1
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:52.042Z 1
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:52.283Z 1
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:52.496Z 0
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:52.716Z 0
root@fnos:/# echo $(date --utc +%FT%T.%3NZ) $(cat /sys/class/leds/sata1\:green\:disk/brightness)
2025-03-25T22:36:52.895Z 0
root@fnos:/# The value looks like "blinking". But my LED is not blinking. This is one of the reasons I first suspected that the PIN number was set incorrectly :( |
I wonder if that "active-high" vs "active-low" state makes a difference, or if it should blink either way (just with on and off states switched if it's set wrong). But it's also possible that the pins are wrong - maybe I misremember and I did not actually test the SATA LEDs before I returned my AS6602T (because on it NVME was even slightly slower than SATA and I could get an AS5402T for about the same price). |
How do I test that? Is it okay to modify active-high to active-low in the source code? |
New discovery: When I execute |
Thank you for sharing your work!
Fan management, power, USB, and LAN LEDs are working for my AS6602T.
However, SATA LEDs still don't work. Only the drive presence LEDs light up.
I see that the sata1-6 LEDs appeared. But none of the changes I've made to its settings are taking effect.
I'm not sure if it's the wrong PIN number that's causing the problem.
Could you direct me how to fix it?
Here is the gpioinfo:
The text was updated successfully, but these errors were encountered: