Versions Compared

Old Version 55

changes.mady.by.user Rajan Vaja

Saved on

compared with

New Version 56

changes.mady.by.user Rajan Vaja

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This tutorial explains procedure to measure transition times and respected power values when either PS or PL suspends or wake up. By following below procedure, suspend and wake up time of APU, These procedures are for 2017.1 and later releases.  There are some differences for later releases which are indicated when appropriate.

...

...

  • Create RPU_0 application rpu_0.elf from SDK as described in above section.

  • Create a new folder and copy pmufw.elf, zynqmp_fsbl.elf, bl31.elf and u-boot.elf from petalinux generated images (present at <plnx-proj-root>/images/linux/). Also copy rpu_0.elf into same folder.

  • Create boot.bif file in same folder as shown below.

    • for 2017.x-2019.2

      Code Block
      the_ROM_image:
{
     [fsbl_config] a53_x64
     [pmufw_image] pmufw.elf
     [bootloader,destination_cpu=a53-0] zynqmp_fsbl.elf
     [bootloader,destination_cpu=r5-0] rpu_0.elf
     [destination_cpu=a53-0, exception_level=el-3,trustzone] bl31.elf
     [destination_cpu=a53-0, exception_level=el-2] u-boot.elf
}

    • For 2020.1-later

      Code Block
      the_ROM_image:
{
        [bootloader, destination_cpu=a53-0] fsbl.elf
        [pmufw_image] pmufw.elf
        [destination_cpu=r5-0] rpu.elf
        [destination_cpu=a53-0,exception_level=el-3,trustzone] bl31.elf
        [destination_cpu=a53-0, load=0x00100000] system.dtb
        [destination_cpu=a53-0,exception_level=el-2] u-boot.elf
}

  • Create BOOT.BIN file using following command.

    Code Block
    bootgen -arch zynqmp -image boot.bif -w -o BOOT.BIN

  • Create a boot partition in SD card and copy BOOT.BIN and image.ub file (present at <plnx-proj-root>/images/linux/) to boot partition.

  • Boot the ZCU102 board in SD boot mode.

  • Once boot start U-boot prompt will appear on serial. Press Enter again and again to interrupt u-boot till ZynqMP prompt appear. Run below command from u-boot to disable cpuidle.

    Code Block
    ZynqMP > setenv bootargs ${bootargs} cpuidle.off=1

  • After that start the linux by writing "boot" on the U-boot prompt

...

  • Power off all 3 secondary APUs and set frequency of primary APU0 to minimum using above commands for minimum latency measurement.

  • Run following command from Linux terminal to release unnecessary nodes and signal the RPU_0:
    (For v2017.1-4)

    Code Block
    root@plnx_aarch64:~# echo request_wakeup 8 1 0 1 > /sys/kernel/debug/zynqmp_pm/power
root@plnx_aarch64:~# echo force_powerdown 8 >  /sys/kernel/debug/zynqmp_pm/power
root@plnx_aarch64:~# echo release_node 69 > /sys/kernel/debug/zynqmp_pm/power
root@plnx_aarch64:~# echo 0 > /sys/module/printk/parameters/console_suspend
root@plnx_aarch64:~# echo MMIO_WRITE 0xFFD80064 1 1 > /sys/kernel/debug/zynqmp_pm/power

    (For v2018.2)

    Code Block
    root@plnx_aarch64:~# echo pm_request_wakeup 8 1 0 1 > /sys/kernel/debug/zynqmp-firmware/pm
root@plnx_aarch64:~# echo pm_force_powerdown 8 >  /sys/kernel/debug/zynqmp-firmware/pm
root@plnx_aarch64:~# echo pm_release_node 69 > /sys/kernel/debug/zynqmp-firmware/pm
root@plnx_aarch64:~# echo 0 > /sys/module/printk/parameters/console_suspend
root@plnx_aarch64:~# echo 0x1 0x1 > /sys/firmware/zynqmp/pggs3

    (For v2018.3)

    Code Block
    root@plnx_aarch64:~# echo disabled > /sys/devices/platform/amba/ffa60000.rtc/power/wakeup
root@plnx_aarch64:~# echo disabled > /sys/devices/platform/amba/ff000000.serial/power/wakeup
root@plnx_aarch64:~# echo disabled > /sys/devices/platform/amba/ff010000.serial/power/wakeup
root@plnx_aarch64:~# echo pm_release_node 69 > /sys/kernel/debug/zynqmp-firmware/pm
root@plnx_aarch64:~# echo 0 > /sys/module/printk/parameters/console_suspend
root@plnx_aarch64:~# echo 0x1 0x1 > /sys/firmware/zynqmp/pggs3

    (For v2019.1 - Later)

    Code Block
    root@plnx_aarch64:~# echo disabled > /sys/devices/platform/amba/ffa60000.rtc/power/wakeup
root@plnx_aarch64:~# echo disabled > /sys/devices/platform/amba/ff000000.serial/power/wakeup
root@plnx_aarch64:~# echo disabled > /sys/devices/platform/amba/ff010000.serial/power/wakeup
root@plnx_aarch64:~# echo disabled > /sys/devices/platform/amba/ff0a0000.gpio/power/wakeup
root@plnx_aarch64:~# echo pm_release_node 69 > /sys/kernel/debug/zynqmp-firmware/pm
root@plnx_aarch64:~# echo 0 > /sys/module/printk/parameters/console_suspend
root@plnx_aarch64:~# echo 0x1 0x1 > /sys/firmware/zynqmp/pggs3

  • Now, Linux will be suspended and it will be resumed by RPU after suspend. RPU has requested NODE_SATA from FPD, so Linux will be suspended with FPD on.

  • After 10 second of Linux suspend, RPU application will release NODE_SATA. Once NODE_SATA is released, FPD will be off. Use Power Advantage Tool in these 10 seconds to get power value for Suspend to RAM.

    Following are two print messages to identify these 10 second window.

    Code Block
    RPU0: Suspended to RAM, FPD is on******************** RPU ON, APU suspend with FPD ON ******************
