Re: [beagleboard] roboticscape library on the Blue - Motors reversed on rc_balance

[David Lechner]

Swapping your motor leads might be the easiest. However, if you are not 
using the BeagleMIP kit, you will probably have to do some more tuning, 
so recompiling your own program would be necessary. The header file 
spells out many of the options you can tweak including reversing motors 
and encoders. It also helps if you have a degree in control systems.


On 04/28/2017 03:00 PM, Mark A. Yoder wrote:
I'm starting to play with the roboticscape library that comes on the 
Blue.  I'm currently running "BeagleBoard.org Debian Image 2017-04-23".


The *rc_test_* routines seem to work well. However, when I run 
*rc_balance*, the wheels appear to spin in the opposite direction than 
what they should.


I've wired the red leads to the + terminals on the motors.

Does anyone know how to fix this?

--Mark

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google 
Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to beagleboard+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f596116f-ccc6-44b6-a307-1abf7dce1810%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.



--
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/816d5ed4-c0fc-effd-2701-7124e56a3920%40lechnology.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beagle Blue Boo Boo - Attached the battery the wrong way

[Mark A. Yoder]

I've added it to My Favorites at Digi Key.  I need a few more things to 
order so the cost is greater than the postage.

--Mark

On Friday, April 28, 2017 at 4:26:27 PM UTC-4, RobertCNelson wrote:
>
> Q1 is the MOSFET-N between the LIBO's BATT_MINUS and GND
>
>
> https://github.com/beagleboard/beaglebone-blue/blob/master/BeagleBone_Blue_sch.pdf
>
>
> https://www.digikey.com/products/en?lang=en&site=us&KeyWords=SI4778DY-T1-GE3
>
>
> https://github.com/beagleboard/beaglebone-blue/blob/master/BeagleBone_Blue_BOM.csv
>
> Regards,
>
>
> On Fri, Apr 28, 2017 at 2:55 PM, Mark A. Yoder  > wrote:
>
>> My son attached an S2 battery to a Blue yesterday and got a spark.  He 
>> thinks he had the plug oriented correctly.  He re plugged it in again and 
>> attached the Blue to a 12V supply.  The Blue fired up and the battery 
>> charged.  Once charged we removed the 12V and the Blue died.  The Blue 
>> reboots when the 12V supply is restored, but won't run on the battery 
>> alone.  It looks like we melted part of the regulator.  Notice the 8 pin 
>> device in the top center of the picture.
>>
>>
>>
>> 
>>
>>
>> I'm assuming the part can be replaced.  Does anyone know what part it is?
>>
>>
>> --Mark
>>
>>
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/7d19a249-4f16-4483-ada9-33118611a804%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Robert Nelson
> https://rcn-ee.com/
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a70447f1-fb3f-42c6-8f82-dc332b462aab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beagle Blue Boo Boo - Attached the battery the wrong way

[Jason Kridner]

Thanks Robert. I should have zoomed in.
On Fri, Apr 28, 2017 at 4:30 PM Jason Kridner  wrote:

>
>
> On Apr 28, 2017, at 3:55 PM, Mark A. Yoder  wrote:
>
> My son attached an S2 battery to a Blue yesterday and got a spark.  He
> thinks he had the plug oriented correctly.  He re plugged it in again and
> attached the Blue to a 12V supply.  The Blue fired up and the battery
> charged.  Once charged we removed the 12V and the Blue died.  The Blue
> reboots when the 12V supply is restored, but won't run on the battery
> alone.  It looks like we melted part of the regulator.  Notice the 8 pin
> device in the top center of the picture.
>
>
>
> 
>
>
> I'm assuming the part can be replaced.  Does anyone know what part it is?
>
> I believe the silkscreen next to it says PROT, which would make it the
> S-8261.
>
> I think this is the 3rd occurrence I've heard about. Though yours is the
> first to identify what might have blown. Guess the keyed connector isn't
> keyed enough. I will add warnings to the wiki.
>
>
> --Mark
>
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/7d19a249-4f16-4483-ada9-33118611a804%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPnowPdV5%3D9EAvV2gijea26tHbqjiQsw2EMKQ%3D%3DePR_Owg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beagle Blue Boo Boo - Attached the battery the wrong way

[Jason Kridner]

> On Apr 28, 2017, at 3:55 PM, Mark A. Yoder  wrote:
> 
> My son attached an S2 battery to a Blue yesterday and got a spark.  He thinks 
> he had the plug oriented correctly.  He re plugged it in again and attached 
> the Blue to a 12V supply.  The Blue fired up and the battery charged.  Once 
> charged we removed the 12V and the Blue died.  The Blue reboots when the 12V 
> supply is restored, but won't run on the battery alone.  It looks like we 
> melted part of the regulator.  Notice the 8 pin device in the top center of 
> the picture.
> 
> 
> 
> 
> 
> 
> 
> I'm assuming the part can be replaced.  Does anyone know what part it is?
> 
I believe the silkscreen next to it says PROT, which would make it the S-8261.

I think this is the 3rd occurrence I've heard about. Though yours is the first 
to identify what might have blown. Guess the keyed connector isn't keyed 
enough. I will add warnings to the wiki. 
> 
> --Mark
> 
> 
> 
> 
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/7d19a249-4f16-4483-ada9-33118611a804%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/DAAE0339-99FD-437C-8ED0-6258F8AF5C4A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beagle Blue Boo Boo - Attached the battery the wrong way

[Robert Nelson]

Q1 is the MOSFET-N between the LIBO's BATT_MINUS and GND

https://github.com/beagleboard/beaglebone-blue/blob/master/BeagleBone_Blue_sch.pdf

https://www.digikey.com/products/en?lang=en&site=us&KeyWords=SI4778DY-T1-GE3

https://github.com/beagleboard/beaglebone-blue/blob/master/BeagleBone_Blue_BOM.csv

Regards,


On Fri, Apr 28, 2017 at 2:55 PM, Mark A. Yoder 
wrote:

> My son attached an S2 battery to a Blue yesterday and got a spark.  He
> thinks he had the plug oriented correctly.  He re plugged it in again and
> attached the Blue to a 12V supply.  The Blue fired up and the battery
> charged.  Once charged we removed the 12V and the Blue died.  The Blue
> reboots when the 12V supply is restored, but won't run on the battery
> alone.  It looks like we melted part of the regulator.  Notice the 8 pin
> device in the top center of the picture.
>
>
>
> 
>
>
> I'm assuming the part can be replaced.  Does anyone know what part it is?
>
>
> --Mark
>
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/7d19a249-4f16-4483-ada9-33118611a804%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgedEqwxijHvgZEYFqH62P8werh5DGmxUusdKyCHbugtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] roboticscape library on the Blue - Motors reversed on rc_balance

[Mark A. Yoder]

I'm starting to play with the roboticscape library that comes on the Blue. 
 I'm currently running "BeagleBoard.org Debian Image 2017-04-23".

The *rc_test_* routines seem to work well. However, when I run *rc_balance*, 
the wheels appear to spin in the opposite direction than what they should.

I've wired the red leads to the + terminals on the motors.

Does anyone know how to fix this?

--Mark

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f596116f-ccc6-44b6-a307-1abf7dce1810%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beagle Blue Boo Boo - Attached the battery the wrong way

[Mark A. Yoder]

My son attached an S2 battery to a Blue yesterday and got a spark.  He 
thinks he had the plug oriented correctly.  He re plugged it in again and 
attached the Blue to a 12V supply.  The Blue fired up and the battery 
charged.  Once charged we removed the 12V and the Blue died.  The Blue 
reboots when the 12V supply is restored, but won't run on the battery 
alone.  It looks like we melted part of the regulator.  Notice the 8 pin 
device in the top center of the picture.





I'm assuming the part can be replaced.  Does anyone know what part it is?


--Mark



-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7d19a249-4f16-4483-ada9-33118611a804%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PRU Pin Toggle

[dinuxbg]

R30 is a bit field of GPIO outputs. Try "__R30 ^= 0x" to toglle all 16 
PRU outputs.

Regards,
Dimitar

