Re: [beagleboard] Re: spidev_test fails on Beaglebone AI

2021-03-17 Thread set_ 
Anand!

They did it again! The image has all the older items I was used to using! 
Anyway, it works. I had a very old image on my AI which was obsolete...


   - git clone https://github.com/beagleboard/BeagleBoard-DeviceTrees
   - cd BeagleBoard-DeviceTrees && make
   - git clone https://github.com/derekmolloy/exploringBB
   - cd exploringBB/chp08/spi/spidev_test/ && nano (or your favorite 
   editor) spidev_test.c
   - On line 32, change '/dev/spidev0.1' to '/dev/spidev1.1'
   - Then...
  - On your overlay that was made w/ make, C & P it in /boot/uEnv.txt
  - The file is in BeagleBoard-DeviceTrees/src/arm/overlays/
  - It is called BBAI-SPI0_1.dtbo
   - That should do it but first, reboot the board w/ sudo shutdown -r now!

That is what I was attempting in my gibberish earlier in my 2000 posts I 
made but all along, I have this outdated image and was thinking I could do 
it w/ the current config.

Seth
On Tuesday, March 16, 2021 at 3:08:44 AM UTC-5 anandp...@gmail.com wrote:

> I already tried with both spidev0 and spidev1. No luck.
>
> On Tue, 16 Mar 2021, 04:39 set_,  wrote:
>
>> Hello,
>>
>> Use SPIDEV0 and not SPIDEV1. I think this may get you closer to running 
>> the test.
>>
>> Seth
>> On Thursday, March 11, 2021 at 11:45:50 AM UTC-6 anandp...@gmail.com 
>> wrote:
>>
>>> An additional information:
>>> I can see the spi interfaces in the /dev/ folder.
>>>
>>> On Thursday, March 11, 2021 at 6:44:38 PM UTC+1 anandp...@gmail.com 
>>> wrote:
>>>
 Hi Everyone,

 I am trying to enable the spi interface on beaglebone AI.
 I used the roboticscape device tree structure from the link below:

 https://github.com/beagleboard/BeagleBoard-DeviceTrees
  The show-pins command shows that spi interface is up. However, when I 
 run the spidev_test, I receive a stream of 0's instead of actual data.

 I bridged the pins p9.29 and P9.30 before running the test.
 Can anyone provide some solution to fix this issue?

 Thanks 
 Anand

>>> -- 
>> 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/e071b9f6-be3a-44c7-9fed-b0d82d8a76f4n%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/90ae5fcb-3c62-41ab-a3fd-b8c9ba22564dn%40googlegroups.com.

Re: [beagleboard] Re: spidev_test fails on Beaglebone AI

2021-03-17 Thread set_ 
Hello Anand,

Seth here (again). Okay...so? I just received some ideas that may work. If 
no one else will help you, I can keep trying. 

...

https://rcn-ee.net/rootfs/bb.org/testing/2021-02-22/buster-console/am57xx-debian-10.8-console-armhf-2021-02-22-1gb.img.xz
 
is an image from rcn-ee.net. I think this fellow is listed on DigiKey as an 
employee and a member of beagleboard.org.

Anyway...that is all I know about him. Well, that and he is very good at 
branding images. Anyway, I got that one from him earlier today. If you do 
not mind losing your info. on the board, back it up it up first, use that 
image, and get back to your briefings. 

Oh and something that is different on this image compared to other images I 
have found recently, uboot-overlays is back in /boot/uEnv.txt.

I am about to test. I will let you know what happens.

Seth

On Tuesday, March 16, 2021 at 3:08:44 AM UTC-5 anandp...@gmail.com wrote:

