Hi, 2018-02-18 12:36 GMT-05:00 <anton@xxxxxxxxxxx>: >> >> >> > >> > This messages confused me, it should not happen unless you >> > reading/writing garbage on SPI bus. >> > We only use IRQ TRX_END and we are sure that we only receive these >> > IRQs by IRQ_MASK_MODE and IRQ_MASK. >> > >> > 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 > > Okay, seems like hardware issue, wiring and connectors on the devboard > are not high frequency friendly. > > I tried to lower spi frequency from 7.5MHz to 4, then 2 and 1. > Most messages disappeared after switching to 4MHz, > but there were still these ones > > at86rf230 spi32765.0: not supported irq 80 received > at86rf230 spi32765.0: not supported irq 00 received > at86rf230 spi32765.0: not supported irq 00 received > > After switching to 1MHz I got only these ones, but > many of them, probably one per packet or more > > 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 > > Now I am able to do wpan-ping and even ssh over IPv6 > from one device to another. Thanks for your advices. > ok. > Now question is, what is the lowest possible spi frequency > still suitable for data transfers at 40kbps? > datasheet doesn't say anything about lowest frequency... > I also tried to change IRQ pin bias settings in device tree > from "bias-disable" to "bias-pull-down", I thought maybe there > are spurious interrupts triggered by interference, but it did not > help. > I suppose your spi controller is buggy, we had the same with the rpi kernel and mainline rpi was always working fine. I getting boring, always people have spi hardware issues and complaining here. We don't/can't fix these issues... - 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