Torpedo based unit fails to resume. - Beacon EmbeddedWorks

Create Account

Create Account

You are here: >> >> >>

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

Forums
Search Forum
Advanced SearchTopicsPosts

Prev Go to previous topic

Go to next topic

Last Post 26 Mar 2012 05:51 AM by common@exensor.se

Torpedo based unit fails to resume.

6 Replies

Sort:


You are not authorized to post a reply.

Author

Messages

common@exensor.se

New Member
Posts:

12 Jan 2012 02:48 AM
Got a Torpedo SOM based platform using the Texas Instruments rowboat-android-2.3.4-devkit2.1. When suspending the platform, everything seems to work fine: [ 396.137908] request_suspend_state: sleep (0->3) at 396666900654 (2000-01-01 00:06:33.208679218 UTC) [ 396.147460] ssd2532 in sleep # [ 397.627502] stop_drawing_early_suspend: timeout waiting for userspace to stop drawing [ 408.907806] PM: Syncing filesystems ... done. [ 419.377899] Freezing user space processes ... (elapsed 0.01 seconds) done. [ 419.403839] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done. [ 419.554168] PM: suspend of devices complete after 117.278 msecs [ 419.560424] PM: suspend devices took 0.125 seconds [ 419.567138] PM: late suspend of devices complete after 1.678 msecs After this, nothing can wake up the platoform. Tried keypad, serial ports and touchscreen. Any ideas on what i might have missed? I sort of suspect that power to the wakeup domain is missing, but from what i can see, all power realated is set up as it should (compared to the EVM board setup). Any suggestions is greatly apreciated. Regards, Robert.

richard.laborde@logicpd.com

Basic Member
Posts:247

12 Jan 2012 08:23 AM
Robert, Have you used our Android image? It does not exhibit the same behavior. There may be something you can change in the Rowboat version based on the changes we made to our current release that would fix the issue. You should also try the S2 button, I think that is what we use for suspend/resume. (see the Android Image User Guide) Thanks

common@exensor.se

New Member
Posts:

18 Jan 2012 05:35 AM
I just realised that this forum might be just for the complete devkits and not for custom built devices. If so, sorry. Mine is based on the torpedo SOM but has other perpherials. I have not tried your image since: I need Android 2.3, and my device has different display and touchscreen. I mainly asked here because i was hoping that someone here would recognise the problem and have a suggestion for troubleshooting/solution. As you suggest, looking at your patches for the kernel could be an idea, but as they are based on kernel 2.6.32 and the rowboat is 2.6.37 it's quite hard to actually compare whats different. Or perhaps you have a 2.6.37 kernel somewhere that i have missed? Regards, Robert.

richard.laborde@logicpd.com

Basic Member
Posts:247

18 Jan 2012 03:55 PM
Robert - you can always post on the TDG. : ) Our next release will be Gingerbread with WiFi support for the new DM3730 T +W. It should be through our SQA process early Feb. Thanks

common@exensor.se

New Member
Posts:

23 Mar 2012 06:14 AM
Hi again. New development on this issue. I still havn't solved the problem. Yesterday I got access to the original zoom development platform with what I guess is your original linux android distribution on it (omap3logic-eng 2.1-update1, kernel 2.6.32). When trying to suspend it (by removing the wakelocks and letting it hit "mem" power state) this hung as well. First it logged alot of errors: Suspending console(s) (use no_console_suspend to debug) pm_op(): usb_dev_suspend+0x0/0x8 returns -2 PM: Device usb2 failed to suspend: error -2 PM: Some devices failed to suspend Restarting tasks ... done. suspend: exit suspend, ret = -2 (2000-01-01 00:03:55.561035155 UTC) PM: Syncing filesystems ... done. Then after a while it just freezes. Any ideas to why this is happening? And is there other firmware that have working suspend that i might download? Regards, Robert.

richard.laborde@logicpd.com

Basic Member
Posts:247

23 Mar 2012 08:13 AM
Robert, If you haven't yet, you can register that kit and have access to all of our documentation. Please review the release notes for the OS image you are targeting. Is this OMAP 35 or DM37?

common@exensor.se

New Member
Posts:

26 Mar 2012 05:51 AM
It's a Torpedo OMAP3530 device. Yes I have registered the device and have looked at the documentation for the Android image. But i can't find any mentioning about if the suspend features are working. The fact that there are a permanent wake lock set named "true" might indicate that it's not. I have also looked at the "OMAP35x Linux Demo Image" but that one actually says "Cannot invoke suspend state." so i guess that one's out of the question as well. Anyways, this was just a sidetrack and I don't think that it would have helped me much in the end as I'm trying to get the newer TI Rowboat gingerbread distribution working (as we need Android 2.3). It would have helped if you had any working linux distribution with a kernel that I could have ported over to the TI distribution (or even only used as a reference) but i can't find one. Regards, Robert.

You are not authorized to post a reply.

Forums Texas Instruments SOMs and Development Kits OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit