Re: [Machinekit] PocketBeagle/BBB custom overlays at boot

2017-10-27 Thread John Morris 



On 10/27/2017 01:36 PM, Robert Nelson wrote:

On Fri, Oct 27, 2017 at 1:32 PM, Robert Nelson  wrote:

On Fri, Oct 27, 2017 at 1:27 PM, Robert Nelson  wrote:

Hi John,

On Fri, Oct 27, 2017 at 1:20 PM, John Morris  wrote:

To get Beagle GPIOs configured correctly at boot, is a custom overlay the
right way to go?  I want a bunch of the PocketBeagle pins configured as GPIO
output low, but some of them start up in other modes with unwanted signals.


So one of the difference between the BBB and the PocketBeagle, we have
'config-pin' built-into the base *.dtb

So if you want a dedicated use of a pin, you need to disable the
config-pin/cape-unversal pinmux:

P1_02_pinmux {
  status = "disabled";
};

So this should work:

https://gist.github.com/RobertCNelson/41ed096d96bede9617c0a1adafb24677


OH and Charles wrote another option, i don't think we ever tested it..

https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-4.9.y/patches/drivers/ti/gpio/0008-bone-pinmux-helper-Add-support-for-mode-device-tree-.patch

P1_02_pinmux {
  mode = "gpio_pd";
};


it looks silly:

https://gist.github.com/RobertCNelson/41ed096d96bede9617c0a1adafb24677#file-gistfile2-txt

but it should work..

There will still be a little noise from power on -> u-boot -> kernel
(kernel loads in about 1 - 2 seconds)


This works perfectly.

I was originally trying to get the pin configured as output at boot too, 
but I was overthinking, since the hal_bb_gpio comp takes care of that.


I gotta say I *love* the PocketBeagle.  It fits in a fraction the space 
of the BBB, and the option to solder on whichever headers one prefers 
helps even more with form factor issues.  Brilliant stuff!


John

--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups "Machinekit" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] PocketBeagle/BBB custom overlays at boot

2017-10-27 Thread Robert Nelson 
On Fri, Oct 27, 2017 at 1:32 PM, Robert Nelson  wrote:
> On Fri, Oct 27, 2017 at 1:27 PM, Robert Nelson  
> wrote:
>> Hi John,
>>
>> On Fri, Oct 27, 2017 at 1:20 PM, John Morris  wrote:
>>> To get Beagle GPIOs configured correctly at boot, is a custom overlay the
>>> right way to go?  I want a bunch of the PocketBeagle pins configured as GPIO
>>> output low, but some of them start up in other modes with unwanted signals.
>>
>> So one of the difference between the BBB and the PocketBeagle, we have
>> 'config-pin' built-into the base *.dtb
>>
>> So if you want a dedicated use of a pin, you need to disable the
>> config-pin/cape-unversal pinmux:
>>
>> P1_02_pinmux {
>>  status = "disabled";
>> };
>>
>> So this should work:
>>
>> https://gist.github.com/RobertCNelson/41ed096d96bede9617c0a1adafb24677
>
> OH and Charles wrote another option, i don't think we ever tested it..
>
> https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-4.9.y/patches/drivers/ti/gpio/0008-bone-pinmux-helper-Add-support-for-mode-device-tree-.patch
>
> P1_02_pinmux {
>  mode = "gpio_pd";
> };

it looks silly:

https://gist.github.com/RobertCNelson/41ed096d96bede9617c0a1adafb24677#file-gistfile2-txt

but it should work..

There will still be a little noise from power on -> u-boot -> kernel
(kernel loads in about 1 - 2 seconds)

Regards,


-- 
Robert Nelson
https://rcn-ee.com/

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] PocketBeagle/BBB custom overlays at boot

2017-10-27 Thread Robert Nelson 
On Fri, Oct 27, 2017 at 1:27 PM, Robert Nelson  wrote:
> Hi John,
>
> On Fri, Oct 27, 2017 at 1:20 PM, John Morris  wrote:
>> To get Beagle GPIOs configured correctly at boot, is a custom overlay the
>> right way to go?  I want a bunch of the PocketBeagle pins configured as GPIO
>> output low, but some of them start up in other modes with unwanted signals.
>
> So one of the difference between the BBB and the PocketBeagle, we have
> 'config-pin' built-into the base *.dtb
>
> So if you want a dedicated use of a pin, you need to disable the
> config-pin/cape-unversal pinmux:
>
> P1_02_pinmux {
>  status = "disabled";
> };
>
> So this should work:
>
> https://gist.github.com/RobertCNelson/41ed096d96bede9617c0a1adafb24677

OH and Charles wrote another option, i don't think we ever tested it..

https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-4.9.y/patches/drivers/ti/gpio/0008-bone-pinmux-helper-Add-support-for-mode-device-tree-.patch

P1_02_pinmux {
 mode = "gpio_pd";
};

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] PocketBeagle/BBB custom overlays at boot

2017-10-27 Thread Robert Nelson 
Hi John,

On Fri, Oct 27, 2017 at 1:20 PM, John Morris  wrote:
> To get Beagle GPIOs configured correctly at boot, is a custom overlay the
> right way to go?  I want a bunch of the PocketBeagle pins configured as GPIO
> output low, but some of them start up in other modes with unwanted signals.

So one of the difference between the BBB and the PocketBeagle, we have
'config-pin' built-into the base *.dtb

So if you want a dedicated use of a pin, you need to disable the
config-pin/cape-unversal pinmux:

P1_02_pinmux {
 status = "disabled";
};

So this should work:

https://gist.github.com/RobertCNelson/41ed096d96bede9617c0a1adafb24677

>
> I attempted an overlay config [1].  It may not be correct, but it at least
> compiles.  It's installed as shown at the top of the file by putting it in
> `/lib/firmware` and adding `dtb_overlay=/lib/firmware/pb_goldibox-00A0.dtbo`
> to `/boot/uEnv.txt`. That doesn't seem to have any effect on the pins in
> question, however.
>
> Hints appreciated!
>
> John
>
> [1]: https://github.com/zultron/goldibox/blob/master/pb_goldibox.dts

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

[Machinekit] PocketBeagle/BBB custom overlays at boot

2017-10-27 Thread John Morris 
To get Beagle GPIOs configured correctly at boot, is a custom overlay 
the right way to go?  I want a bunch of the PocketBeagle pins configured 
as GPIO output low, but some of them start up in other modes with 
unwanted signals.


I attempted an overlay config [1].  It may not be correct, but it at 
least compiles.  It's installed as shown at the top of the file by 
putting it in `/lib/firmware` and adding 
`dtb_overlay=/lib/firmware/pb_goldibox-00A0.dtbo` to `/boot/uEnv.txt`. 
That doesn't seem to have any effect on the pins in question, however.


Hints appreciated!

John

[1]: https://github.com/zultron/goldibox/blob/master/pb_goldibox.dts

--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups "Machinekit" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.