2011/1/13 Wolfgang Grandegger <w...@grandegger.com> > On 01/13/2011 12:25 AM, Willy Lambert wrote: > > 2011/1/12 Willy Lambert <lambert.wi...@gmail.com> > > > >> Because after lots of tests of moving jumpers it ended in this config. > As I > >> don't have serial yet it should work no ? Anyway I'll change because it > is > >> not an accurate choice > >> > >> 2011/1/12 Wolfgang Grandegger <w...@grandegger.com> > >> > >> Hi Willy, > >>> > >>> On 01/12/2011 01:55 AM, Willy Lambert wrote: > >>>> Hi all, > >>>> > >>>> for memory I have been trying to makes socketCan working on my Ixxat > >>> board > >>>> for some time. It is stacked on a PC104 cpu module with a linux debian > >>>> squeeze. After having a fully hardware configuration (a proper node + > >>> can > >>>> analyser) I tried Ixxat drivers and succeed after soldering a jumper > on > >>> the > >>>> board and setting some BIOS values. After this I quickly tested a > >>> socketCan > >>>> version from svn and it seems to works (at least interrupts were > >>> triggered). > >>>> > >>>> Cleaning time arrived and I complety reinstall the linux with only the > >>>> required kernel configuration. The choosed kernel is a 2.6.35.7. > >>>> My first question is : may I use kernel official sources of socketCan > ? > >>> or > >>>> do I need to checkout something ? > >>>> > >>>> I activated theses options : > >>>> > >>>>> [*] Networking Support --> > >>>>> --- [*] CAN bus subsystem support --> > >>>>> ----------[*] Raw Can Protocol (raw access with CAN-ID filtering) > >>>>> ----------[*] Broadcast Manager CAN Protocol (with content filtering) > >>>>> ---------- CAN Device Drivers ---> > >>>>> ----------------- [*] Virtual Local CAN Interface (vcan) > >>>>> ----------------- [*] Platform CAN drivers with Netlonk support > >>>>> ----------------- [*] CAN bit-timing calculation > >>>>> ----------------- [*] Philips/NXP SJA1000 devices --> > >>>>> -------------------------[M] ISA Bus based legacy SJA1000 driver > >>>>> > >>>> All remark is welcome (espacially if I need to choose "M" instead of > "*" > > If you select "M", the drive will be built as module otherwise it's > statically linked into the kernel. > > > Is this usable from the current 2.6.35.7 official Linux tree ? or do I > need > > other sources ? > > Should be fine. > > >>> I setup my can0 interface in the rc.local script : > >>>> > >>>>> modprobe sja1000_isa irq=3 mem=0XD0000 > >>> > >>> Why do you use irq=3 now. IIRC, it's used for the serial port. Why not > >>> irq=5? > >>> > >> > > same with irq5. I have the same problem with Ixxat drivers. so it's again > an > > interrupt problem. Do I need to activate some option into the kernel ? > > I'm a bit confused. What is the current status of using CAN on you > system. Does the BCI driver from IXXAT now work properly? >
So am I :) I reinstalled Ixxat drivers and manage to find my a working state for both Ixxat and SocketCan drivers. A missed a jumper positionning and had some BIOS problems. In conclusion I have : _ a proper HW wiring and 2nd node _ a particular IRQ jumper working configuration on my board _ a particuliar BIOS config with uncertainty about what option made things working. _ a brand new 2.6.35.7 system with only the few required kernel options to made things working. I will now test BIOS options one by one to check which are required, change IRQs to test several configuration, test the second CAN controller and set up a test case with canplayer. I will report this as soon as i finished. > > Wolfgang. >
_______________________________________________ Socketcan-users mailing list Socketcan-users@lists.berlios.de https://lists.berlios.de/mailman/listinfo/socketcan-users