> I already tried with both spidev0 and spidev1. No luck.
>
> On Tue, 16 Mar 2021, 04:39 set_,  wrote:
>
>> Hello,
>>
>> Use SPIDEV0 and not SPIDEV1. I think this may get you closer to running 
>> the test.
>>
>> Seth
>> On Thursday, March 11, 2021 at 11:45:50 AM UTC-6 anandp...@gmail.com 
>> wrote:
>>
>>> An additional information:
>>> I can see the spi interfaces in the /dev/ folder.
>>>
>>> On Thursday, March 11, 2021 at 6:44:38 PM UTC+1 anandp...@gmail.com 
>>> wrote:
>>>
 Hi Everyone,

 I am trying to enable the spi interface on beaglebone AI.
 I used the roboticscape device tree structure from the link below:

 https://github.com/beagleboard/BeagleBoard-DeviceTrees
  The show-pins command shows that spi interface is up. However, when I 
 run the spidev_test, I receive a stream of 0's instead of actual data.

 I bridged the pins p9.29 and P9.30 before running the test.
 Can anyone provide some solution to fix this issue?

 Thanks 
 Anand

>>> -- 
>> 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/e071b9f6-be3a-44c7-9fed-b0d82d8a76f4n%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/6063d018-ef09-40b3-8b7a-50254df06edbn%40googlegroups.com.

[beagleboard] Re: Beaglebone Ai overheating

2021-03-17 Thread Dennis Lee Bieber 
On Tue, 16 Mar 2021 10:20:43 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user
"robert.sty...-re5jqeeqqe8avxtiumw...@public.gmane.org"
 wrote:



>
>Which one of these http://beagleboard.org/latest-images do you put on a 
>SD-Card or USB flash memory stick?

The BBAI is a 5729 SoC. I wouldn't use any of the images from that page
-- they are nearly a year old and you would need a large uSD or eMMC
freespace to run an "apt update/apt upgrade" sequence.

I'd suggest visiting https://rcn-ee.net/rootfs/bb.org/testing/ and
checking for a more recent build that includes the updates of the last
year. Maybe not the most recent build (these /are/ labeled "testing, after
all) but not too old either. (Note that 2021-02-15 has Debian 10.8, vs the
10.3 of the "latest images" page). Decide if you want a graphical desktop
(images with LXQT) or Internet of Things (images with iot), TI Deep
Learning (images with tidl) [Note that these are not mutually exclusive:
LXQT & TIDL, IOT & TIDL, LXQT only, IOT only)]

>Which updates the on board memory?

Updating the eMMC is performed by loading the appropriate "Flasher"
image onto an uSD card, and booting with that card inserted.

Alternatively, non-flasher images can be turned into flasher images by
editing the /boot/uEnv.txt file. Typically the last line of that file has a
commented line; removing the # from the line enables the flashing mode.

Note that if you boot with a flasher image, it WILL rewrite the eMMC --
every time. You would have to mount the uSD after a boot from the eMMC to
recomment the line in uEnv.txt.



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

Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts

2021-03-17 Thread John Allwine 
That did it! Thanks Robert!

On Wednesday, March 17, 2021 at 12:02:07 PM UTC-6 RobertCNelson wrote:

> On Wed, Mar 17, 2021 at 12:40 PM John Allwine  wrote:
> >
> > The kernel doesn't seem to be the problem. Even when I change to that 
> version my /dev/uio* devices aren't showing up. Am I missing a simple step 
> somewhere?
> >
> > $ sudo /opt/scripts/tools/version.sh
>
> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 
> 2019.04-2-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500)]:[location: dd MBR]
> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
> 2019.04-2-gc9b3922522]:[location: dd MBR]
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 
> 2019.04-2-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd MBR]
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2019.04-2-gbb4af0f50f]:[location: dd MBR]
> > UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
> > UBOOT: Loaded Overlay:[BB-ADC-00A0]
> > UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
> > UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0]
> > uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo]
>
> Eh, I see the problem..
>
> "uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo" was a recent change..
> While you have U-boot: 2019.04, it's either: Jul 08 2019 or Aug 24
> 2020, so let's fix that..
>
> sudo apt update
> sudo apt install bb-u-boot-am335x-evm
>
> Then:
>
> cd /opt/u-boot/bb-u-boot-am335x-evm/
> sudo ./install.sh
>
> sudo reboot
>
> Then you should see the uio node here:
>
> UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
> UBOOT: Loaded Overlay:[AM335X-PRU-UIO-00A0]
> UBOOT: Loaded Overlay:[BB-ADC-00A0]
> UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
>
> 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/01f35c97-432e-4cfe-b746-d0d478da0d1an%40googlegroups.com.

Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts

