[beagleboard] Re: PRU Memory Store Instruction with Autoincrement?

[Andrew P. Lentvorski]

Hmm, that's an interesting idea, Dimitar, to encode the increment in the 
immediate.  That's probably ... useful.

That mechanism would give me a 64-sample burst per register which could 
possibly get me to 1920 samples *if* the SBBO doesn't stall out anywhere.

I thought about the BeagleLogic, but it relies on the fact that every other 
cycle is NOP, so it can effectively run something simultaneously at 
half-speed in the interleaved time.

Looks like it's time for some experiments.  I'll report back if I see 
anything interesting.
On Sunday, October 18, 2020 at 12:11:33 PM UTC-7 din...@gmail.com wrote:

> Hi,
>
> Do you require continuous 200MHz sampling? That would be difficult I think.
>
> If you require bursts of 200MHz sampling, how long should those bursts be? 
> Even if you find autoincrement opcode, you would still need to add one jump 
> instruction to "loop".
>
> You can try hardcoding the "increment" into the constant offset field. And 
> load several registers with starting address of each 256-byte chunk of your 
> destination buffer. Example:
>
> init:
>  ldi r0, __buf_start
>  ldi r1, __buf_start+256
>  ldi r2, __buf_start+256*2
>   ...
> burst_store:
>  sbbo &r31, r0, 0, 4
>  sbbo &r31, r0, 4, 4
>  sbbo &r31, r0, 8, 4
>  sbbo &r31, r0, 12, 4
>  sbbo &r31, r0, 16, 4
>  
>  sbbo &r31, r0, 252, 4
>  sbbo &r31, r1, 0, 4
>  sbbo &r31, r0, 4, 4
>  ...
>
> I am not sure what are the buffering limits of PRU's posted writes. I 
> doubt if so many consecutive sbbo instructions would not stall.
>
> You should also examine BeagleLogic firmware's operation mode for 100MHz. 
> Perhaps you can modify it to take 200MHz bursts instead of continuous 
> 100MHz sampling. Difference with above single-PRU example is that you would 
> use PRU register banks for buffering, which would decouple sampling from 
> SBBO bus operations.
>
> Regards,
> Dimitar
>
> On Sunday, October 18, 2020 at 10:16:44 AM UTC+3 Andrew P. Lentvorski 
> wrote:
>
>> Hi, folks,
>>
>> I'm trying to dump R31 over and over into either RAM0 or Shared DRAM 
>> (Data RAM).
>>
>> So, basically it looks like I have to do:
>>
>> Store R31 to address in register
>> Increment address in register
>> (Lather rinse repeat)
>>
>> As that stands, that's a 100MHz sample of R31.  Is there anyway to do the 
>> autoincrement on the store?  That would double my sampling rate to 200MHz 
>> which would be the maximum possible.
>>
>> Alternatively, is there a different way to sample and store R31 
>> repeatedly to RAM0 or Shared DRAM?  I can't seem to see one, but there are 
>> so many permutation of Store Burst, mapping, the broadside transfer bus, 
>> and peripherals that I can quite easily be missing something that someone 
>> more experienced knows about.
>>
>> Thanks.
>>
>

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

[beagleboard] Beagle bone black setup with Intel Real sense camera

[Megha Bhirade]

Hi,

I am using Beagle bone black in Linux Ubuntu platform and i want to use 
Real sense camera for my application.

Please anybody suggest me how to setup the Beagle bone black with Real 
sense Depth and tracking camera??

Please suggest me any related link for step by step setup...

-- 
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/4340e28c-4bb9-4995-95bc-bd2baa009f80o%40googlegroups.com.

[beagleboard] Re: Controling sample rate

[Mark A. Yoder]

If it's the ADC you want to control, I have some note's here[1] on how to 
change the sampling rate.

--Mark

[1] 
https://elinux.org/EBC_Exercise_10a_Analog_In#Analog_in_-_Continuous.2C_Change_the_sample_rate
 

On Saturday, October 17, 2020 at 5:35:59 PM UTC-4 barkan.ugu...@gmail.com 
wrote:

> Hello Frederico,
>
> I assume you want to create a fixed sampling rate so that you can use the 
> BeagleBone as a controller for a feedback system. 
> If this is the case, I advise you to run it via Linux with an RTOS patch, 
> preferably Xenomai:
> https://cvra.ch/blog/2015/xenomai-installation-on-a-beaglebone-black
>
> Barkan
>
>
> On Saturday, September 28, 2019 at 6:55:08 PM UTC+3, Frederico Alves de 
> Oliveira Silva wrote:
>>
>>
>> Helllo guys,
>>
>> I am a total begginner with BeagleBone.
>> I would like to ask how can I control the sample rate of BeagleBone Black.
>> Is there a minimal example?
>>
>> Thank you for the attention!
>> Frederico
>>
>

-- 
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/b5ece2c5-7d0c-4c0d-843c-917ca079b53dn%40googlegroups.com.

[beagleboard] Re: PRU Memory Store Instruction with Autoincrement?

