Re: [beagleboard] Cloud9 + robotics + rcpy... can I run as root?

[Michael Megliola]

works! And I would never have found that on my own. 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/19071cc2-abd1-4498-877e-47a7d2a68da0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Cloud9 + robotics + rcpy... can I run as root?

[Robert Nelson]

Hi Michael,

On Tue, Dec 12, 2017 at 1:31 PM, Michael Megliola
 wrote:
> I installed the latest Debian build (including Cloud9) on a BeagleBone Blue,
> then I downloaded the Strawson Robotics Cape software and the rcpy Python
> library. That all works fine, except for one problem: the robotics cape
> software requires to be run from the root user, while Cloud9 is configured
> to run from debian.
>
> In order to run a Python script, I currently need to use a Cloud9 terminal
> window and switch to root. The regular Cloud9 run facilities fail, with a
> message says that root access is required.
>
> Is there a way to either (a) set up Cloud9 run configurations to run as
> root, (b) configure the Cloud9 service to run from the root account, or (c)
> something else, that would allow me to run directly, using the run button?

This was a security change in cloud9, it can be undone via:

edititing:

/lib/systemd/system/cloud9.service

remove: (debian user)

"User=1000"

and reboot, it should load up as 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/CAOCHtYhsW%2BPw2jYbHPMmc60BcSgsrZk5UgnCmf3D7r_ov-ut-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Cloud9 + robotics + rcpy... can I run as root?

[Michael Megliola]

I installed the latest Debian build (including Cloud9) on a BeagleBone 
Blue, then I downloaded the Strawson Robotics Cape software and the rcpy 
Python library. That all works fine, except for one problem: the robotics 
cape software requires to be run from the *root* user, while Cloud9 is 
configured to run from *debian*.

In order to run a Python script, I currently need to use a Cloud9 terminal 
window and switch to root. The regular Cloud9 run facilities fail, with a 
message says that root access is required.

Is there a way to either (a) set up Cloud9 run configurations to run as 
root, (b) configure the Cloud9 service to run from the root account, or (c) 
something else, that would allow me to run directly, using the run button?

(thanks)

-- Michael

-- 
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/7594f23d-e2a9-4ce7-84c0-c550572d84cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Where are VDD and SYS_RESETn?

[mike . maikaefer]

I soldered the power-wires of an USB-cable to P1/pin 1 and P1/pin 16. So 
USB was not used at all in this scenario.

Regarding SYS_RESETn: I found a signal named RESET_OUT at P2/pin 26 - could 
this the equivalent to SYS_RESETn? Unfortunately I have no idea how to 
measure if it could be it or not...

On Tuesday, December 12, 2017 at 3:03:45 PM UTC+1, Graham wrote:
>
> Mike:
>
> Thanks for the comments.
>
> Were you using the USB0 connector on the board (which is hardwired to 
> P1-pin7), or was it an independent off board connector?
>
> --- Graham
>
>
 

-- 
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/955b31e7-369f-48ac-a922-0f56401663d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Problem Enable UART

[Jeff Andich]

I THINK with the 8250 driver and the beaglebone/board images, 6 UART's show 
up in the /dev/ directory as /dev/ttyS0... /dev/ttyS5 by default, but that 
doesn't  mean that all of those 6 UARTs are enabled.  You have to 
explicitly enable them.  For instance, if you login as root and start 
poking around in /sys/class/tty/ttyS*, you'll see that some of the UARTs 
have an irq of 0, which I think is a sign that they're disabled.




On Tuesday, December 12, 2017 at 8:55:05 AM UTC-6, valentin@gmail.com 
wrote:
>
> Hello,
>
> I have a problem with UART on BeagleBone Black. I succeeded to enable 
> UART1 but UART2 asked me a problem and I can do anything on this port.
> I'm on : Linux beaglebone 4.4.91-ti-r133
> I activated firmware with this : (on /boot/uEnv.txt)
> ###Overide capes with eeprom
> uboot_overlay_addr0=/lib/firmware/BB-UART1-00A0.dtbo
> uboot_overlay_addr1=/lib/firmware/BB-UART2-00A0.dtbo
> ...
>
> and activated everything I needed (all uart and 1 I2C) a little lower in 
> the same file :
> ##Example v4.1.x
> cape_disable=bone_capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>
> cape_enable=bone_capemgr.enable_partno=BB-I2C1,BB-UART4,BB-UART2,BB-UART5,BB-UART3,BB-UART1
>
> Others UART have the same problem...
> I have also this : debian@beaglebone:/boot$ ls -l /dev/ttyS*
> crw--w 1 root tty 4, 64 Dec 12 15:23 /dev/ttyS0
> crw-rw 1 root dialout 4, 65 Dec 12 15:36 /dev/ttyS1
> crw-rw 1 root dialout 4, 66 Dec 12 15:34 /dev/ttyS2
> crw-rw 1 root dialout 4, 67 Dec 12 15:23 /dev/ttyS3
> crw-rw 1 root dialout 4, 68 Dec 12 15:23 /dev/ttyS4
> crw-rw 1 root dialout 4, 69 Dec 12 15:23 /dev/ttyS5
>
> Then all the UART are activated right? 
>
> But I can't communicate with my device and it's work with UART1... Do 
> you have a solution? 
>
> 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/d3356848-53ba-46c8-8ce2-c1cd61db7f45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Problem Enable UART

