XSC1BD serial driver

Hi All,

I'm a little confused about the Serial driver in the
XSC1BD BSP. I have placed debug statements in the
following functions:

OEMInterruptEnable()
OEMInterruptDisable()
OEMInterruptHandler()
OEMInterruptDone()

I added the USB Client and Serial drivers to my Platform
and I appear to be getting receive interrupts from USB
but not from Serial.

I also noticed that the Serial driver code never calls
the "InterruptInitialize()" function.

During initialisation (at startup), from USB I enter the
following functions:

**************OEMInterruptEnable: USB CLIENT.
**************OEMInterruptHandler: INTC_USB
**************OEMInterruptDone: SYSINTR_USB_CLIENT.
**************OEMInterruptHandler: INTC_USB
**************OEMInterruptDone: SYSINTR_USB_CLIENT.

But from serial (FFUART), I only get:
**************OEMInterruptEnable: SYSINTR_SERIAL.
**************OEMInterruptDone: SYSINTR_SERIAL.

How come a serial interrupt isn't automatically created
when "OEMInterruptEnable()" is called like for the USB
driver? Why doesn't the XSC1BD call
the "InterruptInitialize()" function? How does
the "OEMInterruptDone()" function get called without ever
entering the "OEMInterruptHandler()" function?

I can transmit out of the serial port but I cannot
receive any. Any help would be appreciated.

Cheers, Andrew

Mike
Tue Feb 10 02:28:27 CST 2004

Hi Andrew,

the "InterruptInitialize()" function for the serial port is called in the
mdd.c. The upper layer of the serial driver. The BSP only contains the lower
layer for the direct hardware accesses to the serial port (FFUART).
Regarding the Interrupt Handler, I think that when you read or write to the
serial port you should enter into the Interrupt Handler. Look in the debug
output if you van find something like (COM1:) ATTACH. Than the COM port
should working.

Best regrads,

Mike Engel

"Andrew" <anonymous@discussions.microsoft.com> escribió en el mensaje
news:d93001c3ef89$7604cd10$a401280a@phx.gbl...
> Hi All,
>
> I'm a little confused about the Serial driver in the
> XSC1BD BSP. I have placed debug statements in the
> following functions:
>
> OEMInterruptEnable()
> OEMInterruptDisable()
> OEMInterruptHandler()
> OEMInterruptDone()
>
> I added the USB Client and Serial drivers to my Platform
> and I appear to be getting receive interrupts from USB
> but not from Serial.
>
> I also noticed that the Serial driver code never calls
> the "InterruptInitialize()" function.
>
> During initialisation (at startup), from USB I enter the
> following functions:
>
> **************OEMInterruptEnable: USB CLIENT.
> **************OEMInterruptHandler: INTC_USB
> **************OEMInterruptDone: SYSINTR_USB_CLIENT.
> **************OEMInterruptHandler: INTC_USB
> **************OEMInterruptDone: SYSINTR_USB_CLIENT.
>
> But from serial (FFUART), I only get:
> **************OEMInterruptEnable: SYSINTR_SERIAL.
> **************OEMInterruptDone: SYSINTR_SERIAL.
>
> How come a serial interrupt isn't automatically created
> when "OEMInterruptEnable()" is called like for the USB
> driver? Why doesn't the XSC1BD call
> the "InterruptInitialize()" function? How does
> the "OEMInterruptDone()" function get called without ever
> entering the "OEMInterruptHandler()" function?
>
> I can transmit out of the serial port but I cannot
> receive any. Any help would be appreciated.
>
> Cheers, Andrew
>

Andrew
Wed Feb 11 00:08:56 CST 2004

Just to make sure I haven't done something stupid.

In my main batch file I have:
set BSP_DBGSER_UART1=3D
set BSP_NOSERIAL=3D

I assume this turns debug serial off so it won't=20
interfere with the serial driver.

I still find that only the FFUART is active and is=20
assigned com1 ((COM1:) ATTACH). The USB client is=20
assigned com2 ((COM2:) ATTACH). How do I get the BTUART=20
and STUART to operate?

Cheers, Andrew

