hi my kernel 3.4.113 from armbian

my OrangePi Zero dont have poweron - button by default /

 

 i know system can wake up from gpios / IR signal / usb events / wakeonlan and another sourcec

 

bu i try todo standby and wakeup after! withous any success ((((

:/sys/power# cat state
standby mem bootfast

goto sleep

echo mem > /sys/power/state

or

echo standby > /sys/power/state

working fine ) but i cant wakeup system (((( i try gpio usb ir wakeonan 

 

what i do wrong ????

 

somebody can clarify my issue ???

 

my loaded modules

lsmod
g_ether                38598  0
ir_lirc_codec           3685  0
ir_nec_decoder          1556  0
lirc_dev                7846  1 ir_lirc_codec
rc_core                12751  4 ir_nec_decoder,ir_lirc_codec,sunxi_cir
sndspdif                2747  0
sunxi_cir               1601  0
sunxi_sndspdif          3885  0
sunxi_spdif             7049  0
sunxi_spdma             3707  0

i have read some info from

cat /sys/power/wakeup_src

and try diff combination but same ! not have result !!!!

 echo 0x2000 0x200 1 > /sys/power/wakeup_src

OrangePi forum has full instructions:

http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=2048&extra=page%3D1

 

You could use exactly the same principle, except, obviously, path will be different.

tnx but i have read this topic about ir wakeup 2 weeks before )

- and same not work

may be OrangePiZero have some diffs ?

any body have experiences with my  Zero board

i still need sleep and wake up device

 

anybody know how to use arisc may be it can help

/sys/devices/platform/sunxi-arisc

ah, sorry, you mean OPi Zero... Then be sure to connect IR receiver to PL11, otherwise it won't work. ARISC know to use only dedicated IR pin. I believe OPiZero hat use it, but I'm not sure.

ah, sorry, you mean OPi Zero... Then be sure to connect IR receiver to PL11, otherwise it won't work. ARISC know to use only dedicated IR pin. I believe OPiZero hat use it, but I'm not sure.

 

tnx yes its use same PL11 ! but what about gpios wakeups and usb

Ah, I again misread your OP, sorry.

 

So, if you want to wake-up by GPIO, then you have to specify wanted pin in FEX. Find something like:

[wakeup_src_para]
wakeup_src_bt = port:PL03<6><default><default><0>

You can add some wakeup_src_* entries here. Full name of the entry doesn't matter, but it must start with "wakeup_src_" You have to reboot before it will take an effect.

 

I saw USB mentioned as wake up event, but I'm not sure how to set it up.

Ah, I again misread your OP, sorry.

 

So, if you want to wake-up by GPIO, then you have to specify wanted pin in FEX. Find something like:

[wakeup_src_para]
wakeup_src_bt = port:PL03<6><default><default><0>

You can add some wakeup_src_* entries here. Full name of the entry doesn't matter, but it must start with "wakeup_src_" You have to reboot before it will take an effect.

 

I saw USB mentioned as wake up event, but I'm not sure how to set it up.

 

same not work (((( which kernel config and board are u use ?

 

how run sleep ?

 

echo mem > /sys/power/state

echo standby > /sys/power/state

What do you mean by kernel config? I tested this actually on OpenELEC on multiple boards, kernel 3.4.113, but there is no reason that it shouldn't work on legacy Armbian. Be aware that USB hubs for some reason break suspend procedure. Command for go to sleep:

systemctl suspend

Addition: Pin should be pulled up to 3V3 and when you want to wake it up, you have to connect pin to GND. Check schematic for any other board, which has power button.

 

What do you mean by kernel config? I tested this actually on OpenELEC on multiple boards, kernel 3.4.113, but there is no reason that it shouldn't work on legacy Armbian. Be aware that USB hubs for some reason break suspend procedure. Command for go to sleep:

systemctl suspend

i have use opewrt env  which not have systemctl

 

i think its must be same like this action or not ??

echo standby > /sys/power/state 

On 26.01.2017 at 3:15 AM, jernej said:

Ah, I again misread your OP, sorry.

 

So, if you want to wake-up by GPIO, then you have to specify wanted pin in FEX. Find something like:

[wakeup_src_para]
wakeup_src_bt = port:PL03<6><default><default><0>

You can add some wakeup_src_* entries here. Full name of the entry doesn't matter, but it must start with "wakeup_src_" You have to reboot before it will take an effect.

 

I saw USB mentioned as wake up event, but I'm not sure how to set it up.

 

On 26.01.2017 at 6:27 AM, jernej said:

Addition: Pin should be pulled up to 3V3 and when you want to wake it up, you have to connect pin to GND. Check schematic for any other board, which has power button.

Did so:

[wakeup_src_para]
...
wakeup_src_gpio = port:PG07<6><default><default><0>

echo 199 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio199/direction
echo 1 > /sys/class/gpio/gpio199/value

Does not work. What is the problem?

 

p.s. Orange PI PC with OpenELEC.

Sorry, I didn't work on OE or BSP kernel for quiet some time, so I can't help you further.

Hello, same problem here. I can put my Orange PI Zero in standby with:

systemctl suspend

systemctl suspend

And then it seems to be impossible to wake it up. In my FEX file I added:

wakeup_src_bt = port:PA07<6><default><default><0>  

I connected +3.3V to PA07 (GPIO7, AKA the physical pin #12 of the board) with pullup resistor, then I make the OPI Zero sleep and I try to connect PA07 to ground. Nothing happens.

Hello, I'm bumping this question because I'm stil stuck at this resume from standby problem

FLiP-79 before any one can even try to help you, you need to tell exactly which Armbian image you have used, which updates you have done, and the current Armbian and kernel version; they are given when you log in.

 

For example, I have burnt Armbian_5.35_Orangepizero_Ubuntu_xenial_next_4.13.16.img but after updates I got

Welcome to ARMBIAN 5.38 stable Ubuntu 16.04.3 LTS 4.14.18-sunxi

 

There have been major changes between kernel 3 and 4. Many things that used to work via drivers now work via overlays.

4 hours ago, DoubleHP said:

FLiP-79 before any one can even try to help you, you need to tell exactly which Armbian image you have used, which updates you have done, and the current Armbian and kernel version; they are given when you log in.

 

For example, I have burnt Armbian_5.35_Orangepizero_Ubuntu_xenial_next_4.13.16.img but after updates I got

Welcome to ARMBIAN 5.38 stable Ubuntu 16.04.3 LTS 4.14.18-sunxi

 

There have been major changes between kernel 3 and 4. Many things that used to work via drivers now work via overlays.

Hi, this is my current version:

ARMBIAN 5.36 user-built Ubuntu 16.04.3 LTS 3.4.113-sun8i