Omega2 won't reboot?
-
@WereCatf said in Omega2 won't reboot?:
Well, knock yourself out with e.g. https://github.com/WereCatf/source/blob/master/target/linux/ramips/dts/omega2p.dts I only changed a few things to better match how things are done in LEDE-proper.
Did you propose pull requests over Github too? Generally those things were not ignored.
-
OK how about adding this line.
#include <dt-bindings/gpio/gpio.h>and changing this
gpios = <&gpio1 12 1>;to this
<&gpio1 12 GPIO_ACTIVE_LOW>;and since the reset button seems non functional .
try this using another gpio.
such as 2, 11,15, or 17
<&gpio0 11 GPIO_ACTIVE_LOW>;I would suggest 11 because it changes from high to low during testing.
Do we need to submit a ticket on the reset button too?
-
Do we need to submit a ticket on the reset button too?
Ticket #4088
Reset button does not work.
-
@Larry-Pinney said in Omega2 won't reboot?:
and since the reset button seems non functional .
try this using another gpio.I changed it from KEY_WPS_something to KEY_RESTART in my dts, I haven't tried if it works in my dts or not, but it is entirely possible that is the reason why it doesn't work in the official dts. Feel free to try.
-
@Larry-Pinney said in Omega2 won't reboot?:
Ticket #4088
Reset button does not work.Kinda useless without mentioning the repo you're opening the ticket against.
-
Kinda doesn't matter...none of them will work
-
The reset button should be :
linux,code = <KEY_RESTART>;
However it needs to be mapped to the correct GPIO.
-
@Larry-Pinney It is mapped to the correct GPIO. It just seems that the pin is pulled LOW by default and it's active HIGH.
-
Really and you tested it how?
-
@Larry-Pinney By reading the GPIO-pin's state, then connecting the pin to 3.3V and reading it again! Magic.
-
And it's correctly mapped...yet it doesn't work?
Did you add
#include <dt-bindings/gpio/gpio.h>
NO
no...or didn't push it yet anywaydid you make the change to
GPIO_ACTIVE_LOW ? no or failed to push that change as well.did you you read the magic with a meter?
or is it smoke and mirror magic ?
-
@Larry-Pinney said in Omega2 won't reboot?:
did you you read the magic with a meter?
or is it smoke and mirror magic ?No, I just said, I read the GPIO-pin's state. GPIO38 is LOW by default, but when I connect 3.3V to the reset-pin it becomes HIGH, so yes, the GPIO-number is correct.
-
It's NOT on gpio 38 otherwise known as gpio1 6...
apparently that gpio is locked by the "stock" dts file
Please try gpio 0 11And also let's try be so hard to get along with ....
I do not need to establish a reputation (I have numerous commits to OpenWrt/LEDE)
I'm only trying to help make this toy work properly....and do not need additional BS...I actually have better things to do.
-
@Larry-Pinney said in Omega2 won't reboot?:
It's NOT on gpio 38 otherwise known as gpio1 6...
apparently that gpio is locked by the "stock" dts fileYes, it is. You can use the command fast-gpio to read the GPIO's state directly from mmap'ed registers, so it doesn't matter that the GPIO-pin is already defined as being in use by the dts, as fast-gpio bypasses that.
And also let's try be so hard to get along with ....
You're the one trying to insult me.
-
The End...
-
Well, I can confirm the official dts has a bug, changing
gpios = <&gpio1 6 1>;togpios = <&gpio1 6 0>;fixed the reset-button and it's now working in my version of the dts, ie. the button is active HIGH, but the official dts configures it as active LOW.
-
LOL
quit screwing around and use the dt-bindings macros
-
For anyone watching this thread, the issue has been fixed in recent firmware:
https://community.onion.io/topic/1282/omega2-reboot-and-sd-card-fixed
