This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP3530 ISP suspend/wake-up problem

Other Parts Discussed in Thread: OMAP3530

Hey guys, I am working on OMAP3530 ISP module and in order to save power, we need to suspend the system under some certain condition.

Recently I upgrade my BSP to 6.14.01, but I found that if it is running CameraApp, the system could not suspend and wake-up again correctly.

Does anyone know about this? How to solve it?

  • Wanted to get a few more details on this issue.

    - BSP 6.14.01: You only face suspend/resume issue while the cameraapp is active? If camerapp is closed then you don't see a problem with suspend/resume?

    - When you said it does not wake up correctly can you describe what happens? Does it consistently not wake up? 

    - Has this scenario worked for you (with cameraapp) in any earlier version of BSP?

    Thanks.

  • Hi Jatin,

    For the questions you ask:

    1. Yes, only when the cameraapp is active, the system could not suspend/resume correctly,  the last message printed out is :

    before PWR_ON pressed58451.82> kernel IOCTL_POWER_SET setting state 3
    58451.82> -OTG SetPowerState

    (suspended and press the PWR_ON button again to resume)

    58454.39> kernel IOCTL_POWER_SET setting state 2
    58454.39> -OTG SetPowerState

    It seems that the system is trying to resume, but not know what happened and shows nothing.  If cameraapp is closed before suspending, the problem does not exist. My guess is that the problem occurs only when the ISP module is working. I tried to add disable ISP function to the power notification IOCTLs, but it is not working, maybe the message could not be handled in time.

    2. Yes, it does consistently not wake up, the screen is black and nothing shows up. I did not turn any other trace meesages on, but I can try it later.

    3. Yes, the problem is only seen in BSP6.14.01, my guess is that the BSP has made some changes to the MCU power mode, in the earlier version, after the system is suspended, the SYS_OFF_MODE is not active, the Q-current is high, but seems the BSP6.14.01 fix this, that brings the new ISP problem.

     

  • Thanks for the additional info. We will try to recreate the problem and then figure out what could be wrong.

     

  • The issue has been entered into the bug database. Bug ID is SDOCM00074280. You can track the status here. 

     

    https://cqweb.ext.ti.com/cqweb/main?command=GenerateMainFrame&service=CQ&schema=SDO-Web&contextid=SDOWP&queryID=34371711&username=readonly&password=readonly

    Note: If prompted for login/password, please close the browser and click on the link again.