Wolfgang Grandegger wrote: > Luotao Fu wrote: >> Hi Wolfgang, >> >> On Wed, Nov 04, 2009 at 09:30:18AM +0100, Wolfgang Grandegger wrote: >>> Luotao Fu wrote: >>>> Hi, >>>> >>>> On Wed, Nov 04, 2009 at 09:13:03AM +0100, Wolfgang Grandegger wrote: >>>>> Luotao Fu wrote: >>>>>> Hi Wolfgang, >>>>>> >> .... >>>> ? I'm a little confused, just for the record: You called >>>> ifconfig can2 down >>>> before you brought up the interface? >>> No, because the module was just loaded. But even if I do a "ifconfig >>> can2 down", it will fail. >>> >> init_mode (slprq | initrq) is set while the interface is shut down. This >> is the place where the warning comes from. >> >>>> No. The slprq will eventually fail if there're irregular activities on >>>> the bus, like a opposite with wrong baudrate keep resending its stuffs. >>> On my board, it always fails! Even without any traffic on the bus. >> This is really strange, I can't reproduce this on my board here. >> >> # /sbin/ip link set can1 type can bitrate 125000 >> [ 215.118944] mpc52xx_can f0000980.can: setting BTR0=0x15 BTR1=0x18 >> # ifconfig can1 down >> # ifconfig can1 up >> # >> >> Btw. the platform I'm working on is a 1.4 >> # cat /proc/cpuinfo | grep revision >> revision : 1.4 (pvr 8082 2014) >> I will try to do some tests on another mpc5200b hardware here also later >> today. > > As I already said, I use an old MPC5200 (without *B*). Will try later > today with a MPC5200B.
I switched to "MPC5200B v2.2, Core v1.4 at 396 MHz" and the problem does *not* show up any more. Before I used a "MPC5200 v1.2, Core v1.1 at 396 MHz". Now I remember vaguely, that I was indeed fighting with this strange behavior. The manual instructs to enter sleep mode first and thereafter the init mode, but as that did'nt work, sleep and init are set in one step. Maybe we simply do s/dev_err/dev_dbg/. What do you think? Wolfgang, _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