2021-03-17 Thread Robert Nelson 
On Wed, Mar 17, 2021 at 1:01 PM Robert Nelson  wrote:
>
> On Wed, Mar 17, 2021 at 12:40 PM John Allwine  wrote:
> >
> > The kernel doesn't seem to be the problem. Even when I change to that 
> > version my /dev/uio* devices aren't showing up. Am I missing a simple step 
> > somewhere?
> >
> > $ sudo /opt/scripts/tools/version.sh
>
> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 
> > 2019.04-2-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500)]:[location: dd MBR]
> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
> > 2019.04-2-gc9b3922522]:[location: dd MBR]
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 
> > 2019.04-2-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd MBR]
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> > 2019.04-2-gbb4af0f50f]:[location: dd MBR]
> > UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
> > UBOOT: Loaded Overlay:[BB-ADC-00A0]
> > UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
> > UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0]
> > uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo]
>
> Eh, I see the problem..
>
> "uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo" was a recent change..
> While you have U-boot: 2019.04, it's either: Jul 08 2019 or Aug 24
> 2020, so let's fix that..

I changed this back on:

https://github.com/beagleboard/image-builder/commit/442ff4a16ba2814328fa389083e1755a1bd4c9ad#diff-a085e70f4f47ad31ded59514c63774946eeda74fd30875e5abfc36073e574559

When adding u-boot overlays for am57xx devices, and adding "kernel"
specific overlays, vs generic u-boot overlays..

Kernel overlays get applied first vs..

debian@bbg-pwr08-ser16:~$ ls /boot/dtbs/4.19.180-bone-rt-r61/overlays/
BBORG_FAN-A000.dtbo

Generic overlays

