Hi, >> Is there a possibility that there is some loopback route which gets >> messages intot he buffer which are NOT on the physical bus? > > Yes, of course. You have enabled the TX loopback feature via kernel option: > > config XENO_DRIVERS_CAN_TX_LOOPBACK > depends on XENO_DRIVERS_CAN > bool "Enable TX loopback to local sockets" > default n > help > > This options adds support for TX loopback to local sockets. > Normally, > messages sent to the CAN bus are not visible to sockets > listening to > the same local device. When this option is enabled, TX messages are > looped back locally when the transmit has been done by default. > This > behaviour can be deactivated or reactivated with "setsockopt". I'll have a look. But I understnad you correctly that even if I have activated the loopback behaviour in the kernel I can deactivate at runtime with setsockopt?
I still don;t see why this would generate overflows in the case when i only have one socket active? For the case that there are still lingering sockets which have not been closed it is obvious. > TX_Lo tell you that TX messages are loopback to local sockets. I'll turn this off in the morning if i can figure out how to with setsockopt. Thanks a-plenty! Roland > > Wolfgang. > > _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