[Mark A. Yoder]

BeagleLogic[1] does some interesting tricks[2] to get a solid 100MHz 
sampling rate.  The *PRU Cookbook* presents an overview of it. Check it out.

--Mark

[1] https://beaglelogic.readthedocs.io/en/latest/ 
[2] 
https://theembeddedkitchen.net/beaglelogic-building-a-logic-analyzer-with-the-prus-part-1/449
[3] 
https://markayoder.github.io/PRUCookbook/01case/case.html#_beaglelogic_a_14_channel_logic_analyzer

On Monday, October 19, 2020 at 5:25:45 AM UTC-4 Andrew P. Lentvorski wrote:

> Hmm, that's an interesting idea, Dimitar, to encode the increment in the 
> immediate.  That's probably ... useful.
>
> That mechanism would give me a 64-sample burst per register which could 
> possibly get me to 1920 samples *if* the SBBO doesn't stall out anywhere.
>
> I thought about the BeagleLogic, but it relies on the fact that every 
> other cycle is NOP, so it can effectively run something simultaneously at 
> half-speed in the interleaved time.
>
> Looks like it's time for some experiments.  I'll report back if I see 
> anything interesting.
> On Sunday, October 18, 2020 at 12:11:33 PM UTC-7 din...@gmail.com wrote:
>
>> Hi,
>>
>> Do you require continuous 200MHz sampling? That would be difficult I 
>> think.
>>
>> If you require bursts of 200MHz sampling, how long should those bursts 
>> be? Even if you find autoincrement opcode, you would still need to add one 
>> jump instruction to "loop".
>>
>> You can try hardcoding the "increment" into the constant offset field. 
>> And load several registers with starting address of each 256-byte chunk of 
>> your destination buffer. Example:
>>
>> init:
>>  ldi r0, __buf_start
>>  ldi r1, __buf_start+256
>>  ldi r2, __buf_start+256*2
>>   ...
>> burst_store:
>>  sbbo &r31, r0, 0, 4
>>  sbbo &r31, r0, 4, 4
>>  sbbo &r31, r0, 8, 4
>>  sbbo &r31, r0, 12, 4
>>  sbbo &r31, r0, 16, 4
>>  
>>  sbbo &r31, r0, 252, 4
>>  sbbo &r31, r1, 0, 4
>>  sbbo &r31, r0, 4, 4
>>  ...
>>
>> I am not sure what are the buffering limits of PRU's posted writes. I 
>> doubt if so many consecutive sbbo instructions would not stall.
>>
>> You should also examine BeagleLogic firmware's operation mode for 100MHz. 
>> Perhaps you can modify it to take 200MHz bursts instead of continuous 
>> 100MHz sampling. Difference with above single-PRU example is that you would 
>> use PRU register banks for buffering, which would decouple sampling from 
>> SBBO bus operations.
>>
>> Regards,
>> Dimitar
>>
>> On Sunday, October 18, 2020 at 10:16:44 AM UTC+3 Andrew P. Lentvorski 
>> wrote:
>>
>>> Hi, folks,
>>>
>>> I'm trying to dump R31 over and over into either RAM0 or Shared DRAM 
>>> (Data RAM).
>>>
>>> So, basically it looks like I have to do:
>>>
>>> Store R31 to address in register
>>> Increment address in register
>>> (Lather rinse repeat)
>>>
>>> As that stands, that's a 100MHz sample of R31.  Is there anyway to do 
>>> the autoincrement on the store?  That would double my sampling rate to 
>>> 200MHz which would be the maximum possible.
>>>
>>> Alternatively, is there a different way to sample and store R31 
>>> repeatedly to RAM0 or Shared DRAM?  I can't seem to see one, but there are 
>>> so many permutation of Store Burst, mapping, the broadside transfer bus, 
>>> and peripherals that I can quite easily be missing something that someone 
>>> more experienced knows about.
>>>
>>> Thanks.
>>>
>>

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

[beagleboard] Re: /dev/remoteproc/pruss-core0/state not found

[Mark A. Yoder]

*sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=1*  solved the problem. 

On Friday, October 16, 2020 at 4:58:57 PM UTC-4 emil...@gmail.com wrote:

