at86rf212B 868Mhz

at86rf212B 868Mhz

[Baptiste Clenet]

Hi,

I've got two devices with a at86rf212B onboard: device A (ohter OS
with at86rf212b driver) sending frame to device B  (running on Kernel
4.1 with the at86rf230 driver)
Both has got a 868MHz antenna.
Case 1: I set channel to 5 and page to 0 (914MHz according to
datasheet) to both of them, it works fine, I can receive and send
frames.
Case 2: I set channel to 0 and page to 0 (868MHz according to
dataheet) and I can't receive or send any frames.

Alexander, have you already tried to run on 868MHz?

Cheers,

-- 
Baptiste

Re: at86rf212B 868Mhz

[Stefan Schmidt]

Hello.

On 22/03/16 19:48, Baptiste Clenet wrote:
> Hi,
>
> I've got two devices with a at86rf212B onboard: device A (ohter OS
> with at86rf212b driver) sending frame to device B  (running on Kernel
> 4.1 with the at86rf230 driver)
> Both has got a 868MHz antenna.
> Case 1: I set channel to 5 and page to 0 (914MHz according to
> datasheet) to both of them, it works fine, I can receive and send
> frames.
> Case 2: I set channel to 0 and page to 0 (868MHz according to
> dataheet) and I can't receive or send any frames.
>
> Alexander, have you already tried to run on 868MHz?
>

I'm not Alex but I can tell you that neither he or myself have 868 MHz 
capable hardware so we never have been able to test that on our side.

There could still be a bug in the driver or the iwpan page/channel 
setting somewhere. Printing out the values you get in the kernel (first 
the ones you get over netlink from iwpan and second the ones being set 
into the register) might give you a first clue if they actually compare 
to what the chip expects.

regards
Stefan Schmidt

Re: at86rf212B 868Mhz

[Baptiste Clenet]

Thanks Stefan, Ok so my tests show that it doesn't work for the
moment. I may go on Kernel 4.3 if you made any changes on this.


2016-03-23 10:20 GMT+01:00 Stefan Schmidt <stefan@osg.samsung.com>:
> Hello.
>
> On 22/03/16 19:48, Baptiste Clenet wrote:
>>
>> Hi,
>>
>> I've got two devices with a at86rf212B onboard: device A (ohter OS
>> with at86rf212b driver) sending frame to device B  (running on Kernel
>> 4.1 with the at86rf230 driver)
>> Both has got a 868MHz antenna.
>> Case 1: I set channel to 5 and page to 0 (914MHz according to
>> datasheet) to both of them, it works fine, I can receive and send
>> frames.
>> Case 2: I set channel to 0 and page to 0 (868MHz according to
>> dataheet) and I can't receive or send any frames.
>>
>> Alexander, have you already tried to run on 868MHz?
>>
>
> I'm not Alex but I can tell you that neither he or myself have 868 MHz
> capable hardware so we never have been able to test that on our side.
>
> There could still be a bug in the driver or the iwpan page/channel setting
> somewhere. Printing out the values you get in the kernel (first the ones you
> get over netlink from iwpan and second the ones being set into the register)
> might give you a first clue if they actually compare to what the chip
> expects.
>
> regards
> Stefan Schmidt



-- 
Baptiste

Re: at86rf212B 868Mhz

[Alexander Aring]

Hi,

On Thu, Mar 24, 2016 at 09:04:43AM +0100, Baptiste Clenet wrote:
> Thanks Stefan, Ok so my tests show that it doesn't work for the
> moment. I may go on Kernel 4.3 if you made any changes on this.
> 

please check if the registers for page 0 channel 0 are set correctly.
You can dump the registers with:

cat /sys/kernel/debug/regmap/spi32766.0/registers

"spi32766.0" maybe different on your board.

- Alex

Re: at86rf212B 868Mhz

[Stefan Schmidt]

Hello.

On 24/03/16 09:19, Alexander Aring wrote:
> Hi,
>
> On Thu, Mar 24, 2016 at 09:04:43AM +0100, Baptiste Clenet wrote:
>> Thanks Stefan, Ok so my tests show that it doesn't work for the
>> moment. I may go on Kernel 4.3 if you made any changes on this.
>>
> please check if the registers for page 0 channel 0 are set correctly.
> You can dump the registers with:
>
> cat /sys/kernel/debug/regmap/spi32766.0/registers
>
> "spi32766.0" maybe different on your board.
>

Baptiste, have you been able to debug this further? Comparing the 
register content and see if they are correct?

regards
Stefan Schmidt