All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@domain.hid>
To: Daniel Schnell <daniel.schnell@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] RT-SocketCan + Xenomai on MPC5200B
Date: Tue, 07 Nov 2006 15:35:30 +0100	[thread overview]
Message-ID: <455099B2.5030402@domain.hid> (raw)
In-Reply-To: <DD39B5C3F4963040ADC9768BE7E430CB014DEFF0@domain.hid>

Daniel Schnell wrote:
> Wolfgang Grandegger wrote:
>  
>> The first message seems not to go out to the wire and the second send
>> blocks because the TX done interrupt of the first message has not yet
>> occured (no TX hardware slot free). Is there a CAN node able to
>> receive the message?   
> 
> Yes, there is an IO unit which normally reacts on that message
>  
>> Likely, you have a problem with your clock setting, TX/RX routing or
>> cabeling (termination etc.). 
> 
> 
> I would suspect it is the clock setting, as we have also problems with
> clock_nanosleep() running 4 times too fast. I assume then that the IPB
> clock frequency is wrong ?

On a Rev. B you normally set the CAN system clock to 33MHz via kernel 
configuration parameter. Is CAN TX/RX on PSC2?


> How do you setup your CAN network for a test ? Which commands do you use
> ?

Your setup with rtcanconfig was OK, or what do you mean.

Do you have terminators on both ends of the cable?

Wolfgang.



  reply	other threads:[~2006-11-07 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 13:43 [Xenomai-help] RT-SocketCan + Xenomai on MPC5200B Daniel Schnell
2006-11-07 14:03 ` Wolfgang Grandegger
2006-11-07 14:22   ` Daniel Schnell
2006-11-07 14:35     ` Wolfgang Grandegger [this message]
2006-11-07 14:45       ` Daniel Schnell
2006-11-07 20:31     ` Wolfgang Denk
     [not found] <ac3922a00611070616s6efa5e39wa8a2b849d9fc683b@domain.hid>
2006-11-07 14:39 ` Daniel Schnell
2006-11-07 15:02   ` Wolfgang Grandegger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=455099B2.5030402@domain.hid \
    --to=wg@domain.hid \
    --cc=daniel.schnell@domain.hid \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.