> I'm trying to run the pru examples in /var/lib/cloud9 and I am getting 
> this error message. Anyone have any suggestions?
>
> Started /var/lib/cloud9/: neopixelDynamic.pru0.c
> File path: /var/lib/cloud9/BeagleBone/Black/pru
> File: /var/lib/cloud9/BeagleBone/Black/pru/neopixelDynamic.pru0.c
> Arguments: 
> File name: neopixelDynamic.pru0.c
> File extension: c
> File base name: neopixelDynamic.pru0
> Packages: ~.c9/packages
> Project path: /var/lib/cloud9/
> Project name: projectname
> Hostname: localhost
> Hostname path: 
> https://undefined/BeagleBone/Black/pru/neopixelDynamic.pru0.c
> URL: http://localhost
> Port: 8080
> IP: 0.0.0.0
> Command: BeagleBone/Black/pru/neopixelDynamic.pru0.c
> Python: python3
> Python path: 
> /usr/lib/python3.7/dist-packages:/usr/local/lib/python3.7/dist-packages
> /var/lib/cloud9/common/Makefile:27: 
> MODEL=TI_AM335x_BeagleBone_Black,TARGET=neopixelDynamic.pru0,COMMON=/var/lib/cloud9/common
> /var/lib/cloud9/common/Makefile:146: 
> GEN_DIR=/tmp/cloud9-examples,CHIP=am335x,PROC=pru,PRUN=0,PRU_DIR=/dev/remoteproc/pruss-core0,EXE=.out
> -Stopping PRU 0
> /bin/sh: 1: cannot create /dev/remoteproc/pruss-core0/state: Directory 
> nonexistent
> Cannot stop 0
> CC  neopixelDynamic.pru0.c
> "/var/lib/cloud9/common/prugpio.h", line 55: warning #1181-D: #warning 
> directive: "Found am335x"
> LD  /tmp/cloud9-examples/neopixelDynamic.pru0.o
> -   copying firmware file 
> /tmp/cloud9-examples/neopixelDynamic.pru0.out to 
> /lib/firmware/am335x-pru0-fw
> write_init_pins.sh
> writing "pruout" to "/sys/devices/platform/ocp/ocp:P9_31_pinmux/state"
> -Starting PRU 0
> /bin/sh: 1: cannot create /dev/remoteproc/pruss-core0/state: Directory 
> nonexistent
> make: *** [/var/lib/cloud9/common/Makefile:166: start] Error 2
> rm /tmp/cloud9-examples/neopixelDynamic.pru0.o
>
>
>
> *debian@beaglebone:/var/lib/cloud9/BeagleBone/Black/pru$ sudo 
> /opt/scripts/tools/version.sh *
> *[sudo] password for debian: *
> *git:/opt/scripts/:[ef16ffa8c27225005cc2b2c974a83da3dee6c1ef]*
> *eeprom:[A335BNLT000C2025BBBG0598]*
> *model:[TI_AM335x_BeagleBone_Black]*
> *dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-08-31]*
> *bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
> 2019.04-2-gc9b3922522]:[location: dd MBR]*
> *bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2019.04-2-gf15b99f0b6]:[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]*
> *kernel:[4.19.94-ti-r50]*
> *nodejs:[v10.21.0]*
> */boot/uEnv.txt Settings:*
> *uboot_overlay_options:[enable_uboot_overlays=1]*
> *uboot_overlay_options:[disable_uboot_overlay_video=1]*
>
> *uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-RPROC-4-19-TI-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.20200814.0-0~buster+20200814]*
> *pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~buster+20200813]*
> *pkg:[kmod]:[26-1]*
> *pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~buster+20200716]*
> *pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305]*
> *groups:[debian : debian adm kmem dialout cdrom floppy audio dip video 
> plugdev users systemd-journal input bluetooth netdev i2c gpio admin spi iio 
> docker tisdk weston-launch xenomai cloud9ide pwm eqep remoteproc]*
> *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*
> *[   63.167635] remoteproc remoteproc0: wkup_m3 is available*
> *[   63.236184] remoteproc remoteproc0: powering up wkup_m3*
> *[   63.236216] remoteproc remoteproc0: Booting fw image 
> am335x-pm-firmware.elf, size 217168*
> *[   63.236494] remoteproc remoteproc0: remote processor wkup_m3 is now up*
> *dmesg | grep pru*
> *dmesg | grep pinctrl-single*
> *[0.926013] pinctrl-single 44e10800.pinmux: 142 pins, size 568*
> *dmesg | grep gpio-of-helper*
> *[0.939591] gpio-of-helper ocp:cape-universal: ready*
> *lsusb*
> *Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub*
> *END*
> *debian@beaglebone:/var/lib/cloud9/BeagleBone/Black/pru$ *
>
>

-- 
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/8a51b087-8a9f-4fa0-a222-aeee35b4a07en%40googlegroups.com.

Re: [beagleboard] Re: config-pin tool doesn't work.

[Szabó Benedek Ákos]

Hi Jon!
I upgraded the kernel to the same version as you have.
This is the output:
root@beaglebone:~# 
/opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q 
P2_18
P2_18 pinmux file not found!
Cannot read pinmux file: /sys/devices/platform/ocp/ocp*P2_18_pinmux/state

Still not working. In uEnv.txt file, I have this added:
uboot_overlay_addr6=/lib/firmware/PB-MCP2515-SPI1.dtbo
This is the MCP2515 which could read the SWCAN bus if it was set to HIGH.

jonn...@gmail.com a következőt írta (2020. október 19., hétfő, 3:32:13 
UTC+2):

