Here's one possible problem:
> > SysTaskDelay(30*SysTicksPerSecond()/1000);
on most SysTicksPerSecond = 60
SysTaskDelay takes an Int32
Thus 30*60/1000 = 1 not 1.8 or 2 so your delay will always be too short.
If your break signal duration is not critical, try normalizing the value you
pass to SysTaskDelay to the next whole integer value.
----- Original Message -----
From: "Alessandro Zummo" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Friday, September 19, 2003 9:15 AM
Subject: Re: Using Break Signal - Serial Manager
> On Fri, 19 Sep 2003 08:41:28 -0300
> [EMAIL PROTECTED] wrote:
>
> > I'm using the srmControl with srmCtlStartBreak and srmCtlStopBreak,
> > unfortunately, I didn't get a consistent break signal with it.
> >
> > Here is my code :
> >
> > if (blnBreak) {
> >
> > error = SrmControl(gPortID, srmCtlStartBreak, 0,&flagsSize);
> >
> > SysTaskDelay(30*SysTicksPerSecond()/1000);
> >
> > error = SrmControl(gPortID, srmCtlStopBreak, 0,&flagsSize);
> >
> > }
>
>
> We had problems on the m125. Check the value your are passing to
SysTaskDelay()
> and maybe increase it a little bit.
>
> Which Palm(s) are you targeting?
>
> --
>
> Best regards,
>
> Alessandro Zummo,
> Tower Technologies - Turin, Italy
>
> http://www.towertech.it
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
