Bug 13368 - Potential latchup issue with WLAN module
: Potential latchup issue with WLAN module
Status: RESOLVED FIXED
Product: SB Radio
Classification: Unclassified
Component: Networking
: Include FW version in comment
: PC Other
: P1 blocker (vote)
: MP
Assigned To: Caleb Crome
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-12 11:57 UTC by Caleb Crome
Modified: 2009-09-08 09:16 UTC (History)
3 users (show)

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Caleb Crome 2009-08-12 11:57:43 UTC
Steven had a board where the WLAN module latched up.  The cause of the problem could be that the MSP430 drove the 32khz clock when the power was off, causing latchup.

I would like to disable the 32khz clock all together.  My understanding is that this clock is needed only when putting the wlan module into low power mode (i.e. system is ON, but need to reduce power further). 

Are we using this mode in the atheros module?  If so, we may need to turn it off, or use the internal oscillator, which should be okay too, but as reported by atheros, it will cause extra on-time due to missing beacons.
Comment 1 Felix Mueller 2009-08-12 14:53:53 UTC
What do you mean exactly by low power mode? I only know of a power save mode, but maybe that is the same?

Currently we are not using any power saving modes with the Atheros module because we had issues with it, especially during setup. But I understand that the plan is to use it in the future when running from battery.
Comment 2 Caleb Crome 2009-08-12 17:55:30 UTC
So, I updated the MSP code so that it should not cause any problems now.  

Power save mode is what I was talking about.
Comment 3 Richard Titmuss 2009-08-13 03:17:00 UTC
If you used an external crystal would the 32khz clock not be driven all the time anyway?

What do you mean by "latched up"
Comment 4 Caleb Crome 2009-08-13 11:12:56 UTC
Okay, Fixed this in r6886