I am still trying to setup my can interface. From last time I have wired a resistively correct bus with my motor and manage to find a can analyser. For information, as my motor as a 0xFF nodeID and automatic baudrate detection by default which means that I still need to configure it to a proper nodeID and baudrate before I can put it on the bus.
I would like to try both socketCan and Ixxat drivers with the can analyser so I am preparing this a bit and I remark this : ISA adress range is not the same with ixxat and socket can drivers : --> here is Ixxat adresses which seems correct : d0000 to d0fff > > r...@alpha:/opt/ard/bin# cat /proc/iomem > 00000000-0000ffff : reserved > 00010000-0009fbff : System RAM > 0009fc00-0009ffff : reserved > 000a0000-000bffff : Video RAM area > 000c0000-000c7fff : Video ROM > 000d0000-000d0fff : PCI-I03 ISA [0] DPRAM area > --> here is SocketCan which seems incorrect : d0000 to d001f > r...@alpha:/opt/ard/bin# cat /proc/iomem > 00000000-0000ffff : reserved > 00010000-0009fbff : System RAM > 0009fc00-0009ffff : reserved > 000a0000-000bffff : Video RAM area > 000c0000-000c7fff : Video ROM > 000d0000-000d001f : sja1000_isa > 000e0000-000fffff : reserved > Maybe something stands behind this ? --------------------------------------------------------------------------------------------------------------------------- complementary informations for the curious dmesg for Ixxat drivers : > [ 2252.093040] can: controller area network core (rev 20090105 abi 8) > [ 2252.093112] NET: Registered protocol family 29 > [ 2252.100195] can: raw protocol (rev 20090105) > [ 2252.108650] can: broadcast manager protocol (rev 20090105 t) > [ 2252.115236] sja1000 CAN netdevice driver > [ 2252.120307] KINF: CAN PC-I driver v4.1b for BCI v4.5.8 Compiled Nov 22 > 2010 at 00:30:34 > [ 2252.120529] KINF: Device registered successfully for 2 ports. Major > [250] > [ 2252.120700] KINF: IRQ number [5] registered > [ 2252.120846] KINF: IRQ will be not registered for port 1 > [ 2811.803121] KINF: IRQ number [5] freed for port 0 > [ 2811.803146] KINF: IRQ number [0] for port 1 was not registered! Do > nothing. > [ 2811.803155] KINF: Character device unregistered successfully. Major > [250] > [ 2811.827665] sja1000: driver removed > [ 2811.860547] NET: Unregistered protocol family 29 > /proc/interrupts for Ixxat drivers > r...@alpha:/opt/ard/bin# cat /proc/interrupts > CPU0 CPU1 > 0: 6901 7463 IO-APIC-edge timer > 1: 1667 998 IO-APIC-edge i8042 > 5: 0 0 IO-APIC-edge PCI-I03 ISA Port 0 > 8: 0 1 IO-APIC-edge rtc0 > 9: 0 0 IO-APIC-fasteoi acpi > 14: 0 0 IO-APIC-edge ata_piix > 15: 1211 1215 IO-APIC-edge ata_piix > 19: 0 0 IO-APIC-fasteoi uhci_hcd:usb3 > 23: 0 0 IO-APIC-fasteoi ehci_hcd:usb1, > uhci_hcd:usb2 > 24: 9687 9687 PCI-MSI-edge eth0 > NMI: 0 0 Non-maskable interrupts > LOC: 4004 4529 Local timer interrupts > SPU: 0 0 Spurious interrupts > PMI: 0 0 Performance monitoring interrupts > PND: 0 0 Performance pending work > RES: 131 159 Rescheduling interrupts > CAL: 8 20 Function call interrupts > TLB: 143 100 TLB shootdowns > TRM: 0 0 Thermal event interrupts > THR: 0 0 Threshold APIC interrupts > MCE: 0 0 Machine check exceptions > MCP: 10 10 Machine check polls > ERR: 1 > MIS: 0 > dmesg for socketCan drivers : > [ 2969.292003] can: controller area network core (rev 20090105 abi 8) > [ 2969.292101] NET: Registered protocol family 29 > [ 2969.299121] can: raw protocol (rev 20090105) > [ 2969.307471] can: broadcast manager protocol (rev 20090105 t) > [ 2969.313987] sja1000 CAN netdevice driver > [ 2969.319597] sja1000_isa sja1000_isa.0: sja1000_isa device registered > (reg_base=0xc00d0000, irq=5) > [ 2969.325516] Legacy sja1000_isa driver for max. 8 devices registered > [ 2969.329204] sja1000_isa sja1000_isa.0: setting BTR0=0x01 BTR1=0x1c > /proc/interrupts for socketCan drivers > r...@alpha:/opt/ard/bin# cat /proc/interrupts > CPU0 CPU1 > 0: 7662 8194 IO-APIC-edge timer > 1: 1667 998 IO-APIC-edge i8042 > 5: 0 0 IO-APIC-edge can0 > 8: 0 1 IO-APIC-edge rtc0 > 9: 0 0 IO-APIC-fasteoi acpi > 14: 0 0 IO-APIC-edge ata_piix > 15: 1221 1226 IO-APIC-edge ata_piix > 19: 0 0 IO-APIC-fasteoi uhci_hcd:usb3 > 23: 0 0 IO-APIC-fasteoi ehci_hcd:usb1, > uhci_hcd:usb2 > 24: 9949 9977 PCI-MSI-edge eth0 > NMI: 0 0 Non-maskable interrupts > LOC: 4296 4865 Local timer interrupts > SPU: 0 0 Spurious interrupts > PMI: 0 0 Performance monitoring interrupts > PND: 0 0 Performance pending work > RES: 145 164 Rescheduling interrupts > CAL: 9 20 Function call interrupts > TLB: 144 100 TLB shootdowns > TRM: 0 0 Thermal event interrupts > THR: 0 0 Threshold APIC interrupts > MCE: 0 0 Machine check exceptions > MCP: 11 11 Machine check polls > ERR: 1 > MIS: 0 > r...@alpha:/opt/ard/bin# > 2010/11/15 Willy Lambert <[email protected]> > Ok thanks for all Wolfang, you are an angel to deal my request with such > efficiency. > > I am already waiting for an answer from Ixxat. > I will check resistors terminaisons > I will manage to record something with an analyzer, could you describe what > should I look at ? Just messages ? Particular messages like Emergency ? > Heartbits ? > > and I will inform you about this. > > Is there any chance that rtCan drivers manage this hardware better ? > Because we were firstly going to use a xenomai kernel and then turn back > into a nature one for planning issues. As we need the can interface to go > on, it is possible to change this. > > > 2010/11/15 Wolfgang Grandegger <[email protected]> > >> On 11/15/2010 08:55 PM, Willy Lambert wrote: >> >> > Arg, I can't read German (at least not Technical German) so I makes >> things >> > more complicate for me :) >> >> Well, apart from the OCR setting, this document is not really useful. >> >> > I am going to read this. It makes me thinking about time quantas as >> describe >> > in Documentation/networking/can.txt: >> > >> > 708 < >> http://www.mjmwired.net/kernel/Documentation/networking/can.txt#708> >> > "tq 125 prop-seg 6 phase-seg1 7 phase-seg2 2 sjw 1" >> > 709 < >> http://www.mjmwired.net/kernel/Documentation/networking/can.txt#709> >> Shows >> > the time quanta in ns, propagation segment, phase buffer >> > 710 < >> http://www.mjmwired.net/kernel/Documentation/networking/can.txt#710> >> segment >> > 1 and 2 and the synchronisation jump width in units of >> > 711 < >> http://www.mjmwired.net/kernel/Documentation/networking/can.txt#711> >> tq. >> > They allow to define the CAN bit-timing in a hardware >> > 712 < >> http://www.mjmwired.net/kernel/Documentation/networking/can.txt#712> >> independent >> > format as proposed by the Bosch CAN 2.0 spec (see >> > 713 < >> http://www.mjmwired.net/kernel/Documentation/networking/can.txt#713> >> chapter >> > 8 of http://www.semiconductors.bosch.de/pdf/can2spec.pdf). >> > >> > >> > Could I have something to precise after defining baudrate ? >> >> No. If the chips is mapped correctly, it should work like with any other >> SJA1000 hardware. >> >> To be honest, I'm not even sure if this IXXAT card is supported properly >> by the sja1000_isa driver. I still think there is a problem with the irq >> setup or the ocr and cdr setting. Or it needs some special treatment. >> You could try contacting the IXXAT service. Maybe they can tell you more. >> >> Also, a CAN analyzer would be useful. >> >> Wolfgang. >> > >
_______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
