On 04/23/2015 05:37 AM, Alexander Aring wrote:
On Mon, Apr 20, 2015 at 02:04:48PM -0400, Michael C. Cambria wrote:
....
&spi1 {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&spi1_pins>;
at86rf233@0 {
compatible = "atmel,at86rf233";
spi-max-frequency = <500000>;
now I detect this here. Why such low clock? You should use a 7.5 Mhz
clock here not 500 Khz. I had some troubles with such a low clock and
fragmentation handling.
Means:
change it to "spi-max-frequency = <7500000>;"
- Alex
The openlabs blog post [0] used 500 Khz:
&spi {
status = "okay";
at86rf233@0 {
compatible = "atmel,at86rf233";
reg = <0>;
interrupts = <23 1>;
interrupt-parent = <&gpio>;
reset-gpio = <&gpio 24 1>;
sleep-tpio = <&gpio 25 1>;
spi-max-frequency = <500000>;
};
};
I've fixed both the Pi and BBB dts to use 7.5 Mhz as suggested.
I will also change "interrupts = <23 1>': to <23 4> on the Pi to get rid
of the dmesg warning at next reboot.
"[ 7.810095] at86rf230 spi32766.0: Using edge triggered irq's are not
recommended!"
Right now, I'm using the Pi to route over at86rf233 to the BBB to a
local LAN off the BBB.
[0] http://openlabs.co/blog/archives/1-6LoWPAN-kernel-on-a-Raspberry-Pi
--
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
