[ts-7000] Re: CAN Bus access.

["Loren M. Lang" <>]

Loren M. Lang wrote:
<snip>
> Then
> after write() the following message appear:
>
> can.o: Error: status register: 0x20 irq_register: 0x80 error: 0x03
> can.o: Error: status register: 0x60 irq_register: 0x84 error: 0x11
> can.o: Error: status register: 0x60 irq_register: 0xa0 error: 0x11
> can.o: Error: status register: 0x60 irq_register: 0x80 error: 0x03
> can.o: Error: status register: 0x60 irq_register: 0x80 error: 0x03
> <last line repeated many times>
> can.o: Error: status register: 0xd4 irq_register: 0x04 error: 0x03
> can.o: bus-off, resetting sja1000p
> can.o: Error: status register: 0xb4 irq_register: 0x04 error: 0x00
> can.o: bus-off, resetting sja1000p
> can.o: Error: status register: 0x34 irq_register: 0x04 error: 0x00
>
> Once those messages appear, further read() return the error Resource not
> available.
Err, that error message was caused by a programming glitch.  In
non-blocking I/O read() always return EAGAIN as if there was no I/O
detected on the CAN bus, but the write() still causes the above kernel
messages everytime it is called.


--
Loren M. Lang

http://www.north-winds.org/


Public Key: ftp://ftp.north-winds.org/pub/lorenl_pubkey.asc
Fingerprint: CEE1 AAE2 F66C 59B5 34CA  C415 6D35 E847 0118 A3D2

signature.asc
Description: OpenPGP digital signature