I am using Jetson Nano emmc version with Nvidia development board and trying to save power with rtcwake function.
I tried the commands below to make jetson nano sleep and wake up after 10 sec.
sudo rtcwake -v -u -s 10 -m mem
The jetson nano went into mem and woke up again after 10 sec. However, it went back to sleep again (the LED turned off and I couldn’t ping it anymore) after a few seconds and never woke up.
I will need to power cycle the unit to wake it up again. How do I make it stay waking up after the mem state?
please check developer guide, Chipset Power States for the supported power states.
you should refer to the available wake sources to awake Jetson from the deep sleep.
thanks
I issued the commands below.
sudo bash -c “echo date '+%s' -d '+ 20 seconds' > /sys/class/rtc/rtc0/wakealarm”
and tried both way to make my board goes into deep sleep
sudo systemctl suspend
$ sudo bash -c “echo mem > /sys/power/state”
However, I am still having similar issue. My Jetson Nano went into deep sleep mode and could not wake up again. I have tested 2 development board and 2 Jetson Nano emmc version. They all have the same behaviour. Is there any other way I can make this works?
Hi JerrChang,
with cat /etc/nv_tegra_release, I got
R32 (release), REVISION: 5.1, GCID: 26202423, BOARD: t210ref, EABI: aarch64, DATE: Fri Feb 19 16:45:52 UTC 2021
I did more tests and realised sometimes sudo bash -c “echo date ‘+%s’ -d ‘+ 20 seconds’ > /sys/class/rtc/rtc0/wakealarm”
and sudo systemctl suspend worked as expected. However, sometimes the Jetson could not wake up.
Please let me know if there is anyplace I would need to modify to make sleep and wake up stable.
I encountered issue that Jetson nano not waking up with rtc wakealarm and deep sleep again with a customised board.
Issued commands
sudo bash -c “echo date ‘+%s’ -d ‘+ 120 seconds’ > /sys/class/rtc/rtc0/wakealarm”
sudo bash -c “sudo systemctl suspend”
However, the jetson nano did not wake up.
With cat /etc/nv_tegra_release, I get
R32 (release), REVISION: 5.1, GCID: 26202423, BOARD: t210ref, EABI: aarch64, DATE: Fri Feb 19 16:45:52 UTC 2021
I have attached the log here. log_jetson (16.9 KB)
I saw lots of i2c transfer timed-out failures.
could you please confirm you’ve provide the regulator to those i2c device correctly.
BTW,
I think you’re having incorrect commands,
please try add 'now' into the pipeline for sending to wakealarm,
for example, date +%s -d "now + 120 seconds"
thanks