On Friday, April 28, 2017 at 6:56:15 PM UTC+3, M Pitman wrote:
>
> This is a followup to a past post on the PRU's.  I'm looking to provide a 
> clock pulse in the 100kHz range plus send additional pulses out of the PRU 
> and receive a couple other pulses back from a sensor.
>
>  
>
> I've been able to load the device tree overlays for pins P8.11, P8.12, 
> P8.15, P8.16 and P9.24 with no problems.  For output, the overlay sets the 
> mode for pins P8.11 and P8.12 to 0x06.  Plus, I've been able to generate 
> the clock pulse on P8.11 and the other needed outgoing pulse on P8.12 using 
> assembly language but I get the general impression that going forward the 
> preferred method for programming the PRU's is with C.  So for testing I've 
> tried to get PRU_gpioToggle.c to work but for some reason I can't get pins 
> P8.11 or P8.12 to toggle.  Instead, they just read a constant 0 volts.  In 
> the code, gpio is set to 0x000F thinking this should be pin 15, as in 
> pr1_pru0_pru_r30_15. Not being certain for the format of this number I've 
> also tried 0x but with the same results.
>
>  
>
> PRU_gpioToggle compiles OK and the .out file is copied to 
> /lib/firmware/am335x-pru0-fw  The PRU's are stopped and restarted with 
> rmmod -f pru_rproc and modprobe pru_rproc.  dmesg shows they stop and start 
> as expected.  However, still no luck with the toggling.
>
>  
>
> uname -a reads 4.4.54-ti-r93 #1 SMP.
>
>  
>
> Does anybody have any idea what I’m doing wrong?
>
>  
>
> Thanks
>
>  
>
> Mike Pitman
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/c763b55b-2798-4f41-9ffe-eb2b585ac77f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] NHD-7.0CTP-CAPE-N no picture

[Robert Nelson]

Okay got this working, you'll need a u-boot build from today:

U-Boot SPL 2017.05-rc2-2-g86566339a9 (Apr 28 2017 - 10:18:57)

and the latest version of the bb-cape-overlays debian package:
4.4.20170428-0rcnee1~jessie+20170428

(this sunday's snapshot will both of these ready for you)

https://paste.debian.net/929904/

with /boot/uEnv.txt

enable_uboot_overlays=1

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

Regards,

On Thu, Apr 27, 2017 at 11:00 AM, Rasmus Olesen
 wrote:
> Hi Robert
>
> I finaly got this image to boot and give me a picture.
> https://www.dropbox.com/s/n4hgu39ccskbl8c/ubuntu-14.04-3.8.img.gz?dl=0
>
> it is one of the images that NHD links to in the user manual.
>
> I can't get it to flash to the eMMC though. but I gues that is a subject for
> another thread.
>
> I would still be nice to know what it is that makes the display works on
> this image in case I want to upgrade at some point...
>
> Thank you for your time you have been most help full. :)
>
> Regards Rasmus
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/b36d7e6f-cf99-4ad4-a63a-a54b41fa2095%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.



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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjSVBL97Fxpo_R57FJRaGAXa9NFqpYTatkqDN1RVUo26Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] PRU Pin Toggle

[M Pitman]

This is a followup to a past post on the PRU's.  I'm looking to provide a
clock pulse in the 100kHz range plus send additional pulses out of the PRU
and receive a couple other pulses back from a sensor.



I've been able to load the device tree overlays for pins P8.11, P8.12,
P8.15, P8.16 and P9.24 with no problems.  For output, the overlay sets the
mode for pins P8.11 and P8.12 to 0x06.  Plus, I've been able to generate
the clock pulse on P8.11 and the other needed outgoing pulse on P8.12 using
assembly language but I get the general impression that going forward the
preferred method for programming the PRU's is with C.  So for testing I've
tried to get PRU_gpioToggle.c to work but for some reason I can't get pins
P8.11 or P8.12 to toggle.  Instead, they just read a constant 0 volts.  In
the code, gpio is set to 0x000F thinking this should be pin 15, as in
pr1_pru0_pru_r30_15. Not being certain for the format of this number I've
also tried 0x but with the same results.



PRU_gpioToggle compiles OK and the .out file is copied to
/lib/firmware/am335x-pru0-fw  The PRU's are stopped and restarted with
rmmod -f pru_rproc and modprobe pru_rproc.  dmesg shows they stop and start
as expected.  However, still no luck with the toggling.



