date:20171220

[beagleboard] Re: Completely disable screensaver

2017-12-20 Thread Beagle Boner

Hey Carl,

thanks for your suggestions. I´m struggeling with the same problem right 
now.
My /boot/uEnv.txt doesnt contain the mmcargs line. Where did you find it?

cheers,

Max

-- 
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/757dc317-cb2e-4e4b-beda-31535e38bbe5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: [beagleboard] Re: Completely disable screensaver

2017-12-20 Thread carl

Hi Max,

 

There are multiple uEnv.txt files the correct file is /uEnv.txt

 

root@TestDevice:~# cat /uEnv.txt

##These are needed to be compliant with Angstrom's 2013.06.20 u-boot.

 

loadaddr=0x8200

fdtaddr=0x8800

rdaddr=0x8808

 

initrd_high=0x

fdt_high=0x

 

##These are needed to be compliant with Debian 2014-05-14 u-boot.

 

loadximage=echo debug: [/boot/vmlinuz-${uname_r}] ... ; load mmc 0:1 
${loadaddr} /boot/vmlinuz-${uname_r}

loadxfdt=echo debug: [/boot/dtbs/${uname_r}/${fdtfile}] ... ;load mmc 0:1 
${fdtaddr} /boot/dtbs/${uname_r}/${fdtfile}

loadxrd=echo debug: [/boot/initrd.img-${uname_r}] ... ; load mmc 0:1 ${rdaddr} 
/boot/initrd.img-${uname_r}; setenv rdsize ${filesize}

loaduEnvtxt=load mmc 0:1 ${loadaddr} /boot/uEnv.txt ; env import -t ${loadaddr} 
${filesize};

check_dtb=if test -n ${dtb}; then setenv fdtfile ${dtb};fi;

loadall=run loaduEnvtxt; run check_dtb; run loadximage; run loadxrd; run 
loadxfdt;

 

mmcargs=setenv bootargs console=tty0 console=${console} consoleblank=0 
${optargs} ${cape_disable} ${cape_enable} root=/dev/mmcblk0p1 
rootfstype=${mmcrootfstype} ${cmdline}

 

uenvcmd=run loadall; run mmcargs; echo debug: [${bootargs}] ... ; echo debug: 
[bootz ${loadaddr} ${rdaddr}:${rdsize} ${fdtaddr}] ... ; bootz ${loadaddr} 
${rdaddr}:${rdsize} ${fdtaddr};

 

root@SensitDisplay:~#

 

Best regards,

Carl

 

 

 

 

Van: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] Namens 
Beagle Boner
Verzonden: Wednesday, 20 December 2017 12:05
Aan: BeagleBoard 
Onderwerp: [beagleboard] Re: Completely disable screensaver

 

Hey Carl,

thanks for your suggestions. I´m struggeling with the same problem right now.
My /boot/uEnv.txt doesnt contain the mmcargs line. Where did you find it?

cheers,

Max

-- 
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/yQZXFejkwt4/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/757dc317-cb2e-4e4b-beda-31535e38bbe5%40googlegroups.com
 

 .
For more options, visit https://groups.google.com/d/optout.

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

[beagleboard] Re: Completely disable screensaver

2017-12-20 Thread Carl Holzmann



Hi Max,

 

There are multiple uEnv.txt files :


root@TestDevice:~# locate uEnv.txt

/boot/uEnv.txt

/nfs-uEnv.txt

/opt/source/u-boot_ti-2016.05/0001-beagle_x15-uEnv.txt-bootz-n-fixes.patch

/opt/source/u-boot_v2017.01-rc3/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch

/opt/source/u-boot_v2017.01-rc3/0001-omap3_beagle-uEnv.txt-bootz-n-fixes.patch

/uEnv.txt

root@TestDevice:~#

The correct file is /uEnv.txt


root@TestDevice:~# cat /uEnv.txt

##These are needed to be compliant with Angstrom's 2013.06.20 u-boot.


loadaddr=0x8200

fdtaddr=0x8800

rdaddr=0x8808


initrd_high=0x

fdt_high=0x


##These are needed to be compliant with Debian 2014-05-14 u-boot.


loadximage=echo debug: [/boot/vmlinuz-${uname_r}] ... ; load mmc 0:1 
${loadaddr} /boot/vmlinuz-${uname_r}

loadxfdt=echo debug: [/boot/dtbs/${uname_r}/${fdtfile}] ... ;load mmc 0:1 
${fdtaddr} /boot/dtbs/${uname_r}/${fdtfile}

