Hi,

I am porting the mainstoneii serial driver to my platform (wince5, pxa270
based on mainstoneii) for FFUART.
I enable the interrupt as

GetRegister()->Write_IER(bIER | BUL_SERIAL_IER_UUE);

When the serial driver load, after it excuted the above function, there is a
lot of event message print infinitely.

0x87d5e000: ms2_serial:IsDebugSerialPort(x40100000): BSP_ARGS@x000d0000,
dbgSerPhysAddr=x40700000
0x87d5e000: Will Go inside CBulPdd16550::Init()
0x87d5e000: No DMA Support
0x87d5e000: Configuring Pinout
0x87d5e000: Enable FFUART Clock
0x87d5e000: Enable interrupts and UART to take care of rx data without
COM_Open().
0x87d5e000: Postinit - EN Interrupt
0x87d14400: #### EV_CTS changed####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### MS_RLSD_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### MS_RLSD_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### MS_RLSD_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### MS_RLSD_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### MS_RLSD_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### MS_RLSD_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### MS_RLSD_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### MS_RLSD_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### MS_RLSD_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### MS_RLSD_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####
0x87d14400: #### MS_RLSD_ON ####
0x87d14400: #### EV_RLSD changed####
0x87d14400: #### MS_CTS_ON ####

Is there something wrong in my BSP or the hardware itself?

Best regards,
J

Re: ms_serial driver by Luca

Luca
Sun Jun 08 22:52:44 PDT 2008

Is your serial port connetced to some hardware (maybe a modem)? It looks
like someone is toggling
some signals

--

Luca Calligaris
www.eurotech.it

"JamesCool" <u42351@uwe> ha scritto nel messaggio news:8536b5f255b66@uwe...
> Hi,
>
> I am porting the mainstoneii serial driver to my platform (wince5, pxa270
> based on mainstoneii) for FFUART.
> I enable the interrupt as
>
> GetRegister()->Write_IER(bIER | BUL_SERIAL_IER_UUE);
>
> When the serial driver load, after it excuted the above function, there is
> a
> lot of event message print infinitely.
>
> 0x87d5e000: ms2_serial:IsDebugSerialPort(x40100000): BSP_ARGS@x000d0000,
> dbgSerPhysAddr=x40700000
> 0x87d5e000: Will Go inside CBulPdd16550::Init()
> 0x87d5e000: No DMA Support
> 0x87d5e000: Configuring Pinout
> 0x87d5e000: Enable FFUART Clock
> 0x87d5e000: Enable interrupts and UART to take care of rx data without
> COM_Open().
> 0x87d5e000: Postinit - EN Interrupt
> 0x87d14400: #### EV_CTS changed####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### MS_RLSD_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### MS_RLSD_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### MS_RLSD_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### MS_RLSD_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### MS_RLSD_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### MS_RLSD_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### MS_RLSD_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### MS_RLSD_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### MS_RLSD_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### MS_RLSD_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
> 0x87d14400: #### MS_RLSD_ON ####
> 0x87d14400: #### EV_RLSD changed####
> 0x87d14400: #### MS_CTS_ON ####
>
> Is there something wrong in my BSP or the hardware itself?
>
> Best regards,
> J



Re: ms_serial driver by Valter

Valter
Mon Jun 09 01:20:43 PDT 2008

"JamesCool" <u42351@uwe> wrote in news:8536b5f255b66@uwe:

> Hi,
> I am porting the mainstoneii serial driver to my platform (wince5,
> pxa270 based on mainstoneii) for FFUART.
> I enable the interrupt as
>
[...]
> Is there something wrong in my BSP or the hardware itself?


Check that the GPIO pins used for the serial port signals are
configured in the right way (you may use different pins for the
serial port on the PXA and it may be that your board don't use the
same pins the original mainstone II board does).
Check also that you don't have other devices connected to some
serial pins that you considered as unused (you may use FFUART as a
simple TX-RX serial port but you should assign the right alternate
functions to the other pins or set their AF to 0 if they are used
for direct I/O).
Check also that your interrupt handling code cleans-up all the
pending interrupt requests or you may get a new interrupt
immediately after you re-enable it calling InterruptDone.


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