uname -a reads 4.4.54-ti-r93 #1 SMP.



Does anybody have any idea what I’m doing wrong?



Thanks



Mike Pitman

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAJ2u6KNtBbN0zyxGmgOgp_iq94EbEqhGwPn-_RpBrBOpH633vA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Element14 exact Debian image?

[Robert Nelson]

On Fri, Apr 28, 2017 at 9:59 AM, Michael Wood  wrote:
> I'm looking for the exact disk image flashed to every new Element14
> beaglebone "industrial."
>
> I use a bunch of these, and would rather keep the number of different Linux
> dists to a minimum.

cat /etc/dogtag

Regards,

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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYg56Kz6RfmsxTF3QUpvY%3DuMJzO1KauUbmYz-H49QbxdBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Element14 exact Debian image?

[Michael Wood]

I'm looking for the exact disk image flashed to every new Element14 
beaglebone "industrial."

I use a bunch of these, and would rather keep the number of different Linux 
dists to a minimum. 

Thanks!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/8f568c8f-5aec-41ca-91ae-e9ce7aa1ffa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Depauperate Beagle Board Green

[Andrea Rondini]

Hello, should we create a modular card to which we can add and remove ports 
via DIP connectors (something like this 
https://www.digikey.com/catalog/en/partgroup/pppc-and-pptc-series/2709? Mpart 
= PPTC062LFBN-RC & vendor = 35) and insert external cards that make the 
interface with the necessary port.



Il giorno venerdì 28 aprile 2017 16:30:59 UTC+2, Przemek Klosowski ha 
scritto:
>
>
> On Fri, Apr 28, 2017 at 4:57 AM, Andrea Rondini  > wrote:
>
>> My problem is i've to midfy this board, not add an adpter.
>
>
> Perhaps you could explain what exactly do you want to do. From what you 
> said so far, it appears that you want to use the beagleboard as a 
> controller in some sort of musical instrument---but I am just guessing 
> based on snippets of information from several of your posts. It would be 
> simpler if you wrote down your requirements and plans---then people on this 
> group could give you advice based on their own experiences implementing 
> their own Beaglebone-based builds.
> It's quite possible that there are easier ways of accomplishing what you 
> want, but nobody will be able to help unless they know what's on your mind.
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f9e41b57-12f7-427b-b05f-c68b73700ece%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Depauperate Beagle Board Green

[Przemek Klosowski]

On Fri, Apr 28, 2017 at 4:57 AM, Andrea Rondini  wrote:

> My problem is i've to midfy this board, not add an adpter.


Perhaps you could explain what exactly do you want to do. From what you
said so far, it appears that you want to use the beagleboard as a
controller in some sort of musical instrument---but I am just guessing
based on snippets of information from several of your posts. It would be
simpler if you wrote down your requirements and plans---then people on this
group could give you advice based on their own experiences implementing
their own Beaglebone-based builds.
It's quite possible that there are easier ways of accomplishing what you
want, but nobody will be able to help unless they know what's on your mind.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAC%3D1GgGjgq-bwRTp_H%2BkBCgwQBtKBvTGXcFFUF58bx61bv_TgQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BoneScript for BeagleboneBlue?

[pacolvr]

Is there any plan to update the bonescript library to work with the beaglebone 
blue?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/cd3f5b7b-6521-4f36-8abf-d1b938c7513d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

[Metelko]

Thanks Robert!  That seemed to have worked.  I can control it from my user 
account.  I do believe we will be working with PWM devices soon, so I will 
watch for any updates on that.

/sys/class/gpio/gpio43$ ls -al
total 0
drwxrwxr-x 3 root gpio0 Apr 27 21:48 .
drwxrwxr-x 3 root gpio0 Apr 27 21:48 ..
-rw-rw-r-- 1 root gpio 4096 Apr 27 21:48 active_low
lrwxrwxrwx 1 root gpio0 Apr 27 21:48 device -> ../../../gpiochip1
-rw-rw-r-- 1 root gpio 4096 Apr 27 21:48 direction
-rw-rw-r-- 1 root gpio 4096 Apr 27 21:48 edge
-rw-rw-r-- 1 root gpio 4096 Apr 27 21:48 label
drwxrwxr-x 2 root gpio0 Apr 27 21:48 power
lrwxrwxrwx 1 root gpio0 Apr 27 21:48 subsystem -> 
../../../../../../../class/gpio
-rw-rw-r-- 1 root gpio 4096 Apr 27 21:48 uevent
-rw-rw-r-- 1 root gpio 4096 Apr 27 21:48 value