> This is how to set say P2_18 as an output and high.
>
> debian@beaglebone:~$* 
> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q 
> P2.18*
> *P2_18 Mode: gpio Direction: in Value: 0*
> debian@beaglebone:~$ 
> */opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin 
> P2.18 gpio*
> debian@beaglebone:~$* 
> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin P2.18 
> out*
> debian@beaglebone:~$ 
> */opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin 
> P2.18 hi*
> debian@beaglebone:~$ 
> */opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin 
> -q P2.18*
> *P2_18 Mode: gpio Direction: out Value: 1*
>
>
> I don't think the /usr/bin/config-pin tool can do this.
>
> Cheers,
>
> Jon
>
> On Sun, Oct 18, 2020 at 6:17 PM jonnymo  wrote:
>
>> With a PocketBeagle running Debian 10 (Buster) IoT image and kernel 
>> 4.19.94-ti-r51 I see this:
>>
>> *debian@beaglebone:~$ 
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q 
>> P2_06*
>> *P2_06 Mode: default Direction: in Value: 0*
>> *debian@beaglebone:~$ 
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -i 
>> P2_06*
>> *Pin name: P2_06*
>> *Function if no cape loaded: gpio*
>> *Function if cape loaded: default gpio gpio_pu gpio_pd gpio_input*
>> *Function information: gpio1_25 default gpio1_25 gpio1_25 gpio1_25 
>> gpio1_25*
>> *Kernel GPIO id: 57*
>> *PRU GPIO id: 89*
>> *debian@beaglebone:~$ 
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -l 
>> P2_06*
>> *default gpio gpio_pu gpio_pd gpio_input*
>>
>> *debian@beaglebone:~$ 
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q 
>> P2_18*
>> *P2_18 Mode: default Direction: in Value: 0*
>> *debian@beaglebone:~$ 
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -i 
>> P2_18*
>> *Pin name: P2_18*
>> *Function if no cape loaded: gpio*
>> *Function if cape loaded: default gpio gpio_pu gpio_pd gpio_input qep 
>> pru_ecap pruin*
>> *Function information: gpio1_15 default gpio1_15 gpio1_15 gpio1_15 
>> gpio1_15 eqep2_strobe pru_ecap pru0_in15*
>> *Kernel GPIO id: 47*
>> *PRU GPIO id: 79*
>> *debian@beaglebone:~$ 
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -l 
>> P2_18*
>> *default gpio gpio_pu gpio_pd gpio_input qep pru_ecap pruin*
>>
>>
>> *debian@beaglebone:~$ config-pin -q P2_18 
>>*
>> *Current mode for P2_18 is: default*
>>
>> *debian@beaglebone:~$ config-pin -q P2_06*
>>
>> *Current mode for P2_06 is: default*
>>
>>
>> Note, I did do a 'sudo apt-get update' and sudo apt-get upgrade' and then 
>> updated the scripts and such listed in the following Beaglebone Upgrade 
>> link including the 'update_kernel.sh' script.
>> https://beagleboard.org/upgrade
>>
>>
>> Cheers,
>>
>> Jon
>>
>> On Sun, Oct 18, 2020 at 5:50 PM Szabó Benedek Ákos  
>> wrote:
>>
>>> Hi there!
>>> Sorry for the late reply.
>>> So, here is a summary, what I already did, and what I tried:
>>> I have a problem configuring a pin P2_18 and P2_06 on PocketBeagle.
>>>
>>> What I'm trying is to get SWCAN working on a GM car, but I have to set 
>>> it up to HIGH.
>>> When I run config-pin P2_18 hi it returns error:
>>> config-pin P2_18 hi ERROR: open() for 
>>> /sys/devices/platform/ocp/ocp:P2_18_pinmux/state failed, No such file or 
>>> directory 
>>>
>>> I found no P2_18 or P2_06 pinmux file exists here:
>>>
>>> 
>>>
>>> /sys/devices/platform/ocp/ocp:
>>>
>>> version.sh output:
>>> opt/scripts/tools/version.sh
>>> git:/opt/scripts/:[7cdc270818b76d829d247cf05fe309c320a3929a]
>>> eeprom:[A335PBGL00A21743GPB30299]
>>> model:[TI_AM335x_PocketBeagle]
>>> dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-08-25]
>>> bootloader:[microSD]:[/dev/mmcblk0]:[U-Boot 
>>> 2019.04-2-gc9b3922522]:[location: dd MBR]
>>> UBOOT: Booted Device-Tree:[am335x-pocketbeagle.dts]
>>> UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0]
>>> UBOOT: Loaded Overlay:[BB-ADC-00A0]
>>> UBOOT: Loaded Overlay:[PB-CAN0-00A0]
>>> UBOOT: Loaded Overlay:[PB-CAN1-00A0]
>>> UBOOT: Loaded Overlay:[PB-MCP2515-SPI1]
>>> kernel:[4.19.94-ti-r50]
>>> nodejs:[v10.21.0]
>>> /boot/uEnv.txt Settings:
>>> uboot_overlay_options:[enable_uboot_overlays=1]
>>>
>>> uboot_overlay_options:[ub

Re: [beagleboard] Re: /dev/remoteproc/pruss-core0/state not found

[jonnymo]

Try updating your scripts and kernel.
https://beagleboard.org/upgrade

I am able to run the blinkInternalLED.pru1.c example without issue.

This is what I am running on my BB Black:

*debian@beaglebone:/var/lib/cloud9/common$ sudo
/opt/scripts/tools/version.sh*
*git:/opt/scripts/:[20c080bc91f243ef852a704758788a31083b0f9e]*
*eeprom:[A335BNLT00C0414BBBK0218▒]*
*model:[TI_AM335x_BeagleBone_Black]*
*dogtag:[BeagleBoard.org Debian Buster LXQt Image 2020-08-25]*
*bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
2019.04-2-gc9b3922522]:[location: dd MBR]*
*bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2019.04-2-gc9b3922522]:[location: dd MBR]*
*UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]*
*UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0]*
*UBOOT: Loaded Overlay:[BB-ADC-00A0]*
*UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]*
*UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0]*
*kernel:[4.19.94-ti-r51]*
*nodejs:[v10.21.0]*


