Re: [beagleboard] TI AM335x vs. Octavio OSD3358

[acheesehead]

FYI...my contact at Octavo informed me today that the industrial version of 
the cSIP currently has a lead time of 6 weeks. They are flying off the 
shelves.

On Sunday, January 31, 2021 at 4:40:14 PM UTC-7 d...@kulp.com wrote:

>
>
> On Jan 30, 2021, at 10:36 PM, Richard Sewell  wrote:
>
> Thanks Daniel, (cool site btw!) I have headers exactly the same on my 
> prototype board set up. Do you have any automation for soldering the female 
> headers or do you hand solder them? Someone has made an automatic header 
> soldering machine which is interesting, but quite a project 
> https://hackaday.com/2015/05/05/open-source-diy-soldering-robot/ . I have 
> also heard of 'pin in paste' headers,  which would require some kind of 
> reflow process only on the edge of the board. I'm trying to avoid as many 
> manual assembly processes as possible. 
>
>
> I’ve gone two different directions with this..
>
> When volume was lower, I actually paid my 13yo son to solder them.  He 
> wanted to save up for a new composite Baseball Bat so I paid him $3 for 
> each one that he soldered.   At one point, he got good enough to do about 8 
> an hour (I can do about 9/10) so he made out pretty well.However, you 
> could use this idea and maybe find a couple enterprising high school 
> students or something that would like a socially distant work from home job 
> that could be just a couple hours a day.   Give them $3 or $4 each and 
> they’d make out really well once they got good at it.  (Assuming they have 
> the soldering station or you could loan them one or something)
>
> With higher volume, I’m just having the cape manufacturer do it.   They 
> are more than happy to solder headers on and mount them onto the capes.   
> The trick here is getting them to the board manufacturer since the PB’s 
> aren’t available everywhere or is very expensive in some locations.  Thus, 
> it kind of depends on where you have your boards made.   I’ve had bunches 
> of PB’s shipped to me, I’ve ripped them out of the retail packaging (to 
> save weight/space) and then shipped them off to manufacture.   Anyway, talk 
> to your board manufacturer. 
>
> -- 
> Daniel Kulp
> d...@kulp.com - http://dankulp.com/blog 
>
>

-- 
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/4c08436a-c177-413f-85e8-57ab7181f180n%40googlegroups.com.

Re: [beagleboard] Comms Cape

[Steve Lentz]

Dwayne:

Interesting question - I built my own shunt circuits on a protoboard so I was 
able to bring out a connection to P9_34.

After looking at the BBB schematic, I see there is a ferrite bead connecting 
GNDA to GND, so there is continuity between them and you should be able to use 
the GND on positions 1 or 10 of X1.  

-Steve


> On Feb 2, 2021, at 8:47 PM, Dwayne Zimmerman  wrote:
> 
> Steve
> Thanks that helps a lot, but the agnd is not actually brought out to the 
> terminal strip only the gnd. How do I attach to agnd?
> 
> On Tuesday, February 2, 2021 at 8:27:25 PM UTC-5 stl...@gmail.com wrote:
> The comms board 4-20mA current loop input consists of a 75Ω shunt resistor 
> across one of the analog input pins.  
> 
> You need to connect an appropriate voltage source to your device and the 
> other end of your device to the comms board input.  Connect the ground of 
> your voltage source to the Analog Ground pin.  
> 
> Divide the measured voltage by 75 to obtain the current.
> 
> The cape does not provide a voltage source,  Many devices use 24V excitation, 
> but this is not universal.  Thus the choice of voltage source is left to you.
> 
> Hope this helps someone.  Schematic can be found here if you have any doubts: 
>  
> https://github.com/beagleboard/capes/blob/master/beaglebone/Comms/Comms_Cape_sch.pdf
>  
> 
> 
> 
> 
> 
> 
> 
>> On Feb 2, 2021, at 8:14 PM, evilwulfie > > wrote:
>> 
> 
>> you can use an current to voltage converter then an opamp to level shift it
>> 
>> On 2/2/2021 5:03 PM, Dwayne Zimmerman wrote:
>>> Can anyone tell me how to connect a sensor to the 4-20mA input on the comms 
>>> board.I need temperature and all 4-20mA temperature sensors I'm familiar 
>>> with are 24 VDC not 1.8
>>> 
>>> On Monday, February 1, 2021 at 7:29:46 PM UTC-5 Dennis Bieber wrote:
>>> On Mon, 1 Feb 2021 15:46:51 -0800 (PST), in 
>>> gmane.comp.hardware.beagleboard.user Dwayne Zimmerman 
>>> > wrote: 
>>> 
>>> >So the pull down is to keep the voltage under 1.8 correct? My confusion is 
>>> >I have one screw per input, 4-20mA is two wire where is the other half of 
>>> >the circut? 
>>> > 
>>> 
>>> I suspect the pull-down is only ensuring that the floating voltage is 
>>> tied to 0V; feeding anything with a voltage over 1.8V will still fry the 
>>> input. And since 0V likely also means 0mA, it indicates a fault condition 
>>> in the loop. 
>>> 
>>> https://www.fluke.com/en-us/learn/best-practices/test-tools-basics/process-tools/what-is-a-4-20-ma-current-loop
>>>  
>>> 
>>>  
>>> https://www.predig.com/indicatorpage/back-basics-fundamentals-4-20-ma-current-loops
>>>  
>>> 
>>>  
>>> {Many others| 
>>> 
>>> The input to the BBB likely needs to consist of a current->voltage 
>>> tranform, so the ADC can measure the voltage corresponding to the current. 
>>> Which might be built-into the cape (I've not looked at it). 
>>> 
>>> 
>>> -- 
>>> Dennis L Bieber 
>>> 
>>> -- 
>>> 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/5fd03d5f-b21f-43b8-b3d3-ae464ff8d1bdn%40googlegroups.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...@googlegroups.com 
>> .
> 
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/9654dc5a-2d31-6f0f-a745-ae085db30859%40gmail.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 
> 

Re: [beagleboard] Re: Image duplication

[Paul Beam]

Thanks!

On Tue, Feb 2, 2021 at 8:54 PM Robert Nelson 
wrote:

> On Tue, Feb 2, 2021 at 7:53 PM Tom Stepleton  wrote:
> >
> > I've never had trouble duplicating modified images --- it's how I
> distribute the software for my own project.
> >
> > This said, I suspect (but haven't checked) that all PocketBeagles
> running my images will have the same host key. It's not a big problem for
> me since my application is a standalone appliance for retrocomputing (so
> you seldom ever plug it into anything except the old computer and a power
> source).
>
> sudo touch /etc/ssh/ssh.regenerate
>
> and reboot, lots of things will get regenerated..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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/l7Clv4mdDFQ/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/CAOCHtYgrHFc2R6jUm%3D2vQGDWSZ%3D%2BzOs1Coe5qqmSNpTM%3DMg2Tw%40mail.gmail.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/CAA_M65Mby4q%3DaoRcjduqoHqYjOah1NRi2FEuTLFgjDLoXsxjnQ%40mail.gmail.com.

Re: [beagleboard] Re: Image duplication

[Paul Beam]

I could be networked so common host key or MAC address would be less than
optimal.  I will double check that.

On Tue, Feb 2, 2021 at 8:53 PM Tom Stepleton  wrote:

> I've never had trouble duplicating modified images --- it's how I
> distribute the software for my own project.
>
> This said, I suspect (but haven't checked) that all PocketBeagles running
> my images will have the same host key. It's not a big problem for me since
> my application is a standalone appliance for retrocomputing (so you seldom
> ever plug it into anything except the old computer and a power source).
>
> --Tom
> On Wednesday, February 3, 2021 at 12:15:01 AM UTC rpau...@gmail.com wrote:
>
>> Let's say I have tweaked an image for the PocketBeagle and want to
>> duplicate it for additional units.  Is it valid to just duplicate my
>> revised image, or is there something unique that has to be done for each
>> one?  I seem to recall somewhere in a boot script is something that runs
>> only the first time, but I currently can't find it and don't remember what
>> it does.
>
> --
> 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/l7Clv4mdDFQ/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/f5795d8d-75fa-4208-a7d5-398f4ca82343n%40googlegroups.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/CAA_M65PUOXmDhChw_n4R7FM%3Drxb%3DQyPtDGTWd0u4LG7rWoFi4w%40mail.gmail.com.

Re: [beagleboard] Re: Image duplication

[Robert Nelson]

On Tue, Feb 2, 2021 at 7:53 PM Tom Stepleton  wrote:
>
> I've never had trouble duplicating modified images --- it's how I distribute 
> the software for my own project.
>
> This said, I suspect (but haven't checked) that all PocketBeagles running my 
> images will have the same host key. It's not a big problem for me since my 
> application is a standalone appliance for retrocomputing (so you seldom ever 
> plug it into anything except the old computer and a power source).

sudo touch /etc/ssh/ssh.regenerate

and reboot, lots of things will get regenerated..

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/CAOCHtYgrHFc2R6jUm%3D2vQGDWSZ%3D%2BzOs1Coe5qqmSNpTM%3DMg2Tw%40mail.gmail.com.

[beagleboard] Re: Image duplication

[Tom Stepleton]

I've never had trouble duplicating modified images --- it's how I 
distribute the software for my own project.

This said, I suspect (but haven't checked) that all PocketBeagles running 
my images will have the same host key. It's not a big problem for me since 
my application is a standalone appliance for retrocomputing (so you seldom 
ever plug it into anything except the old computer and a power source).

--Tom
On Wednesday, February 3, 2021 at 12:15:01 AM UTC rpau...@gmail.com wrote:

> Let's say I have tweaked an image for the PocketBeagle and want to 
> duplicate it for additional units.  Is it valid to just duplicate my 
> revised image, or is there something unique that has to be done for each 
> one?  I seem to recall somewhere in a boot script is something that runs 
> only the first time, but I currently can't find it and don't remember what 
> it does.

-- 
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/f5795d8d-75fa-4208-a7d5-398f4ca82343n%40googlegroups.com.

Re: [beagleboard] Comms Cape

[Dwayne Zimmerman]

Steve
Thanks that helps a lot, but the agnd is not actually brought out to the 
terminal strip only the gnd. How do I attach to agnd?

On Tuesday, February 2, 2021 at 8:27:25 PM UTC-5 stl...@gmail.com wrote:

> The comms board 4-20mA current loop input consists of a 75Ω shunt resistor 
> across one of the analog input pins.  
>
> You need to connect an appropriate voltage source to your device and the 
> other end of your device to the comms board input.  Connect the ground of 
> your voltage source to the Analog Ground pin.  
>
> Divide the measured voltage by 75 to obtain the current.
>
> The cape does not provide a voltage source,  Many devices use 24V 
> excitation, but this is not universal.  Thus the choice of voltage source 
> is left to you.
>
> Hope this helps someone.  Schematic can be found here if you have any 
> doubts:  
> https://github.com/beagleboard/capes/blob/master/beaglebone/Comms/Comms_Cape_sch.pdf
>
>
>
>
>
> On Feb 2, 2021, at 8:14 PM, evilwulfie  wrote:
>
> you can use an current to voltage converter then an opamp to level shift it
>
> On 2/2/2021 5:03 PM, Dwayne Zimmerman wrote:
>
> Can anyone tell me how to connect a sensor to the 4-20mA input on the 
> comms board.I need temperature and all 4-20mA temperature sensors I'm 
> familiar with are 24 VDC not 1.8
>
> On Monday, February 1, 2021 at 7:29:46 PM UTC-5 Dennis Bieber wrote:
>
>> On Mon, 1 Feb 2021 15:46:51 -0800 (PST), in 
>> gmane.comp.hardware.beagleboard.user Dwayne Zimmerman 
>>  wrote: 
>>
>> >So the pull down is to keep the voltage under 1.8 correct? My confusion 
>> is 
>> >I have one screw per input, 4-20mA is two wire where is the other half 
>> of 
>> >the circut? 
>> > 
>>
>> I suspect the pull-down is only ensuring that the floating voltage is 
>> tied to 0V; feeding anything with a voltage over 1.8V will still fry the 
>> input. And since 0V likely also means 0mA, it indicates a fault condition 
>> in the loop. 
>>
>>
>> https://www.fluke.com/en-us/learn/best-practices/test-tools-basics/process-tools/what-is-a-4-20-ma-current-loop
>>  
>>
>> https://www.predig.com/indicatorpage/back-basics-fundamentals-4-20-ma-current-loops
>>  
>> {Many others| 
>>
>> The input to the BBB likely needs to consist of a current->voltage 
>> tranform, so the ADC can measure the voltage corresponding to the 
>> current. 
>> Which might be built-into the cape (I've not looked at it). 
>>
>>
>> -- 
>> Dennis L Bieber 
>>
>> -- 
> 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/5fd03d5f-b21f-43b8-b3d3-ae464ff8d1bdn%40googlegroups.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...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/9654dc5a-2d31-6f0f-a745-ae085db30859%40gmail.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/9f22b7ef-9eff-4f16-aa73-65fe71c9ff0dn%40googlegroups.com.

Re: [beagleboard] Image duplication

[Paul Beam]

That’s basically what I have been doing, but just wanted to make sure there
weren’t some one time operations that were being skipped.

On Tue, Feb 2, 2021 at 7:57 PM Robert Nelson 
wrote:

> On Tue, Feb 2, 2021 at 6:15 PM Paul Beam  wrote:
> >
> > Let's say I have tweaked an image for the PocketBeagle and want to
> duplicate it for additional units.  Is it valid to just duplicate my
> revised image, or is there something unique that has to be done for each
> one?  I seem to recall somewhere in a boot script is something that runs
> only the first time, but I currently can't find it and don't remember what
> it does.
>
> For the PocketBeagle, just dd the microSD to another microSD..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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/l7Clv4mdDFQ/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/CAOCHtYis9TTDd7DgtpJ18SJ0WyoKiJt7HRRwGnxgtcN9-7ERYQ%40mail.gmail.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/CAA_M65P3iYc2Swu_Od-ceF_PMtTSQhTUxcP5VRk6oZCkN3%2Benw%40mail.gmail.com.

Re: [beagleboard] Comms Cape

[Steve Lentz]

The comms board 4-20mA current loop input consists of a 75Ω shunt resistor 
across one of the analog input pins.  

You need to connect an appropriate voltage source to your device and the other 
end of your device to the comms board input.  Connect the ground of your 
voltage source to the Analog Ground pin.  

Divide the measured voltage by 75 to obtain the current.

The cape does not provide a voltage source,  Many devices use 24V excitation, 
but this is not universal.  Thus the choice of voltage source is left to you.

Hope this helps someone.  Schematic can be found here if you have any doubts:  
https://github.com/beagleboard/capes/blob/master/beaglebone/Comms/Comms_Cape_sch.pdf
 






> On Feb 2, 2021, at 8:14 PM, evilwulfie  wrote:
> 
> you can use an current to voltage converter then an opamp to level shift it
> 
> On 2/2/2021 5:03 PM, Dwayne Zimmerman wrote:
>> Can anyone tell me how to connect a sensor to the 4-20mA input on the comms 
>> board.I need temperature and all 4-20mA temperature sensors I'm familiar 
>> with are 24 VDC not 1.8
>> 
>> On Monday, February 1, 2021 at 7:29:46 PM UTC-5 Dennis Bieber wrote:
>> On Mon, 1 Feb 2021 15:46:51 -0800 (PST), in 
>> gmane.comp.hardware.beagleboard.user Dwayne Zimmerman 
>> > > wrote: 
>> 
>> >So the pull down is to keep the voltage under 1.8 correct? My confusion is 
>> >I have one screw per input, 4-20mA is two wire where is the other half of 
>> >the circut? 
>> > 
>> 
>> I suspect the pull-down is only ensuring that the floating voltage is 
>> tied to 0V; feeding anything with a voltage over 1.8V will still fry the 
>> input. And since 0V likely also means 0mA, it indicates a fault condition 
>> in the loop. 
>> 
>> https://www.fluke.com/en-us/learn/best-practices/test-tools-basics/process-tools/what-is-a-4-20-ma-current-loop
>>  
>> 
>>  
>> https://www.predig.com/indicatorpage/back-basics-fundamentals-4-20-ma-current-loops
>>  
>> 
>>  
>> {Many others| 
>> 
>> The input to the BBB likely needs to consist of a current->voltage 
>> tranform, so the ADC can measure the voltage corresponding to the current. 
>> Which might be built-into the cape (I've not looked at it). 
>> 
>> 
>> -- 
>> Dennis L Bieber 
>> 
>> -- 
>> 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/5fd03d5f-b21f-43b8-b3d3-ae464ff8d1bdn%40googlegroups.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/9654dc5a-2d31-6f0f-a745-ae085db30859%40gmail.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/2C68CEE2-3A98-4D73-95E2-1851938D8C73%40gmail.com.

Re: [beagleboard] RE: MotorCape w/ uboot_overlay and Errors with Sysfs Entries/BBBW

[set_]

Oh and Hello Again,

I forgot to mention the major change. 

So, instead of each motor handling its own PWM frequency in source along w/ 
duty_cycle, I had previously a method that handled one value that all 
motors were being controlled.

For instance:

def set_motorOne(v1):
motor1.set(v1)

def set_motorTwo(v2):
motor2.set(v2)

def set_motorThree(v3):
motor3.set(v3)

def set_motorFour(v4):
motor4.set(v4)

app = Flask(__name__)

@app.route("/")
def homepage(title="homepage"):
return render_template("BootGoOne.html", title=title)

def add_motors_routeOne(state, v1):
@app.route("/" + state, endpoint=state)
def handlerOne():
set_motorOne(v1)
if add_motors_routeOne == 0:
PWM.stop("P9_16")
else:
pass

return homepage(title=state)

add_motors_routeOne("0",   0)
add_motors_routeOne('40', 40)
add_motors_routeOne('50', 50)
add_motors_routeOne('60', 60)
add_motors_routeOne('70', 70)
add_motors_routeOne('80', 80)
add_motors_routeOne('90', 90)
add_motors_routeOne('100', 100)


   - The above source handles, what I thought would be, one motor and the 
   peripherals of pwm and gpio.
   - The below source is what worked w/out the addition of three motors, 
   separate values per motor, and no "failsafe."

def set_motors(v1, v2, v3, v4):
motor1.set(v1)
motor2.set(v2)
motor3.set(v3)
motor4.set(v4)

 app = Flask(__name__)

@app.route("/")
def homepage(title="homepage"):
return render_template("BootGoOne.html", title=title)

def add_motors_route(state, v1, v2, v3, v4):
@app.route("/" + state, endpoint=state)
def handlerOne():
set_motors(v1, v2, v3, v4)
# if add_motors_routeOne == 0:
# PWM.stop("P9_16")
else:
pass

return homepage(title=state)

add_motors_route('0',   0)
add_motors_route('25',  25)

and etc...

That is all. 

Seth
On Tuesday, February 2, 2021 at 7:15:43 PM UTC-6 set_ wrote:

> Hello,
>
> Well...when I say working, I mean remedially working. Sysfs did return 
> errors and I was always receiving the error about multiple values that are 
> exactly the same.
>
> I basically changed the source to handle four motors, added a server, and 
> managed to adopt a "kill switch" in source via the Adafruit_BBIO.PWM 
> functions and Adafruit_BBIO.GPIO functions.
>
> Seth
>
> P.S. One of the four motors seems nice but when I am making a quadruped, 
> four motors are needed so far. Anyway, do you see an issue w/ the source as 
> it may be as of now?
>
> On Tuesday, February 2, 2021 at 7:32:08 AM UTC-6 evilw...@gmail.com wrote:
>
>> On 2/2/2021 6:20 AM, set_ wrote:
>>
>> Hello, 
>>
>> I have just come across some issues:
>>
>>
>>- What once worked does not work any longer 
>>
>> What did you do between it working and it not working ?
>>
>>
>>
>>- The source has changed a bit but I am receiving an error before the 
>>changes 
>>- I have some Python3 source and a server via Flask and HTML 
>>
>> I am giving this source below to better make you understand what is 
>> happening on my end of the spectrum. Oh and...for some reason, the source 
>> only allows for non-like numerical values.
>>
>> uname -a >>> Linux beaglebone 4.19.94-ti-r58
>> cat /etc/dogtag >>> BeagleBoard.org Debian Buster IoT Image 2020-04-06
>> ...
>>
>> For the uboot_overlay, here is the command to look it over w/ my overlay:
>>
>> cat /boot/uEnv.txt >>> ###Overide capes with eeprom
>> uboot_overlay_addr0=/lib/firmware/BBORG_MOTOR-00A2.dtbo
>>
>> oh and the source:
>>
>> #!/usr/bin/python3
>>
>> from flask import Flask, render_template
>> import Adafruit_BBIO.GPIO as GPIO
>> import Adafruit_BBIO.PWM as PWM
>> from time import sleep
>>
>> class Motor:
>> def __init__(self, dir_pin, pwm_pin, pwm_freq):
>> self.dir_pin = dir_pin
>> self.pwm_pin = pwm_pin
>> self.value = 0
>>
>> PWM.start(pwm_pin, 0, pwm_freq)
>> GPIO.setup(dir_pin, GPIO.OUT)
>>
>> def set(self, value):
>> if value == self.value:
>> return
>>
>> assert -100 <= value <= 100
>>
>> if (value < 0) != (self.value < 0):
>> # changing direction
>> PWM.set_duty_cycle(self.pwm_pin, 0)
>> GPIO.output(self.dir_pin, value < 0)
>>
>> PWM.set_duty_cycle(self.pwm_pin, abs(value))
>> self.value = value
>>
>> motor1 = Motor(dir_pin="P8_18", pwm_pin="P9_16", pwm_freq=1000)
>> motor2 = Motor(dir_pin="P8_16", pwm_pin="P9_14", pwm_freq=1000)
>> motor3 = Motor(dir_pin="P8_14", pwm_pin="P8_13", pwm_freq=1000)
>> motor4 = Motor(dir_pin="P8_26", pwm_pin="P8_19", pwm_freq=1000)
>>
>> def 

Re: [beagleboard] Re: Comms Cape

[evilwulfie]

you can use an current to voltage converter then an opamp to level shift it

On 2/2/2021 5:03 PM, Dwayne Zimmerman wrote:
Can anyone tell me how to connect a sensor to the 4-20mA input on the 
comms board.I need temperature and all 4-20mA temperature sensors I'm 
familiar with are 24 VDC not 1.8


On Monday, February 1, 2021 at 7:29:46 PM UTC-5 Dennis Bieber wrote:

On Mon, 1 Feb 2021 15:46:51 -0800 (PST), in
gmane.comp.hardware.beagleboard.user Dwayne Zimmerman
 wrote:

>So the pull down is to keep the voltage under 1.8 correct? My
confusion is
>I have one screw per input, 4-20mA is two wire where is the other
half of
>the circut?
>

I suspect the pull-down is only ensuring that the floating voltage is
tied to 0V; feeding anything with a voltage over 1.8V will still
fry the
input. And since 0V likely also means 0mA, it indicates a fault
condition
in the loop.


https://www.fluke.com/en-us/learn/best-practices/test-tools-basics/process-tools/what-is-a-4-20-ma-current-loop




https://www.predig.com/indicatorpage/back-basics-fundamentals-4-20-ma-current-loops



{Many others|

The input to the BBB likely needs to consist of a current->voltage
tranform, so the ADC can measure the voltage corresponding to the
current.
Which might be built-into the cape (I've not looked at it).


-- 
Dennis L Bieber


--
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/5fd03d5f-b21f-43b8-b3d3-ae464ff8d1bdn%40googlegroups.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/9654dc5a-2d31-6f0f-a745-ae085db30859%40gmail.com.

Re: [beagleboard] RE: MotorCape w/ uboot_overlay and Errors with Sysfs Entries/BBBW

[set_]

Hello,

Well...when I say working, I mean remedially working. Sysfs did return 
errors and I was always receiving the error about multiple values that are 
exactly the same.

I basically changed the source to handle four motors, added a server, and 
managed to adopt a "kill switch" in source via the Adafruit_BBIO.PWM 
functions and Adafruit_BBIO.GPIO functions.

Seth

P.S. One of the four motors seems nice but when I am making a quadruped, 
four motors are needed so far. Anyway, do you see an issue w/ the source as 
it may be as of now?

On Tuesday, February 2, 2021 at 7:32:08 AM UTC-6 evilw...@gmail.com wrote:

> On 2/2/2021 6:20 AM, set_ wrote:
>
> Hello, 
>
> I have just come across some issues:
>
>
>- What once worked does not work any longer 
>
> What did you do between it working and it not working ?
>
>
>
>- The source has changed a bit but I am receiving an error before the 
>changes 
>- I have some Python3 source and a server via Flask and HTML 
>
> I am giving this source below to better make you understand what is 
> happening on my end of the spectrum. Oh and...for some reason, the source 
> only allows for non-like numerical values.
>
> uname -a >>> Linux beaglebone 4.19.94-ti-r58
> cat /etc/dogtag >>> BeagleBoard.org Debian Buster IoT Image 2020-04-06
> ...
>
> For the uboot_overlay, here is the command to look it over w/ my overlay:
>
> cat /boot/uEnv.txt >>> ###Overide capes with eeprom
> uboot_overlay_addr0=/lib/firmware/BBORG_MOTOR-00A2.dtbo
>
> oh and the source:
>
> #!/usr/bin/python3
>
> from flask import Flask, render_template
> import Adafruit_BBIO.GPIO as GPIO
> import Adafruit_BBIO.PWM as PWM
> from time import sleep
>
> class Motor:
> def __init__(self, dir_pin, pwm_pin, pwm_freq):
> self.dir_pin = dir_pin
> self.pwm_pin = pwm_pin
> self.value = 0
>
> PWM.start(pwm_pin, 0, pwm_freq)
> GPIO.setup(dir_pin, GPIO.OUT)
>
> def set(self, value):
> if value == self.value:
> return
>
> assert -100 <= value <= 100
>
> if (value < 0) != (self.value < 0):
> # changing direction
> PWM.set_duty_cycle(self.pwm_pin, 0)
> GPIO.output(self.dir_pin, value < 0)
>
> PWM.set_duty_cycle(self.pwm_pin, abs(value))
> self.value = value
>
> motor1 = Motor(dir_pin="P8_18", pwm_pin="P9_16", pwm_freq=1000)
> motor2 = Motor(dir_pin="P8_16", pwm_pin="P9_14", pwm_freq=1000)
> motor3 = Motor(dir_pin="P8_14", pwm_pin="P8_13", pwm_freq=1000)
> motor4 = Motor(dir_pin="P8_26", pwm_pin="P8_19", pwm_freq=1000)
>
> def set_motorOne(v1):
> motor1.set(v1)
>
> def set_motorTwo(v2):
> motor2.set(v2)
>
> def set_motorThree(v3):
> motor3.set(v3)
>
> def set_motorFour(v4):
> motor4.set(v4)
>
> app = Flask(__name__)
>
> @app.route("/")
> def homepage(title="homepage"):
> return render_template("BootGoOne.html", title=title)
>
> def add_motors_routeOne(state, v1):
> @app.route("/" + state, endpoint=state)
> def handlerOne():
> set_motorOne(v1)
> if add_motors_routeOne == 0:
> PWM.stop("P9_16")
> else:
> pass
>
> return homepage(title=state)
>
> add_motors_routeOne("0",   0)
> add_motors_routeOne('40', 40)
> add_motors_routeOne('50', 50)
> add_motors_routeOne('60', 60)
> add_motors_routeOne('70', 70)
> add_motors_routeOne('80', 80)
> add_motors_routeOne('90', 90)
> add_motors_routeOne('100', 100)
>
> Okay...so:
>
>
>- When I add another 'add_motors_routeOne' as a separate call under 
>another motor, I get some odd behavior. 
>   - For instance, 'add_motors_routeTwo', would begin to make issues 
>   with calling 'add_motors_routeTwo("0", 0) at the value 0.  
>
> Anyway...the issue is that it begins to be a sysfs issue or an assertion 
> error on my part.
>
> Traceback (most recent call last):
>   File "Moto/motocape/MotorCapeOne/MotorCapeTwo.py", line 92, in 
> 
> add_motors_routeTwo("0",   0)
>   File "Moto/motocape/MotorCapeOne/MotorCapeTwo.py", line 83, in
>  add_motors_routeTwo
> @app.route("/" + state, endpoint=state)
>   File "/usr/lib/python3/dist-packages/flask/app.py", line 1250, in 
> decorator
> self.add_url_rule(rule, endpoint, f, **options)
>   File "/usr/lib/python3/dist-packages/flask/app.py", line 66, in 
> wrapper_func
> return f(self, *args, **kwargs)
>   File "/usr/lib/python3/dist-packages/flask/app.py", line 1221, in 
> add_url_rule
> 'existing endpoint function: %s' % endpoint)
> AssertionError: View function mapping is overwriting an existing 
> endpoint function: 0
>
> Above is where you can find my error with the current config. of the 
> python3 source from above.
>

Re: [beagleboard] Image duplication

[Robert Nelson]

On Tue, Feb 2, 2021 at 6:15 PM Paul Beam  wrote:
>
> Let's say I have tweaked an image for the PocketBeagle and want to duplicate 
> it for additional units.  Is it valid to just duplicate my revised image, or 
> is there something unique that has to be done for each one?  I seem to recall 
> somewhere in a boot script is something that runs only the first time, but I 
> currently can't find it and don't remember what it does.

For the PocketBeagle, just dd the microSD to another microSD..

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/CAOCHtYis9TTDd7DgtpJ18SJ0WyoKiJt7HRRwGnxgtcN9-7ERYQ%40mail.gmail.com.

[beagleboard] Image duplication

[Paul Beam]

Let's say I have tweaked an image for the PocketBeagle and want to 
duplicate it for additional units.  Is it valid to just duplicate my 
revised image, or is there something unique that has to be done for each 
one?  I seem to recall somewhere in a boot script is something that runs 
only the first time, but I currently can't find it and don't remember what 
it does.

-- 
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/58b8b2dc-d776-4c35-aa4c-a62c1bbba119n%40googlegroups.com.

[beagleboard] Re: Comms Cape

[Dwayne Zimmerman]

Can anyone tell me how to connect a sensor to the 4-20mA input on the comms 
board.I need temperature and all 4-20mA temperature sensors I'm familiar 
with are 24 VDC not 1.8

On Monday, February 1, 2021 at 7:29:46 PM UTC-5 Dennis Bieber wrote:

> On Mon, 1 Feb 2021 15:46:51 -0800 (PST), in
> gmane.comp.hardware.beagleboard.user Dwayne Zimmerman
>  wrote:
>
> >So the pull down is to keep the voltage under 1.8 correct? My confusion 
> is 
> >I have one screw per input, 4-20mA is two wire where is the other half of 
> >the circut?
> >
>
> I suspect the pull-down is only ensuring that the floating voltage is
> tied to 0V; feeding anything with a voltage over 1.8V will still fry the
> input. And since 0V likely also means 0mA, it indicates a fault condition
> in the loop.
>
>
> https://www.fluke.com/en-us/learn/best-practices/test-tools-basics/process-tools/what-is-a-4-20-ma-current-loop
>
> https://www.predig.com/indicatorpage/back-basics-fundamentals-4-20-ma-current-loops
> {Many others|
>
> The input to the BBB likely needs to consist of a current->voltage
> tranform, so the ADC can measure the voltage corresponding to the current.
> Which might be built-into the cape (I've not looked at it).
>
>
> -- 
> Dennis L Bieber
>
>

-- 
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/5fd03d5f-b21f-43b8-b3d3-ae464ff8d1bdn%40googlegroups.com.

[beagleboard] Re: Please roast my new PocketBeagle device tree overlay

[Tom Stepleton]

I've come up with a minimal working version of the file now for my 
application (appended below), and rather than see if anyone's up for a 
general review like I did earlier, maybe it would be easier to post some 
more specific questions here. I would love to understand better what the 
parts of this device tree overlay are doing, so if anyone has any insights, 
I'd be very grateful to hear them.


   1. I compile my device tree overlay this way: is it correct?
 cpp -I/opt/source/bb.org-overlays/include MY-DT-OVERLAY.dts -P -o 
   tmp.dts
 dtc -@ -I dts -O dtb -o MY-DT-OVERLAY.dtbo tmp.dts
   Is it right to use the C preprocessor in this way? I note that the 
   preprocessor is substituting a value for __TIMESTAMP__ in fragment@0 --- is 
   this correct, or should __TIMESTAMP__ be left un-substituted so that dtc 
   can see it?
   
   2. fragment@1 reserves some header pins so that the pinmux helper 
   doesn't use them. Is this necessary? Is there a reason that PB-eqep2.dts 
   

 
   doesn't reserve the resources it uses? (I studied a lot of examples in the 
   BB.org overlays and this stood out to me.)
   
   3. fragment@2 --- is it the case that this fragment is just defining a 
   pinmux configuration, and that the configuration actually gets put to use 
   elsewhere?
   
   4. fragment@3 --- is it correct that this fragment does both of the 
   following things:
  1. enable the PRUs somehow?
  2. somehow makes the PRU system configuration put the fragment@2 
  pinmux configuration into effect?
  Is there anything else that this fragment does? Does it make the pins 
  available to the PRUs in some way beyond just configuring the pinmux? (In 
  other words, why does the pruss fragment have pinctrl-names and pinctrl-0 
  parameters?)
  
  5. Potentially answering my Question #2, I think that PB-eqep2.dts 
   

 
   is basically doing things in a different way --- it's turning on some 
   on-chip peripherals and then configuring the pinmux with some new symbols, 
   but in a way that would still allow you to use config-pins to reuse the 
   header pins for something else. (My fragment@1 does not allow this.) Is 
   that interpretation correct? Could I have taken this approach somehow, or 
   is it better to set up pins for a "PRU-heavy" application using the method 
   I'm using here?
   
   6. In the pruss fragment for the Replicape, I found some additional 
   labeling of pins 
   
.
 
   What's that all about? I don't need it for my application, but as that 
   stuff uses custom names, I've found it hard to search for what's going on.
   
   7. Finally, *just in case* you happened to notice --- did anything look 
   weird or wrong in my overlay file below?
   

Thanks as ever,
--Tom


/dts-v1/;
/plugin/;

/* This header file doesn't exist on our pocketbeagle, so we replicate
 * necessary symbols manually. */
/* #include  */
#define PB_P1_02 0x08e4
#define PB_P1_29 0x09ac
#define PB_P1_30 0x0974
#define PB_P1_31 0x09a0
#define PB_P1_33 0x0994
#define PB_P1_36 0x0990
#define PB_P2_09 0x0984
#define PB_P2_24 0x0830
#define PB_P2_28 0x09a8
#define PB_P2_30 0x099c
#define PB_P2_32 0x0998
#define PB_P2_34 0x09a4
#define PB_P2_35 0x08e0

#include 
#include 

/ {
/* For showing loaded overlays at 
/proc/device-tree/chosen/overlays/ */
fragment@0 {
target-path = "/";
__overlay__ {
chosen {
overlays {
PB-CAMEO-APHID = __TIMESTAMP__;
};
};
};
};

/* Reserve these header pins so the pinmux helpers don't claim 
them. */
fragment@1 {
target = <>;
__overlay__ {
P1_02_pinmux { status = "disabled"; };
P1_29_pinmux { status = "disabled"; };
P1_30_pinmux { status = "disabled"; };
P1_31_pinmux { status = "disabled"; };
P1_33_pinmux { status = "disabled"; };
P1_36_pinmux { status = "disabled"; };
P2_09_pinmux { status = "disabled"; };
P2_24_pinmux { status = "disabled"; };
P2_28_pinmux { status = "disabled"; };
P2_30_pinmux { status = "disabled"; };
P2_32_pinmux { status = "disabled"; };
P2_34_pinmux { status = "disabled"; };
P2_35_pinmux { status = "disabled"; };
};
};

/* Introduce a pinmux configuration for 

Re: [beagleboard] BBB cannot access Internet

[Eli]

Thank you Jonny!

Your link looks great. Some of the steps I already performed,  but some - I
will hopefully try this evening. The article also helped my to realize a
mistake. I saw a different configuration for Ethernet and WiFi, but I
thought it refers to how my BBB is connected to the laptop, while now I
understand it refers to how my laptop is connected to the router.

Will update you with the result.
Appreciate your help !

Eli

בתאריך יום ג׳, 2 בפבר׳ 2021, 21:45, מאת jonnymo ‏:

> Try the instructions from this link.  It works for me:
>
> https://www.digikey.com/en/maker/blogs/how-to-connect-a-beaglebone-black-to-the-internet-using-usb
>
> Cheers,
>
> Jon
>
> On Tue, Feb 2, 2021 at 11:41 AM Eli  wrote:
>
>> Hello
>>
>> I am an absolute beginner with the BeagleBone Black and Linux, the
>> learning is not easy ...
>> I can boot my BBB from the SD Card and then get access the board from the
>> browser.
>> http://192.168.7.2/
>>
>> The BBB is connected to my laptop  through USB and I also tried to
>> connect through the Ethernet cable, while USB is used as Power Supply.
>>
>> There  I see the message that I "need to upgrade my SW". However I have
>> been fighting a few days and so far I have failed. I am trying to get the
>> update by performing git pull, but that what I see:
>>
>> fatal: unable to access 'https://github.com/RobertCNelson/boot-scripts/':
>> Could not resolve host: github.com
>>
>> I removed Antivirus and tried to disable Windows firewalls - still can't.
>> I did that because I believe the problem is in some TCP IP Network
>> configuration on my laptop.
>>
>> I tried to follow these instructions:
>> http://derekmolloy.ie/set-ip-address-to-be-static-on-the-beaglebone-black/
>>
>> I am facing the same result. Derek in the article above writes:
>> "The BBB then has a static IP address after reboot. The same procedure
>> applies to other adapter entries, such as the wlan0 wireless Ethernet
>> adapter. Do not pick an address that is within the DHCP pool or assigned to
>> another device, or it will result in IP conflicts on the network." Actually
>> did not apply the required procedure on my laptop, because I actually
>> didn't understand the instruction.
>>
>> Do you have any idea that can help me to troubleshoot and resolve the
>> problem? Thank you in advance for any help !
>>
>> Eli
>>
>>
>>
>>
>> --
>> 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/e086baee-84fd-4810-b97f-1ae55ceeb49fn%40googlegroups.com
>> 
>> .
>>
> --
> 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/E5SYPwLenSg/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/CAG99bkoxmn2fE%2BTGeRu23VAJ%2BNhPw8De-OJogvOD%3DONruufegg%40mail.gmail.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/CAE0w4R8FpxuWofB5UDdVXisWx2OTt-ef36Y1o5D38G-oFb7Pug%40mail.gmail.com.

Re: [beagleboard] BBB cannot access Internet

[jonnymo]

Try the instructions from this link.  It works for me:
https://www.digikey.com/en/maker/blogs/how-to-connect-a-beaglebone-black-to-the-internet-using-usb

Cheers,

Jon

On Tue, Feb 2, 2021 at 11:41 AM Eli  wrote:

> Hello
>
> I am an absolute beginner with the BeagleBone Black and Linux, the
> learning is not easy ...
> I can boot my BBB from the SD Card and then get access the board from the
> browser.
> http://192.168.7.2/
>
> The BBB is connected to my laptop  through USB and I also tried to connect
> through the Ethernet cable, while USB is used as Power Supply.
>
> There  I see the message that I "need to upgrade my SW". However I have
> been fighting a few days and so far I have failed. I am trying to get the
> update by performing git pull, but that what I see:
>
> fatal: unable to access 'https://github.com/RobertCNelson/boot-scripts/':
> Could not resolve host: github.com
>
> I removed Antivirus and tried to disable Windows firewalls - still can't.
> I did that because I believe the problem is in some TCP IP Network
> configuration on my laptop.
>
> I tried to follow these instructions:
> http://derekmolloy.ie/set-ip-address-to-be-static-on-the-beaglebone-black/
>
> I am facing the same result. Derek in the article above writes:
> "The BBB then has a static IP address after reboot. The same procedure
> applies to other adapter entries, such as the wlan0 wireless Ethernet
> adapter. Do not pick an address that is within the DHCP pool or assigned to
> another device, or it will result in IP conflicts on the network." Actually
> did not apply the required procedure on my laptop, because I actually
> didn't understand the instruction.
>
> Do you have any idea that can help me to troubleshoot and resolve the
> problem? Thank you in advance for any help !
>
> Eli
>
>
>
>
> --
> 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/e086baee-84fd-4810-b97f-1ae55ceeb49fn%40googlegroups.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/CAG99bkoxmn2fE%2BTGeRu23VAJ%2BNhPw8De-OJogvOD%3DONruufegg%40mail.gmail.com.

[beagleboard] BBB cannot access Internet

[Eli]

Hello

I am an absolute beginner with the BeagleBone Black and Linux, the learning 
is not easy ...
I can boot my BBB from the SD Card and then get access the board from the 
browser. 
http://192.168.7.2/

The BBB is connected to my laptop  through USB and I also tried to connect 
through the Ethernet cable, while USB is used as Power Supply.

There  I see the message that I "need to upgrade my SW". However I have 
been fighting a few days and so far I have failed. I am trying to get the 
update by performing git pull, but that what I see:

fatal: unable to access 'https://github.com/RobertCNelson/boot-scripts/': 
Could not resolve host: github.com

I removed Antivirus and tried to disable Windows firewalls - still can't. I 
did that because I believe the problem is in some TCP IP Network 
configuration on my laptop.

I tried to follow these instructions:
http://derekmolloy.ie/set-ip-address-to-be-static-on-the-beaglebone-black/

I am facing the same result. Derek in the article above writes:
"The BBB then has a static IP address after reboot. The same procedure 
applies to other adapter entries, such as the wlan0 wireless Ethernet 
adapter. Do not pick an address that is within the DHCP pool or assigned to 
another device, or it will result in IP conflicts on the network." Actually 
did not apply the required procedure on my laptop, because I actually 
didn't understand the instruction.

Do you have any idea that can help me to troubleshoot and resolve the 
problem? Thank you in advance for any help !

Eli




-- 
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/e086baee-84fd-4810-b97f-1ae55ceeb49fn%40googlegroups.com.

[beagleboard] Re: BeagleBone Green does not work after kernel update

[willy simangunsong]

Hello everyone, I need a hand from all of you, if you have a driver for 
BBG, please reply my email

Regards,


Pada Minggu, 17 Januari 2021 pukul 13.27.22 UTC+7 set_ menulis:

> Hello,
>
> Use the serial console instead of ssh. Then, use this command: ip addr. 
> Find what the ip address to your machine is currently. Then, use that to 
> sign in.
>
> Seth
>
> On Saturday, January 16, 2021 at 12:31:47 PM UTC-6 zuzh...@gmail.com 
> wrote:
>
>> Hi everyone
>>
>> I have a BeagleBone Green on my hand and ran with a old kernel from 2017. 
>> I notice the device has some issues and they may lie in the kernel, so I 
>> did a kernel update as instructed here .
>>
>> After the update, I tried to reboot it but it never came up again, so I 
>> unplugged the power and powered on again. 
>> The BeagleBone started, but I couldn't SSH to the device. And the USB is 
>> enumerated as USB COM PORT on my PC (WIN10 64bits)
>>
>> I tried many things to bring it back but it didn't work.
>>
>> What should I do now? Should I re-flash the whole image with SD card?
>>
>> Thanks a lot in advance!
>>
>

-- 
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/36886a60-a130-4c2f-8970-238294a04250n%40googlegroups.com.

Re: [beagleboard] Re: WiFi connectivity and possible external power supplies for BBAI

[willy simangunsong]

Haloo guyss, I need your hand please, if you have a driver for BBG please 
reply this email. Thank you so much


Regards,

Pada Senin, 28 September 2020 pukul 01.19.27 UTC+7 Fisher Grubb menulis:

> Hi all,
>
> Thanks for your input, its very strange.  I got it working, by pinging the 
> IP address from my laptop.
>
> They are both connected to the same WiFi network.  The routing table 
> hasn't changed at all, but I noticed that it took like 5 seconds to 
> generate.  I assumed that might have been normal for this board, but now 
> its instantaneous.
>
> This device was given 192.168.1.175 via DHCP by my WiFi modem, so, I could 
> ping it from my laptop through the WiFi network.
>
> I've rebooted, and it connects as normal, and internet via WiFi works 
> immediately.
>
> Very strange, any ideas?
>
> I'll reply here if anything changes.
> Fisher
>
> On Sat, 26 Sep 2020 at 03:38, jonnymo  wrote:
>
>> In your /var/lib/connman folder you should have a file associated with 
>> your wlan0 config.
>>
>> ex:
>> * $  sudo ls 
>>  /var/lib/connman/wifi_8091334a1523_4d6f4e6574494f54_managed_psk/*
>> *data  settings*
>>
>> In the psk settings file, I tend to set this manually as such:
>>
>> *Name=MySSID*
>> *SSID=pk2-passwd*
>> *Frequency=2462*
>> *Favorite=true*
>> *AutoConnect=true*
>> *Modified=2020-09-24T07:36:19.092924Z*
>> *Passphrase=mypasswd*
>> *IPv4.method=manual*
>> *IPv4.netmask_prefixlen=21*
>> *IPv6.method=off*
>> *IPv6.privacy=disabled*
>> *Hidden=true*
>> *IPv4.local_address=192.168.2.210*
>> *IPv4.gateway=192.168.2.1*
>> *Nameservers=8.8.8.8;8.8.4.4;4.4.4.4;*
>>
>> The "Nameservers" setting wll set the /etc/resolv.conf with the 
>> nameserver associated with wlan0 and the same is so for  IPv4.gateway if 
>> you are running IPv4.
>>
>> This can be done manually as such:
>>
>> *# connmanctl config  --ipv4 manual   
>> *
>> *# connmanctl config  --nameservers *
>>
>> Ref:
>>  https://variwiki.com/index.php?title=Static_IP_Address
>>
>> If your eth0 is not defined with nameservers and gateway, it is possible 
>> it will overwrite the /etc/resolv.conf when you plug in an ethernet cable 
>> and not set it when it is disconnected.  One test would be to reboot the 
>> board and see if the wlan0 connection recovers. Another is to  check 
>> /etc/resolv.conf when you plug in the ethernet cable and then when you 
>> disconnect it.
>>
>> You can also use 'dmesg' to see if there are any networking errors being 
>> reported when you are changing network connects. 
>>
>>
>> Cheers,
>>
>> Jon
>>
>>
>>
>> On Fri, Sep 25, 2020 at 8:21 AM  wrote:
>>
>>> Hi all,
>>>
>>> I'm also having issues with getting internet via WiFi on this BB-AI 
>>> board.
>>>
>>> It connects to my WiFi network, gets a DHCP address, the routing table 
>>> shows the default route is 192.168.1.1, through wlan0 interface etc, 
>>> exactly the same top line of Matt's table.
>>> The WiFi LED goes green (right next to the Ethernet port).
>>>
>>> I've connected through Ethernet and upgraded the software, but same 
>>> issue with WiFi connected but no network through it.
>>>
>>> It automatically sets the routing interface to Eth0 when I plug the 
>>> Ethernet in, then sets its back to wlan0 when I unplug it so that's great 
>>> but still no signs of life.
>>>
>>> There are a bunch of scripts in /opt/scripts, and configs in 
>>> /etc/default.
>>> In /etc/default, there's a settings file bb-wl18xx with 
>>> "TETHER_ENABLED=yes", I've changed it to "no".  That caused connman to not 
>>> connect the WiFi automatically, so I used connmancltl to set the agent back 
>>> on for it to connect again.
>>>
>>> What else can I check and change?  I've put my connman settings and 
>>> route command output are below, to me they show everything set up for this 
>>> to work.
>>> My assumption is that either its a separate setting relating to boot 
>>> scripts etc, or its a driver/firmware issue.
>>>
>>> I've had this issue previously, but it worked once on the original board 
>>> image, but after updating to the latest image, it just doesn't work at all.
>>>
>>> My connman settings file in /var/lib/connman/
>>>
>>> [global]
>>> OfflineMode=false
>>>
>>> [Wired]
>>> Enable=true
>>> Tethering=false
>>>
>>> [WiFi]
>>> Enable=true
>>> Tethering=false
>>>
>>> [Gadget]
>>> Enable=false
>>> Tethering=false
>>>
>>> [P2P]
>>> Enable=false
>>> Tethering=false
>>>
>>> [Bluetooth]
>>> Enable=true
>>> Tethering=false
>>>
>>>
>>> *fisher@beaglebone*:*~*$route 
>>> Kernel IP routing table 
>>> DestinationGateway GenmaskFlags Metric Ref   Use 
>>> Iface 
>>> default 192.168.1.10.0.0.0 UG   0  00 
>>> wlan0 
>>> 192.168.1.0 0.0.0.0255.255.255.0   U0  00 
>>> wlan0 
>>> 192.168.1.1 0.0.0.0255.255.255.255 UH   0  00 
>>> wlan0 
>>> 192.168.6.0 0.0.0.0255.255.255.0   U0  00 
>>> usb1 
>>> 192.168.7.0 0.0.0.0255.255.255.0   U0  00 

Re: [beagleboard] RE: MotorCape w/ uboot_overlay and Errors with Sysfs Entries/BBBW

[evilwulfie]

On 2/2/2021 6:20 AM, set_ wrote:

Hello,

I have just come across some issues:

  * What once worked does not work any longer


What did you do between it working and it not working ?



  * The source has changed a bit but I am receiving an error before
the changes
  * I have some Python3 source and a server via Flask and HTML

I am giving this source below to better make you understand what is 
happening on my end of the spectrum. Oh and...for some reason, the 
source only allows for non-like numerical values.


uname -a >>> Linux beaglebone 4.19.94-ti-r58
cat /etc/dogtag >>> BeagleBoard.org Debian Buster IoT Image 2020-04-06
...

For the uboot_overlay, here is the command to look it over w/ my overlay:

cat /boot/uEnv.txt >>> ###Overide capes with eeprom
uboot_overlay_addr0=/lib/firmware/BBORG_MOTOR-00A2.dtbo

oh and the source:

    #!/usr/bin/python3

    from flask import Flask, render_template
    import Adafruit_BBIO.GPIO as GPIO
    import Adafruit_BBIO.PWM as PWM
    from time import sleep

    class Motor:
        def __init__(self, dir_pin, pwm_pin, pwm_freq):
            self.dir_pin = dir_pin
            self.pwm_pin = pwm_pin
            self.value = 0

            PWM.start(pwm_pin, 0, pwm_freq)
            GPIO.setup(dir_pin, GPIO.OUT)

        def set(self, value):
            if value == self.value:
                return

            assert -100 <= value <= 100

            if (value < 0) != (self.value < 0):
                # changing direction
                PWM.set_duty_cycle(self.pwm_pin, 0)
                GPIO.output(self.dir_pin, value < 0)

            PWM.set_duty_cycle(self.pwm_pin, abs(value))
            self.value = value

    motor1 = Motor(dir_pin="P8_18", pwm_pin="P9_16", pwm_freq=1000)
    motor2 = Motor(dir_pin="P8_16", pwm_pin="P9_14", pwm_freq=1000)
    motor3 = Motor(dir_pin="P8_14", pwm_pin="P8_13", pwm_freq=1000)
    motor4 = Motor(dir_pin="P8_26", pwm_pin="P8_19", pwm_freq=1000)

    def set_motorOne(v1):
        motor1.set(v1)

    def set_motorTwo(v2):
        motor2.set(v2)

    def set_motorThree(v3):
        motor3.set(v3)

    def set_motorFour(v4):
        motor4.set(v4)

    app = Flask(__name__)

    @app.route("/")
    def homepage(title="homepage"):
        return render_template("BootGoOne.html", title=title)

    def add_motors_routeOne(state, v1):
        @app.route("/" + state, endpoint=state)
        def handlerOne():
            set_motorOne(v1)
            if add_motors_routeOne == 0:
                PWM.stop("P9_16")
            else:
                pass

            return homepage(title=state)

    add_motors_routeOne("0",   0)
    add_motors_routeOne('40', 40)
    add_motors_routeOne('50', 50)
    add_motors_routeOne('60', 60)
    add_motors_routeOne('70', 70)
    add_motors_routeOne('80', 80)
    add_motors_routeOne('90', 90)
    add_motors_routeOne('100', 100)

Okay...so:

  * When I add another 'add_motors_routeOne' as a separate call under
another motor, I get some odd behavior.
  o For instance, 'add_motors_routeTwo', would begin to make
issues with calling 'add_motors_routeTwo("0", 0) at the value 0.

Anyway...the issue is that it begins to be a sysfs issue or an 
assertion error on my part.


    Traceback (most recent call last):
      File "Moto/motocape/MotorCapeOne/MotorCapeTwo.py", line 92, in 


        add_motors_routeTwo("0",   0)
      File "Moto/motocape/MotorCapeOne/MotorCapeTwo.py", line 83, in  
   add_motors_routeTwo

        @app.route("/" + state, endpoint=state)
      File "/usr/lib/python3/dist-packages/flask/app.py", line 1250, 
in decorator

        self.add_url_rule(rule, endpoint, f, **options)
      File "/usr/lib/python3/dist-packages/flask/app.py", line 66, in 
wrapper_func

        return f(self, *args, **kwargs)
      File "/usr/lib/python3/dist-packages/flask/app.py", line 1221, 
in add_url_rule

        'existing endpoint function: %s' % endpoint)
    AssertionError: View function mapping is overwriting an existing 
endpoint function: 0


Above is where you can find my error with the current config. of the 
python3 source from above.


Seth
--
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/df02989e-74bf-4678-8300-2c7d968b0c3an%40googlegroups.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 

[beagleboard] RE: MotorCape w/ uboot_overlay and Errors with Sysfs Entries/BBBW

[set_]

Hello,

I have just come across some issues:


   - What once worked does not work any longer
   - The source has changed a bit but I am receiving an error before the 
   changes
   - I have some Python3 source and a server via Flask and HTML

I am giving this source below to better make you understand what is 
happening on my end of the spectrum. Oh and...for some reason, the source 
only allows for non-like numerical values.

uname -a >>> Linux beaglebone 4.19.94-ti-r58
cat /etc/dogtag >>> BeagleBoard.org Debian Buster IoT Image 2020-04-06
...

For the uboot_overlay, here is the command to look it over w/ my overlay:

cat /boot/uEnv.txt >>> ###Overide capes with eeprom
uboot_overlay_addr0=/lib/firmware/BBORG_MOTOR-00A2.dtbo

oh and the source:

#!/usr/bin/python3

from flask import Flask, render_template
import Adafruit_BBIO.GPIO as GPIO
import Adafruit_BBIO.PWM as PWM
from time import sleep

class Motor:
def __init__(self, dir_pin, pwm_pin, pwm_freq):
self.dir_pin = dir_pin
self.pwm_pin = pwm_pin
self.value = 0

PWM.start(pwm_pin, 0, pwm_freq)
GPIO.setup(dir_pin, GPIO.OUT)

def set(self, value):
if value == self.value:
return

assert -100 <= value <= 100

if (value < 0) != (self.value < 0):
# changing direction
PWM.set_duty_cycle(self.pwm_pin, 0)
GPIO.output(self.dir_pin, value < 0)

PWM.set_duty_cycle(self.pwm_pin, abs(value))
self.value = value

motor1 = Motor(dir_pin="P8_18", pwm_pin="P9_16", pwm_freq=1000)
motor2 = Motor(dir_pin="P8_16", pwm_pin="P9_14", pwm_freq=1000)
motor3 = Motor(dir_pin="P8_14", pwm_pin="P8_13", pwm_freq=1000)
motor4 = Motor(dir_pin="P8_26", pwm_pin="P8_19", pwm_freq=1000)

def set_motorOne(v1):
motor1.set(v1)

def set_motorTwo(v2):
motor2.set(v2)

def set_motorThree(v3):
motor3.set(v3)

def set_motorFour(v4):
motor4.set(v4)

app = Flask(__name__)

@app.route("/")
def homepage(title="homepage"):
return render_template("BootGoOne.html", title=title)

def add_motors_routeOne(state, v1):
@app.route("/" + state, endpoint=state)
def handlerOne():
set_motorOne(v1)
if add_motors_routeOne == 0:
PWM.stop("P9_16")
else:
pass

return homepage(title=state)

add_motors_routeOne("0",   0)
add_motors_routeOne('40', 40)
add_motors_routeOne('50', 50)
add_motors_routeOne('60', 60)
add_motors_routeOne('70', 70)
add_motors_routeOne('80', 80)
add_motors_routeOne('90', 90)
add_motors_routeOne('100', 100)

Okay...so:


   - When I add another 'add_motors_routeOne' as a separate call under 
   another motor, I get some odd behavior.
  - For instance, 'add_motors_routeTwo', would begin to make issues 
  with calling 'add_motors_routeTwo("0", 0) at the value 0. 
   
Anyway...the issue is that it begins to be a sysfs issue or an assertion 
error on my part.

Traceback (most recent call last):
  File "Moto/motocape/MotorCapeOne/MotorCapeTwo.py", line 92, in 

add_motors_routeTwo("0",   0)
  File "Moto/motocape/MotorCapeOne/MotorCapeTwo.py", line 83, in
 add_motors_routeTwo
@app.route("/" + state, endpoint=state)
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1250, in 
decorator
self.add_url_rule(rule, endpoint, f, **options)
  File "/usr/lib/python3/dist-packages/flask/app.py", line 66, in 
wrapper_func
return f(self, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/flask/app.py", line 1221, in 
add_url_rule
'existing endpoint function: %s' % endpoint)
AssertionError: View function mapping is overwriting an existing 
endpoint function: 0

Above is where you can find my error with the current config. of the 
python3 source from above.

Seth

-- 
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/df02989e-74bf-4678-8300-2c7d968b0c3an%40googlegroups.com.

Re: [beagleboard] apt on BBB *very* slow, anyone else noticed?

[Steve Lentz]

Mine runs fast when there’s nothing to be found:

debian@beaglebone:/var/lib/cloud9$ time apt search abcxyz
Sorting... Done
Full Text Search... Done

real0m11.625s
user0m10.423s
sys 0m0.482s


But slower when it does get results:

debian@beaglebone:/var/lib/cloud9$ time apt search vile
Sorting... Done
Full Text Search... Done
bubblewrap/stable 0.3.1-4 armhf
  setuid wrapper for unprivileged chroot and namespace manipulation

calife/stable 1:3.0.1-5 armhf
  Provides super user privileges to specific users



real1m20.150s
user1m16.055s
sys 0m2.485s


Although no where near as long as OP.

> On Feb 2, 2021, at 7:13 AM, Chris Green  wrote:
> 
> Chris Green  wrote:
>> That's interesting, it looks as if there is some sort of bug/oddity on
>> the BBB then.  It does seem to affect some other things as well, my
>> BBB feels a lot slower in general than previous incarnations were.
>> Maybe I'll try an older Debian and see if it acts the same.
>> 
> The problem isn't unique to the BBB/Debian, I've found quite a few
> other people with similar issues where parts of apt take a very long
> time.
> 
> The time taken seems to relate to how many hits there are in the
> search!  If you search for something that doesn't exist it takes (on
> my BBB) about 30 seconds:-
> 
>chris@beaglebone$ time apt search xyzabc
>Sorting... Done
>Full Text Search... Done
> 
>real0m27.532s
>user0m26.315s
>sys 0m1.035s
> 
> Searching for something that has three hits takes longer:-
> 
>chris@beaglebone$ time apt search xvile
>Sorting... Done
>Full Text Search... Done
>vile-common/stable,now 9.8t-1 all [installed,automatic]
>  VI Like Emacs - support files for vile/xvile
> 
>vile-filters/stable,now 9.8t-1 armhf [installed]
>  VI Like Emacs - highlighting filters for vile/xvile
> 
>xvile/stable 9.8t-1 armhf
>  VI Like Emacs - vi work-alike (X11)
> 
> 
>real1m2.063s
>user0m59.874s
>sys 0m1.862s
> 
> 
> Searching for just 'vile' produces quite a lot of hits because there's quite 
> a few packages 
> with the word 'privilege' in them, so it takes around four minutes.
> 
> 
> A workaround is to use 'apt-cache search' instead:-
> 
>chris@beaglebone$ time apt-cache search vile
>bubblewrap - setuid wrapper for unprivileged chroot and namespace 
> manipulation
>calife - Provides super user privileges to specific users
>chiark-really - really - a tool for gaining privilege (simple, realistic 
> sudo)
>cups-pk-helper - PolicyKit helper to configure cups with fine-grained 
> privileges
>fakeroot - tool for simulating superuser privileges
>libfakeroot - tool for simulating superuser privileges - shared libraries
>gssproxy - Privilege separation daemon for GSSAPI
>libkf5su5 - Integration with su for elevated privileges.
>lacme - ACME client written with process isolation and minimal privileges 
> in mind
>libprivileges-drop-perl - module to make it simple to drop all privileges
>libutempter-dev - privileged helper for utmp/wtmp updates (development)
>libutempter0 - privileged helper for utmp/wtmp updates (runtime)
>policykit-1 - framework for managing administrative policies and privileges
>privbind - Allow unprivileged apps to bind to a privileged port
>libpseudo - advanced tool for simulating superuser privileges
>pseudo - advanced tool for simulating superuser privileges
>python-oslo.privsep - OpenStack library for privilege separation - Python 
> 2.7
>python-oslo.privsep-doc - OpenStack library for privilege separation - doc
>python3-oslo.privsep - OpenStack library for privilege separation - Python 
> 3.x
>slirp4netns - User-mode networking for unprivileged network namespaces
>sudo - Provide limited super user privileges to specific users
>sudo-ldap - Provide limited super user privileges to specific users
>vile - VI Like Emacs - vi work-alike
>vile-common - VI Like Emacs - support files for vile/xvile
>vile-filters - VI Like Emacs - highlighting filters for vile/xvile
>xvile - VI Like Emacs - vi work-alike (X11)
>weborf - Fast and small webserver meant to be run without root privileges
>libyubikey-udev - udev rules for unprivileged access to YubiKeys
>zulupolkit - handler the polkit privileges
> 
>real0m21.826s
>user0m20.697s
>sys 0m0.944s
>chris@beaglebone$ 
> 
> That's not affected by the number of hits:-
> 
>chris@beaglebone$ time apt-cache search xvile
>vile-common - VI Like Emacs - support files for vile/xvile
>vile-filters - VI Like Emacs - highlighting filters for vile/xvile
>xvile - VI Like Emacs - vi work-alike (X11)
> 
>real0m21.663s
>user0m20.614s
>sys 0m0.924s
> 
> 
> 
> 
> -- 
> Chris Green
> ·
> 
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google 

[beagleboard] Re: apt on BBB *very* slow, anyone else noticed?

[Chris Green]

Chris Green  wrote:
> That's interesting, it looks as if there is some sort of bug/oddity on
> the BBB then.  It does seem to affect some other things as well, my
> BBB feels a lot slower in general than previous incarnations were.
> Maybe I'll try an older Debian and see if it acts the same.
> 
The problem isn't unique to the BBB/Debian, I've found quite a few
other people with similar issues where parts of apt take a very long
time.

The time taken seems to relate to how many hits there are in the
search!  If you search for something that doesn't exist it takes (on
my BBB) about 30 seconds:-

chris@beaglebone$ time apt search xyzabc
Sorting... Done
Full Text Search... Done

real0m27.532s
user0m26.315s
sys 0m1.035s

Searching for something that has three hits takes longer:-

chris@beaglebone$ time apt search xvile
Sorting... Done
Full Text Search... Done
vile-common/stable,now 9.8t-1 all [installed,automatic]
  VI Like Emacs - support files for vile/xvile

vile-filters/stable,now 9.8t-1 armhf [installed]
  VI Like Emacs - highlighting filters for vile/xvile

xvile/stable 9.8t-1 armhf
  VI Like Emacs - vi work-alike (X11)


real1m2.063s
user0m59.874s
sys 0m1.862s


Searching for just 'vile' produces quite a lot of hits because there's quite a 
few packages 
with the word 'privilege' in them, so it takes around four minutes.


A workaround is to use 'apt-cache search' instead:-

chris@beaglebone$ time apt-cache search vile
bubblewrap - setuid wrapper for unprivileged chroot and namespace 
manipulation
calife - Provides super user privileges to specific users
chiark-really - really - a tool for gaining privilege (simple, realistic 
sudo)
cups-pk-helper - PolicyKit helper to configure cups with fine-grained 
privileges
fakeroot - tool for simulating superuser privileges
libfakeroot - tool for simulating superuser privileges - shared libraries
gssproxy - Privilege separation daemon for GSSAPI
libkf5su5 - Integration with su for elevated privileges.
lacme - ACME client written with process isolation and minimal privileges 
in mind
libprivileges-drop-perl - module to make it simple to drop all privileges
libutempter-dev - privileged helper for utmp/wtmp updates (development)
libutempter0 - privileged helper for utmp/wtmp updates (runtime)
policykit-1 - framework for managing administrative policies and privileges
privbind - Allow unprivileged apps to bind to a privileged port
libpseudo - advanced tool for simulating superuser privileges
pseudo - advanced tool for simulating superuser privileges
python-oslo.privsep - OpenStack library for privilege separation - Python 
2.7
python-oslo.privsep-doc - OpenStack library for privilege separation - doc
python3-oslo.privsep - OpenStack library for privilege separation - Python 
3.x
slirp4netns - User-mode networking for unprivileged network namespaces
sudo - Provide limited super user privileges to specific users
sudo-ldap - Provide limited super user privileges to specific users
vile - VI Like Emacs - vi work-alike
vile-common - VI Like Emacs - support files for vile/xvile
vile-filters - VI Like Emacs - highlighting filters for vile/xvile
xvile - VI Like Emacs - vi work-alike (X11)
weborf - Fast and small webserver meant to be run without root privileges
libyubikey-udev - udev rules for unprivileged access to YubiKeys
zulupolkit - handler the polkit privileges

real0m21.826s
user0m20.697s
sys 0m0.944s
chris@beaglebone$ 

That's not affected by the number of hits:-

chris@beaglebone$ time apt-cache search xvile
vile-common - VI Like Emacs - support files for vile/xvile
vile-filters - VI Like Emacs - highlighting filters for vile/xvile
xvile - VI Like Emacs - vi work-alike (X11)

real0m21.663s
user0m20.614s
sys 0m0.924s




-- 
Chris Green
·

-- 
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/o8sneh-eb5.ln1%40esprimo.zbmc.eu.

[beagleboard] Re: apt on BBB *very* slow, anyone else noticed?

[Chris Green]

jonnymo  wrote:
> [-- text/plain, encoding quoted-printable, charset: UTF-8, 121 lines --]
> 
> On my Beaglebone AI via Wi-Fi, I got this:
> 
> debian@beaglebone:~$  *time apt search vile*
> Sorting... Done
> Full Text Search... Done
> 
> *real2m10.764s*
> *user2m5.185s*
> *sys 0m3.954s*
> 
> 
> Raspberry Pi 4 Wi-Fi:
> 
> *real0m2.637s*
> *user0m2.349s*
> *sys 0m0.288s*
> 
> 
> 
> Running 'strace  apt search vile' on the BBAI, it appears to be stuck in
> some sort of read loop which is taking all the time.
>*.*
> *   .*
> *   .*
> 
> *read(5,
> "\344\255\246h4F\314\330y\241\250D2\350i3\0044H\253\16\250\306\364\212`2\27\331\355\323J"...,
> 4096) = 4096*
> *read(5,
> "I\210\363\32\364o$\16[\201]bS`S\357\3620\372QC\202\245b\271\300\312|\311Q\355\27"...,
> 4096) = 4096*
> *read(5, "
> n\206Z\225\271\264\35\r,\203\331f\5;\260k\200p\314\16\355\222\204\332A/\226\267\237\277\33"...,
> 4096) = 4096*
> *read(5,
> "\250\235\303\34B\216GE\2<\266\275P\262\210]`0{\222\306\270p\245\214\310\6\33\231\3343\33"...,
> 4096) = 3200*
> *read(5, "", 4096)   = 0*
> *) = 26ext Search... Donearch... Done\r", 26*
> 
> 
> On the RasPi, it runs through quite quickly and done.
> 
That's interesting, it looks as if there is some sort of bug/oddity on
the BBB then.  It does seem to affect some other things as well, my
BBB feels a lot slower in general than previous incarnations were.
Maybe I'll try an older Debian and see if it acts the same.

-- 
Chris Green
·

-- 
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/r9lneh-5anp.ln1%40esprimo.zbmc.eu.