On Thursday, April 27, 2017 at 4:51:35 PM UTC-5, RobertCNelson wrote:
>
> On Thu, Apr 27, 2017 at 4:46 PM, William Hermans  > wrote: 
> > By the way, I think the small amount I talked about udev, and 
> permissions on 
> > my git for bonejs. I pretty much got most of that information from rPI 
> > content all over the web. I did have to make several modifications 
> though . 
>
> if only they had a pwm udev rule. ;) 
>
> still no go with v4.9.x-ti 
>
> debian@beaglebone:/sys/class/pwm$ ls -lha 
> total 0 
> drwxrwxr-x  2 root pwm  0 Apr 27 21:39 . 
> drwxr-xr-x 61 root root 0 Apr 27 21:39 .. 
> lrwxrwxrwx  1 root pwm  0 Apr 27 21:39 pwmchip0 -> 
> ../../devices/platform/ocp/4830.epwmss/48300100.ecap/pwm/pwmchip0 
> lrwxrwxrwx  1 root pwm  0 Apr 27 21:39 pwmchip1 -> 
> ../../devices/platform/ocp/4830.epwmss/48300200.pwm/pwm/pwmchip1 
> lrwxrwxrwx  1 root pwm  0 Apr 27 21:39 pwmchip3 -> 
> ../../devices/platform/ocp/48302000.epwmss/48302200.pwm/pwm/pwmchip3 
> lrwxrwxrwx  1 root pwm  0 Apr 27 21:39 pwmchip5 -> 
> ../../devices/platform/ocp/48304000.epwmss/48304100.ecap/pwm/pwmchip5 
> lrwxrwxrwx  1 root pwm  0 Apr 27 21:39 pwmchip6 -> 
> ../../devices/platform/ocp/48304000.epwmss/48304200.pwm/pwm/pwmchip6 
>
> debian@beaglebone:/sys/class/pwm/pwmchip3$ ls -lha 
> total 0 
> drwxrwxr-x 4 root pwm 0 Apr 27 21:48 . 
> drwxr-xr-x 3 root root0 Apr 27 21:38 .. 
> lrwxrwxrwx 1 root pwm 0 Apr 27 21:39 device -> ../../../48302200.pwm 
> -rw-rw 1 root pwm  4.0K Apr 27 21:39 export 
> -rw-rw-r-- 1 root pwm  4.0K Apr 27 21:39 npwm 
> drwxrwxr-x 2 root pwm 0 Apr 27 21:39 power 
> drwxr-xr-x 3 root root0 Apr 27 21:48 pwm0 
> lrwxrwxrwx 1 root pwm 0 Apr 27 21:39 subsystem -> 
> ../../../../../../../class/pwm 
> -rw-rw-r-- 1 root pwm  4.0K Apr 27 21:39 uevent 
> -rw-rw 1 root pwm  4.0K Apr 27 21:39 unexport 
>
> debian@beaglebone:/sys/class/pwm/pwmchip3/pwm0$ ls -lha 
> total 0 
> drwxr-xr-x 3 root root0 Apr 27 21:49 . 
> drwxrwxr-x 4 root pwm 0 Apr 27 21:48 .. 
> -r--r--r-- 1 root root 4.0K Apr 27 21:50 capture 
> -rw-r--r-- 1 root root 4.0K Apr 27 21:50 duty_cycle 
> -rw-r--r-- 1 root root 4.0K Apr 27 21:48 enable 
> -rw-r--r-- 1 root root 4.0K Apr 27 21:50 period 
> -rw-r--r-- 1 root root 4.0K Apr 27 21:50 polarity 
> drwxr-xr-x 2 root root0 Apr 27 21:50 power 
> -rw-r--r-- 1 root root 4.0K Apr 27 21:50 uevent 
>
> the "pwm0" node always comes up root:root.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/dc41fbd4-b970-461a-bf78-2daef61a6493%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: [beagle-alpha] Re: Cloud9 IDE Update (c9-core-installer_3.1.3543)