/lib/firmware/*.dtbo

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

Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts

2021-03-17 Thread Robert Nelson 
On Wed, Mar 17, 2021 at 12:40 PM John Allwine  wrote:
>
> The kernel doesn't seem to be the problem. Even when I change to that version 
> my /dev/uio* devices aren't showing up. Am I missing a simple step somewhere?
>
> $ sudo /opt/scripts/tools/version.sh

> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 
> 2019.04-2-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500)]:[location: dd MBR]
> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
> 2019.04-2-gc9b3922522]:[location: dd MBR]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 
> 2019.04-2-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd MBR]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2019.04-2-gbb4af0f50f]:[location: dd MBR]
> UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
> UBOOT: Loaded Overlay:[BB-ADC-00A0]
> UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
> UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0]
> uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo]

Eh, I see the problem..

"uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo" was a recent change..
While you have U-boot: 2019.04, it's either: Jul 08 2019 or Aug 24
2020, so let's fix that..

sudo apt update
sudo apt install bb-u-boot-am335x-evm

Then:

cd /opt/u-boot/bb-u-boot-am335x-evm/
sudo ./install.sh

sudo reboot

Then you should see the uio node here:

UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
UBOOT: Loaded Overlay:[AM335X-PRU-UIO-00A0]
UBOOT: Loaded Overlay:[BB-ADC-00A0]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]

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/CAOCHtYjjJt-f%3DKF2Thg02UnFttLFXehZ8dgGvGyW97LSF7KoVg%40mail.gmail.com.

Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts

2021-03-17 Thread John Allwine 
I switched to that kernel after the fact using:
sudo /opt/scripts/tools/update_kernel.sh --bone-rt-kernel --lts-4_19

Would it matter if I built the image originally with that kernel?

On Wednesday, March 17, 2021 at 11:40:24 AM UTC-6 John Allwine wrote:

> The kernel doesn't seem to be the problem. Even when I change to that 
> version my /dev/uio* devices aren't showing up. Am I missing a simple step 
> somewhere?
>
> $ sudo /opt/scripts/tools/version.sh 
> git:/opt/scripts/:[481db95174653ba485cca3797d4bbbe03c0cded0]
> eeprom:[A335BNLT000C1626BBBG0552]
> model:[TI_AM335x_BeagleBone_Black]
> dogtag:[Pocket NC Debian Buster Image 2021-02-01]
> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 
> 2019.04-2-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500)]:[location: dd MBR]
> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
> 2019.04-2-gc9b3922522]:[location: dd MBR]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 
> 2019.04-2-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd MBR]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2019.04-2-gbb4af0f50f]:[location: dd MBR]
> UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
> UBOOT: Loaded Overlay:[BB-ADC-00A0]
> UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
> UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0]
> kernel:[4.19.180-bone-rt-r61]
> /boot/uEnv.txt Settings:
> uboot_overlay_options:[enable_uboot_overlays=1]
> uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo]
> uboot_overlay_options:[enable_uboot_cape_universal=1]
> pkg check: to individually upgrade run: [sudo apt install --only-upgrade 
> ]
> pkg:[bb-cape-overlays]:[4.14.20210225.0-0~buster+20210225]
> pkg:[bb-customizations]:[1.20201105.0-0~buster+20201110]
> pkg:[bb-usb-gadgets]:[1.20200504.0-0~buster+20200504]
> pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~buster+20200813]
> pkg:[kmod]:[26-1]
> WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
> cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
> root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
> net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet]
> dmesg | grep remote
> [1.160381] remoteproc remoteproc0: wkup_m3 is available
> [1.423096] remoteproc remoteproc0: powering up wkup_m3
> [1.423115] remoteproc remoteproc0: Booting fw image 
> am335x-pm-firmware.elf, size 217168
> [1.425226] remoteproc remoteproc0: remote processor wkup_m3 is now up
> dmesg | grep pru
> dmesg | grep pinctrl-single
> [0.785028] pinctrl-single 44e10800.pinmux: 142 pins, size 568
> dmesg | grep gpio-of-helper
> [0.796784] gpio-of-helper ocp:cape-universal: ready
> END
>
> $ lsmod
> Module  Size  Used by
> uio_pruss  16384  0
> evdev  20480  1
> 8021q  24576  0
> garp   16384  1 8021q
> stp16384  1 garp
> mrp16384  1 8021q
> llc16384  2 garp,stp
> usb_f_acm  16384  2
> u_serial   20480  3 usb_f_acm
> usb_f_ncm  20480  2
> usb_f_rndis20480  4
> u_ether20480  2 usb_f_ncm,usb_f_rndis
> libcomposite   40960  16 usb_f_acm,usb_f_ncm,usb_f_rndis
> uio_pdrv_genirq16384  0
> uio16384  2 uio_pruss,uio_pdrv_genirq
> iptable_nat16384  0
> nf_nat_ipv416384  1 iptable_nat
> nf_nat 40960  1 nf_nat_ipv4
> nf_conntrack  118784  2 nf_nat_ipv4,nf_nat
> nf_defrag_ipv6 16384  1 nf_conntrack
> nf_defrag_ipv4 16384  1 nf_conntrack
> iptable_mangle 16384  0
> iptable_filter 16384  0
> ip_tables  20480  3 iptable_mangle,iptable_filter,iptable_nat
> x_tables   20480  3 iptable_mangle,ip_tables,iptable_filter
> spidev 16384  0
>
> $ ls /dev/uio* -la
> ls: cannot access '/dev/uio*': No such file or directory
>
> On Wednesday, March 17, 2021 at 11:24:53 AM UTC-6 RobertCNelson wrote:
>
>> On Wed, Mar 17, 2021 at 12:17 PM John Allwine  
>> wrote: 
>> > 
>> > I tried a different kernel, one that I know works with uio_pruss 
>> because I'm using it on a different image (4.19.59-bone-rt-r36). In my 
>> custom image, though, the /dev/uio* devices aren't showing up. Here's 
>> version.sh output on it: 
>> > 
>> > git:/opt/scripts/:[481db95174653ba485cca3797d4bbbe03c0cded0] 
>> > eeprom:[A335BNLT000C1626BBBG0552] 
>> > model:[TI_AM335x_BeagleBone_Black] 
>> > dogtag:[Pocket NC Debian Buster Image 2021-02-01] 
>> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 
>> 2019.04-2-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500)]:[location: dd 
>> MBR] 
>> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
>> 2019.04-2-gc9b3922522]:[location: dd MBR] 
>> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 
>> 2019.04-2-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd 
>> MBR] 
>> >

Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts

2021-03-17 Thread John Allwine 
The kernel doesn't seem to be the problem. Even when I change to that 
version my /dev/uio* devices aren't showing up. Am I missing a simple step 
somewhere?

$ sudo /opt/scripts/tools/version.sh 
git:/opt/scripts/:[481db95174653ba485cca3797d4bbbe03c0cded0]
eeprom:[A335BNLT000C1626BBBG0552]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[Pocket NC Debian Buster Image 2021-02-01]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 
2019.04-2-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500)]:[location: dd MBR]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
2019.04-2-gc9b3922522]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 
2019.04-2-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
2019.04-2-gbb4af0f50f]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
UBOOT: Loaded Overlay:[BB-ADC-00A0]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0]
kernel:[4.19.180-bone-rt-r61]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade 
]
pkg:[bb-cape-overlays]:[4.14.20210225.0-0~buster+20210225]
pkg:[bb-customizations]:[1.20201105.0-0~buster+20201110]
pkg:[bb-usb-gadgets]:[1.20200504.0-0~buster+20200504]
pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~buster+20200813]
pkg:[kmod]:[26-1]
WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet]
dmesg | grep remote
[1.160381] remoteproc remoteproc0: wkup_m3 is available
[1.423096] remoteproc remoteproc0: powering up wkup_m3
[1.423115] remoteproc remoteproc0: Booting fw image 
am335x-pm-firmware.elf, size 217168
[1.425226] remoteproc remoteproc0: remote processor wkup_m3 is now up
dmesg | grep pru
dmesg | grep pinctrl-single
[0.785028] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
[0.796784] gpio-of-helper ocp:cape-universal: ready
END

$ lsmod
Module  Size  Used by
uio_pruss  16384  0
evdev  20480  1
8021q  24576  0
garp   16384  1 8021q
stp16384  1 garp
mrp16384  1 8021q
llc16384  2 garp,stp
usb_f_acm  16384  2
u_serial   20480  3 usb_f_acm
usb_f_ncm  20480  2
usb_f_rndis20480  4
u_ether20480  2 usb_f_ncm,usb_f_rndis
libcomposite   40960  16 usb_f_acm,usb_f_ncm,usb_f_rndis
uio_pdrv_genirq16384  0
uio16384  2 uio_pruss,uio_pdrv_genirq
iptable_nat16384  0
nf_nat_ipv416384  1 iptable_nat
nf_nat 40960  1 nf_nat_ipv4
nf_conntrack  118784  2 nf_nat_ipv4,nf_nat
nf_defrag_ipv6 16384  1 nf_conntrack
nf_defrag_ipv4 16384  1 nf_conntrack
iptable_mangle 16384  0
iptable_filter 16384  0
ip_tables  20480  3 iptable_mangle,iptable_filter,iptable_nat
x_tables   20480  3 iptable_mangle,ip_tables,iptable_filter
spidev 16384  0

$ ls /dev/uio* -la
ls: cannot access '/dev/uio*': No such file or directory

On Wednesday, March 17, 2021 at 11:24:53 AM UTC-6 RobertCNelson wrote:

> On Wed, Mar 17, 2021 at 12:17 PM John Allwine  wrote:
> >
> > I tried a different kernel, one that I know works with uio_pruss because 
> I'm using it on a different image (4.19.59-bone-rt-r36). In my custom 
> image, though, the /dev/uio* devices aren't showing up. Here's version.sh 
> output on it:
> >
> > git:/opt/scripts/:[481db95174653ba485cca3797d4bbbe03c0cded0]
> > eeprom:[A335BNLT000C1626BBBG0552]
> > model:[TI_AM335x_BeagleBone_Black]
> > dogtag:[Pocket NC Debian Buster Image 2021-02-01]
> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 
> 2019.04-2-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500)]:[location: dd MBR]
> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
> 2019.04-2-gc9b3922522]:[location: dd MBR]
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 
> 2019.04-2-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd MBR]
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2019.04-2-gbb4af0f50f]:[location: dd MBR]
> > UBOOT: Loaded Overlay:[BB-ADC-00A0]
> > UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
> > UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0]
> > kernel:[4.19.59-bone-rt-r36]
>
> probably fixed, between r36 and r61...
>
>
> http://gfnd.rcn-ee.org:81/farm/uptime/pwr08-ser16-bbg-4.19.180-bone-rt-r61.log
>
> kernel:[4.19.180-bone-rt-r61]
>
> ls /dev/uio* -la
>

Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts

2021-03-17 Thread Robert Nelson 
On Wed, Mar 17, 2021 at 12:17 PM John Allwine  wrote:
>
> I tried a different kernel, one that I know works with uio_pruss because I'm 
> using it on a different image (4.19.59-bone-rt-r36). In my custom image, 
> though, the /dev/uio* devices aren't showing up. Here's version.sh output on 
> it:
>
> git:/opt/scripts/:[481db95174653ba485cca3797d4bbbe03c0cded0]
> eeprom:[A335BNLT000C1626BBBG0552]
> model:[TI_AM335x_BeagleBone_Black]
> dogtag:[Pocket NC Debian Buster Image 2021-02-01]
> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 
> 2019.04-2-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500)]:[location: dd MBR]
> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
> 2019.04-2-gc9b3922522]:[location: dd MBR]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 
> 2019.04-2-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd MBR]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2019.04-2-gbb4af0f50f]:[location: dd MBR]
> UBOOT: Loaded Overlay:[BB-ADC-00A0]
> UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
> UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0]
> kernel:[4.19.59-bone-rt-r36]

probably fixed, between r36 and r61...

http://gfnd.rcn-ee.org:81/farm/uptime/pwr08-ser16-bbg-4.19.180-bone-rt-r61.log

kernel:[4.19.180-bone-rt-r61]

ls /dev/uio* -la
crw-rw 1 root users 240, 0 Mar 16 15:10 /dev/uio0
crw-rw 1 root users 240, 1 Mar 16 15:10 /dev/uio1
crw-rw 1 root users 240, 2 Mar 16 15:10 /dev/uio2
crw-rw 1 root users 240, 3 Mar 16 15:10 /dev/uio3
crw-rw 1 root users 240, 4 Mar 16 15:10 /dev/uio4
crw-rw 1 root users 240, 5 Mar 16 15:10 /dev/uio5
crw-rw 1 root users 240, 6 Mar 16 15:10 /dev/uio6
crw-rw 1 root users 240, 7 Mar 16 15:10 /dev/uio7

( we need to change that to root:gpio...)

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/CAOCHtYgU252vMO3pxq%3DV5bbN0Kzdg2z-jmk%2Bznc1E3CDrr%3DHrw%40mail.gmail.com.

Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts

2021-03-17 Thread John Allwine 
I tried a different kernel, one that I know works with uio_pruss because
I'm using it on a different image (4.19.59-bone-rt-r36). In my custom
image, though, the /dev/uio* devices aren't showing up. Here's version.sh
output on it:

git:/opt/scripts/:[481db95174653ba485cca3797d4bbbe03c0cded0]
eeprom:[A335BNLT000C1626BBBG0552]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[Pocket NC Debian Buster Image 2021-02-01]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL
2019.04-2-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500)]:[location: dd MBR]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
2019.04-2-gc9b3922522]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL
2019.04-2-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2019.04-2-gbb4af0f50f]:[location: dd MBR]
UBOOT: Loaded Overlay:[BB-ADC-00A0]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0]
kernel:[4.19.59-bone-rt-r36]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade
]
pkg:[bb-cape-overlays]:[4.14.20210225.0-0~buster+20210225]
pkg:[bb-customizations]:[1.20201105.0-0~buster+20201110]
pkg:[bb-usb-gadgets]:[1.20200504.0-0~buster+20200504]
pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~buster+20200813]
pkg:[kmod]:[26-1]
WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M
net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet]
dmesg | grep remote
[1.242393] remoteproc remoteproc0: wkup_m3 is available
[1.515377] remoteproc remoteproc0: powering up wkup_m3
[1.515394] remoteproc remoteproc0: Booting fw image
am335x-pm-firmware.elf, size 217168
[1.517496] remoteproc remoteproc0: remote processor wkup_m3 is now up
dmesg | grep pru
dmesg | grep pinctrl-single
[0.868764] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
[0.879941] gpio-of-helper ocp:cape-universal: ready
END

On Wed, Mar 17, 2021 at 11:05 AM Robert Nelson 
wrote:

> On Wed, Mar 17, 2021 at 11:24 AM John Allwine  wrote:
> >
> > How about the rt kernel? I'm using 4.19.94-ti-rt-r57 and don't seem to
> have the /dev/uio* devices. Is there something else I need to activate
> those devices or does the rt kernel not support uio_pruss?
>
> sudo /opt/scripts/tools/version.sh
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYhP359QSK0P8ZJmupNqJ0Ap870jOgbQdYVPQHcncEqxxA%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/CAPEK9qYpZOuZmRCyxVa1QiRtk_j0GpvVroYGC4Fq9hKyUEjbYQ%40mail.gmail.com.

Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts

2021-03-17 Thread Robert Nelson 
On Wed, Mar 17, 2021 at 11:24 AM John Allwine  wrote:
>
> How about the rt kernel? I'm using 4.19.94-ti-rt-r57 and don't seem to have 
> the /dev/uio* devices. Is there something else I need to activate those 
> devices or does the rt kernel not support uio_pruss?

sudo /opt/scripts/tools/version.sh

Regards,

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

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

Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts

2021-03-17 Thread John Allwine 
How about the rt kernel? I'm using 4.19.94-ti-rt-r57 and don't seem to have
the /dev/uio* devices. Is there something else I need to activate those
devices or does the rt kernel not support uio_pruss?

On Wed, Mar 17, 2021 at 9:49 AM Robert Nelson 
wrote:

> On Wed, Mar 17, 2021 at 10:46 AM John Allwine  wrote:
> >
> > Great, and so if I had used one of those --enable-uboot-pru* options and
> I wanted to manually change an image to using uio_pruss, is it just a
> matter of changing /boot/uEnv.txt to use that overlay?
>
> Correct, 4.14.x-ti & 4.19.x-ti kernels support changing the pru driver
> from /boot/uEnv.txt.. Just un-comment the version you want..
>
> 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/CAOCHtYgrETMrZjb_QUBS5WSRRCz38KOkD64TR3sTcU%2BDCVnb7A%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/CAPEK9qb1zqFCJT_UHUo94zO7ukXFLGxKTayGdd8EhTn4X%3Db5kA%40mail.gmail.com.

Re: [beagleboard] Re: Recomended practices for using the PRUs

2021-03-17 Thread TJF 
libpruio checks for claimed pins in sysfs file

/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins

This path changed in kernel 4.19 to

/sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pinmux-pins

so that pinmuxing fails.

You can fix it by creating a link named as the old path pointing to the new 
path (admin privilegues).

PS:
Regarding FreeBASIC just execute

sudo apt install freebasic

-- 
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/6b9c78d0-7af3-4834-86d5-313e6375af37n%40googlegroups.com.

Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts

2021-03-17 Thread Robert Nelson 
On Wed, Mar 17, 2021 at 10:46 AM John Allwine  wrote:
>
> Great, and so if I had used one of those --enable-uboot-pru* options and I 
> wanted to manually change an image to using uio_pruss, is it just a matter of 
> changing /boot/uEnv.txt to use that overlay?

Correct, 4.14.x-ti & 4.19.x-ti kernels support changing the pru driver
from /boot/uEnv.txt.. Just un-comment the version you want..

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

Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts

2021-03-17 Thread John Allwine 
Great, and so if I had used one of those --enable-uboot-pru* options and I 
wanted to manually change an image to using uio_pruss, is it just a matter 
of changing /boot/uEnv.txt to use that overlay?

On Wednesday, March 17, 2021 at 9:39:21 AM UTC-6 RobertCNelson wrote:

> On Wed, Mar 17, 2021 at 10:33 AM John Allwine  wrote:
> >
> > What is necessary to set up a Beaglebone Black image with uio_pruss 
> enabled rather than remoteproc?
> >
> > If I wanted to build an image using this config file, for example: 
> https://github.com/beagleboard/image-builder/blob/master/configs/bb.org-debian-buster-console-v4.19.conf
> >
> > What steps would I have to take?
>
> When you run "setup_sdcard.sh" to generate your target *.img or
> microsd, just don't pass any "--enable-uboot-pru*" options..
>
>
> https://github.com/beagleboard/image-builder/blob/master/tools/setup_sdcard.sh#L2070-L2084
>
> as the default is:
>
> uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo
>
>
> https://github.com/beagleboard/image-builder/blob/master/tools/setup_sdcard.sh#L1303-L1348
>
> 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/c7f63533-e612-410a-8414-056b167dee6fn%40googlegroups.com.

Re: [beagleboard] setting up uio_pruss on BBB image using image-builder scripts

2021-03-17 Thread Robert Nelson 
On Wed, Mar 17, 2021 at 10:33 AM John Allwine  wrote:
>
> What is necessary to set up a Beaglebone Black image with uio_pruss enabled 
> rather than remoteproc?
>
> If I wanted to build an image using this config file, for example: 
> https://github.com/beagleboard/image-builder/blob/master/configs/bb.org-debian-buster-console-v4.19.conf
>
> What steps would I have to take?

When you run "setup_sdcard.sh" to generate your target *.img or
microsd, just don't pass any "--enable-uboot-pru*" options..

https://github.com/beagleboard/image-builder/blob/master/tools/setup_sdcard.sh#L2070-L2084

as the default is:

uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo

https://github.com/beagleboard/image-builder/blob/master/tools/setup_sdcard.sh#L1303-L1348

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

[beagleboard] setting up uio_pruss on BBB image using image-builder scripts

2021-03-17 Thread John Allwine 
What is necessary to set up a Beaglebone Black image with uio_pruss enabled 
rather than remoteproc?

If I wanted to build an image using this config file, for 
example: 
https://github.com/beagleboard/image-builder/blob/master/configs/bb.org-debian-buster-console-v4.19.conf

What steps would I have to take?

-- 
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/cd5c60f9-41a5-46b8-b808-8377d77897e9n%40googlegroups.com.