[Robert Nelson]

On Tue, Dec 12, 2017 at 8:52 AM,   wrote:
> Hello,
>
> I have a problem with UART on BeagleBone Black. I succeeded to enable UART1
> but UART2 asked me a problem and I can do anything on this port.
> I'm on : Linux beaglebone 4.4.91-ti-r133
> I activated firmware with this : (on /boot/uEnv.txt)
> ###Overide capes with eeprom
> uboot_overlay_addr0=/lib/firmware/BB-UART1-00A0.dtbo
> uboot_overlay_addr1=/lib/firmware/BB-UART2-00A0.dtbo
> ...
>
> and activated everything I needed (all uart and 1 I2C) a little lower in the
> same file :
> ##Example v4.1.x
> cape_disable=bone_capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
> cape_enable=bone_capemgr.enable_partno=BB-I2C1,BB-UART4,BB-UART2,BB-UART5,BB-UART3,BB-UART1
>
> Others UART have the same problem...
> I have also this : debian@beaglebone:/boot$ ls -l /dev/ttyS*
> crw--w 1 root tty 4, 64 Dec 12 15:23 /dev/ttyS0
> crw-rw 1 root dialout 4, 65 Dec 12 15:36 /dev/ttyS1
> crw-rw 1 root dialout 4, 66 Dec 12 15:34 /dev/ttyS2
> crw-rw 1 root dialout 4, 67 Dec 12 15:23 /dev/ttyS3
> crw-rw 1 root dialout 4, 68 Dec 12 15:23 /dev/ttyS4
> crw-rw 1 root dialout 4, 69 Dec 12 15:23 /dev/ttyS5
>
> Then all the UART are activated right?
>
> But I can't communicate with my device and it's work with UART1... Do
> you have a solution?

Probally ancient u-boot in eMMC, run this script to confirm:

sudo /opt/scripts/tools/version.sh

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/CAOCHtYjYxfTFF1yOvpNX0U3h8W9mqrdMZ114MV8pM_Ec3puoRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Problem Enable UART

[valentin . girard . ela]

Hello,

I have a problem with UART on BeagleBone Black. I succeeded to enable UART1 
but UART2 asked me a problem and I can do anything on this port.
I'm on : Linux beaglebone 4.4.91-ti-r133
I activated firmware with this : (on /boot/uEnv.txt)
###Overide capes with eeprom
uboot_overlay_addr0=/lib/firmware/BB-UART1-00A0.dtbo
uboot_overlay_addr1=/lib/firmware/BB-UART2-00A0.dtbo
...

and activated everything I needed (all uart and 1 I2C) a little lower in 
the same file :
##Example v4.1.x
cape_disable=bone_capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
cape_enable=bone_capemgr.enable_partno=BB-I2C1,BB-UART4,BB-UART2,BB-UART5,BB-UART3,BB-UART1

Others UART have the same problem...
I have also this : debian@beaglebone:/boot$ ls -l /dev/ttyS*
crw--w 1 root tty 4, 64 Dec 12 15:23 /dev/ttyS0
crw-rw 1 root dialout 4, 65 Dec 12 15:36 /dev/ttyS1
crw-rw 1 root dialout 4, 66 Dec 12 15:34 /dev/ttyS2
crw-rw 1 root dialout 4, 67 Dec 12 15:23 /dev/ttyS3
crw-rw 1 root dialout 4, 68 Dec 12 15:23 /dev/ttyS4
crw-rw 1 root dialout 4, 69 Dec 12 15:23 /dev/ttyS5

Then all the UART are activated right? 

But I can't communicate with my device and it's work with UART1... Do 
you have a solution? 

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/36aab07d-e20b-490f-8f40-00ec9d4d0256%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Custom Board - Editing U-Boot to load the correct values