[Metelko]

I used the following udev rule (similar to William Hermans, without the 
pinmux/state changes using a new 'gpio' group). 

udev rule:
SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c 'chown -R root:gpio 
/sys/class/gpio; chmod -R 770 /sys/class/gpio; chown -R root:gpio 
/sys/devices/platform/ocp/4000.gpio/gpio/; chmod -R 770 
/sys/devices/platform/ocp/4000.gpio/gpio/'"

This worked successfully for an image that had the following setup (uname): 
 Linux bbb-3ed2 4.4.12-ti-rt-r30 #1 SMP PREEMPT RT Thu Jun 9 07:50:04 UTC 
2016 armv7l armv7l armv7l GNU/Linux

I am now moving to a newer image (uname):  Linux bbb-f652 4.9.24-ti-rt-r31 
#1 SMP PREEMPT RT Wed Apr 26 23:38:10 UTC 2017 armv7l armv7l armv7l 
GNU/Linux.  I see the /sys/class/gpio directory setup with the 'gpio' group 
name.  But when I export a pin and look at that directory, the ownership of 
all the files are root:root.  This will not allow me to control the GPIO 
from a non-root account.  Any idea on what might have changed that would 
effect this would be greatly appreciated.

/sys/class/gpio$ ls -al
total 0
drwxrwx---  2 root gpio0 Apr 27 20:54 .
drwxr-xr-x 59 root root0 Apr 27 20:46 ..
-rwxrwx---  1 root gpio 4096 Apr 27 20:54 export
lrwxrwxrwx  1 root gpio0 Apr 27 20:54 gpio10 -> 
../../devices/platform/ocp/44e07000.gpio/gpiochip0/gpio/gpio10
lrwxrwxrwx  1 root gpio0 Apr 27 20:38 gpiochip0 -> 
../../devices/platform/ocp/44e07000.gpio/gpio/gpiochip0
lrwxrwxrwx  1 root gpio0 Apr 27 20:38 gpiochip32 -> 
../../devices/platform/ocp/4804c000.gpio/gpio/gpiochip32
lrwxrwxrwx  1 root gpio0 Apr 27 20:38 gpiochip64 -> 
../../devices/platform/ocp/481ac000.gpio/gpio/gpiochip64
lrwxrwxrwx  1 root gpio0 Apr 27 20:38 gpiochip96 -> 
../../devices/platform/ocp/481ae000.gpio/gpio/gpiochip96
-rwxrwx---  1 root gpio 4096 Apr 27 20:54 unexport

/sys/class/gpio/gpio10$ ls -al
total 0
drwxr-xr-x 3 root root0 Apr 27 20:54 .
drwxr-xr-x 3 root root0 Apr 27 20:54 ..
-rw-r--r-- 1 root root 4096 Apr 27 20:54 active_low
lrwxrwxrwx 1 root root0 Apr 27 20:54 device -> ../../../gpiochip0
-rw-r--r-- 1 root root 4096 Apr 27 20:54 direction
-rw-r--r-- 1 root root 4096 Apr 27 20:54 edge
-r--r--r-- 1 root root 4096 Apr 27 20:54 label
drwxr-xr-x 2 root root0 Apr 27 20:54 power
lrwxrwxrwx 1 root root0 Apr 27 20:54 subsystem -> 
../../../../../../../class/gpio
-rw-r--r-- 1 root root 4096 Apr 27 20:54 uevent
-rw-r--r-- 1 root root 4096 Apr 27 20:54 value

