Hi Wolfgang,
Thanks for the reply.
>> I'm using the at91_can driver on a custom board. The following
sequence
>> seems to cause the driver to hit a flood of error frames:
>
> $ ifconfig can0 down ? See below.
"ifconfig can0 down" results in an "unknown host" error. The output of
"ifconfig can0" is:
can0 Link encap:(hwtype unknown)
UP RUNNING NOARP MTU:16
txqueuelen:10
I'm using ifconfig from inetutils 1.5.
>> *snip*
>> (1259913144.766140) can0 20000020#0000000000000000
>
> Wired, I would expect error messages here. Looks like a separate
issue.
Driver-level or user-level?
>> The syslog output is also revealing, indicating a flood of "AERR irq"
>> errors.
> OK.
Is this a problem or expected? CONFIG_CAN_DEBUG is on, in case it
matters.
> The bit-rate error is rather high due to ...
>> clock 99328000
> this exotic clock frequency. Is it really correct?
Yes, this is the correct clock. We're running our AT91SAM9263 around
200 MHz -- keyword "around". It's actually more like 198 MHz, and the
1/2 clock becomes around 99 MHz.
> I suspect CAN bus errors due to improper bit-timing parameters.
OK, I'll try tweaking all these to see where we get.
Thanks again!
Chris
_______________________________________________
Socketcan-core mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-core