[masterlienert via BeagleBoard]

Hey guys,
I have a Fastbot board (Beagleboneblack fork) that has some custom EEPROM 
data,
so it's not possible to get any stock images running on that board.

When I load a stock image with the boot from SD card button nothing happens in 
the serial terminal.

The developers of that board are out of business so there won't be any 
updates available.

The U-Boot source changed over the years so I'm not able to easy change it 
like the developers did 
I only could fix the memory and EEPROM adress by their method for the 
newest U-Boot.
(You have to take a look at this commits 

 
on github)

So now I'm stucking at the last point:

3.force change board information for Beagleboneblack.

With the new U-Boot I've no idea how to do this.
I guess that the board/ti/am335x/board.c loads the EEPROM values with the 
board/ti/common/board_detect.c
but which lines will be the right to edit? 

Maybe you have some better ideas to get U-Boot working.



-- 
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/ce7cb99b-de65-4fca-9530-d7496cf4a048%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Where are VDD and SYS_RESETn?

[Graham]

Mike:

Thanks for the comments.

Were you using the USB0 connector on the board (which is hardwired to
P1-pin7), or was it an independent off board connector?

--- Graham


On Tue, Dec 12, 2017 at 1:19 AM,  wrote:

> Hello Graham,
>
> thanks for your feedback.
>
> I tried running PocketBeagle from Vin/pin1 and it worked smoothly here for
> more than 13 hours. It was powered via 5V that came from a USB connector.
>
> But I was running a bare metal application with no Linux involved. So may
> be there is a bug rather in the Linux system you are using than in the
> hardware?
>
> I remember the PMIC of the BeagleBone could be accessed from software,
> watchdog with some illegal parameters would be a candidate too (OK,
> watchdog would not explain why the power pin has an influence...).
>
> With kind regards
>
> Mike
>
>
>
> On Saturday, December 9, 2017 at 6:11:39 AM UTC+1, Graham wrote:
>>
>> I have been unable to get a PocketBeagle to run for more than about 12
>> hours without rebooting when powered from Vin (P1-pin1), using a trusted
>> power supply.
>> It usually reboots itself successfully, so in order to see it, run some
>> commands to turn off the blinking blue lights. If they come back on by
>> themselves, it has rebooted.
>> Or you can read the system logs.
>>
>> It works fine when powered from Vi (P1-pin7) which is the same as the
>> Vusb +5 Volt input/output.
>> It works fine when Vi and Vin are paralleled, but I am uncomfortable
>> paralleling power supplies, unless someone who really understands them says
>> it is OK.
>>
>> The docs indicate that Vin (P1-pin1) should be the primary power input
>> for power inputs other than battery or USB, and this input should have the
>> highest current handling capability of the three.
>>
>> So far, I find that Vin is approximately worthless.
>> Your mileage may vary.
>> So far, no reaction or comment from Jason or Robert.
>>
>> If you can, or can not, duplicate my observations, please comment.
>>
>> As far as a replacement for  SYS_RESETn, I don't think that the external
>> 3V3 power appears until the system has booted, so you could use this
>> Voltage to gate things that might upset the boot process, or break things
>> prior to the CPU booting.
>> At least that is how it worked on the BBB, so I assume the same on the
>> PocketBone.
>>
>> --- Graham
>>
>> ==
>>
>> On Friday, December 8, 2017 at 3:16:45 AM UTC-6, mike.ma...@gmail.com
>> wrote:
>>>
>>> Nobody an idea? While searching through the board here I find two
>>> different opinions about VDD/where to apply external power to, so some
>>> clarification would be really nice...
>>>
>>>
>>>
>>> On Saturday, December 2, 2017 at 6:22:47 PM UTC+1, mike.ma...@gmail.com
>>> wrote:

 Can somebody verify where the following pins/signals can be found at
 the PocketBeagle (comparing to BeagleBone Black):

 - VDD (to supply externel power apart from USB)
 - SYS_RESETn (signalling SiP is in reset state and no inputs are
 allowed to be pulled to LOW or HIGH)

 ?

 Thanks!


 --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/beagleboard/4mHqSR0zOGU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/e79f8f6c-d001-4662-9f45-d8291a55fac3%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/CAC_N71qGtVx%3DLyiSBKd8Rvb-Osa_dC6umstLow0%2BvbardOqZbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Use eQEP on 4.4.23-ti-r51 kernel

[gibson . strickland]

Do you remember how you got eQEP to work? Ours just reads 0