On Friday, April 21, 2017 at 11:20:58 PM UTC-5, William Hermans wrote:
>
> This is what I had to do with the gpio pins, note the last two parts of 
> the rules.
>
> SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c 'chown -R root:gpio /sys/class/gpio; 
> chmod -R 770 /sys/class/gpio; 
> chown -R root:gpio /sys/devices/platform/ocp/4000.gpio/gpio/; chmod -R 
> 770 /sys/devices/platform/ocp/4000.gpio/gpio/;
> chown root:gpio /sys/devices/platform/ocp/ocp:??_??_pinmux/state; chmod 770 
> /sys/devices/platform/ocp/ocp:??_??_pinmux/state'"
>
> So in my own mind, mode 770 is a really bad idea. But I seem to recall having 
> issues unless I gave myself executable permissions as well. Why, I'm not 
> sure. 
> I'm definitely not a udev expert. I also recall, some paths gave me issues, 
> which is why above I had to place additional rules on the "state" file. Also 
> note my SUBSYSTEM "define" 
> which is "gpio*". Other obvious differences is the order in which I used 
> chown, and chmod, but I'm not positive that would make any difference. Since 
> the system udev is running 
> these rules when the sysfs file / directory structure is created. As such, it 
> should be root, or better, if possible.
>
> Anyway, you could create a systemd one-shot timer at boot, that waits a 
> certain amount of time ( maybe 5-10 seconds ), then does this "manually". I'm 
> pretty sure that would work. 
> But that would feel like a "hack" to me. e.g. not really the proper way to go 
> about things. But short term, it would work. Which is what really is 
> important. 
>
>
> On Fri, Apr 21, 2017 at 7:35 PM, Robert Nelson  > wrote:
>
>> This is what the analog.js application shows:
>>
>> https://i.imgur.com/4ifEFBQ.png
>>
>> if i manually do:
>>
>> debian@test-bbb-2:/sys/class/pwm/pwmchip4$ sudo /bin/chown -R root:pwm 
>> ./pwm0/
>> debian@test-bbb-2:/sys/class/pwm/pwmchip4$ sudo /bin/chmod -R ug+rw 
>> ./pwm0/
>>
>> debian@test-bbb-2:/sys/class/pwm/pwmchip4$ ls -lha
>> total 0
>> drwxrwxr-x 4 root pwm 0 Apr 22 02:30 .
>> drwxr-xr-x 3 root root0 Apr 22 02:31 ..
>> lrwxrwxrwx 1 root pwm 0 Apr 22 02:26 device -> ../../../48302200.pwm
>> -rw-rw 1 root pwm  4.0K Apr 22 02:26 export
>> -rw-rw-r-- 1 root pwm  4.0K Apr 22 02:26 npwm
>> drwxrwxr-x 2 root pwm 0 Apr 22 02:26 power
>> drwxrwxr-x 3 root pwm 0 Apr 22 02:30 pwm0
>> lrwxrwxrwx 1 root pwm 0 Apr 22 02:26 subsystem ->
>> ../../../../../../../class/pwm
>

Re: [beagleboard] Re: Depauperate Beagle Board Green

[Andrea Rondini]

My problem is i've to midfy this board, not add an adpter.
Sorry :(

Il giorno giovedì 27 aprile 2017 20:30:00 UTC+2, William Hermans ha scritto:
>
> Andrea,
>
> Maybe this will solve your problem: https://www.adafruit.com/product/909
>
> There are also panel mount USB pass through cables too. I'm not sure if 
> adafruit has them, but if not amazon has them for sure.
>
> On Thu, Apr 27, 2017 at 9:59 AM, William Hermans  > wrote:
>
>> Seems I was not awake, enough, before I read the post. But was still good 
>> for a laugh while I was off in left field somewhere. But changing out 
>> ethernet, *AND* USB for DIP connectors is still odd to me. I'll just chalk 
>> that up to me not being an EE, and move on with my life.
>>
>> Andrea, OrCAD is a very expensive piece of software that requires a skill 
>> set from an engineer who has spent years mastering the software, and 
>> electronics design concepts in general. Normally, when changes are made to 
>> a design of this nature, you're not going to get these changes made free of 
>> charge.
>>
>> I only know this because my buddy has spent 30 + years in the electronics 
>> field, and many years of that working with the OrCAD, or similar software. 
>> Also keep in mind what I'm about to say is not an offer at all, but rather 
>> a statement. He could make these changes, but because of his large time 
>> investment using the software, and considerable amount of time studying 
>> electronics in general. Those would not be free, or even cheap.
>> ​
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/b080b2c5-988c-4014-9bcc-9c51e2218bbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.