Cheers,

Jon

On Mon, Oct 19, 2020 at 9:51 AM Mark A. Yoder 
wrote:

> *sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=1*  solved the problem.
>
> On Friday, October 16, 2020 at 4:58:57 PM UTC-4 emil...@gmail.com wrote:
>
>> I'm trying to run the pru examples in /var/lib/cloud9 and I am getting
>> this error message. Anyone have any suggestions?
>>
>> Started /var/lib/cloud9/: neopixelDynamic.pru0.c
>> File path: /var/lib/cloud9/BeagleBone/Black/pru
>> File: /var/lib/cloud9/BeagleBone/Black/pru/neopixelDynamic.pru0.c
>> Arguments:
>> File name: neopixelDynamic.pru0.c
>> File extension: c
>> File base name: neopixelDynamic.pru0
>> Packages: ~.c9/packages
>> Project path: /var/lib/cloud9/
>> Project name: projectname
>> Hostname: localhost
>> Hostname path:
>> https://undefined/BeagleBone/Black/pru/neopixelDynamic.pru0.c
>> URL: http://localhost
>> Port: 8080
>> IP: 0.0.0.0
>> Command: BeagleBone/Black/pru/neopixelDynamic.pru0.c
>> Python: python3
>> Python path:
>> /usr/lib/python3.7/dist-packages:/usr/local/lib/python3.7/dist-packages
>> /var/lib/cloud9/common/Makefile:27:
>> MODEL=TI_AM335x_BeagleBone_Black,TARGET=neopixelDynamic.pru0,COMMON=/var/lib/cloud9/common
>> /var/lib/cloud9/common/Makefile:146:
>> GEN_DIR=/tmp/cloud9-examples,CHIP=am335x,PROC=pru,PRUN=0,PRU_DIR=/dev/remoteproc/pruss-core0,EXE=.out
>> -Stopping PRU 0
>> /bin/sh: 1: cannot create /dev/remoteproc/pruss-core0/state: Directory
>> nonexistent
>> Cannot stop 0
>> CC  neopixelDynamic.pru0.c
>> "/var/lib/cloud9/common/prugpio.h", line 55: warning #1181-D: #warning
>> directive: "Found am335x"
>> LD  /tmp/cloud9-examples/neopixelDynamic.pru0.o
>> -   copying firmware file
>> /tmp/cloud9-examples/neopixelDynamic.pru0.out to
>> /lib/firmware/am335x-pru0-fw
>> write_init_pins.sh
>> writing "pruout" to "/sys/devices/platform/ocp/ocp:P9_31_pinmux/state"
>> -Starting PRU 0
>> /bin/sh: 1: cannot create /dev/remoteproc/pruss-core0/state: Directory
>> nonexistent
>> make: *** [/var/lib/cloud9/common/Makefile:166: start] Error 2
>> rm /tmp/cloud9-examples/neopixelDynamic.pru0.o
>>
>>
>>
>> *debian@beaglebone:/var/lib/cloud9/BeagleBone/Black/pru$ sudo
>> /opt/scripts/tools/version.sh *
>> *[sudo] password for debian: *
>> *git:/opt/scripts/:[ef16ffa8c27225005cc2b2c974a83da3dee6c1ef]*
>> *eeprom:[A335BNLT000C2025BBBG0598]*
>> *model:[TI_AM335x_BeagleBone_Black]*
>> *dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-08-31]*
>> *bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
>> 2019.04-2-gc9b3922522]:[location: dd MBR]*
>> *bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
>> 2019.04-2-gf15b99f0b6]:[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]*
>> *kernel:[4.19.94-ti-r50]*
>> *nodejs:[v10.21.0]*
>> */boot/uEnv.txt Settings:*
>> *uboot_overlay_options:[enable_uboot_overlays=1]*
>> *uboot_overlay_options:[disable_uboot_overlay_video=1]*
>>
>> *uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-RPROC-4-19-TI-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.20200814.0-0~buster+20200814]*
>> *pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~buster+20200813]*
>> *pkg:[kmod]:[26-1]*
>> *pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~buster+20200716]*
>> *pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305]*
>> *groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
>> plugdev users systemd-journal input bluetooth netdev i2c gpio admin spi iio
>> docker tisdk weston-launch xenomai cloud9ide pwm eqep remoteproc]*
>> *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*
>> *[   63.167635] remoteproc remoteproc0: wkup_m3