loadxrd=echo debug: [/boot/initrd.img-${uname_r}] ... ; load mmc 0:1 
${rdaddr} /boot/initrd.img-${uname_r}; setenv rdsize ${filesize}

loaduEnvtxt=load mmc 0:1 ${loadaddr} /boot/uEnv.txt ; env import -t 
${loadaddr} ${filesize};

check_dtb=if test -n ${dtb}; then setenv fdtfile ${dtb};fi;

loadall=run loaduEnvtxt; run check_dtb; run loadximage; run loadxrd; run 
loadxfdt;


mmcargs=setenv bootargs console=tty0 console=${console} consoleblank=0 
${optargs} ${cape_disable} ${cape_enable} root=/dev/mmcblk0p1 
rootfstype=${mmcrootfstype} ${cmdline}


uenvcmd=run loadall; run mmcargs; echo debug: [${bootargs}] ... ; echo 
debug: [bootz ${loadaddr} ${rdaddr}:${rdsize} ${fdtaddr}] ... ; bootz 
${loadaddr} ${rdaddr}:${rdsize} ${fdtaddr};


root@TestDevice:~# 


 

Best regards,

 Carl



On Wednesday, 20 December 2017 12:05:25 UTC+1, Beagle Boner wrote:
>
> Hey Carl,
>
> thanks for your suggestions. I´m struggeling with the same problem right 
> now.
> My /boot/uEnv.txt doesnt contain the mmcargs line. Where did you find it?
>
> cheers,
>
> Max
>

-- 
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/627bd69f-a655-4b27-afa3-55cbfa10ad52%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Use analogue inputs with 5 or 10 V signal

2017-12-20 Thread mike . maikaefer

Hi,

this is somewhat a noob-question, but my skills in analogue hardware are 
limited.

The BeagleBones (and variants) come with six analogue inputs which each 
have a separate ground line GNDA and also a separate power supply VADC.

My questions here: how can I connect an external signal with 0..5V or 
0..10V to these inputs in order to read their analogue value?

And how about GNDA, has it to be separated from normal GND?

Thanks!

Mike

-- 
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/04be8395-5747-42ad-a6b5-2ef440f6f3f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How to read ADC inputs?

2017-12-20 Thread anthony . schluchin

I was using a BBB (rev C) and able to read analog inputs on it :
- enable ADC : 
/sys/bus/iio/devices$ *ls*
iio_sysfs_trigger
/sys/bus/iio/devices$ *sudo sh -c "echo BB-ADC > $ SLOTS"*

- read value :
/sys/bus/iio/devices$ *ls*
iio:device0 iio_sysfs_trigger
$* cat /sys/bus/iio/devices/iio:device0/in_voltage0_raw*
3831
 
but on the BBB wireless i don't know how!?

-- 
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/594a7125-057b-489e-af9d-14060619a21f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Use analogue inputs with 5 or 10 V signal

2017-12-20 Thread Adam Saenz

You will need to use a voltage divider to lower the detectable voltage of 
your 0-5V or 0-10V inputs to a range of 0-1.8V or less.  Google voltage 
divider to see how this is done; sparkfun provides a pretty nice 
explanation of voltage dividers.  If you look at the schematic, an example 
of a voltage divider is done for AIN7 to read the 3.3V supply voltage.  
AIN7 will see is 1.65V when VDD_3V3B is 3.3V.

ADCs are most accurate when the voltage they are reading is stable and free 
from noise or ripple voltages.  Digital circuits (e.g. the processor cor) 
are sources of digital noise so a separate VADC and GNDA are provided to 
minimize the influence of noisy digital sources.   If you look on the 
schematic VDD_ADC is actually connected to VDD_1V8 through a ferrite bead 
(inductor). The ferrite bead is there to block high frequency noise caused 
by the digital circuits, while allowing DC voltages to pass; so VDD_ADC is 
actually connected to 1.8V.  The AM3358 datasheet lists the max voltage 
input of VDD_ADC as 2.1V so you cannot connect a 5V or 10V reference 
directly to it.  It's best to use the existing 1.8V reference and scale the 
analog input voltages you want to measure so they are less than 1.8V.

Adam

On Wednesday, December 20, 2017 at 4:46:11 AM UTC-8, mike.ma...@gmail.com 
wrote:
>
> Hi,
>
> this is somewhat a noob-question, but my skills in analogue hardware are 
> limited.
>
> The BeagleBones (and variants) come with six analogue inputs which each 
> have a separate ground line GNDA and also a separate power supply VADC.
>
> My questions here: how can I connect an external signal with 0..5V or 
> 0..10V to these inputs in order to read their analogue value?
>
> And how about GNDA, has it to be separated from normal GND?
>
> Thanks!
>
> Mike
>
>

