How can I chek the "Timer" of the operating system

Hello,

I’m working with a TOTAL5200SDP.
On my host PC I have installed QNX6.3.0 and on the Total5200SDP I have
installed the OS QNX6.3.0. But these OS I’ve got from Freescale.

I want to receive CAN massages and there are my problems. It isn’t
working.

In my programm I use the function MsgReceivePulse().
If I run the my programm, it goes into the function MsgReceivePulse()
but it don’t leave the function!

I think there are some troubles with the “Timer” of the OS !
! !

I need some commands with which I can chek the “Timer” of
the OS.

Who can tell me how can I chek it ? ? ?

Thanks,

wowtschik

wowtschik wrote:

Hello,

I’m working with a TOTAL5200SDP.
On my host PC I have installed QNX6.3.0 and on the Total5200SDP I have
installed the OS QNX6.3.0. But these OS I’ve got from Freescale.

I want to receive CAN massages and there are my problems. It isn’t
working.

In my programm I use the function MsgReceivePulse().
If I run the my programm, it goes into the function MsgReceivePulse()
but it don’t leave the function!

That’s because the resource manager isn’t sending a notification pulse
because there isn’t received a single CAN frame.

You should know that because the receive FIFO is always empty!!

I think there are some troubles with the “Timer” of the OS !
! !

There is absolutely no “Timer” involved !

Did you check the bus cable ???

–Armin

I need some commands with which I can chek the “Timer” of
the OS.

Who can tell me how can I chek it ? ? ?

Thanks,

wowtschik

The bus cable is OK!!!

So the problem is either in the BSP or the hardware.
Is taht right?

But one thing I don’t understand!
If the function MsgReceivePulse don’t get a notify impuls. But the
programm must leave the function (MsgReceivePulse)
after some time is ago. Is that correct?
In the help contents of QNX there is written in the description of the
function MsgReceivePulse() under the point ERRORS:

The function MsgReceivePulse returns ETIMEDOUT → A kernel timeout
unblocked the call.

wowtschik wrote:

The bus cable is OK!!!

So the problem is either in the BSP or the hardware.
Is taht right?

Please check it …

But one thing I don’t understand!
If the function MsgReceivePulse don’t get a notify impuls. But the
programm must leave the function (MsgReceivePulse)
after some time is ago. Is that correct?
In the help contents of QNX there is written in the description of the
function MsgReceivePulse() under the point ERRORS:

The function MsgReceivePulse returns ETIMEDOUT → A kernel timeout
unblocked the call.

That happens only if you have setup a kernel timeout …

–Armin

“wowtschik” <wowa1981@arcor-dot-de.no-spam.invalid> wrote in message
news:e8lb90$h2p$1@inn.qnx.com

The bus cable is OK!!!

So the problem is either in the BSP or the hardware.
Is taht right?

But one thing I don’t understand!
If the function MsgReceivePulse don’t get a notify impuls. But the
programm must leave the function (MsgReceivePulse)
after some time is ago. Is that correct?
In the help contents of QNX there is written in the description of the
function MsgReceivePulse() under the point ERRORS:

The function MsgReceivePulse returns ETIMEDOUT → A kernel timeout
unblocked the call.

Yes but a timeout must be setup which by default isn’t. If MsgReceivePulse
doesn’t return it’s because it has not received a pulse.

\