[beagleboard] Server Communication Setting in BeagleBone Black (Tech Question)

[Albert]

Hi, BeagleBone Community.

I have specific questions about BeagleBone Black software setting for 
server communication.

 

1. Does the Beaglebone have built-in modules (or programs) that send status 
information to a particular server? 

 

2. If so, how do you save the target IP / Port inside of Beaglebone?

 

3. What are the protocol (TCP or UDP) and the data format for the data sent 
to the server?

 

Best,

-- 
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/9f672dfe-7640-4fe2-9c14-eb467b2ba92a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Server Communication Setting in BeagleBone Black (Tech Question)

[Albert]

Hi, BeagleBone Community.

I have specific questions about BeagleBone Black software setting for 
server communication.

 

1. Does the Beaglebone have built-in modules (or programs) that send status 
information to a particular server? 

 

2. If so, how do you save the target IP / Port inside of Beaglebone?

 

3. What are the protocol (TCP or UDP) and the data format for the data sent 
to the server?

 

Best,

-- 
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/e299d893-8f6b-47af-8783-5ce8262bdb82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Server Communication Setting in BeagleBone Black (Tech Question)

[Albert]

Hi, BeagleBone Community.

I have specific questions about BeagleBone Black software setting for 
server communication.

 

1. Does the Beaglebone have built-in modules (or programs) that send status 
information to a particular server? 

 

2. If so, how do you save the target IP / Port inside of Beaglebone?

 

3. What are the protocol (TCP or UDP) and the data format for the data sent 
to the server?

 

Best,

-- 
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/c015cf58-8707-4b93-9157-d9b24e0b7b18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PRU Communications: Beaglebone Black

[Venkatesh Vadde]

Sounds a tad more intricate, but seems powerful. Thanks for letting us
know, Steinkuehler.

On Wed, Jul 3, 2019, 9:05 PM Charles Steinkuehler 
wrote:

> As has been discussed, the PRUs have no direct "interrupt" like
> functionality that interrupts and redirects program execution.
>
> In addition to the various methods already discussed, if you are
> trying to tightly couple program execution between the two PRU cores,
> I suggest using the transfer instructions (XIN/XOUT).  While these
> instructions are typically used to access the scratchpad and hardware
> multiplier, you can also specify a direct connection between the two
> PRU cores.  In this case, one PRU core executes an XIN instruction and
> the other core executes an XOUT.  The core that executes the
> instruction first will stall until the other PRU executes it's
> transfer instruction, at which point the two PRU cores will continue
> executing code, synchronized by the transfer instruction.  The
> transfer is terminated if either PRU core stalls for more than 1024
> cycles.
>
> Details are in the TRM, but you have to have one of the versions with
> full details on the PRU cores (eg: spruh73c or similar).
>
> On 7/2/2019 7:49 AM, Venkatesh Vadde wrote:
> > We are a group working with a Beaglebone and trying to get more time
> > determinism between the PRUs. We are trying to get one PRU to respond to
> a
> > trigger from the other PRU. The INTC framework seems quite complex, and
> we
> > are finding it quite difficult to decipher or understand (but an example
> > might help us build on it). Does the PRU allow for a timed response like
> an
> > interrupt based mechanism? Can someone suggest something for our
> > requirement of communication between the PRUs?
> >
> > Thank you,
> > -Vadde
> >
>
>
> --
> Charles Steinkuehler
> char...@steinkuehler.net
>
> --
> 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/30cf3e82-eae4-07cb-7be8-0bf34137de0d%40steinkuehler.net
> .
> 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/CAHW0bcxPVtppGTkVd51nkYWgg3J3hvZuJtV1yV%2BhC9TaVhSzWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How do I change the pin mode to a new value even after rebooting? (Beaglebone Black)

[TJF]

Am Mittwoch, 3. Juli 2019 17:06:30 UTC+2 schrieb LuminousShadow:
>
> Yes you can. By creating the device tree binary overlay you can not only 
> set the mux mode, but its output as well.
>
> I'll add another resource that explains this:
>
> http://derekmolloy.ie/gpios-on-the-beaglebone-black-using-device-tree-overlays/
>  (basically 
> a walk-through on how to do it. However, its a bit outdated as "SLOTS" are 
> obsolete).
>

Nonsens!

This is good, but obsolete stuff. Nothing about PWM output from an eCAP 
module. Only about GPIO, using sysfs to manipulate the settings.

>From a device tree blob you cannot manipulate the register settings unless 
the driver supports this. And the PWM driver has no such feature, yet,

Regards

-- 
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/b09b1007-1df6-4345-8856-865024d47bd6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beaglebone ADC

[Venkatesh Vadde]

The ADC is one of the most useful parts of the BBB, but unfortunately there
is not a lot of support documentation in terms of working examples. I have
a few questions, and would appreciate getting some clarity on them.

a) What are some good examples of using the BB-ADC with or without PRU
intervention? It would be nice to see examples of high-rate continuous
capture and also regular low-rate captures. Just for context, 100Ksps is
high for us and 50Sps is low.

b) Is the BBB-ADC capable of synchronous (simultaneous or near
simultaneous) multichannel capture? If we really lower the rate requirement
down to 50-100Sps, can we THEN do multichannel data acquisition? Are there
code examples for multichannel capture at any rate?

c) If the answer to b) is "No", what would be the way to do a fairly
low-rate, sequential multichannel capture i.e., in a round-robin fashion.
Any examples of this type of capture?

Thanks much,
-Vadde

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

Re: [beagleboard] PRU Communications: Beaglebone Black

[Charles Steinkuehler]

As has been discussed, the PRUs have no direct "interrupt" like
functionality that interrupts and redirects program execution.

In addition to the various methods already discussed, if you are
trying to tightly couple program execution between the two PRU cores,
I suggest using the transfer instructions (XIN/XOUT).  While these
instructions are typically used to access the scratchpad and hardware
multiplier, you can also specify a direct connection between the two
PRU cores.  In this case, one PRU core executes an XIN instruction and
the other core executes an XOUT.  The core that executes the
instruction first will stall until the other PRU executes it's
transfer instruction, at which point the two PRU cores will continue
executing code, synchronized by the transfer instruction.  The
transfer is terminated if either PRU core stalls for more than 1024
cycles.

Details are in the TRM, but you have to have one of the versions with
full details on the PRU cores (eg: spruh73c or similar).

On 7/2/2019 7:49 AM, Venkatesh Vadde wrote:
> We are a group working with a Beaglebone and trying to get more time
> determinism between the PRUs. We are trying to get one PRU to respond to a
> trigger from the other PRU. The INTC framework seems quite complex, and we
> are finding it quite difficult to decipher or understand (but an example
> might help us build on it). Does the PRU allow for a timed response like an
> interrupt based mechanism? Can someone suggest something for our
> requirement of communication between the PRUs?
> 
> Thank you,
> -Vadde
> 


-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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/30cf3e82-eae4-07cb-7be8-0bf34137de0d%40steinkuehler.net.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How do I change the pin mode to a new value even after rebooting? (Beaglebone Black)

[LuminousShadow]

Yes you can. By creating the device tree binary overlay you can not only 
set the mux mode, but its output as well.

I'll add another resource that explains this:
http://derekmolloy.ie/gpios-on-the-beaglebone-black-using-device-tree-overlays/ 
(basically 
a walk-through on how to do it. However, its a bit outdated as "SLOTS" are 
obsolete).
 

On Tuesday, July 2, 2019 at 11:17:22 AM UTC-4, TJF wrote:
>
> Am Dienstag, 2. Juli 2019 16:28:04 UTC+2 schrieb LuminousShadow:
>>
>> You can have the pins configured upon bootup with a custom device tree 
>> overlay.
>>
>
> Yes, you can specify the mux mode to connect the pin to the output of the 
> eCAP module in a device tree blob. But can you configure the modules 
> registers to generate a certain output?
>
> I'd try a start script for systemd, ie. invoking a small libpruio prg to 
> enable the desired output.
>
> Regards
>

-- 
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/3a6e8677-d1a1-444d-ac80-992145f01399%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How to identify GPIO Chip and pin

[Tarmo Kuuse]

Hi!

On Wednesday, 3 July 2019 04:51:55 UTC+3, simonm...@gmail.com wrote:
>
> I am trying to use GPIO with the robot control library.
> But I cant find the value to pass to chip and pin
>
> ex : 
> int  rc_gpio_init 
> 
>  
> (int chip, int pin, int handle_flags)
>

I've used Derek Molloy's excellent GPIO tables for reference. Regarding 
your question column "Mode 7" would seem to indicate chip and pin numbers, 
e.g. gpio1[6] would be chip 1, pin 6.

https://github.com/derekmolloy/boneDeviceTree/tree/master/docs 

--
Kind regards,
Tarmo

-- 
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/1423737c-e4d5-4a84-8d7b-ac1a1b7efe91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: PRU Communications: Beaglebone Black

[TJF]

Yes, that's a further option. You can HALT one PRU and restart it by 
setting bit 1 (ENABLE) in the CONTROL register, using the other PRU.

But note, you also have to increase the STATUS register, in order to jump 
over the HALT statement.

Regards

-- 
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/906bd7ad-651c-42f9-97a7-5469da0fed54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.