-- 
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/4f3a7e4d-eceb-47bb-9be7-7e04ee1997b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Use analogue inputs with 5 or 10 V signal

2017-12-20 Thread Adam Saenz

Forgot to add that you should use the GNDA as the ground reference to your 
external analog input sources.

Adam

On Wednesday, December 20, 2017 at 6:57:26 AM UTC-8, Adam Saenz wrote:
>
> You will need to use a voltage divider to lower the detectable voltage of 
> your 0-5V or 0-10V inputs to a range of 0-1.8V or less.  Google voltage 
> divider to see how this is done; sparkfun provides a pretty nice 
> explanation of voltage dividers.  If you look at the schematic, an example 
> of a voltage divider is done for AIN7 to read the 3.3V supply voltage.  
> AIN7 will see is 1.65V when VDD_3V3B is 3.3V.
>
> ADCs are most accurate when the voltage they are reading is stable and 
> free from noise or ripple voltages.  Digital circuits (e.g. the processor 
> cor) are sources of digital noise so a separate VADC and GNDA are provided 
> to minimize the influence of noisy digital sources.   If you look on the 
> schematic VDD_ADC is actually connected to VDD_1V8 through a ferrite bead 
> (inductor). The ferrite bead is there to block high frequency noise caused 
> by the digital circuits, while allowing DC voltages to pass; so VDD_ADC is 
> actually connected to 1.8V.  The AM3358 datasheet lists the max voltage 
> input of VDD_ADC as 2.1V so you cannot connect a 5V or 10V reference 
> directly to it.  It's best to use the existing 1.8V reference and scale the 
> analog input voltages you want to measure so they are less than 1.8V.
>
> Adam
>
>
> On Wednesday, December 20, 2017 at 4:46:11 AM UTC-8, mike.ma...@gmail.com 
> wrote:
>>
>> Hi,
>>
>> this is somewhat a noob-question, but my skills in analogue hardware are 
>> limited.
>>
>> The BeagleBones (and variants) come with six analogue inputs which each 
>> have a separate ground line GNDA and also a separate power supply VADC.
>>
>> My questions here: how can I connect an external signal with 0..5V or 
>> 0..10V to these inputs in order to read their analogue value?
>>
>> And how about GNDA, has it to be separated from normal GND?
>>
>> Thanks!
>>
>> Mike
>>
>>

-- 
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/8c75e48e-a7b2-449c-ab8b-d02307d53370%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] cannot enable pru pins (uBoot/cape/pinmux mismatch issue?)

2017-12-20 Thread ags

I've been building a prototype using the uio_pruss driver and one "test" 
pin (P9_27) which was easily allocated using config-pin.
I'm now trying to complete the prototype and need to enable a total of 8 
PRU pins (pr1_pru0_pru_r30_[0-7]). I am unable to enable most of these pins:

debian@BBB:~$ uname -r
4.4.30-ti-r64

debian@BBB:~$ config-pin -a p9_29 pruout

P9_29 pinmux file not found!

P9_29 overlay not found

Loading cape-universala overlay

bash: line 0: echo: write error: File exists

Error loading device tree overlay file: cape-universala
 

After searching I found 
this: https://github.com/cdsteinkuehler/beaglebone-universal-io/issues/43

recommending updating overlays ("things have changed")...

So I went here: https://github.com/beagleboard/bb.org-overlays

and did this:


debian@BBB:~$ sudo apt update ; sudo apt install bb-cape-overlays


debian@BBB:~$ apt show bb-cape-overlays

Package: bb-cape-overlays

Version: 4.4.20171215.0-0rcnee1~jessie+20171215

Maintainer: Robert Nelson 

Installed-Size: 2,003 kB

Depends: device-tree-compiler

Priority: extra

Section: misc

Download-Size: 59.5 kB

APT-Manual-Installed: yes

APT-Sources: http://repos.rcn-ee.com/debian/ jessie/main armhf Packages

Description: Device tree overlays for Beaglebone.

 Device tree overlays for Beaglebone /lib/firmware/


But now have a new problem:


debian@BBB:~$ config-pin p9_29 pruout

bash: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state: No such file or 
directory

Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state

debian@BBBr0C0-1:~/node$ config-pin -a p9_29 pruout