On Sunday, November 13, 2016 at 12:44:06 PM UTC-6, Theodosis Ntegiannakis 
wrote:
>
> I am sorry for the multiple messages but I am finding new information 
> every time!
>
> eQEP just worked!
> The only pins i could enable with config-pin though are P8_11, P8_12, 
> P9_27, P9_92 (42B).
> P8_33 and P8_35 still have the invalid mode qep.
>
>
> Now my only problem is how to read position from python. Any help would be 
> appreciated
>
>
> On Sunday, November 13, 2016 at 7:29:55 PM UTC+2, Theodosis Ntegiannakis 
> wrote:
>>
>> Just updated kernel to 4.4.31-ti-r67.
>> now i can find position and period in the 
>> /sys/devices/platform/ocp/48304000.epwmss/48304180.eqep/
>>
>> but cat position keeps returning 0.
>>
>> when trying to use other pins: 
>> config-pin P8_33 qep  and
>> config-pin P8_35 qep
>> it returns invalid mode qep
>>
>> the same in P8_41 and P8_42 ...
>>
>> have anyone tried it? is it working?
>> I am not sure if it is not working or if i am looking wrong pins or my 
>> encoder doesnt work ok... 
>> My encoder middle pin is hooked to GND and the other two pins in eqepA 
>> and eqepB respectively.
>>
>>
>>
>>
>> On Sunday, November 13, 2016 at 6:09:55 PM UTC+2, Theodosis Ntegiannakis 
>> wrote:
>>>
>>> Hello all,
>>>
>>> I am trying to read a Quadrature Encoder with the Beaglebone Black 
>>> using kenel  4.4.23-ti-r51 and Ubuntu.
>>>
>>> I have enabled cape-universala 
>>> and also enabled pins P8_11 and P8_12 using:
>>> config-pin P8_11 qep
>>> config-pin P8_12 qep
>>>
>>> But i cannot find "position" or "period" in the 
>>> /sys/devices/platform/ocp/48304000.epwmss/48304180.eqep/
>>> Is there something wrong i have done? 
>>> How can i read the position using python?
>>>
>>>

-- 
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/7a47e9f1-f3fe-481a-a760-0e5d70d1e39f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBone Green Wireless Audio using tlv320dac3100 codec

[ritesh . singh]

Always show-
[3.594762] bone_capemgr bone_capemgr: loader: failed to load slot-5 
BB-BONE-AUDI-03:00A0 (prio 0)



On Monday, December 11, 2017 at 2:21:42 PM UTC+5:30, 
ritesh...@kritikalsolutions.com wrote:
>
> Hi, 
>  
> *Info:*
>I am using BeagleBone Green Wireless(BBGW) with SITARA AM3358xx 
> processor on board  for audio driver. For that I am using external 
> tlv320dac3100 codec for audio speaker.
> As you know, this codec is I2C controlled I2S(MCASP) based. So I want to 
> enable McAsp0(I2S)
> pins and I2C1 as hardware interface. I2C1 is reflected successfully by 
> making an entry in /boot/uEnv.txt but unable to show any Audio device by 
> default while throwing command *aplay -L* on the terminal.
>
> Then i start taking action as followed below-
>
> *Actions Taken:*
> As discussed in forum - 
> opened the BB-BONE-AUDI-02-00A0.dts file and edited 
> according to my hardware connections. but unable to compile showing error 
> in header files so i commented the header file and macros used for 
> pinmuxing and used the hard coded values for that. Finally compiled and 
> copied the .dtbo file into /lib/firmware/. then reboot and saw the dmesg-  
>
> *It is showing failed to load BB-BONE-AUDI-02 in slots.*
>
> *Hardware Connection:PIN Muxing:*
> P8.37 - mcasp0-aclkx   0x0C00x73
> P8.38 - mcasp0-fsx   0x0C4   0x77
> P8.34 - mcasp0-axr2 0x0CC   0x85
> P8.37 - mcasp0-ahclkx  0x0DC   0x89
> P8.37 - mcasp0-axr0 0x0C80x81
>
> Please help me to resolve this asap. I am stucked badly. If possible 
> please provide step by step procedure to this.
>
>

-- 
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/03b46ecf-b296-430e-9739-85882ebcd445%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PWM in Pocket Beagle Bone

[mike . maikaefer]

What software are you talking about? Linux? Bare metal/StarterWare?



On Friday, December 8, 2017 at 10:55:39 AM UTC+1, Rohit Karkala wrote:
>
> Hello All, 
>
> I want to disable the PWM functionality of Pocket Beagle Bone and use it 
> as GPIO.
>
> How can i do this.
>

-- 
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/93cc01ec-08e5-4dc8-9ed5-194baa5c2a55%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.