Re: [beagleboard] Re: config-pin tool doesn't work.

[jonnymo]

If you look at the P2_18 define, do you see a state listed?
Ex:

*debian@beaglebone:~$ ls -lt
/sys/devices/platform/ocp/ocp:P2_18_pinmux/state*
*-rw-rw-r-- 1 root gpio 4096 Oct 19 07:17
/sys/devices/platform/ocp/ocp:P2_18_pinmux/state*


I have no other overlays enabled, so perhaps try removing what you have
enabled and then see if the config-pin tool will work. Perhaps something in
the overlay is over writing the pinmux config:
This is my config:

*debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh*
*[sudo] password for debian:*
*git:/opt/scripts/:[20c080bc91f243ef852a704758788a31083b0f9e]*
*eeprom:[A335PBGL00A21750EPB01280]*
*model:[TI_AM335x_PocketBeagle]*
*dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-08-25]*
*bootloader:[microSD]:[/dev/mmcblk0]:[U-Boot
2019.04-2-gc9b3922522]:[location: dd MBR]*
*UBOOT: Booted Device-Tree:[am335x-pocketbeagle.dts]*
*UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0]*
*UBOOT: Loaded Overlay:[BB-ADC-00A0]*
*kernel:[4.19.94-ti-r51]*
*nodejs:[v10.21.0]*
*/boot/uEnv.txt Settings:*
*uboot_overlay_options:[enable_uboot_overlays=1]*
*uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]*
*uboot_overlay_options:[enable_uboot_cape_universal=1]*
*pkg check: to individually upgrade run: [sudo apt install --only-upgrade
]*


Cheers,

Jon





On Mon, Oct 19, 2020 at 10:12 AM Szabó Benedek Ákos <
szabobenedeka...@gmail.com> wrote:

> Hi Jon!
> I upgraded the kernel to the same version as you have.
> This is the output:
> root@beaglebone:~#
> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q
> P2_18
> P2_18 pinmux file not found!
> Cannot read pinmux file: /sys/devices/platform/ocp/ocp*P2_18_pinmux/state
>
> Still not working. In uEnv.txt file, I have this added:
> uboot_overlay_addr6=/lib/firmware/PB-MCP2515-SPI1.dtbo
> This is the MCP2515 which could read the SWCAN bus if it was set to HIGH.
>
> jonn...@gmail.com a következőt írta (2020. október 19., hétfő, 3:32:13
> UTC+2):
>
>> This is how to set say P2_18 as an output and high.
>>
>> debian@beaglebone:~$*
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q
>> P2.18*
>> *P2_18 Mode: gpio Direction: in Value: 0*
>> debian@beaglebone:~$ 
>> */opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin
>> P2.18 gpio*
>> debian@beaglebone:~$*
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin P2.18
>> out*
>> debian@beaglebone:~$ 
>> */opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin
>> P2.18 hi*
>> debian@beaglebone:~$ 
>> */opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin
>> -q P2.18*
>> *P2_18 Mode: gpio Direction: out Value: 1*
>>
>>
>> I don't think the /usr/bin/config-pin tool can do this.
>>
>> Cheers,
>>
>> Jon
>>
>> On Sun, Oct 18, 2020 at 6:17 PM jonnymo  wrote:
>>
>>> With a PocketBeagle running Debian 10 (Buster) IoT image and kernel
>>> 4.19.94-ti-r51 I see this:
>>>
>>> *debian@beaglebone:~$
>>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q
>>> P2_06*
>>> *P2_06 Mode: default Direction: in Value: 0*
>>> *debian@beaglebone:~$
>>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -i
>>> P2_06*
>>> *Pin name: P2_06*
>>> *Function if no cape loaded: gpio*
>>> *Function if cape loaded: default gpio gpio_pu gpio_pd gpio_input*
>>> *Function information: gpio1_25 default gpio1_25 gpio1_25 gpio1_25
>>> gpio1_25*
>>> *Kernel GPIO id: 57*
>>> *PRU GPIO id: 89*
>>> *debian@beaglebone:~$
>>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -l
>>> P2_06*
>>> *default gpio gpio_pu gpio_pd gpio_input*
>>>
>>> *debian@beaglebone:~$
>>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q
>>> P2_18*
>>> *P2_18 Mode: default Direction: in Value: 0*
>>> *debian@beaglebone:~$
>>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -i
>>> P2_18*
>>> *Pin name: P2_18*
>>> *Function if no cape loaded: gpio*
>>> *Function if cape loaded: default gpio gpio_pu gpio_pd gpio_input qep
>>> pru_ecap pruin*
>>> *Function information: gpio1_15 default gpio1_15 gpio1_15 gpio1_15
>>> gpio1_15 eqep2_strobe pru_ecap pru0_in15*
>>> *Kernel GPIO id: 47*
>>> *PRU GPIO id: 79*
>>> *debian@beaglebone:~$
>>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -l
>>> P2_18*
>>> *default gpio gpio_pu gpio_pd gpio_input qep pru_ecap pruin*
>>>
>>>
>>> *debian@beaglebone:~$ config-pin -q P2_18
>>>  *
>>> *Current mode for P2_18 is: default*
>>>
>>> *debian@beaglebone:~$ config-pin -q P2_06*
>>>
>>> *Current mode for P2_06 is: default*
>>>
>>>
>>> Note, I did do a 'sudo apt-get update' and sudo apt-get upgrade' and
>>> then updated the scripts and such listed in the following Beaglebone
>>> Upgrade link including the 'update_kernel.sh' script.
>>> https://beagleboard.org/upgrade
>>>
>>>
>>> Cheers,
>>>
>>> Jon
>>>
>>> On Sun, Oct 18, 2020 at 5:50 PM Szabó Benedek Ákos <
>>> szaboben.