bash: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state: No such file or 
directory

Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state


I did read about moving away from kernel overlays to uBoot overlays 
here: https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

but am no closer to a solution. I am now under time pressure and prefer to 
make minimal changes to my system. Can anyone help with suggestions to work 
around this?

-- 
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/9e3bdb6f-a378-4fe9-8e60-23f6b5ba0c29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] cannot enable pru pins (uBoot/cape/pinmux mismatch issue?)

2017-12-20 Thread Robert Nelson

On Wed, Dec 20, 2017 at 3:33 PM, ags  wrote:
> I've been building a prototype using the uio_pruss driver and one "test" pin
> (P9_27) which was easily allocated using config-pin.
> I'm now trying to complete the prototype and need to enable a total of 8 PRU
> pins (pr1_pru0_pru_r30_[0-7]). I am unable to enable most of these pins:
>
> debian@BBB:~$ uname -r
> 4.4.30-ti-r64
>
> debian@BBB:~$ config-pin -a p9_29 pruout
>
> P9_29 pinmux file not found!
>
> P9_29 overlay not found
>
> Loading cape-universala overlay
>
> bash: line 0: echo: write error: File exists
>
> Error loading device tree overlay file: cape-universala
>
>
>
> After searching I found this:
> https://github.com/cdsteinkuehler/beaglebone-universal-io/issues/43
>
> recommending updating overlays ("things have changed")...
>
> So I went here: https://github.com/beagleboard/bb.org-overlays
>
> and did this:
>
>
> debian@BBB:~$ sudo apt update ; sudo apt install bb-cape-overlays
>
>
> debian@BBB:~$ apt show bb-cape-overlays
>
> Package: bb-cape-overlays
>
> Version: 4.4.20171215.0-0rcnee1~jessie+20171215
>
> Maintainer: Robert Nelson 
>
> Installed-Size: 2,003 kB
>
> Depends: device-tree-compiler
>
> Priority: extra
>
> Section: misc
>
> Download-Size: 59.5 kB
>
> APT-Manual-Installed: yes
>
> APT-Sources: http://repos.rcn-ee.com/debian/ jessie/main armhf Packages
>
> Description: Device tree overlays for Beaglebone.
>
>  Device tree overlays for Beaglebone /lib/firmware/
>
>
> But now have a new problem:
>
>
> debian@BBB:~$ config-pin p9_29 pruout
>
> bash: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state: No such file or
> directory
>
> Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state
>
> debian@BBBr0C0-1:~/node$ config-pin -a p9_29 pruout
>
> bash: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state: No such file or
> directory
>
> Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state
>
>
> I did read about moving away from kernel overlays to uBoot overlays here:
> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
>
> but am no closer to a solution. I am now under time pressure and prefer to
> make minimal changes to my system. Can anyone help with suggestions to work
> around this?

The package "bb-cape-overlays" needs to stay in sync with the kernel.
(Since config-pin does not auto-generate the pin options.)

Your going to need to update the kernel:

4.4.30-ti-r64 -> 4.4.91-ti-r140

Switch to u-boot overlays, with these options in /boot/uEnv.txt


enable_uboot_overlays=1
disable_uboot_overlay_audio=1
uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo
enable_uboot_cape_universal=1

if you run into any issues with settting up ^

Just run:

sudo /opt/scripts/tools/version.sh

then we can debug it..

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/CAOCHtYjM%2Bn2T_6kpVKRdjNX-ykWzwxzN%3DMZ36gGqzSSGH1-C9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: cannot enable pru pins (uBoot/cape/pinmux mismatch issue?)

2017-12-20 Thread ags

Thank you Robert. In the long term I will certainly do as you suggest. Is 
there no way to "downgrade" or use an overlay for pin configuration that is 
in sync with my current (4.4.30) kernel version?

If that is not possible, will the 4.4.91 version you recommend support 
uio_pruss? I will have to review my notes, but my recollection is the 
remoteproc/uio driver debate was raging when I decided on this route, and 
it took some effort for me to figure out how to make it work.

Finally, if I must move to 4.4.91, would you kindly state how I can 
accomplish this with all pinmux/helper/config/overlay items also being 
synced without disrupting uio_pruss?
I presume this:

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh
sudo reboot


will result in the latest kernel version (4.9.x??) which is not what I 
want...

