Re: issues with at86rf212b transceiver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

2018-02-18 14:04 GMT-05:00  <anton@xxxxxxxxxxx>:
> On Sun, Feb 18, 2018 at 10:50:57AM -0500, Alexander Aring wrote:
>> >
>> > Check your wiring, make a lower spi clock (Maybe we should make the
>> > clock at the devicetree documentation lower).
>> >
>> > But... this messages should not happen unless something is broken.
>> >
>>
>> You can try to read registers with debugfs and regmap entry... and
>> look if the registers are the same as hw_init in the driver... if not
>> something weird going on e.g. lossy connection, too high spi-clock,
>> magnetic field, moon position, etc.
>>
>> - Alex
>
> I set SPI clock to 500 000, still have
>
> at86rf230 spi32765.0: not supported irq 00 received
>
> probably it is an IRQ pin wiring issue, not SPI frequency.
>
> I am trying to do wpan-ping and ping over IPv6,
> ping values seem too high for devices located on the same table
> and IPv6 ping has more than double RTT time, maybe it is due to
> protocol overhead and so on, but does 45ms for wpan-ping look normal?
>
>
> # wpan-ping -a 0x0002
> PING 0x0002 (PAN ID 0xbeef) 5 data bytes
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> 5 bytes from 0x0002 seq=0 time=59.9 ms
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> 5 bytes from 0x0002 seq=1 time=44.5 ms
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> 5 bytes from 0x0002 seq=2 time=59.8 ms
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> 5 bytes from 0x0002 seq=3 time=57.9 ms
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> 5 bytes from 0x0002 seq=4 time=47.0 ms
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> 5 bytes from 0x0002 seq=5 time=57.9 ms
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> 5 bytes from 0x0002 seq=6 time=43.6 ms
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> # at86rf230 spi32765.0: not supported irq 00 received
>
> # ping -6 fe80::bcef:ff:fe00:2%lowpan0at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
>
> PING fe80::bcef:ff:fe00:2%lowpan0(fe80::bcef:ff:fe00:2) 56 data bytes
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> 64 bytes from fe80::bcef:ff:fe00:2: icmp_seq=2 ttl=64 time=105 ms
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> 64 bytes from fe80::bcef:ff:fe00:2: icmp_seq=3 ttl=64 time=109 ms
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> 64 bytes from fe80::bcef:ff:fe00:2: icmp_seq=4 ttl=64 time=109 ms
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> 64 bytes from fe80::bcef:ff:fe00:2: icmp_seq=5 ttl=64 time=114 ms
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> ^C
> --- fe80::bcef:ff:fe00:2%lowpan0 ping statistics ---
> 6 packets transmitted, 4 received, 33% packet loss, time 5033ms
> rtt min/avg/max/mdev = 105.572/109.775/114.680/3.239 ms
> # at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received
> at86rf230 spi32765.0: not supported irq 00 received

definitely the irq line, it is triggered and IRQ_STATUS says "no irq
signaled". This is cleaned only if you read irq stats out.

- Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux