Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: "Michael C. Cambria" <mcc@fid4.com>
To: Varka Bhadram <varkabhadram@gmail.com>, linux-wpan@vger.kernel.org
Cc: Alexander Aring <alex.aring@gmail.com>
Subject: Re: at86rf233 on BeagleBone Black
Date: Fri, 17 Apr 2015 09:28:37 -0400	[thread overview]
Message-ID: <55310A85.5080601@fid4.com> (raw)
In-Reply-To: <55307D66.7020606@gmail.com>



On 04/16/2015 11:26 PM, Varka Bhadram wrote:
> On 04/17/2015 02:38 AM, Michael C. Cambria wrote:
>>
>> On 04/14/2015 11:06 AM, Alexander Aring wrote:
>>> Hi,
>> [deleted]
>>
>>> since somebody noticed me about several pinmux issues on this setup. I
>>> will update them now with:
>>>
>>> &am33xx_pinmux {
>>>           spi1_pins: pinmux_spi1_pins {
>>>                   pinctrl-single,pins = <
>>>                           0x190 (PIN_INPUT_PULLDOWN | MUX_MODE3) /*
>>> mcasp0_aclkx.spi1_sclk */
>>>                           0x194 (PIN_INPUT | MUX_MODE3) /*
>>> mcasp0_fsx.spi1_d0 */
>>>                           0x198 (PIN_OUTPUT_PULLDOWN | MUX_MODE3) /*
>>> mcasp0_axr0.spi1_d1 */
>>>                           0x19c (PIN_OUTPUT_PULLUP | MUX_MODE3) /*
>>> mcasp0_ahclkr.spi1_cs0 */
>>>                           0x1a4 (PIN_INPUT | MUX_MODE7)  /* IRQ:
>>> mcasp0_fsr.gpio3_19 */
>>>                           0x1ac (PIN_OUTPUT_PULLDOWN | MUX_MODE7) /*
>>> SLP_TR: mcasp0_ahclkx.gpio3_21 */
>>>                           0x044 (PIN_OUTPUT_PULLUP | MUX_MODE7) /*
>>> RESET: gpmc_a1.gpio1_17 */
>>>                   >;
>>>           };
>>> };
>>>
>>> This is what [0] describes at page 11, I hope. Can somebody report if it
>>> was successful to get openlabs with bb/bbw working?
>>>
>>> - Alex
>>>
>>> [0]
>>> http://www.atmel.com/images/atmel-8351-mcu_wireless-at86rf233_datasheet.pdf
>>> (1.3.2 Pull-up and Pull-down Configuration)
>> On BBB, I'm using:
>>
>> &am33xx_pinmux {
>>          spi1_pins: pinmux_spi1_pins {
>>                  pinctrl-single,pins = <
>>                          0x190 (PIN_INPUT_PULLDOWN | MUX_MODE3) /*
>> mcasp0_aclkx.spi1_sclk */
>>                          0x194 (PIN_INPUT | MUX_MODE3) /*
>> mcasp0_fsx.spi1_d0 */
>>                          0x198 (PIN_OUTPUT_PULLDOWN | MUX_MODE3) /*
>> mcasp0_axr0.spi1_d1 */
>>                          0x19c (PIN_OUTPUT_PULLUP | MUX_MODE3) /*
>> mcasp0_ahclkr.spi1_cs0 */
>>                          0x1a4 (PIN_INPUT | MUX_MODE7)  /* IRQ:
>> mcasp0_fsr.gpio3_19 */
>>                          0x1ac (PIN_OUTPUT_PULLDOWN | MUX_MODE7) /*
>> SLP_TR: mcasp0_ahclkx.gpio3_21 */
>>                          0x044 (PIN_OUTPUT_PULLUP | MUX_MODE7) /*
>> RESET: gpmc_a1.gpio1_17 */
>>                  >;
>>          };
>> };
>>
>>
>> &spi1 {
>>          status = "okay";
>>          pinctrl-names = "default";
>>          pinctrl-0 = <&spi1_pins>;
>>          at86rf231@0 {
>>                  compatible = "atmel,at86rf231";
>>                  spi-max-frequency = <7500000>;
>>                  reg = <0>;
>>                  interrupts = <19 4>;
>>                  interrupt-parent = <&gpio3>;
>>                  reset-gpio = <&gpio1 17>;
> Here you are missing the initial state of the reset gpio pin status.
>
> It has to be something like this:
> 	
> 		reset-gpio = <&gpio1 17 1>;
>
>>                  sleep-gpio = <&gpio3 31>;
> Same here also...
>
> 		sleep-gpio = <&gpio3 31 1>;
>
>>                  xtal-trim = /bits/ 8 <0xF>;
>>          };
>> };
>>
>>
>> At probe time, I get
>>
>> [    8.203574] /ocp/spi@481a0000/at86rf231@0: arguments longer than
>> property
>> [    8.210963] of_get_named_gpiod_flags: can't parse 'reset-gpio'
>> property of node '/ocp/spi@481a0000/at86rf231@0[0]'
>> [    8.210992] /ocp/spi@481a0000/at86rf231@0: arguments longer than
>> property
>> [    8.218231] of_get_named_gpiod_flags: can't parse 'sleep-gpio'
>> property of node '/ocp/spi@481a0000/at86rf231@0[0]'
>> [    9.830628] using random self ethernet address
>>
>>
>> Using e.g. "gpio1_17" doesn't compile, nor do other guesses.  What
>> syntax is expected for reset-gpio and sleep-gpio?
>>
>> My kernel id bluetooth-next pulled Monday,
>>
>> Linux beaglebone 4.0.0-rc7-244798-gf86c0e3 #1 SMP Wed Apr 15 10:34:12
>> EDT 2015 armv7l GNU/Linux
>>

With those changes the "arguments longer than property" message does go 
away.  I now get this probe error:


[    9.815400] of_get_named_gpiod_flags: parsed 'reset-gpio' property of 
node '/ocp/spi@481a0000/at86rf231@0[0]' - stat)
[    9.815437] of_get_named_gpiod_flags: parsed 'sleep-gpio' property of 
node '/ocp/spi@481a0000/at86rf231@0[0]' - stat)
[   10.287193] at86rf230 spi1.0: Non-Atmel dev found (MAN_ID 00 00)
[   10.971416] at86rf230: probe of spi1.0 failed with error -22




  reply	other threads:[~2015-04-17 13:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <551EDFCA.3070905@fid4.com>
2015-04-03 19:13 ` at86rf233 on BeagleBone Black Alexander Aring
2015-04-03 19:36   ` Alexander Aring
2015-04-14 15:06   ` Alexander Aring
2015-04-16 21:08     ` Michael C. Cambria
2015-04-17  3:26       ` Varka Bhadram
2015-04-17 13:28         ` Michael C. Cambria [this message]
2015-04-17 22:19           ` Alexander Aring
2015-04-20 18:04             ` Michael C. Cambria
2015-04-20 18:24               ` Alexander Aring
2015-04-21  7:23               ` "Thomas B. Rücker"
2015-04-22  6:57                 ` "Thomas B. Rücker"
2015-04-23  9:37               ` Alexander Aring
2015-04-23 13:47                 ` Michael C. Cambria
2015-04-23 14:59                   ` Alexander Aring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55310A85.5080601@fid4.com \
    --to=mcc@fid4.com \
    --cc=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=varkabhadram@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox