[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[TJF]

I forgot to mention that the modified file doesn't work in python2 any more:

src/test$ python 1.py
>   File "1.py", line 32
> print("%4X" % AdcV[i], end=" ") #output one channel in hex
>   ^
> SyntaxError: invalid syntax
>
>  

-- 
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/d0824dc4-514d-4a97-bde2-6dc728319841o%40googlegroups.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[TJF]

I tried the tool Denis mentioned. It works:

libpruio/src$ cp python test 
>
libpruio/src$ 2to3 -w test
> root: Generating grammar tables from 
> /usr/lib/python2.7/lib2to3/PatternGrammar.txt
> root: Generating grammar tables from 
> /usr/lib/python2.7/lib2to3/PatternGrammar.txt
> root: Generating grammar tables from 
> /usr/lib/python2.7/lib2to3/PatternGrammar.txt
> root: Generating grammar tables from 
> /usr/lib/python2.7/lib2to3/PatternGrammar.txt
> ... 
>
RefactoringTool: Files that were modified:
> RefactoringTool: test/1.py
> RefactoringTool: test/button.py
> RefactoringTool: test/button2.py
> RefactoringTool: test/io_input.py
> RefactoringTool: test/performance.py
> RefactoringTool: test/pruss_add.py
> RefactoringTool: test/pruss_toggle.py
> RefactoringTool: test/pwm_cap.py
> RefactoringTool: test/qep.py
> RefactoringTool: test/rb_file.py
> RefactoringTool: test/sos.py
> RefactoringTool: test/stepper.py
> RefactoringTool: test/libpruio/__init__.py
> RefactoringTool: test/libpruio/ctypesloader.py
> RefactoringTool: test/libpruio/pruio.py
> libpruio/src$ cd test/
> libpruio/src/test$ python3 1.py
> F8F0 EC10 F470 83C0 55B0 9D60 BC80 F2D0 
> F970 EF50 F560 C630 9C00 93F0 9C30 F2C0 
> F980 EF00 F500 CCF0 AE40 A6E0 A5D0 F2F0 
> F9A0 EE90 F510 CD50 B0D0 AC00 AB50 F2B0 
> F950 EE40 F500 CC60 B070 ACE0 AC80 F2B0 
> F990 EE70 F4F0 CC70 B060 ACC0 ACD0 F2D0 
> F960 EE70 F540 CCA0 B0C0 ACD0 AD60 F300 
> F930 EEF0 F560 CD00 B1D0 ADD0 AED0 F2F0 
> F950 EF30 F530 CD10 B230 AEE0 B000 F2C0 
> F970 EEE0 F4E0 CD00 B210 AEB0 B050 F2A0 
> F980 EE90 F510 CD20 B1C0 AF20 B050 F2D0 
> F980 EEC0 F540 CD00 B240 AEE0 B030 F2F0 
> F960 EF50 F5A0 CDA0 B350 B100 B1A0 F2E0 
>  
>
 
 Regarding the pinmux-pins file permission: I've no clue why they're 
different on your systems. But you can adapt them, ie by adding a line to 
file /lib/systemd/system/libpruio-lkm.service like

ExecStartPost=/bin/chown root:pruio /sys/kernel/debug/pinctrl/
> 44e10800.pinmux-pinctrl-single/pinmux-pins
>
 
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/2c9e79b6-b495-4688-81ba-8087a1213b6bo%40googlegroups.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[Andrew Harres]

debian@beaglebone:~$ uname -r
5.4.52-ti-r16
debian@beaglebone:~$ sudo ls -l 
/sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pinmux-pins
-r--r--r-- 1 root root 0 Jan  1  1970 
/sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pinmux-pins

On Wednesday, August 12, 2020 at 4:17:34 PM UTC-5 Andrew Harres wrote:

> debian@beaglebone:~$ uname -r
> 4.19.94-ti-r45
> debian@beaglebone:~$ sudo ls -l 
> /sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pinmux-pins
> -r--r--r-- 1 root root 0 Jan  1  1970 
> /sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pinmux-pins
>
> On Wednesday, August 12, 2020 at 3:25:38 PM UTC-5 Andrew Harres wrote:
>
>> I set enable_uboot_cape_universal=0 and I have the same result. My 
>> permissions for pinmux-pins looks much different than yours.
>>
>> debian@beaglebone:~$ ls -l 
>> /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
>> ls: cannot access 
>> '/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins': Permission denied
>> debian@beaglebone:~$ sudo ls -l 
>> /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
>> -r--r--r-- 1 root root 0 Jan  1  1970 
>> /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
>>
>> I'll try a different kernel.
>>
>

-- 
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/9230b892-6ee8-4c83-9d7d-c8b5f89ecaf6n%40googlegroups.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[Andrew Harres]

debian@beaglebone:~$ uname -r
4.19.94-ti-r45
debian@beaglebone:~$ sudo ls -l 
/sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pinmux-pins
-r--r--r-- 1 root root 0 Jan  1  1970 
/sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pinmux-pins

On Wednesday, August 12, 2020 at 3:25:38 PM UTC-5 Andrew Harres wrote:

> I set enable_uboot_cape_universal=0 and I have the same result. My 
> permissions for pinmux-pins looks much different than yours.
>
> debian@beaglebone:~$ ls -l 
> /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
> ls: cannot access '/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins': 
> Permission denied
> debian@beaglebone:~$ sudo ls -l 
> /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
> -r--r--r-- 1 root root 0 Jan  1  1970 
> /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
>
> I'll try a different kernel.
>

-- 
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/5bd09148-7786-4f3d-a7d3-e4159b2db744n%40googlegroups.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[Andrew Harres]

I set enable_uboot_cape_universal=0 and I have the same result. My 
permissions for pinmux-pins looks much different than yours.

debian@beaglebone:~$ ls -l 
/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
ls: cannot access '/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins': 
Permission denied
debian@beaglebone:~$ sudo ls -l 
/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
-r--r--r-- 1 root root 0 Jan  1  1970 
/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins

I'll try a different kernel.

-- 
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/13e708a5-6f31-47ab-8cde-7261ec54e56cn%40googlegroups.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[TJF]

I forgot:

$ python --version
> Python 2.7.13
> $ python3 --version
> Python 3.5.3
>
>

-- 
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/cc0bf2f1-c7ff-4f15-90f6-91ec6acacc7ao%40googlegroups.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[TJF]

I did some testing here on a similar system:

$ uname -r
> 4.14.69-ti-r76
> $ python 1.py
> F800 E9C0 F3B0 8230 5370 9830 B450 F2B0 
> F910 EEC0 F540 C600 9BA0 9230 9830 F2F0 
> F920 EEE0 F500 CC90 ABC0 A190 9FB0 F2E0 
> F960 EF20 F4B0 CDA0 AEF0 A6D0 A440 F2B0 
> F960 EEA0 F510 CDB0 B240 ACF0 AAF0 F300 
> F910 EEF0 F4E0 CDE0 B310 AEC0 AE50 F310 
> F960 EF00 F4D0 CDE0 B360 AF60 AFF0 F2F0 
> F980 EEF0 F500 CDC0 B340 B000 B0A0 F2E0 
> F960 EF20 F550 CE70 B4F0 B1F0 B330 F320 
> F950 EF00 F4E0 CED0 B530 B280 B480 F310 
> F980 EEE0 F4F0 CED0 B530 B300 B480 F2F0 
> F920 EEF0 F500 CE40 B4D0 B250 B410 F310 
> F940 EF00 F4D0 CE30 B450 B170 B340 F2C0 
> $ python3 1.py
> Traceback (most recent call last):
>   File "1.py", line 18, in 
> from libpruio import *
>   File "/home/debian/Projekte/libpruio/src/python/libpruio/__init__.py", 
> line 1, in 
> from pruio import *
> ImportError: No module named 'pruio' 
>
$ ls -l /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
> -rw-rw-r-- 1 root gpio 0 Jan  1  1970 
> /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
> $ cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
> Pinmux settings per pin
> Format: pin (name): mux_owner gpio_owner hog?
> pin 0 (PIN0): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
> group pinmux_emmc_pins
> pin 1 (PIN1): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
> group pinmux_emmc_pins
> pin 2 (PIN2): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
> group pinmux_emmc_pins
> pin 3 (PIN3): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
> group pinmux_emmc_pins
> ...
>

 python2 works, python3 doesn't.

The file pinmux-pins is acessable for users of group gpio on my system. In 
your output the lines containing ocp:Px_xx_pinmux indicate that the 
cape-universal device-tree blob is loaded and claims the pins. Try 
enable_uboot_cape_universal=0 in uEnv.txt.

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/a4264e52-28bb-4e6b-a43b-2c31f47b90f4o%40googlegroups.com.

Re: [beagleboard] Building the bone debian image worked before, but after upgrading my OS I run into errors.

[Samuel Park]

Ah I see, thank you. I think I may have messed something up during the build 
process. Thanks for the clarification. 

-- 
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/1720c4fa-effb-490e-a8d0-f850e7f8feeao%40googlegroups.com.

[beagleboard] v4.19.x: BBAI + BBB = Capes

[Robert Nelson]

Thanks to the work of our GSOC 2020 Student Deepak Khatri!

ttps://github.com/lorforlinux

We now have Device Tree Overlays that work on both the BBAI and BBB.

Here is the full testing list:

https://github.com/beagleboard/BeagleBoard-DeviceTrees/commits/v4.19.x-ti-overlays

This will require a new version of u-boot for both BBB and BBAI, i'll
have testing images available in a day or two.

But just heads up for everyone, an upgrade to 4.19.94-ti-r47 and
4.19.94-ti-rt-r47 'might' cause a boot failure.. So only upgrade if
you have a serial console

To Upgrade u-boot on your current booting medium (eMMC or microSD) just run:

sudo /opt/scripts/tools/developers/update_bootloader.sh

Background, we are following the path of RPi's kernel, the "dtbo's"
are now built into the kernel again, so any ABI changes can be hidden.

Our previous dual repo approach, separate overlay repo and kernel
repo, made some interesting requirements of the overlay files for
v4.4.x -> v5.4.x kernel versions..

The old overlay repo will still be used, but slowly all overlays will
be moved to the kernel repo.. Thus u-boot will now search for the
*.dtbo vs just hardcoding the path..

Thus:
uboot_overlay_addr4=/lib/firmware/.dtbo

can be written as:
uboot_overlay_addr4=.dtbo

1: /boot/dtbs//overlays/*.dtbo
2: /lib/firmware/*.dtbo
3: /  (*aka the old way..)

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/CAOCHtYihYJ%2Bh0m0uXUVjnJy7QUj03gKUeaSewv3DiqQnSJTHyA%40mail.gmail.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[Andrew Harres]

I do not.

debian@beaglebone:~$ cat 
/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
cat: /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins: Permission 
denied

On Wednesday, August 12, 2020 at 12:42:04 PM UTC-5 TJF wrote:

> The pinmux-pins output is reasonable. Do you have read access to the file 
> from user space?
>
> Regarding the errors in ctypesloader.py: this isn't my code. I just 
> reduced code from the ctypes documentation to the bare minimum. Perhaps you 
> can try the original file?
>
> 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/ee8d027d-ad2f-4fad-a39d-982b5aa8b6afn%40googlegroups.com.

[beagleboard] gpiod C and python examples in /var/lib/cloud9

[Mark A. Yoder]

Beaglers:
   I've just created some gpiod examples in both C and python.  You can get 
to them via:

bone$ *cd /var/lib/cloud9*
bone$ *git pull*
bone$ *git checkout v2020.08*
bone$ *cd BeagleBone/Black/gpiod*
bone$ *sudo apt update; sudo apt install libgpiod-dev*

(Or go to 
https://github.com/beagleboard/cloud9-examples/tree/v2020.08/BeagleBone/Black/gpiod
)

Here's the ReadMe.md

libgpiod is a new C library and tools for interacting with the linux GPIO 
character device. Detailed information is here 
 and 
Adafruit 

 also 
has information.

One of the advantages of gpiod is that it can toggle multiple bits on the 
same gpio chip at the same time. The toggle2 examples show how it's done.

The directory contains examples of using gpiod with *C* and *python* to 
read/write a gpio pin.
FileDescription
toggle1 

Toggles one pin as fast as possible. (300KHz in C, 57KHz in python)
toggle2 

Toggles two pins as fast as possible. (280KHz in C, 55KHz in python)
get 

Reads an input pin and prints its value.
getset 

Reads an input pin and writes its value to an output pin. (5us delay in C, 
20 us Delay in python)
getsetEvent 

Like *getset*, but uses events. (40 us delay in C, 75 us delay in python)
toggleLED 

Toggles the four built in USR LEDs.

Tip: Use *gpioinfo* to lookup chip and line numbers for various pins.


Feedback is welcome.

--Mark

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

Re: [beagleboard] U-Boot patches for 2018.03rc1

[Robert Nelson]

On Wed, Aug 12, 2020 at 12:58 PM Joshua Park  wrote:
>
>
> I am currently attempting to make u-boot recognize a blank board ID as 
> described this guide (section 4.2). The problem is that the 
> 0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch does not work 
> because the first two patches in the guide must be applied first and they do 
> not work either because they are made for the wrong code version. I would 
> like to know if newer versions for the first two patches 
> (0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch and 
> 0002-U-Boot-BeagleBone-Cape-Manager.patch) exist for u-boot version 
> 2018.03rc1.

Here is the whole historical archive:

https://github.com/RobertCNelson/Bootloader-Builder/tree/master/patches

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/CAOCHtYgDSov32dk%3D_s%3DDLN1Ac6xdq3ssnqQs_eDLwfJRgvY09A%40mail.gmail.com.

[beagleboard] U-Boot patches for 2018.03rc1

[Joshua Park]

I am currently attempting to make u-boot recognize a blank board ID as 
described this guide (section 4.2). 
 
The problem is that the 
0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch does not 
work because the first two patches in the guide must be applied first and 
they do not work either because they are made for the wrong code version. I 
would like to know if newer versions for the first two patches 
(0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch and 
0002-U-Boot-BeagleBone-Cape-Manager.patch) exist for u-boot version 
2018.03rc1. 

-- 
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/dda193d1-202f-430b-bc13-6ef2f2291d7bn%40googlegroups.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[Dennis Lee Bieber]

On Wed, 12 Aug 2020 10:20:35 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Andrew Harres
 wrote:


>def count(self, sub, start=0, end=sys.maxint):
>AttributeError: module 'sys' has no attribute 'maxint'

https://stackoverflow.com/questions/13795758/what-is-sys-maxint-in-python-3

Short answer: Python 3 unified the logic of native ints vs Python 2
"longints"; they automatically roll over to a longint if incremented far
enough. As a result, there isn't really a "maxint" anymore.


I'd suggest running the entire library through the 2 to 3 conversion
process.

https://docs.python.org/3.8/library/2to3.html
"""
except
Converts except X, T to except X as T.



renames
Changes sys.maxint to sys.maxsize.
"""

handle both of the cases you have encountered. There are MANY other changes
that may apply.



-- 
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/rha8jfph3crr8fq4l3e3n0nq9omo5p85mn%404ax.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[TJF]

The pinmux-pins output is reasonable. Do you have read access to the file 
from user space?

Regarding the errors in ctypesloader.py: this isn't my code. I just reduced 
code from the ctypes documentation to the bare minimum. Perhaps you can try 
the original file?

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/23b526fd-8e7d-454c-979c-19462a645e87o%40googlegroups.com.

[beagleboard] Re: Networking setup on robot with multiple debian SBCs

[Dennis Lee Bieber]

On Wed, 12 Aug 2020 06:12:26 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Peter Gaskell
 wrote:

>On my RPi, eth1 and eth2 get the proper IPv4 addresses (192.168.7.1 and 
>192.168.6.1) 
>
Interesting...

>Really I think I just want to route the multicast traffic between the two 
>to the usb0/eth1 interface network but also be able to have them both on 
>the internet and be able to "sniff" the traffic on the usb0/eth1 network by 
>connecting to an access point on one of them.  Unfortunately it seams 
>having multicast packets go out to the wireless interfaces slows down the 
>communication significantly.
>

I'd have to ask why you are using multicast?

https://tools.ietf.org/id/draft-mcbride-mboned-wifi-mcast-problem-statement-01.html
"""
One of the primary problems multicast over wifi faces is that link local
802.11 doesn't necessarily support multicast, it supports broadcast. To
make make multicast over wifi work successfully we often need to modify the
multicast to instead be sent as unicast in order for it to successfully
transmit with useable quality. Multicast over wifi experiences high packet
error rates, no acknowledgements, and low data rate. This draft reviews
these problems found with multicast over wifi. While this is not a
solutions draft, common workarounds to some of the problems will be listed,
along with the impact of the workarounds. 
"""
A big problem is that the 802.11 multicast channel is an afterthought and
only given 100th of the bandwidth. Multicast is basically a second class
citizen, to unicast, over wifi. Unicast may have allocated 10mb while
Multicast will be allocated 1mb.
"""

https://wirelesslywired.com/2019/05/02/multicast-over-wireless/
"""
Multicast has brought a lot of efficiencies to IP networks. But multicast
wasn’t designed for wireless, and especially isn’t well suited for
high-bandwidth multicast applications like video. I’ll cover the challenges
of multicast over wireless and design considerations.
"""


-- 
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/5v88jflka0okukkfho8g0q3qo4v0il2rpo%404ax.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[Andrew Harres]

I'm not sure about the differences between importing in python 2 vs 3. I'll 
look into it more. I did try running python3 interactively in the libpruio 
directory and tried an import directly.

debian@beaglebone:~/src/pruio_examples/libpruio$ ls
__init__.py   __pycache__  ctypesloader.pyc  pruio.pyc
__init__.pyc  ctypesloader.py  pruio.py
debian@beaglebone:~/src/pruio_examples/libpruio$ python3
Python 3.5.3 (default, Jul  9 2020, 13:00:10)
[GCC 6.3.0 20170516] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pruio
Traceback (most recent call last):
  File "", line 1, in 
  File "/home/debian/src/pruio_examples/libpruio/pruio.py", line 3, in 

from ctypesloader import *
  File "/home/debian/src/pruio_examples/libpruio/ctypesloader.py", line 375
except OSError,e:
  ^
SyntaxError: invalid syntax

I think that line should read "except OSError as e:" to be valid python 3. 
I changed that and got another error.

debian@beaglebone:~/src/pruio_examples/libpruio$ vim ctypesloader.py
debian@beaglebone:~/src/pruio_examples/libpruio$ python3
Python 3.5.3 (default, Jul  9 2020, 13:00:10)
[GCC 6.3.0 20170516] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pruio
Traceback (most recent call last):
  File "", line 1, in 
  File "/home/debian/src/pruio_examples/libpruio/pruio.py", line 3, in 

from ctypesloader import *
  File "/home/debian/src/pruio_examples/libpruio/ctypesloader.py", line 48, 
in 
class UserString:
  File "/home/debian/src/pruio_examples/libpruio/ctypesloader.py", line 
100, in UserString
def count(self, sub, start=0, end=sys.maxint):
AttributeError: module 'sys' has no attribute 'maxint'

-- 
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/67822a3e-476f-45ac-896f-7c455eb3cdb4n%40googlegroups.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[Andrew Harres]

I'm not sure what counts as reasonable.

debian@beaglebone:~$ sudo cat 
/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-p
ins
Pinmux settings per pin
Format: pin (name): mux_owner gpio_owner hog?
pin 0 (PIN0): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins group 
pinmux_emmc_pins
pin 1 (PIN1): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins group 
pinmux_emmc_pins
pin 2 (PIN2): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins group 
pinmux_emmc_pins
pin 3 (PIN3): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins group 
pinmux_emmc_pins
pin 4 (PIN4): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins group 
pinmux_emmc_pins
pin 5 (PIN5): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins group 
pinmux_emmc_pins
pin 6 (PIN6): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins group 
pinmux_emmc_pins
pin 7 (PIN7): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins group 
pinmux_emmc_pins
pin 8 (PIN8): ocp:P8_19_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_19_default_pin group pinmux_P8_19_default_pin
pin 9 (PIN9): ocp:P8_13_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_13_default_pin group pinmux_P8_13_default_pin
pin 10 (PIN10): ocp:P8_14_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_14_default_pin group pinmux_P8_14_default_pin
pin 11 (PIN11): ocp:P8_17_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_17_default_pin group pinmux_P8_17_default_pin
pin 12 (PIN12): ocp:P8_12_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_12_default_pin group pinmux_P8_12_default_pin
pin 13 (PIN13): ocp:P8_11_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_11_default_pin group pinmux_P8_11_default_pin
pin 14 (PIN14): ocp:P8_16_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_16_default_pin group pinmux_P8_16_default_pin
pin 15 (PIN15): ocp:P8_15_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_15_default_pin group pinmux_P8_15_default_pin
pin 16 (PIN16): ocp:P9_15_pinmux (GPIO UNCLAIMED) function 
pinmux_P9_15_default_pin group pinmux_P9_15_default_pin
pin 17 (PIN17): ocp:P9_23_pinmux (GPIO UNCLAIMED) function 
pinmux_P9_23_default_pin group pinmux_P9_23_default_pin
pin 18 (PIN18): ocp:P9_14_pinmux (GPIO UNCLAIMED) function 
pinmux_P9_14_default_pin group pinmux_P9_14_default_pin
pin 19 (PIN19): ocp:P9_16_pinmux (GPIO UNCLAIMED) function 
pinmux_P9_16_default_pin group pinmux_P9_16_default_pin
pin 20 (PIN20): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 21 (PIN21): leds (GPIO UNCLAIMED) function user_leds_s0 group 
user_leds_s0
pin 22 (PIN22): leds (GPIO UNCLAIMED) function user_leds_s0 group 
user_leds_s0
pin 23 (PIN23): leds (GPIO UNCLAIMED) function user_leds_s0 group 
user_leds_s0
pin 24 (PIN24): leds (GPIO UNCLAIMED) function user_leds_s0 group 
user_leds_s0
pin 25 (PIN25): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 26 (PIN26): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 27 (PIN27): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 28 (PIN28): ocp:P9_11_pinmux (GPIO UNCLAIMED) function 
pinmux_P9_11_default_pin group pinmux_P9_11_default_pin
pin 29 (PIN29): ocp:P9_13_pinmux (GPIO UNCLAIMED) function 
pinmux_P9_13_default_pin group pinmux_P9_13_default_pin
pin 30 (PIN30): ocp:P9_12_pinmux (GPIO UNCLAIMED) function 
pinmux_P9_12_default_pin group pinmux_P9_12_default_pin
pin 31 (PIN31): ocp:P8_26_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_26_default_pin group pinmux_P8_26_default_pin
pin 32 (PIN32): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
group pinmux_emmc_pins
pin 33 (PIN33): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
group pinmux_emmc_pins
pin 34 (PIN34): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 35 (PIN35): ocp:P8_18_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_18_default_pin group pinmux_P8_18_default_pin
pin 36 (PIN36): ocp:P8_07_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_07_default_pin group pinmux_P8_07_default_pin
pin 37 (PIN37): ocp:P8_08_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_08_default_pin group pinmux_P8_08_default_pin
pin 38 (PIN38): ocp:P8_10_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_10_default_pin group pinmux_P8_10_default_pin
pin 39 (PIN39): ocp:P8_09_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_09_default_pin group pinmux_P8_09_default_pin
pin 40 (PIN40): ocp:P8_45_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_45_default_pin group pinmux_P8_45_default_pin
pin 41 (PIN41): ocp:P8_46_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_46_default_pin group pinmux_P8_46_default_pin
pin 42 (PIN42): ocp:P8_43_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_43_default_pin group pinmux_P8_43_default_pin
pin 43 (PIN43): ocp:P8_44_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_44_default_pin group pinmux_P8_44_default_pin
pin 44 (PIN44): ocp:P8_41_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_41_default_pin group pinmux_P8_41_default_pin
pin 45 (PIN45): ocp:P8_42_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_42_default_pin group pinmux_P8_42_default_pin
pin 46 (PIN46): ocp:P8_39_pinmux (GPIO UNCLAIMED) function 
pinmux_P8_39_default_pin group pinmux_P8_39_default_pin
pin 47 (PIN47): ocp:P8_40_pinmux (GPIO 

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[TJF]

Hi Andrew!

First, the boot process seems to be OK. The driver uio_pruss as well as the 
libpruio-lkm are loading.

Am Mittwoch, 12. August 2020 17:40:45 UTC+2 schrieb Andrew Harres:
debian@beaglebone:~$ python src/pruio_examples/1.py

> Traceback (most recent call last):
>   File "src/pruio_examples/1.py", line 25, in 
> if IO.Errr: raise AssertionError("pruio_new failed (%s)" % IO.Errr)
> AssertionError: pruio_new failed (parsing kernel claims)
>
> This seems to be a kernel issue. Does the command cat 
/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins print anything 
reasonable?
 

> debian@beaglebone:~$ python3 src/pruio_examples/1.py
> Traceback (most recent call last):
>   File "src/pruio_examples/1.py", line 18, in 
> from libpruio import *
>   File "/home/debian/src/pruio_examples/libpruio/__init__.py", line 1, in 
> 
> from pruio import *
> ImportError: No module named 'pruio'
>
> Here the python interpreter cannot find the file pruio.py in folder 
/home/debian/src/pruio_examples/libpruio/. But it should be present since 
python2 did find it. (Is there any difference between python2 and python3 
regarding module import? Sorry, I'm not keen on python.)

Regards

PS: Google groups is really strange, it's a desaster!



-- 
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/26fab7be-9df9-48bd-9cd3-a2f74ca889eeo%40googlegroups.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[Andrew Harres]

google groups has been strange. Looks like it has just updated and I don't 
see how to include code tags.

debian@beaglebone:~$ python --version
Python 2.7.13
debian@beaglebone:~$ python3 --version
Python 3.5.3

-- 
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/600265f2-41bd-4c05-82fc-ba9ef5792f94n%40googlegroups.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

[andrew . harres]

I didn't see cape_universal=enable in cmdline. I set uboot_overlay_pru to 
the UIO option. I also tried both commenting out enable_uboot_cape_universal
=1 and just setting it to 0. I get the same error as before.

debian@beaglebone:~$ cat /boot/uEnv.txt
#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

uname_r=4.14.108-ti-r136
#uuid=
#dtb=

###U-Boot Overlays###
###Documentation: 
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
###Master Enable
enable_uboot_overlays=1
###
###Overide capes with eeprom
#uboot_overlay_addr0=/lib/firmware/.dtbo
#uboot_overlay_addr1=/lib/firmware/.dtbo
#uboot_overlay_addr2=/lib/firmware/.dtbo
#uboot_overlay_addr3=/lib/firmware/.dtbo
###
###Additional custom capes
#uboot_overlay_addr4=/lib/firmware/.dtbo
#uboot_overlay_addr5=/lib/firmware/.dtbo
#uboot_overlay_addr6=/lib/firmware/.dtbo
#uboot_overlay_addr7=/lib/firmware/.dtbo
###
###Custom Cape
#dtb_overlay=/lib/firmware/.dtbo
###
###Disable auto loading of virtual capes (emmc/video/wireless/adc)
#disable_uboot_overlay_emmc=1
disable_uboot_overlay_video=1
disable_uboot_overlay_audio=1
disable_uboot_overlay_wireless=1
#disable_uboot_overlay_adc=1
###
###PRUSS OPTIONS
###pru_rproc (4.14.x-ti kernel)
#uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo
###pru_rproc (4.19.x-ti kernel)
#uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo
###pru_uio (4.14.x-ti, 4.19.x-ti & mainline/bone kernel)
uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo
###
###Cape Universal Enable
#enable_uboot_cape_universal=1
###
###Debug: disable uboot autoload of Cape
#disable_uboot_overlay_addr0=1
#disable_uboot_overlay_addr1=1
#disable_uboot_overlay_addr2=1
#disable_uboot_overlay_addr3=1
###
###U-Boot fdt tweaks... (6 = 384KB)
#uboot_fdt_buffer=0x6
###U-Boot Overlays###

cmdline=coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=
100 quiet

#In the event of edid real failures, uncomment this next line:
#cmdline=coherent_pool=1M net.ifnames=0 lpj=1990656 
rng_core.default_quality=100 quiet video=HDMI-A-1:1024x768@60e

##enable Generic eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh


debian@beaglebone:~$ lsmod
Module  Size  Used by
pvrsrvkm  442368  0
spidev 20480  0
uio_pdrv_genirq16384  0
usb_f_acm  16384  2
u_serial   20480  3 usb_f_acm
usb_f_ncm  28672  2
usb_f_rndis32768  4
u_ether20480  2 usb_f_ncm,usb_f_rndis
libcomposite   65536  16 usb_f_acm,usb_f_ncm,usb_f_rndis
libpruio   16384  0
uio_pruss  16384  0
uio20480  2 uio_pruss,uio_pdrv_genirq

debian@beaglebone:~$ ls -l /dev/uio*
crw-rw 1 root users 244, 0 Aug 12 15:28 /dev/uio0
crw-rw 1 root users 244, 1 Aug 12 15:28 /dev/uio1
crw-rw 1 root users 244, 2 Aug 12 15:28 /dev/uio2
crw-rw 1 root users 244, 3 Aug 12 15:28 /dev/uio3
crw-rw 1 root users 244, 4 Aug 12 15:28 /dev/uio4
crw-rw 1 root users 244, 5 Aug 12 15:28 /dev/uio5
crw-rw 1 root users 244, 6 Aug 12 15:28 /dev/uio6
crw-rw 1 root users 244, 7 Aug 12 15:28 /dev/uio7

debian@beaglebone:~$ python src/pruio_examples/1.py
Traceback (most recent call last):
  File "src/pruio_examples/1.py", line 25, in 
if IO.Errr: raise AssertionError("pruio_new failed (%s)" % IO.Errr)
AssertionError: pruio_new failed (parsing kernel claims)

debian@beaglebone:~$ python3 src/pruio_examples/1.py
Traceback (most recent call last):
  File "src/pruio_examples/1.py", line 18, in 
from libpruio import *
  File "/home/debian/src/pruio_examples/libpruio/__init__.py", line 1, in 

from pruio import *
ImportError: No module named 'pruio'



On Tuesday, August 11, 2020 at 4:15:25 PM UTC-5, TJF wrote:
>
> Am Dienstag, 11. August 2020 21:24:48 UTC+2 schrieb andrew...@gmail.com:
>>
>> Is python 3 not supported?
>>
>
> AFAIR I tested on python 2 and 3.
>
> The message
>
> (cannot open /dev/uio5)
>>
>
> is related to the uio_pruss driver. The interupt handler is either not 
> present (command lsmod doesn't list uio_pruss, or command ls -l /dev/uio* 
> has no output). Or you don't have write access to that file.
>
> In any case you need to load the adapted uEnv.txt (uboot_overlay_pru 
> modification). And it's also recommended to remove cape_universal=enable 
> from the cmdline in order to get free pinmux access to all pins from user 
> space.
>
> 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/a7a30031-5651-4931-9662-c55546b44649o%40googlegroups.com.

Re: [beagleboard] LCD driver

[Mark A. Yoder]

I've used a 2.4" LCD in my class.  Here 
 are 
details.

--Mark

On Wednesday, August 12, 2020 at 9:22:48 AM UTC-4 evilw...@gmail.com wrote:

> read the datasheet, that has SPI  there is already a frame buffer written 
> for it
> I have used it
>
>
> On 8/11/2020 10:41 AM, Mehul Shah wrote:
>
> i want SPI interface LCD
>
> On Wed, Aug 12, 2020 at 4:33 AM evilwulfie  wrote:
>
>> I have used this
>>
>> https://www.buydisplay.com/tft-5-inch-lcd-display-module-controller-board-serial-i2c-ra8875
>> your mileage may vary
>>
>>
>> On 8/11/2020 3:49 PM, voip...@gmail.com wrote:
>>
>> Hi All.
>>
>> I want to write/test a basic framebuffer  based driver for LCD on 
>> Beaglebone black
>> having an SPI interface.
>> My question is 
>>
>> 1> which LCD should I order? I think I should order the LCD whose driver 
>> already there in the kernel, am I right? but which one.
>>
>> 2> Any TFT or STN LCD, please let me know.  How I go about it, I 
>> basically want to 
>> change some parameters and experiment and test...
>>
>> I do not have a monitor.
>>
>>
>>
>> Regards,
>> Mehul  
>>
>> -- 
>> 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/8d35e694-11e4-463c-b1ea-85f050ef1e7co%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/VWZs5zxB0nM/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> beagleboard...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/90786190-2419-425c-534b-f72dabb2708f%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...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/CAGk2dzrFDgJVrR_gPyFRaK4GkkmeW0OiP33ApPb9eKAG7F0_tw%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/7f1b5f11-63d7-4575-bc0e-b346786f420bn%40googlegroups.com.

Re: [beagleboard] LCD driver

[evilwulfie]

read the datasheet, that has SPI  there is already a frame buffer 
written for it

I have used it

On 8/11/2020 10:41 AM, Mehul Shah wrote:

i want SPI interface LCD

On Wed, Aug 12, 2020 at 4:33 AM evilwulfie > wrote:


I have used this

https://www.buydisplay.com/tft-5-inch-lcd-display-module-controller-board-serial-i2c-ra8875
your mileage may vary


On 8/11/2020 3:49 PM, voip@gmail.com
 wrote:

Hi All.

I want to write/test a basic framebuffer  based driver for LCD on
Beaglebone black
having an SPI interface.
My question is

1> which LCD should I order? I think I should order the LCD whose
driver already there in the kernel, am I right? but which one.

2> Any TFT or STN LCD, please let me know.  How I go about it, I
basically want to
change some parameters and experiment and test...

I do not have a monitor.



Regards,
Mehul

-- 
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/8d35e694-11e4-463c-b1ea-85f050ef1e7co%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/VWZs5zxB0nM/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/90786190-2419-425c-534b-f72dabb2708f%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/CAGk2dzrFDgJVrR_gPyFRaK4GkkmeW0OiP33ApPb9eKAG7F0_tw%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/2f9e3c1c-7220-46b6-7cff-8906c90e911d%40gmail.com.

[beagleboard] Re: Networking setup on robot with multiple debian SBCs

[Peter Gaskell]

On my RPi, eth1 and eth2 get the proper IPv4 addresses (192.168.7.1 and 
192.168.6.1) 

Really I think I just want to route the multicast traffic between the two 
to the usb0/eth1 interface network but also be able to have them both on 
the internet and be able to "sniff" the traffic on the usb0/eth1 network by 
connecting to an access point on one of them.  Unfortunately it seams 
having multicast packets go out to the wireless interfaces slows down the 
communication significantly.

-p

On Tuesday, August 11, 2020 at 1:49:20 PM UTC-4, Dennis Bieber wrote:
>
> On Mon, 10 Aug 2020 15:06:44 -0400, in 
> gmane.comp.hardware.beagleboard.user 
> Dennis Lee Bieber  > 
> wrote: 
>
>
> > 
> >...I wouldn't even use WiFi between the R-Pi and the BBbl. While 
> the BBx 
> >USB client port does set up a USB network gadget (rndis on 192.168.7.x), 
> I 
> >don't know what it would take to have an R-Pi set up a matching USB 
> gadget 
> >on its host port (plug them together and see if a new network device 
> >appears on the R-Pi?). 
> > 
>
> Just tried an experiment... Powered the BBB from a 5V barrel 
> supply 
> (since an R-Pi USB probably can't power it), then connected the BBB client 
> port to the R-Pi host port... 
>
> pi@rpi3bplus-1:~$ ifconfig 
> eth0: flags=4099  mtu 1500 
> ether b8:27:eb:fb:d8:30  txqueuelen 1000  (Ethernet) 
> RX packets 0  bytes 0 (0.0 B) 
> RX errors 0  dropped 0  overruns 0  frame 0 
> TX packets 0  bytes 0 (0.0 B) 
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
>
> eth1: flags=4163  mtu 1500 
> inet6 fe80::d22b:73ea:8bef:c781  prefixlen 64  scopeid 0x20 
> ether d0:39:72:18:3e:ea  txqueuelen 1000  (Ethernet) 
> RX packets 32  bytes 5556 (5.4 KiB) 
> RX errors 0  dropped 0  overruns 0  frame 0 
> TX packets 20  bytes 2661 (2.5 KiB) 
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
>
> eth2: flags=4163  mtu 1500 
> inet6 fe80::4f35:ad14:88b8:4a1a  prefixlen 64  scopeid 0x20 
> ether d0:39:72:18:3e:e8  txqueuelen 1000  (Ethernet) 
> RX packets 33  bytes 5376 (5.2 KiB) 
> RX errors 0  dropped 0  overruns 0  frame 0 
> TX packets 18  bytes 2961 (2.8 KiB) 
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
>
> lo: flags=73  mtu 65536 
> inet 127.0.0.1  netmask 255.0.0.0 
> inet6 ::1  prefixlen 128  scopeid 0x10 
> loop  txqueuelen 1000  (Local Loopback) 
> RX packets 0  bytes 0 (0.0 B) 
> RX errors 0  dropped 0  overruns 0  frame 0 
> TX packets 0  bytes 0 (0.0 B) 
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
>
> wlan0: flags=4163  mtu 1500 
> inet 192.168.1.76  netmask 255.255.255.0  broadcast 192.168.1.255 
> inet6 2600:1700:e630:890:e51e:f96a:9476:3412  prefixlen 64 
>  scopeid 
> 0x0 
> inet6 fe80::6471:7a90:88f3:79c0  prefixlen 64  scopeid 0x20 
> inet6 2600:1700:e630:890::1b  prefixlen 128  scopeid 0x0 
> ether b8:27:eb:ae:8d:65  txqueuelen 1000  (Ethernet) 
> RX packets 19022  bytes 27611083 (26.3 MiB) 
> RX errors 0  dropped 0  overruns 0  frame 0 
> TX packets 10635  bytes 1253318 (1.1 MiB) 
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
>
> pi@rpi3bplus-1:~$ 
>
> eth1 and eth2 are IPv6 and exist while the BBB is connected, 
> removing 
> the USB cable leaves the R-Pi with 
>
> pi@rpi3bplus-1:~$ ifconfig 
> eth0: flags=4099  mtu 1500 
> ether b8:27:eb:fb:d8:30  txqueuelen 1000  (Ethernet) 
> RX packets 0  bytes 0 (0.0 B) 
> RX errors 0  dropped 0  overruns 0  frame 0 
> TX packets 0  bytes 0 (0.0 B) 
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
>
> lo: flags=73  mtu 65536 
> inet 127.0.0.1  netmask 255.0.0.0 
> inet6 ::1  prefixlen 128  scopeid 0x10 
> loop  txqueuelen 1000  (Local Loopback) 
> RX packets 0  bytes 0 (0.0 B) 
> RX errors 0  dropped 0  overruns 0  frame 0 
> TX packets 0  bytes 0 (0.0 B) 
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
>
> wlan0: flags=4163  mtu 1500 
> inet 192.168.1.76  netmask 255.255.255.0  broadcast 192.168.1.255 
> inet6 2600:1700:e630:890:e51e:f96a:9476:3412  prefixlen 64 
>  scopeid 
> 0x0 
> inet6 fe80::6471:7a90:88f3:79c0  prefixlen 64  scopeid 0x20 
> inet6 2600:1700:e630:890::1b  prefixlen 128  scopeid 0x0 
> ether b8:27:eb:ae:8d:65  txqueuelen 1000  (Ethernet) 
> RX packets 19047  bytes 27613467 (26.3 MiB) 
> RX errors 0  dropped 0  overruns 0  frame 0 
> TX packets 10660  bytes 1261140 (1.2 MiB) 
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
>
> pi@rpi3bplus-1:~$ 
>
> The lack of IPv4 may be due to the lack of DHCP server. I did not 
> try 
> to pass traffic (ping) 

[beagleboard] LCD framebuffer driver

[real time]

Hi All,

I want to write/test a basic framebuffer  based driver for LCD on
Beaglebone black
having an SPI interface.
My question is

1> which LCD should I order? I think I should order the LCD whose driver
already there in the kernel, am I right? but which one.

2> Any TFT or STN LCD, please let me know.  How I go about it, I basically
want to
change some parameters and experiment and test...
I do not have a monitor


Regards,
Mehul

-- 
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/CAFO2MTc%3D4%3D4oFLSgDmNc9cNCOCs4A3-QuRHFx-UTHVurxSjO4w%40mail.gmail.com.

Re: [beagleboard] LCD driver

[Mehul Shah]

i want SPI interface LCD

On Wed, Aug 12, 2020 at 4:33 AM evilwulfie  wrote:

> I have used this
>
> https://www.buydisplay.com/tft-5-inch-lcd-display-module-controller-board-serial-i2c-ra8875
> your mileage may vary
>
>
> On 8/11/2020 3:49 PM, voip@gmail.com wrote:
>
> Hi All.
>
> I want to write/test a basic framebuffer  based driver for LCD on
> Beaglebone black
> having an SPI interface.
> My question is
>
> 1> which LCD should I order? I think I should order the LCD whose driver
> already there in the kernel, am I right? but which one.
>
> 2> Any TFT or STN LCD, please let me know.  How I go about it, I basically
> want to
> change some parameters and experiment and test...
>
> I do not have a monitor.
>
>
>
> Regards,
> Mehul
>
> --
> 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/8d35e694-11e4-463c-b1ea-85f050ef1e7co%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/VWZs5zxB0nM/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/90786190-2419-425c-534b-f72dabb2708f%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/CAGk2dzrFDgJVrR_gPyFRaK4GkkmeW0OiP33ApPb9eKAG7F0_tw%40mail.gmail.com.