Initial audio volume issue

I'm working on a board with WinCE 5.0 that use pxa270 and ucb1400, the audio
working fine and through the control panel I can set the audio volume
correctly.

I have a problem after a reset, the volmue registry settings are ignored and
the audio volume start always as maximum level.
The registry keys are saved correctly on flash disk, so the control panel
settings are kept after the reset, but seems are not applied at startup.
Can anyone help me, please?

Thanks in advance

Stefano Bianconi

Valter
Wed Apr 09 06:46:05 PDT 2008

=?Utf-8?B?U3RlZmFubyBCaWFuY29uaQ==?= <Stefano
Bianconi@discussions.microsoft.com> wrote in
news:7536871E-016F-409F-B575-708B06267C26@microsoft.com:

> I'm working on a board with WinCE 5.0 that use pxa270 and ucb1400,
> the audio working fine and through the control panel I can set the
> audio volume correctly.
>
> I have a problem after a reset, the volmue registry settings are
> ignored and the audio volume start always as maximum level.
> The registry keys are saved correctly on flash disk, so the
> control panel settings are kept after the reset, but seems are not
> applied at startup. Can anyone help me, please?
>
> Thanks in advance
>
> Stefano Bianconi
>

The first thing you can do is build a debug image and put a breakpoint
where the WPDM_SETVOLUME message is passed to your PDD (if you are
using the mainstoneII wav driver).
If it's not called, you may need to add your code to read it and
update the volume when the driver is loaded.
If it's called with the wrong parameters you may try to move up in the
call stack and understand why you get the wrong values. It may be that
your wav device is loaded during the first boot phase (it's \drivers
\builtin key is inside a HIVE BOOT SECTION) and so it can't access the
information stored in the hive-registry. There's no point in loading
that driver in the fist booth phase, I think, but it may have been
included there by mistake.

--
Valter Minute
www.fortechembeddedlabs.it
Training, support and development for Windows CE
(the reply address of this message is invalid)

StefanoBianconi
Fri Apr 11 08:22:05 PDT 2008

Thanks Valter,
I'm finally found the problem, it's related to our BSP because loading
touch.dll driver preform a cold reset on the UCB1400.

Regards
Stefano


"Valter Minute" wrote:

> =?Utf-8?B?U3RlZmFubyBCaWFuY29uaQ==?= <Stefano
> Bianconi@discussions.microsoft.com> wrote in
> news:7536871E-016F-409F-B575-708B06267C26@microsoft.com:
>
> > I'm working on a board with WinCE 5.0 that use pxa270 and ucb1400,
> > the audio working fine and through the control panel I can set the
> > audio volume correctly.
> >
> > I have a problem after a reset, the volmue registry settings are
> > ignored and the audio volume start always as maximum level.
> > The registry keys are saved correctly on flash disk, so the
> > control panel settings are kept after the reset, but seems are not
> > applied at startup. Can anyone help me, please?
> >
> > Thanks in advance
> >
> > Stefano Bianconi
> >
>
> The first thing you can do is build a debug image and put a breakpoint
> where the WPDM_SETVOLUME message is passed to your PDD (if you are
> using the mainstoneII wav driver).
> If it's not called, you may need to add your code to read it and
> update the volume when the driver is loaded.
> If it's called with the wrong parameters you may try to move up in the
> call stack and understand why you get the wrong values. It may be that
> your wav device is loaded during the first boot phase (it's \drivers
> \builtin key is inside a HIVE BOOT SECTION) and so it can't access the
> information stored in the hive-registry. There's no point in loading
> that driver in the fist booth phase, I think, but it may have been
> included there by mistake.
>
> --
> Valter Minute
> www.fortechembeddedlabs.it
> Training, support and development for Windows CE
> (the reply address of this message is invalid)
>