PEAK-System Forum

Hi,

Good news! The problem has been solved. This is mainly caused by the following two reasons:
· shared interrupt (should be enabled in kernel)
· VT-D option in (should be disabled in bios)

Thanks a lot for your helps.

Regards.

Hi, Stéphane

I have send an Email to linux@peak-system.com.

Today, we found it seems to be the irq problem, because the irq process for rtcan is not successful when using the command

$ cat /proc/interrupt.

We can not find the corresponding irq number. But in non-RT linux, can0 & can1 irq can ...

Hi, Stéphane

Bios options for VT-D and PCI-E are both setted.

So would you like to tell me what is the configuration of your tested system, e.g., linux kernel, xenomai kernel, and menuconfig options.

We have been strucked here for a long time. In non-RT linux systems, using can-uitls for the ...

Thank you,

I have disabled Intel VT for Directed I/O technology in the BIOS. But it still doesnot work.

We have tested on two computers:

· EPIC-KBS9, i5-7650, x8, mSATA/Mini-PCIe Full Size x 1 (Default: mSATA, Optional for Mini-PCIe by BOM Change)
· UP2, N4200, x4, Intel HD Graphics 505 ...

Again, type the dmesg when failing to send data:

[ 429.981561] perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
[ 441.533958] DMAR: DRHD: handling fault status reg 2
[ 441.533977] DMAR: [INTR-REMAP] Request device [fa:1f.0] fault index 0 [fault ...

Thanks a lot,

We have do the following test with your suggestions:

1. Enable the shared interrupt

$ grep CONFIG_XENO_OPT_SHIRQ /boot/config-`uname -r`
CONFIG_XENO_OPT_SHIRQ=y


2. The can device can be registered successfully:

$ dmesg | grep EAK
[ 3.413147] PEAK-PCI-CAN: initializing device ...

Thank you,

So if we should enable the shared interrupt ?

To the 'rtcansend' & 'rtcanrecv' command, we have tested with the specified CAN ID.

For the first call of 'rtcansend' command, with the instructioin
./rtcansend rtcan0 -i x 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 -v
data seems to send ...

*******- RT-socket-CAN which is not related to the pcan driver******
In the first post, we want to use RT-socket-CAN under xenomai, which is integrated in xenomai kernal. But it fails to send/receive datas. Testing steps are listed in post 1. We have enable the shared interrupts, since disable the ...

Thank you, Stéphane:

Acutally, we want to use the miniPCIe PEAK-CAN device in Xenomai3.0.5. That is the first post want to be solved.

RTCAN device is failed to register when disable the shared interrupt in Xenomai core features.

If we enable the shared interrupt option, RTCAN can be registered ...

Sorry, the first picture