RPU0: (10 seconds delay)
RPU0: Release NODE_SATA, FPD will be off after releasing NODE_SATA

  • Once FPD is off, RPU will resume APU after 10 second of FPD off. To measure power with FPD off, Use Power Advantage Tool in these 10 seconds.
    Following are two print messages to identify these 10 second window.

    Code Block
    RPU0: Suspended.
RPU0: (10 seconds delay)
RPU0: Resuming APU.
    Above loop will run for 5 
     ******************** RPU ON, APU suspend with FPD OFF ******************
RPU0: Suspended.
RPU0: (10 seconds delay)
RPU0: Resuming APU.

  • Above loop will run for 3 times and print minimum, maximum and average values for latency. On console, you should able to see suspend/wakeup latency of APU from RPU print message as shown below.

    Code Block
    RPU0: Request Suspend Latency in useconds of Node NODE_APU_0:  Min: 42701, Max: 45728, Avg: 45058
RPU0: FPD off Latency in useconds of Node NODE_APU_0:  Min: 5902, Max: 5902, Avg: 5902
RPU0: FPD on Latency in useconds of Node NODE_APU_0:  Min: 121025, Max: 121251, Avg: 121116
RPU0: APU0 Wakeup Latency in useconds of Node NODE_APU_0:  Min: 8061, Max: 8067, Avg: 8063
RPU0: Wakeup Latency in useconds of Node NODE_APU_0:  Min: 14062, Max: 14088, Avg: 14080

    Here,
    RPU0: Request Suspend Latency in useconds of Node NODE_APU_0: Latency for power state transition from "3 APU off (min frequency)" to "Suspend to RAM".
    RPU0: FPD off Latency in useconds of Node NODE_APU_0:                  Latency for power state transition from "Suspend to RAM" to "FPD off".
    RPU0: FPD on Latency in useconds of Node NODE_APU_0:                  Latency for power state transition from FPD off to "Suspend to RAM".
    RPU0: APU0 Wakeup Latency in useconds of Node NODE_APU_0:       Time require to wakeup APU_0 after RequestWakeup call.
    RPU0: Wakeup Latency in useconds of Node NODE_APU_0:                 Latency for power state transition from "Suspend to RAM" to "3 APU off (min frequency).

  • R5 Sleep and Deep-Sleep mode

    • Once above measurements are done, RPU puts FPD in off state and goes to idle mode (wfi state) for 10 seconds.

    • To measure power with R5 sleep mode, Use Power Advantage Tool in these 10 seconds.
      Following are two print messages to identify these 10 second window.

      Code Block
      RPU0: Go to******************** RPU Sleepidle, mode
RPU0: (10 seconds timer)APU suspend with FPD OFF ******************
RPU0: Go to deep sleep RPU Sleep mode
RPU0: (10 seconds timer)

    • After 10 seconds RPU gets timer interrupt after that it suspend itself and goes to deep sleep mode for 10 seconds.

    • After RPU goes to deep sleep, Use Power Advantage tool for measuring power values within these 10 seconds.
      Following are two print messages to identify these 10 second window.

      Code Block
      RPU0: Go to deep sleep
RPU0: (10 seconds timer)
RPU0: Disabling RPU Lock-Step Fault Log...*************************** Deep Sleep Mode *********************

    • After 10 seconds timer will generate interrupt and Resumes RPU. Then RPU resumes APU. This state is same as 3 APU off with minimum frequency.

    • Now to measure latency/power from left to right of dimmer mode table, use below commands:

      • Set max APU0 frequency using frequency scaling.

      • Power on all 3 secondary APUs.

      • Power on PL.

...

    • After resuming, RPU will automatically execute the demo again.

      Code Block
      RPU0: Resume APU
RPU0: **************** Demo executed successfully ********************
RPU0: ******** Executing Typical power state demo again **************

Measure transition time of RPU

...

...

  • Create rpu_0.elf and apu.elf from SDK as described in above section.

  • Create a new folder and copy pmufw.elf and zynqmp_fsbl.elf from petalinux generated images (present at <plnx-proj-root>/images/linux/). Also copy rpu_0.elf and apu.elf into same folder.

  • Create boot.bif file in same folder as shown below.

    Code Block
    the_ROM_image:
{
     [fsbl_config] a53_x64
     [pmufw_image] pmufw.elf
     [bootloader,destination_cpu=a53-0] zynqmp_fsbl.elf
     [destination_cpu=r5-0] rpu_0.elf
     [destination_cpu=a53-0] apu.elf
}

  • Create BOOT.BIN file using following command.

    Code Block
    bootgen -arch zynqmp -image boot.bif -w -o BOOT.BIN

  • Create a boot partition in SD card and copy BOOT.BIN to boot partition.

  • Boot the ZCU102 board in SD boot mode and observe the output on uart console.

  • APU suspends and resumes RPU and measures its transition time.

...