just for info information, here is what I got during the boot up sequence that is different between my board sleeping properly and NOT sleeping properly

 

Sleep properly:

omap_device: omap2_mcspi.4: new worst case deactivate latency 0: 30517

NOT Sleep Properly:

Missing

------------------------------------------------------------------------------------------------------

Sleep properly:

omap_device: omap_i2c.1: new worst case deactivate latency 0: 30517

NOT Sleep Properly:

Missing

------------------------------------------------------------------------------------------------------

 

Sleep properly:

omap_device: omap_wdt.-1: new worst case activate latency 0: 30517

 

NOT Sleep Properly:

Missing

 

The rest seems to be matching

 

Furthermore, here is what is missing when I press the power button to put the system to sleep:

Sleep Properly:

[  168.757568] dm3730_torpedo_bl_set_intensity: level 17 (6% on)
[  168.763732] dm3730_torpedo_bl_set_intensity: turn on GPIO_154 as backlight!
[  168.776489] dm3730_torpedo_bl_set_intensity: level 0 (0% on)
[  168.782562] dm3730_torpedo_bl_set_intensity: turn off GPIO_154 as backlight!
[  168.794342] request_suspend_state: sleep (0->3) at 111738677984 (2000-01-01 01:58:27.055633545 UTC)
[  168.814056] mmc0: Starting deferred resume
[  169.056823] smartreflex smartreflex.0: sr_v2_disable: Smartreflex disable timedout
[  169.157501] mmc0: Deferred resume completed
[  169.205230] PM: Syncing filesystems ... done.
[  169.218200] Freezing user space processes ... (elapsed 0.02 seconds) done.
[  169.246215] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
[  169.277740] smartreflex smartreflex.0: sr_v2_disable: Smartreflex disable timedout
[  169.285980] Suspending console(s) (use no_console_suspend to debug)

NOT Sleep properly:

[   63.475311] dm3730_torpedo_bl_set_intensity: level 17 (6% on)
[   63.481445] dm3730_torpedo_bl_set_intensity: turn on GPIO_154 as backlight!
[   63.494171] dm3730_torpedo_bl_set_intensity: level 0 (0% on)
[   63.500244] dm3730_torpedo_bl_set_intensity: turn off GPIO_154 as backlight!
[   63.509765] request_suspend_state: sleep (0->3) at 63506896975 (2000-01-01 01:54:05.769012452 UTC)

 

It seems to me like the SOM is not sleeping properly because it is not executing those other commands. Is there a way to ensure they do execute?

 

 

 

Also I forgot to mention, but it seems like this has to do with the USB1_ID pin on the P2 connector. We have changed something different from what the eval board does. Is there some signaling required during boot up to make it work properly?

As a side issue, I also notice that if I do not have any USB plugged into the SOM before boot up, the device fails to detect the USB. However if I do have it connected before boot up, then everything works as planned. I am not sure if this issue is related.

I think you're describing a bug that was reported here: http://support.logicpd.co...ft/1763/Default.aspx

We have bug ticket entered, but unfortunately, we don't have an estimated time for completion.

If you wanted to sign up for a support contract, we'd be happy to review your schematics and make hardware recommendations.

adam

OK I got the USB mode to work. It turns out it was my fancy hardware setup that was causing the issue. I just removed the hardware and made it look like the evaluation board and everything detected as planned.

 

However I would like to know if the OTG issue brought up by the other user will eventually be addressed in future BSP including the android 2.3.4.