Adding a twig to the pile. No where in the documentation or user guides, or even the product home page does the chestnut board tell you gpio145_PWM10 is wire to the backlight driver. I'd planned on using McBSP3 (or even if I had planned on using the PWM line). So even beyond a high level block diagram of the gumstix itself, what would be REALLY helpful is a block diagram for everything. For instance a system level diagram of all daughter cards. Would save a lot of time knowing that a IO line brought out to a header is not usable because its tied up on the daughter card. In the case of the chestnut board, gpio144_pwm9 is also used as the lcd_en signal. 

On Tue, Dec 22, 2009 at 12:35 AM, Graham Henstridge <graham@capgo.com> wrote:
It would also be useful to know if the Overo has any intrinsic limitations on minimum achievable standby power i.e. what is the power consumption with all clock domains off (except 32kHz) and supplies scaled back. Low standby power is a vital requirement for many applications.

I support the sentiments expressed in this thread - Gumstix needs to support OEM's with adequate information if it wishes its products to be more widely adopted. Presently, the evaluation process takes excessive time because of the multitude of references, forums and websites that need to be consulted for even basic information.

Gordon, we have great expectation!

Graham




On 22/12/2009, at 11:08 AM, R. P. McMurphy wrote:

> Great.
>
> Please don't forget to show the 26MHz clocking connections/ICs. I
> would like to be able to turn that crystal off to reduce power during
> standby. Apparently the OMAP supports static clocks with auto restart
> upon GPIO event but so far I have not been able to figure out how to
> get the clock to stop. If I can get my standby power down, and get the
> battery life up, then the Overo can become a really useful module.
>
> RP
>
> On 12/22/09, Gordon Kruberg <gordon@gumstix.com> wrote:
>> Hello all,
>> Yes we can, and we will, get something out that will help here.
>> Gordon
>>
>>> or gumstix could just publish this info, and not leave their customers to
>>> infer it from these multiple references :(
>>> The block diagram is simply the first part of a reasonable hardware spec.
>>> The document it came from goes into detail on available and unavailable
>>> ports on the COM. Why is that too much to ask of Gumstix?
>>>
>>>
>>> Elvis Dowson wrote:
>>>
>>>> Hi,
>>>>
>>>> On Dec 21, 2009, at 8:02 PM, comrex wrote:
>>>>
>>>>
>>>>> What I need is something like this, from the competing product's manual
>>>>> http://old.nabble.com/file/p26875977/block.jpg
>>>>>
>>>> That diagram in itself it pretty generic. You would need a combination of
>>>> the TI OMAP 35xx technical reference manual, the gumstix published
>>>> materials (existing h/w pin outs) and  take a look at the sources to
>>>> figure things out.
>>>>
>>>> The TRM docs tell you stuff relating to the platform and its various
>>>> subsystems. It also covers stuff like pin-muxing for the OMAP. Then you
>>>> try to see which connectors are physically used using the gumstix h/w
>>>> docs. Then start looking at the linux sources.
>>>>
>>>> The s/w code usually is an implementation of system behavior published in
>>>> the TRM docs.
>>>>
>>>> Best regards,
>>>>
>>>> Elvis Dowson
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> This SF.Net email is sponsored by the Verizon Developer Community
>>>> Take advantage of Verizon's best-in-class app development support
>>>> A streamlined, 14 day to market process makes app distribution fast and
>>>> easy
>>>> Join now and get one step closer to millions of Verizon customers
>>>> http://p.sf.net/sfu/verizon-dev2dev
>>>> _______________________________________________
>>>> gumstix-users mailing list
>>>> gumstix-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>>>
>>>>
>>>>
>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Verizon Developer Community
>> Take advantage of Verizon's best-in-class app development support
>> A streamlined, 14 day to market process makes app distribution fast and easy
>> Join now and get one step closer to millions of Verizon customers
>> http://p.sf.net/sfu/verizon-dev2dev
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users