On Wednesday, December 20, 2017 at 1:33:46 PM UTC-8, ags wrote:
>
> I've been building a prototype using the uio_pruss driver and one "test" 
> pin (P9_27) which was easily allocated using config-pin.
> I'm now trying to complete the prototype and need to enable a total of 8 
> PRU pins (pr1_pru0_pru_r30_[0-7]). I am unable to enable most of these pins:
>
> debian@BBB:~$ uname -r
> 4.4.30-ti-r64
>
> debian@BBB:~$ config-pin -a p9_29 pruout
>
> P9_29 pinmux file not found!
>
> P9_29 overlay not found
>
> Loading cape-universala overlay
>
> bash: line 0: echo: write error: File exists
>
> Error loading device tree overlay file: cape-universala
>  
>
> After searching I found this: 
> https://github.com/cdsteinkuehler/beaglebone-universal-io/issues/43
>
> recommending updating overlays ("things have changed")...
>
> So I went here: https://github.com/beagleboard/bb.org-overlays
>
> and did this:
>
>
> debian@BBB:~$ sudo apt update ; sudo apt install bb-cape-overlays
>
>
> debian@BBB:~$ apt show bb-cape-overlays
>
> Package: bb-cape-overlays
>
> Version: 4.4.20171215.0-0rcnee1~jessie+20171215
>
> Maintainer: Robert Nelson 
>
> Installed-Size: 2,003 kB
>
> Depends: device-tree-compiler
>
> Priority: extra
>
> Section: misc
>
> Download-Size: 59.5 kB
>
> APT-Manual-Installed: yes
>
> APT-Sources: http://repos.rcn-ee.com/debian/ jessie/main armhf Packages
>
> Description: Device tree overlays for Beaglebone.
>
>  Device tree overlays for Beaglebone /lib/firmware/
>
>
> But now have a new problem:
>
>
> debian@BBB:~$ config-pin p9_29 pruout
>
> bash: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state: No such file or 
> directory
>
> Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state
>
> debian@BBBr0C0-1:~/node$ config-pin -a p9_29 pruout
>
> bash: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state: No such file or 
> directory
>
> Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state
>
>
> I did read about moving away from kernel overlays to uBoot overlays here: 
> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
>
> but am no closer to a solution. I am now under time pressure and prefer to 
> make minimal changes to my system. Can anyone help with suggestions to work 
> around this?
>

-- 
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/ef4d04f4-ec1d-4bca-81c2-1777e0d42338%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: cannot enable pru pins (uBoot/cape/pinmux mismatch issue?)

2017-12-20 Thread Robert Nelson

On Wed, Dec 20, 2017 at 4:29 PM, ags  wrote:
> Thank you Robert. In the long term I will certainly do as you suggest. Is
> there no way to "downgrade" or use an overlay for pin configuration that is
> in sync with my current (4.4.30) kernel version?

Yes, source is available:

https://github.com/beagleboard/bb.org-overlays

>
> If that is not possible, will the 4.4.91 version you recommend support
> uio_pruss? I will have to review my notes, but my recollection is the
> remoteproc/uio driver debate was raging when I decided on this route, and it
> took some effort for me to figure out how to make it work.

You said you were using uio_pruss, so i gave you specific directions
for uio_pruss with v4.4.x-ti. ;)

>
> Finally, if I must move to 4.4.91, would you kindly state how I can
> accomplish this with all pinmux/helper/config/overlay items also being
> synced without disrupting uio_pruss?
> I presume this:
>
> cd /opt/scripts/tools/
> git pull
> sudo ./update_kernel.sh
> sudo reboot
>
>
> will result in the latest kernel version (4.9.x??) which is not what I
> want...

Nope, if you have v4.4.x-ti installed, that ^ will install the latest
v4.4.x-ti..

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/CAOCHtYghPJfqA-PXW3ftzp_jEwA%2B_QkP6hTGDr433aJ1%2BP1Euw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Measure frequency of a square wave input without PRU?

2017-12-20 Thread thomaslolson63

As far as I can tell there is no support in the Debian kernel for the eCAP 
feature.  You can use eCAP to output a PWM signal but I can't find anything 
that supports the eCAP capture feature.

On Tuesday, November 28, 2017 at 8:44:53 AM UTC-6, Jason Kridner wrote:
>
>
>
> On Nov 28, 2017, at 12:50 AM, Drew Fustini  > wrote:
>
> Any suggestion on how to measure the frequency of a square wave input?
>
>  Signal would be 3kHz or less.  The goal is to use the appropriate AM3358 
> peripherals from the ARM core, not the PRU.
>
> The eCAP peripheral comes to mind but I'm not sure it that would be 
> appropriate for this use case.
>
>
> If you know it is a square wave input, the eCAP pulse counting would work 
> well. 
>
>
>
> For reference, the question comes from this github issue:
>
> https://github.com/adafruit/adafruit-beaglebone-io-python/issues/204#issuecomment-347415768
>
> -- 
> 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/5045e3af-ac56-4d54-9cd2-2188059b55d8%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>

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