Re: [beagleboard] Beagle bone black setup with Intel Real sense camera

[jonnymo]

I personally have no experience with the RealSense camera, but I am
interested in this combo as well.

I would suspect the best place to start would be the github location:
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md

There was a post by someone who was setting this up with a BeagleBone so
you could try to track them down:
https://github.com/IntelRealSense/librealsense/issues/3394

This looks like a good resource for info.
https://support.intelrealsense.com/hc/en-us/community/topics

Good luck.

Cheers,

Jon


On Mon, Oct 19, 2020 at 5:18 AM Megha Bhirade 
wrote:

> Hi,
>
> I am using Beagle bone black in Linux Ubuntu platform and i want to use
> Real sense camera for my application.
>
> Please anybody suggest me how to setup the Beagle bone black with Real
> sense Depth and tracking camera??
>
> Please suggest me any related link for step by step setup...
>
> --
> 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/4340e28c-4bb9-4995-95bc-bd2baa009f80o%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/CAG99bkq%2BXoCB1-2H8Rnoz41wEw7G%3DHQHwPAmgyBrjWHjy9ARTw%40mail.gmail.com.

Re: [beagleboard] Re: config-pin tool doesn't work.

[jonnymo]

It looks like P2_18 and P2_06 are being disabled in  PB-MCP2515-SPI1 to
prevent a driver load but I suppose this is by design.

/opt/source/bb.org-overlays/src/arm/PB-MCP2515-SPI1.dts














*fragment@1 {target = <&ocp>;
__overlay__ {P2_25_pinmux { status = "disabled"; };
 /* SPI1 MOSI - gpio1_9 */P2_27_pinmux { status =
"disabled"; };  /* SPI1 MISO - gpio1_8 */
P2_29_pinmux { status = "disabled"; };  /* SPI1 CLK - gpio0_7 */
P2_30_pinmux { status = "disabled"; };  /* SPI1 CS0 - gpio3_17
*/P2_31_pinmux { status = "disabled"; };  /* SPI1
CS1 - gpio0_19 */P2_08_pinmux { status =
"disabled"; };  /* SWC nINT */P2_32_pinmux { status
= "disabled"; };  /* SWC nRESET */P2_06_pinmux {
status = "disabled"; };  /* SWC M0 */P2_18_pinmux {
status = "disabled"; };  /* SWC M1 */};}*

Have you looked at this older issue posting for  PB-MCP2515-SPI1? Perhaps
this will help.
https://gist.github.com/pdp7/e0dcfaca4e478be000987fb0105f2560


Jon

On Mon, Oct 19, 2020 at 11:06 AM jonnymo  wrote:

> If you look at the P2_18 define, do you see a state listed?
> Ex:
>
> *debian@beaglebone:~$ ls -lt
> /sys/devices/platform/ocp/ocp:P2_18_pinmux/state*
> *-rw-rw-r-- 1 root gpio 4096 Oct 19 07:17
> /sys/devices/platform/ocp/ocp:P2_18_pinmux/state*
>
>
> I have no other overlays enabled, so perhaps try removing what you have
> enabled and then see if the config-pin tool will work. Perhaps something in
> the overlay is over writing the pinmux config:
> This is my config:
>
> *debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh*
> *[sudo] password for debian:*
> *git:/opt/scripts/:[20c080bc91f243ef852a704758788a31083b0f9e]*
> *eeprom:[A335PBGL00A21750EPB01280]*
> *model:[TI_AM335x_PocketBeagle]*
> *dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-08-25]*
> *bootloader:[microSD]:[/dev/mmcblk0]:[U-Boot
> 2019.04-2-gc9b3922522]:[location: dd MBR]*
> *UBOOT: Booted Device-Tree:[am335x-pocketbeagle.dts]*
> *UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0]*
> *UBOOT: Loaded Overlay:[BB-ADC-00A0]*
> *kernel:[4.19.94-ti-r51]*
> *nodejs:[v10.21.0]*
> */boot/uEnv.txt Settings:*
> *uboot_overlay_options:[enable_uboot_overlays=1]*
>
> *uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]*
> *uboot_overlay_options:[enable_uboot_cape_universal=1]*
> *pkg check: to individually upgrade run: [sudo apt install --only-upgrade
> ]*
>
>
> Cheers,
>
> Jon
>
>
>
>
>
> On Mon, Oct 19, 2020 at 10:12 AM Szabó Benedek Ákos <
> szabobenedeka...@gmail.com> wrote:
>
>> Hi Jon!
>> I upgraded the kernel to the same version as you have.
>> This is the output:
>> root@beaglebone:~#
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q
>> P2_18
>> P2_18 pinmux file not found!
>> Cannot read pinmux file: /sys/devices/platform/ocp/ocp*P2_18_pinmux/state
>>
>> Still not working. In uEnv.txt file, I have this added:
>> uboot_overlay_addr6=/lib/firmware/PB-MCP2515-SPI1.dtbo
>> This is the MCP2515 which could read the SWCAN bus if it was set to HIGH.
>>
>> jonn...@gmail.com a következőt írta (2020. október 19., hétfő, 3:32:13
>> UTC+2):
>>
>>> This is how to set say P2_18 as an output and high.
>>>
>>> debian@beaglebone:~$*
>>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q
>>> P2.18*
>>> *P2_18 Mode: gpio Direction: in Value: 0*
>>> debian@beaglebone:~$ 
>>> */opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin
>>> P2.18 gpio*
>>> debian@beaglebone:~$*
>>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin P2.18
>>> out*
>>> debian@beaglebone:~$ 
>>> */opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin
>>> P2.18 hi*
>>> debian@beaglebone:~$ 
>>> */opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin
>>> -q P2.18*
>>> *P2_18 Mode: gpio Direction: out Value: 1*
>>>
>>>
>>> I don't think the /usr/bin/config-pin tool can do this.
>>>
>>> Cheers,
>>>
>>> Jon
>>>
>>> On Sun, Oct 18, 2020 at 6:17 PM jonnymo  wrote:
>>>
 With a PocketBeagle running Debian 10 (Buster) IoT image and kernel
 4.19.94-ti-r51 I see this:

 *debian@beaglebone:~$
 /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q
 P2_06*
 *P2_06 Mode: default Direction: in Value: 0*
 *debian@beaglebone:~$
 /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -i
 P2_06*
 *Pin name: P2_06*
 *Function if no cape loaded: gpio*
 *Function if cape loaded: default gpio gpio_pu gpio_pd gpio_input*
 *Function information: gpio1_25 default gpio1_25 gpio1_25 gpio1_25
 gpio1_25*
 *Kernel GPIO id: 57*
 *PRU GPIO id: 89*
 *debian@beaglebone:~$
 /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -l
 P2_06*
 *default gpio g

Re: [beagleboard] Re: Remote access for the beagle bone black (BBB) to modify /upgrade file from cloud server

[Niresh]

Thank you for the information. I remember my ex-colleague used to download
a file from a server using curl utility and run those files. So, I would
like to know any similar simple procedure to download and upgrade BBB
binary files which are stored in the server.


Regards,
NK

On Thu, Oct 15, 2020 at 7:09 PM Tarmo  wrote:

> On Thursday, October 15, 2020 at 8:43:46 AM UTC+3 Niresh wrote:
>
>> Is there a way to access the beagle-bone using SSH or something like that
>> without registering the device to another server?
>>
>
> This is a network setup issue. Any remote access solution requires that a
> network route exist from your computer to the BBB. If you and the BBB are
> in the same local network, it's routable and you can connect to it. If the
> BBB has a public IP address (or port forwarding is set up to it), it's
> routable and you can connect to it. If the BBB is behind a NAT and no port
> forwarding is set up, it's not routable and you cannot connect to it.
>
> Here's where the various tunnelling and VPN solutions come in. You can
> choose one which is best for your requirements, but you cannot get remote
> access to a non-routable device without them.
>
> I've used a simple jumpbox in the form of an SSH server where all the
> different BBB-s connect to. Each opens a remote tunnel on a specific port
> which leads back to it. Eg. port 20013 would have a tunnel to device nr 13,
> port 20014 to nr 14 etc. There's a Debian package called autossh with a
> script which maintains a persistent SSH connection to the jumpbox. This is
> a fairly simple solution to set up and use initially, but not a very good
> one - mainly because it doesn't scale beyond a few dozen devices. I'd go
> for a VPN next time.
>
> --
> Kind regards,
> Tarmo
>
> --
> 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/dMyq5C7HGyw/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/43e35925-e214-450b-8f64-2b0f99b31491n%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/CAF7-PaQ6yfqGxZmw1ooeadgAHdqj-k%3D_zciKAhy9Yo69UDvHBw%40mail.gmail.com.