• State
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 91 views
  • Users 0 members are here
Support feedback
Options
Options
Related

Original question:

AM625: M4 MCU Only Deep Sleep mode

AM625: Continuation: M4 MCU Only Deep Sleep mode

Johannes Schraml
Prodigy 10 points
Part Number: AM625

Tool/software:

Hi, 

I am currently facing the same issue as mentioned in https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1370768/am625-m4-mcu-only-deep-sleep-mode , notably: 

  • The SoC is able to enter the MCU only mode. 
  • The SoC is able to wake up from the MCU only mode, either using the MCU based IPC interrupt or the RTC.
  • The MCU is not able to toggle peripherals (tested with: toggling MCU domain GPIO pins, running MCU domain I2C Reads, Printing to the MCU Domain UART during the Suspend phase)...
  • ...but the M4F core itself keeps running (this was confirmed by incrementing a counter during the suspended phase and printing the output; on resuming from suspend, a  jump in the counter value can be observed that is consistent with the suspended time). 

Since this thread was closed without a resolution to the issue, and the last message from Vaibhav Kumar confirmed the issue is reproducible on Ti's side, I am opening this thread to ask about the current state of this issue. 

  • Can you confirm this is still relevant/hasn't been solved?
  • Can you inform me if the non-functionality of peripherals in the MCU-only LPM is a known limitation of the current SDKs? 
  • Will there be any further investigation into this? 

Detailed version information: 

  • Hardware: Ti AM625-SK EVM
  • Processor Linux SDK version: 11.00.09.04, linux image: tisdk-default-image-am62xx-evm-11.00.09.04
  • uname: Linux am62xx-evm 6.12.17-ti-00771-gc85877d40f8e
  • devicetree: not modified. 
  • MCU+ SDK Version: 11.01.05.03
  • CCS: v.20.1.1.8__1.7.1
  • M4F Firmware: modified version of SDK example: "ipc_rpmsg_echo_linux_am62x-sk_m4fss0" according to previous thread. 


Note: Due to external constraints, our application would involve SDK Version 09.02.01.10, however, since this issue affects the more recent SDKv11 as well, I am opening this thread for the newer SDK Version. The same behavior was observed for both SDK Versions. 


Our current application would heavily rely on external peripheral control in MCU only mode, so any input on this would be greatly appreciated. 

Best Regards and thank you for your help, 
Johannes