>-----Original Message-----
>Hi Andrew,
>
>the "InterruptInitialize()" function for the serial port=20
is called in the
>mdd.c. The upper layer of the serial driver. The BSP=20
only contains the lower
>layer for the direct hardware accesses to the serial=20
port (FFUART).
>Regarding the Interrupt Handler, I think that when you=20
read or write to the
>serial port you should enter into the Interrupt Handler.=20
Look in the debug
>output if you van find something like (COM1:) ATTACH.=20
Than the COM port
>should working.
>
>Best regrads,
>
>Mike Engel
>
>"Andrew" <anonymous@discussions.microsoft.com> escribi=F3=20
en el mensaje
>news:d93001c3ef89$7604cd10$a401280a@phx.gbl...
>> Hi All,
>>
>> I'm a little confused about the Serial driver in the
>> XSC1BD BSP. I have placed debug statements in the
>> following functions:
>>
>> OEMInterruptEnable()
>> OEMInterruptDisable()
>> OEMInterruptHandler()
>> OEMInterruptDone()
>>
>> I added the USB Client and Serial drivers to my=20
Platform
>> and I appear to be getting receive interrupts from USB
>> but not from Serial.
>>
>> I also noticed that the Serial driver code never calls
>> the "InterruptInitialize()" function.
>>
>> During initialisation (at startup), from USB I enter=20
the
>> following functions:
>>
>> **************OEMInterruptEnable: USB CLIENT.
>> **************OEMInterruptHandler: INTC_USB
>> **************OEMInterruptDone: SYSINTR_USB_CLIENT.
>> **************OEMInterruptHandler: INTC_USB
>> **************OEMInterruptDone: SYSINTR_USB_CLIENT.
>>
>> But from serial (FFUART), I only get:
>> **************OEMInterruptEnable: SYSINTR_SERIAL.
>> **************OEMInterruptDone: SYSINTR_SERIAL.
>>
>> How come a serial interrupt isn't automatically created
>> when "OEMInterruptEnable()" is called like for the USB
>> driver? Why doesn't the XSC1BD call
>> the "InterruptInitialize()" function? How does
>> the "OEMInterruptDone()" function get called without=20
ever
>> entering the "OEMInterruptHandler()" function?
>>
>> I can transmit out of the serial port but I cannot
>> receive any. Any help would be appreciated.
>>
>> Cheers, Andrew
>>
>
>
>.
>

Mike
Wed Feb 11 04:22:24 CST 2004

Hi Andrew,

your settings are right. Have you checked in the reginit.ini, that the
registry settings for the BTUART are in your image?
The file is located in your project directory.

Cheers,

Mike Engel

"Andrew" <anonymous@discussions.microsoft.com> escribió en el mensaje
news:e7b501c3f065$88613160$a501280a@phx.gbl...
Just to make sure I haven't done something stupid.

In my main batch file I have:
set BSP_DBGSER_UART1=
set BSP_NOSERIAL=

I assume this turns debug serial off so it won't
interfere with the serial driver.

I still find that only the FFUART is active and is
assigned com1 ((COM1:) ATTACH). The USB client is
assigned com2 ((COM2:) ATTACH). How do I get the BTUART
and STUART to operate?

Cheers, Andrew

>-----Original Message-----
>Hi Andrew,
>
>the "InterruptInitialize()" function for the serial port
is called in the
>mdd.c. The upper layer of the serial driver. The BSP
only contains the lower
>layer for the direct hardware accesses to the serial
port (FFUART).
>Regarding the Interrupt Handler, I think that when you
read or write to the
>serial port you should enter into the Interrupt Handler.
Look in the debug
>output if you van find something like (COM1:) ATTACH.
Than the COM port
>should working.
>
>Best regrads,
>
>Mike Engel
>
>"Andrew" <anonymous@discussions.microsoft.com> escribió
en el mensaje
>news:d93001c3ef89$7604cd10$a401280a@phx.gbl...
>> Hi All,
>>
>> I'm a little confused about the Serial driver in the
>> XSC1BD BSP. I have placed debug statements in the
>> following functions:
>>
>> OEMInterruptEnable()
>> OEMInterruptDisable()
>> OEMInterruptHandler()
>> OEMInterruptDone()
>>
>> I added the USB Client and Serial drivers to my
Platform
>> and I appear to be getting receive interrupts from USB
>> but not from Serial.
>>
>> I also noticed that the Serial driver code never calls
>> the "InterruptInitialize()" function.
>>
>> During initialisation (at startup), from USB I enter
the
>> following functions:
>>
>> **************OEMInterruptEnable: USB CLIENT.
>> **************OEMInterruptHandler: INTC_USB
>> **************OEMInterruptDone: SYSINTR_USB_CLIENT.
>> **************OEMInterruptHandler: INTC_USB
>> **************OEMInterruptDone: SYSINTR_USB_CLIENT.
>>
>> But from serial (FFUART), I only get:
>> **************OEMInterruptEnable: SYSINTR_SERIAL.
>> **************OEMInterruptDone: SYSINTR_SERIAL.
>>
>> How come a serial interrupt isn't automatically created
>> when "OEMInterruptEnable()" is called like for the USB
>> driver? Why doesn't the XSC1BD call
>> the "InterruptInitialize()" function? How does
>> the "OEMInterruptDone()" function get called without
ever
>> entering the "OEMInterruptHandler()" function?
>>
>> I can transmit out of the serial port but I cannot
>> receive any. Any help would be appreciated.
>>
>> Cheers, Andrew
>>
>
>
>.
>