Re: [beagleboard] Measure frequency of a square wave input without PRU?

2017-12-20 Thread thomaslolson63

I wrote a C program that uses inotify to watch the gpioxx/value file.  It 
can see changes up to 20kHz, so 3kHz should be no problem at all.

On Tuesday, November 28, 2017 at 8:44:53 AM UTC-6, Jason Kridner wrote:
>
>
>
> On Nov 28, 2017, at 12:50 AM, Drew Fustini  > wrote:
>
> Any suggestion on how to measure the frequency of a square wave input?
>
>  Signal would be 3kHz or less.  The goal is to use the appropriate AM3358 
> peripherals from the ARM core, not the PRU.
>
> The eCAP peripheral comes to mind but I'm not sure it that would be 
> appropriate for this use case.
>
>
> If you know it is a square wave input, the eCAP pulse counting would work 
> well. 
>
>
>
> For reference, the question comes from this github issue:
>
> https://github.com/adafruit/adafruit-beaglebone-io-python/issues/204#issuecomment-347415768
>
> -- 
> 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/5045e3af-ac56-4d54-9cd2-2188059b55d8%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>

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

[beagleboard] problem getting u-boot to read uEnv.txt in sdcard

2017-12-20 Thread onio

HI All,

I have built custom zImage and am335-boneblack.dtb file together with 
u-boot and its associated files.
The problem I am having is getting u-boot to automatically boot Linux 
kernel image from SD Card using the uEnv.txt file. I have partitioned my SD 
card into 2 part, first partition contains FAT partition while the second 
is an ext4 . The first partition contains the following files

   1. u-boot.img
   2. MLO
   3. zImage
   4. am335x-boneblack.dtb
   5. uEnv.txt 

I am not currently using the second partition as I am using nfs for the 
root files system. The problem is that when I halt the u-boot boot process 
and it drop to the "u-boot command prompt". l can enter the flowing 
commands manually 

   - setenv serverip 192.168.1.100
   - setenv ipaddr 192.168.1.101
   - setenv npath /home/onio/rootfs
   - setenv bootargs console=ttyO0,115200 root=/dev/nfs rw 
   nfsroot=${serverip}:${npath} ip=${ipaddr}
   - saveenv
   - fatload mmc 0:1 0x8020 zImage
   - fatload mmc 0:1 0x80f0 am335x-boneblack.dtb
   - bootz 0x8020 - 0x80f0
   

*The "serverip" is the IP address of my development PC and ipaddr is the IP 
address of the beaglebone black. The root file system is located in the 
following path /home/myuser/rootfs on the development PC.*

As previously mentioned I can enter the above commands at the u-boot prompt 
and the board would boot to Linux command prompt. I want to avoid the 
process of entering this data manually and get u-boot to do the loading and 
booting of the board using the u-env.txt file. If my understanding is 
correct u-boot should be able to perform this process automatically. 

Many thanks in advance.

Regards

onio

-- 
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/df1c8168-554e-406b-abbb-609da1dcedbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Completely disable screensaver

RE: [beagleboard] Re: Completely disable screensaver

[beagleboard] Re: Completely disable screensaver

[beagleboard] Use analogue inputs with 5 or 10 V signal

[beagleboard] How to read ADC inputs?

[beagleboard] Re: Use analogue inputs with 5 or 10 V signal

[beagleboard] Re: Use analogue inputs with 5 or 10 V signal

[beagleboard] cannot enable pru pins (uBoot/cape/pinmux mismatch issue?)

Re: [beagleboard] cannot enable pru pins (uBoot/cape/pinmux mismatch issue?)

[beagleboard] Re: cannot enable pru pins (uBoot/cape/pinmux mismatch issue?)

Re: [beagleboard] Re: cannot enable pru pins (uBoot/cape/pinmux mismatch issue?)

Re: [beagleboard] Measure frequency of a square wave input without PRU?

Re: [beagleboard] Measure frequency of a square wave input without PRU?

[beagleboard] problem getting u-boot to read uEnv.txt in sdcard

14 matches

Site Navigation

Mail list logo

Footer information