date:20170529

Re: [beagleboard] Re: Serial Debug Header access query

2017-05-29 Thread William Hermans

Graham, that wont fix the issue. The problem he's having is because the OS(
Linux ) is not setup to use the serial interface. You can tell, because he
is getting serial messages from the kernel until after the kernel is
loaded. Which means the rootfs is meant to "take over" but isn't.

On Mon, May 29, 2017 at 4:46 PM, Graham  wrote:

> Peter:
>
> Edit the line in /boot/uEnv.txt
>
> cmdline=coherent_pool=1M net.ifnames=0 quiet cape_universal=enable
>
> to remove the work 'quiet'
>
> --- Graham
>
> ==
>
>
> On Monday, May 29, 2017 at 4:35:24 PM UTC-5, Peter Lawler wrote:
>
>> Hi!
>> Just wondering if something's changed recently in the way the Serial
>> Debug Header operates?
>>
>> I'm asking because I've grabbed the recent release, updated to stretch,
>> and OK yes sure added a couple of what I'd call 'basic' things in -
>> nothing too major - but now I don't get access via the Serial Debug
>> Header. All output looks normal on boot and I can't see anything in
>> particular standing out in the boot log, either.
>>
>> It may well be that I'm missing sufficient amounts of coffee. But any
>> thoughts/comments appreciated at this stage.
>>
>> Cheers,
>>
>> Pete.
>>
>>
>> Output on Serial Debug:
>>
>> U-Boot SPL 2017.03-2-gd12b1519b4 (Mar 14 2017 - 10:28:26)
>> Trying to boot from MMC2
>>
>>
>> U-Boot 2017.03-2-gd12b1519b4 (Mar 14 2017 - 10:28:26 -0500), Build:
>> jenkins-github_Bootloader-Builder-532
>>
>> CPU  : AM335X-GP rev 2.1
>> I2C:   ready
>> DRAM:  512 MiB
>> Reset Source: Power-on reset has occurred.
>> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
>> Using default environment
>>
>>  not set. Validating first E-fuse MAC
>> BeagleBone Black:
>> BeagleBone: cape eeprom: i2c_probe: 0x54:
>> BeagleBone: cape eeprom: i2c_probe: 0x55:
>> BeagleBone: cape eeprom: i2c_probe: 0x56:
>> BeagleBone: cape eeprom: i2c_probe: 0x57:
>> Net:   eth0: MII MODE
>> cpsw
>> Press SPACE to abort autoboot in 2 seconds
>> board_name=[A335BNLT] ...
>> board_rev=[00A5] ...
>> switch to partitions #0, OK
>> mmc0 is current device
>> SD/MMC found on device 0
>> ** Bad device 0:2 0x8200 **
>> ** Bad device 0:2 0x8200 **
>> switch to partitions #0, OK
>> mmc0 is current device
>> Scanning mmc 0:1...
>> gpio: pin 56 (gpio 56) value is 0
>> gpio: pin 55 (gpio 55) value is 0
>> gpio: pin 54 (gpio 54) value is 0
>> gpio: pin 53 (gpio 53) value is 1
>> switch to partitions #0, OK
>> mmc0 is current device
>> gpio: pin 54 (gpio 54) value is 1
>> Checking for: /uEnv.txt ...
>> Checking for: /boot.scr ...
>> Checking for: /boot/boot.scr ...
>> Checking for: /boot/uEnv.txt ...
>> gpio: pin 55 (gpio 55) value is 1
>> 1972 bytes read in 42 ms (44.9 KiB/s)
>> Loaded environment from /boot/uEnv.txt
>> Checking if uname_r is set in /boot/uEnv.txt...
>> gpio: pin 56 (gpio 56) value is 1
>> Running uname_boot ...
>> loading /boot/vmlinuz-4.4.68-ti-r106 ...
>> 8608104 bytes read in 590 ms (13.9 MiB/s)
>> loading /boot/dtbs/4.4.68-ti-r106/am335x-boneblack.dtb ...
>> 56827 bytes read in 88 ms (629.9 KiB/s)
>> uboot_overlays: add [enable_uboot_overlays=1] to /boot/uEnv.txt to
>> enable...
>> loading /boot/initrd.img-4.4.68-ti-r106 ...
>> 5940425 bytes read in 424 ms (13.4 MiB/s)
>> debug: [console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4
>> rootwait coherent_pool=1M net.ifnames=0 quiet cape_universal=enable] ...
>> debug: [bootz 0x8200 0x8808:5aa4c9 0x8800] ...
>> ## Flattened Device Tree blob at 8800
>> Booting using the fdt blob at 0x8800
>> Loading Ramdisk to 8fa55000, end 84c9 ... OK
>> Loading Device Tree to 8fa44000, end 8fa54dfa ... OK
>>
>> Starting kernel ...
>>
>> [0.001026] clocksource_probe: no matching clocksources found
>> [2.109460] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc
>> handle
>> [2.291426] omap_voltage_late_init: Voltage driver support not added
>> [2.299156] PM: Cannot get wkup_m3_ipc handle
>> rootfs: clean, 112476/959616 files, 663500/3888512 blocks
>>
>> Debian GNU/Linux 9 beaglebone ttyS0
>> beaglebone login:
>>
>> ---
>>
>> dmesg
>>
>> [0.00] Booting Linux on physical CPU 0x0
>> [0.00] Initializing cgroup subsys cpuset
>> [0.00] Initializing cgroup subsys cpu
>> [0.00] Initializing cgroup subsys cpuacct
>> [0.00] Linux version 4.4.68-ti-r106 (root@b1-omap5-uevm-2gb)
>> (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Sat May 27
>> 15:52:44 UTC 2017
>> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7),
>> cr=10c5387d
>> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
>> instruction cache
>> [0.00] Machine model: TI AM335x BeagleBone Black
>> [0.00] cma: Reserved 48 MiB at 0x9c80
>> [0.00] Memory policy: Data cache writeback
>> [0.00] On node 0 totalpages: 130560
>> [0.00] free_area_init_node: node 0, pgdat c1059200, node_mem_map
>> df961000
>> [0.00]   Normal

[beagleboard] Re: Windows 10 Bone_D64.exe Failing

2017-05-29 Thread moremohr

Thanks! Worked for me.

On Friday, March 24, 2017 at 9:11:27 PM UTC-7, spstr...@gmail.com wrote:
>
> Hi,
> I was having this issue on a windows 10 machine. When I went to install 
> the software that was on the BBB the windows popup was yellow asking if I 
> wanted to install from an unknown publisher. I tried the suggestions listed 
> here and they didn't work. I then went to 
> http://beagleboard.org/static/beaglebone/latest/README.htm and downloaded 
> the driver from there. When I ran that it listed it was from a verified 
> publisher and the installation worked properly. At that point I was also 
> able to access the BBB through the ip address. Hope this works for 
> everybody else finding their way to this page.
>
>
> On Wednesday, August 12, 2015 at 8:13:13 PM UTC-7, mscleavite wrote:
>>
>> I have just upgraded to Windows 10 on a machine that I have not 
>> previously connected my BBB to.  I had success on other windows 8 machines 
>> as well as SSHing using Putty.  I have spent SOME time searching forums and 
>> not finding much at all on Windows 10.  During the install of the 
>> Bone_D64.exe, the driver the status returned on all the drivers is "Install 
>> Failed".  Let the flaming begin.  Or hopefully there is someone out 
>> there that has encountered and concurred 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/5d575af8-2dd7-4851-885e-0c0e57d4b6fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] help pru allocating 320mb

2017-05-29 Thread catmona

I tried modprobe uio_pruss extram_pool_sz=0x1400 but get an error. My 
ultimate goal is to use the PRU to acquire data and store it inside a 
memory ring buffer.

For now I am just copying the data from the small memory to a bigger 
location in memory, but sometimes it is slow. How do I manage 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/c1dbc31a-73c0-42ae-914e-ed7443a1d958%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Multiple USB Cameras on BBB

2017-05-29 Thread Robert Nelson

On Mon, May 29, 2017 at 8:00 PM, Mujin  wrote:
> We have been struggling to get more than one USB based board camera
> functioning simultaneously,
> We have an external Powered USB hub with the cameras hooked to it.
> We can use each of the cameras one at a time but cannot have them all
> streaming so we can switch between them quickly.
> This same code base functions as expected on the RPi
>
> We are getting the error
> "Error: CAMERA ERROR [VIDIOC_STREAMON] 28 No space left on device"

This means there is not enough USB bandwidth for the additional device.

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/CAOCHtYhB0AeHGuRf%3DgCWYbd6jnvJGL9qu8gixi%2B5L%2BGmSVf00w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] setting Beagle Bone pinmux directly

2017-05-29 Thread Greg

The kernel is doing what a kernel does, manager of the resources!
Try this in a terminal:

config-pin -h

Here's an example usage:

config-pin P9.14 low_pd

That set header pin P9.14 to a GPIO direction output and set to LOW and 
with pull-down resistor.
It works great!

Use this extremely useful spreadsheet for reference:
https://github.com/selsinork/beaglebone-black-pinmux

The file is pinmux.ods.

Regards,
Greg

-- 
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/8caf20fa-47d3-49c8-8bb8-4e6e26bcf7ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Multiple USB Cameras on BBB

2017-05-29 Thread Mujin

We have been struggling to get more than one USB based board camera 
functioning simultaneously, 
We have an external Powered USB hub with the cameras hooked to it. 
We can use each of the cameras one at a time but cannot have them all 
streaming so we can switch between them quickly. 
This same code base functions as expected on the RPi  

We are getting the error 
"Error: CAMERA ERROR [VIDIOC_STREAMON] 28 No space left on device"



The Cameras are 
https://www.amazon.com/gp/product/B00VFQK1Q6/ref=oh_aui_detailpage_o01_s00?ie=UTF8=1

-- 
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/48537644-d495-428c-83ae-3f34b6bdc4c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Serial Debug Header access query

2017-05-29 Thread Graham

Peter:

Edit the line in /boot/uEnv.txt

cmdline=coherent_pool=1M net.ifnames=0 quiet cape_universal=enable

to remove the work 'quiet'

--- Graham

==

On Monday, May 29, 2017 at 4:35:24 PM UTC-5, Peter Lawler wrote:
>
> Hi! 
> Just wondering if something's changed recently in the way the Serial 
> Debug Header operates? 
>
> I'm asking because I've grabbed the recent release, updated to stretch, 
> and OK yes sure added a couple of what I'd call 'basic' things in - 
> nothing too major - but now I don't get access via the Serial Debug 
> Header. All output looks normal on boot and I can't see anything in 
> particular standing out in the boot log, either. 
>
> It may well be that I'm missing sufficient amounts of coffee. But any 
> thoughts/comments appreciated at this stage. 
>
> Cheers, 
>
> Pete. 
>
>
> Output on Serial Debug: 
>
> U-Boot SPL 2017.03-2-gd12b1519b4 (Mar 14 2017 - 10:28:26) 
> Trying to boot from MMC2 
>
>
> U-Boot 2017.03-2-gd12b1519b4 (Mar 14 2017 - 10:28:26 -0500), Build: 
> jenkins-github_Bootloader-Builder-532 
>
> CPU  : AM335X-GP rev 2.1 
> I2C:   ready 
> DRAM:  512 MiB 
> Reset Source: Power-on reset has occurred. 
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1 
> Using default environment 
>
>  not set. Validating first E-fuse MAC 
> BeagleBone Black: 
> BeagleBone: cape eeprom: i2c_probe: 0x54: 
> BeagleBone: cape eeprom: i2c_probe: 0x55: 
> BeagleBone: cape eeprom: i2c_probe: 0x56: 
> BeagleBone: cape eeprom: i2c_probe: 0x57: 
> Net:   eth0: MII MODE 
> cpsw 
> Press SPACE to abort autoboot in 2 seconds 
> board_name=[A335BNLT] ... 
> board_rev=[00A5] ... 
> switch to partitions #0, OK 
> mmc0 is current device 
> SD/MMC found on device 0 
> ** Bad device 0:2 0x8200 ** 
> ** Bad device 0:2 0x8200 ** 
> switch to partitions #0, OK 
> mmc0 is current device 
> Scanning mmc 0:1... 
> gpio: pin 56 (gpio 56) value is 0 
> gpio: pin 55 (gpio 55) value is 0 
> gpio: pin 54 (gpio 54) value is 0 
> gpio: pin 53 (gpio 53) value is 1 
> switch to partitions #0, OK 
> mmc0 is current device 
> gpio: pin 54 (gpio 54) value is 1 
> Checking for: /uEnv.txt ... 
> Checking for: /boot.scr ... 
> Checking for: /boot/boot.scr ... 
> Checking for: /boot/uEnv.txt ... 
> gpio: pin 55 (gpio 55) value is 1 
> 1972 bytes read in 42 ms (44.9 KiB/s) 
> Loaded environment from /boot/uEnv.txt 
> Checking if uname_r is set in /boot/uEnv.txt... 
> gpio: pin 56 (gpio 56) value is 1 
> Running uname_boot ... 
> loading /boot/vmlinuz-4.4.68-ti-r106 ... 
> 8608104 bytes read in 590 ms (13.9 MiB/s) 
> loading /boot/dtbs/4.4.68-ti-r106/am335x-boneblack.dtb ... 
> 56827 bytes read in 88 ms (629.9 KiB/s) 
> uboot_overlays: add [enable_uboot_overlays=1] to /boot/uEnv.txt to 
> enable... 
> loading /boot/initrd.img-4.4.68-ti-r106 ... 
> 5940425 bytes read in 424 ms (13.4 MiB/s) 
> debug: [console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 
> rootwait coherent_pool=1M net.ifnames=0 quiet cape_universal=enable] ... 
> debug: [bootz 0x8200 0x8808:5aa4c9 0x8800] ... 
> ## Flattened Device Tree blob at 8800 
> Booting using the fdt blob at 0x8800 
> Loading Ramdisk to 8fa55000, end 84c9 ... OK 
> Loading Device Tree to 8fa44000, end 8fa54dfa ... OK 
>
> Starting kernel ... 
>
> [0.001026] clocksource_probe: no matching clocksources found 
> [2.109460] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc 
> handle 
> [2.291426] omap_voltage_late_init: Voltage driver support not added 
> [2.299156] PM: Cannot get wkup_m3_ipc handle 
> rootfs: clean, 112476/959616 files, 663500/3888512 blocks 
>
> Debian GNU/Linux 9 beaglebone ttyS0 
> beaglebone login: 
>
> --- 
>
> dmesg 
>
> [0.00] Booting Linux on physical CPU 0x0 
> [0.00] Initializing cgroup subsys cpuset 
> [0.00] Initializing cgroup subsys cpu 
> [0.00] Initializing cgroup subsys cpuacct 
> [0.00] Linux version 4.4.68-ti-r106 (root@b1-omap5-uevm-2gb) 
> (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Sat May 27 
> 15:52:44 UTC 2017 
> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), 
> cr=10c5387d 
> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
> instruction cache 
> [0.00] Machine model: TI AM335x BeagleBone Black 
> [0.00] cma: Reserved 48 MiB at 0x9c80 
> [0.00] Memory policy: Data cache writeback 
> [0.00] On node 0 totalpages: 130560 
> [0.00] free_area_init_node: node 0, pgdat c1059200, node_mem_map 
> df961000 
> [0.00]   Normal zone: 1152 pages used for memmap 
> [0.00]   Normal zone: 0 pages reserved 
> [0.00]   Normal zone: 130560 pages, LIFO batch:31 
> [0.00] CPU: All CPU(s) started in SVC mode. 
> [0.00] AM335X ES2.1 (sgx neon ) 
> [0.00] PERCPU: Embedded 13 pages/cpu @df92 s24268 r8192 
> d20788 u53248 
> [0.00] pcpu-alloc: s24268 r8192 d20788 u53248

[beagleboard] Re: how delete or uninstall a software

2017-05-29 Thread Greg

Hi Eduardo-

The operating systems are based on Debian:

http://www.debian.org/

The manual for the apt system for installing/uninstalling software:

https://www.debian.org/doc/manuals/debian-handbook/sect.apt-get.en.html

This manual is very detailed, and probably more than you need.
If you do a few searches on Debian, you can find numerous help guides.
The most common command executed in a terminal is

sudo apt-get install (name of software package)

Regards,
Greg

-- 
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/b00774e3-4b19-4fc7-9b15-ad7382446d27%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Serial Debug Header access query

2017-05-29 Thread Peter Lawler

Thanks for that, Robert. On my way to second job. Will check it out when I
get back to the desk in about 6 hours.

On 30 May 2017 08:31, "Robert Nelson"  wrote:

Hi Peter,





systemd should trigger on:

debug: [console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4
rootwait coherent_pool=1M net.ifnames=0 quiet cape_universal=enable]
...

and setup a serial login console...

do you have this udev rule installed?

https://github.com/rcn-ee/repos/blob/master/bb-customizations/suite/jessie/
debian/60-omap-tty.rules

-- 
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/CAG73kvW5z4i1O%3DccPzYGBFS5QLD7NxoOU%2BA%2BrHh%3DOPiKAY7V2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Serial Debug Header access query

2017-05-29 Thread Robert Nelson

Hi Peter,

On Mon, May 29, 2017 at 4:35 PM, Peter Lawler  wrote:
> Hi!
> Just wondering if something's changed recently in the way the Serial Debug
> Header operates?

There shouldn't be anything that changed that. I use the hardware
serial debug interface on a daily basis..

>
> I'm asking because I've grabbed the recent release, updated to stretch, and
> OK yes sure added a couple of what I'd call 'basic' things in - nothing too
> major - but now I don't get access via the Serial Debug Header. All output
> looks normal on boot and I can't see anything in particular standing out in
> the boot log, either.
>
> It may well be that I'm missing sufficient amounts of coffee. But any
> thoughts/comments appreciated at this stage.

systemd should trigger on:

debug: [console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4
rootwait coherent_pool=1M net.ifnames=0 quiet cape_universal=enable]
...

and setup a serial login console...

do you have this udev rule installed?

https://github.com/rcn-ee/repos/blob/master/bb-customizations/suite/jessie/debian/60-omap-tty.rules

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

[beagleboard] Serial Debug Header access query

2017-05-29 Thread Peter Lawler


Hi!
Just wondering if something's changed recently in the way the Serial 
Debug Header operates?


I'm asking because I've grabbed the recent release, updated to stretch, 
and OK yes sure added a couple of what I'd call 'basic' things in - 
nothing too major - but now I don't get access via the Serial Debug 
Header. All output looks normal on boot and I can't see anything in 
particular standing out in the boot log, either.


It may well be that I'm missing sufficient amounts of coffee. But any 
thoughts/comments appreciated at this stage.


Cheers,

Pete.


Output on Serial Debug:

U-Boot SPL 2017.03-2-gd12b1519b4 (Mar 14 2017 - 10:28:26)
Trying to boot from MMC2


U-Boot 2017.03-2-gd12b1519b4 (Mar 14 2017 - 10:28:26 -0500), Build: 
jenkins-github_Bootloader-Builder-532


CPU  : AM335X-GP rev 2.1
I2C:   ready
DRAM:  512 MiB
Reset Source: Power-on reset has occurred.
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

 not set. Validating first E-fuse MAC
BeagleBone Black:
BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_probe: 0x55:
BeagleBone: cape eeprom: i2c_probe: 0x56:
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net:   eth0: MII MODE
cpsw
Press SPACE to abort autoboot in 2 seconds
board_name=[A335BNLT] ...
board_rev=[00A5] ...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
** Bad device 0:2 0x8200 **
** Bad device 0:2 0x8200 **
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
gpio: pin 55 (gpio 55) value is 1
1972 bytes read in 42 ms (44.9 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
gpio: pin 56 (gpio 56) value is 1
Running uname_boot ...
loading /boot/vmlinuz-4.4.68-ti-r106 ...
8608104 bytes read in 590 ms (13.9 MiB/s)
loading /boot/dtbs/4.4.68-ti-r106/am335x-boneblack.dtb ...
56827 bytes read in 88 ms (629.9 KiB/s)
uboot_overlays: add [enable_uboot_overlays=1] to /boot/uEnv.txt to enable...
loading /boot/initrd.img-4.4.68-ti-r106 ...
5940425 bytes read in 424 ms (13.4 MiB/s)
debug: [console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 
rootwait coherent_pool=1M net.ifnames=0 quiet cape_universal=enable] ...

debug: [bootz 0x8200 0x8808:5aa4c9 0x8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Loading Ramdisk to 8fa55000, end 84c9 ... OK
   Loading Device Tree to 8fa44000, end 8fa54dfa ... OK

Starting kernel ...

[0.001026] clocksource_probe: no matching clocksources found
[2.109460] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[2.291426] omap_voltage_late_init: Voltage driver support not added
[2.299156] PM: Cannot get wkup_m3_ipc handle
rootfs: clean, 112476/959616 files, 663500/3888512 blocks

Debian GNU/Linux 9 beaglebone ttyS0
beaglebone login:

---

dmesg

[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 4.4.68-ti-r106 (root@b1-omap5-uevm-2gb) 
(gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Sat May 27 
15:52:44 UTC 2017
[0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), 
cr=10c5387d
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instruction cache

[0.00] Machine model: TI AM335x BeagleBone Black
[0.00] cma: Reserved 48 MiB at 0x9c80
[0.00] Memory policy: Data cache writeback
[0.00] On node 0 totalpages: 130560
[0.00] free_area_init_node: node 0, pgdat c1059200, node_mem_map 
df961000

[0.00]   Normal zone: 1152 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 130560 pages, LIFO batch:31
[0.00] CPU: All CPU(s) started in SVC mode.
[0.00] AM335X ES2.1 (sgx neon )
[0.00] PERCPU: Embedded 13 pages/cpu @df92 s24268 r8192 
d20788 u53248

[0.00] pcpu-alloc: s24268 r8192 d20788 u53248 alloc=13*4096
[0.00] pcpu-alloc: [0] 0
[0.00] Built 1 zonelists in Zone order, mobility grouping on. 
Total pages: 129408
[0.00] Kernel command line: console=ttyO0,115200n8 
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
net.ifnames=0 quiet cape_universal=enable

[0.00] PID hash table entries: 2048 (order: 1, 8192 bytes)
[0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 
bytes)
[0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 
bytes)
[0.00] Memory:

[beagleboard] MikroBus Cape quick-start with drivers?

2017-05-29 Thread Niels Jakob Buch

Hi there, I am wondering about the ease of use of the MikroBus Cape from 
MikroElektronika https://shop.mikroe.com/click/shields/beaglebone-mikrobus-cape

Is there anywhere to go for drivers and configuration assistance when 
sliding in a new click board?

It seems that the drivers and examples from MikroE are all based on their 
own compilers, and not suited for Linux compilation.

-- 
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/27365d67-e7bb-43d0-a791-96c940da2423%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Custom SPI protocol kernel module and device tree

2017-05-29 Thread Георгий Одишария

Also:

root@arm:~# cat /sys/bus/spi/devices/spi1.0/of_node/spi-max-frequency | 
hexdump 
000 6e01 0036   
004

-- 
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/88782478-b5bd-4443-8a44-955bf42371dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] how delete or uninstall a software

2017-05-29 Thread Eduardo castillo

I need uninstall or delete a software charged in the Beagle Bone Green 
Wirless but i don't find information about how do that.

-- 
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/ead1188c-0b13-412e-ae83-6d21d4ae6b16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Custom SPI protocol kernel module and device tree

2017-05-29 Thread Георгий Одишария

Hello. I have trouble trying to get information from DT in my kernel module.

I made and built device tree overlay similar to one for spidev kernel 
module. Here it is:
/dts-v1/;
/plugin/;


/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";


/* identification */
part-number = "BB-ARDUINO-ECHO";
version = "00A0";
 
fragment@0 {
target = <_pinmux>;
__overlay__ {
spi0_pins_s0: spi0_pins_s0 {
 pinctrl-single,pins = <
 0x150 0x30  /* mcasp0_aclkx.spi0_sclk, INPUT_PULLUP  | MODE0 */
 0x154 0x30  /* mcasp0_fsx.spi0_d0, INPUT_PULLUP  | MODE0 */
 0x158 0x10  /* mcasp0_axr0.spi0_d1,OUTPUT_PULLUP | MODE0 */
 0x15c 0x10  /* mcasp0_ahclkr.spi0_cs0, OUTPUT_PULLUP | MODE0 */
 >;
};
};
};


fragment@1 {
target = <>;
__overlay__ {


#address-cells = <1>;
#size-cells = <0>;
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <_pins_s0>;

ardiuno_echo@0 {
compatible = "arduino,pro-mini-spi-generic";
reg = <0>;
spi-max-frequency = <10>;
};
};
};
};

And here I trying to access spi-max-frequency property from my probe() 
function of device driver:
static int spi_protocol_generic_probe(struct spi_device *spi)
{
 int err, ret;
 int devData = 0;
 const struct of_device_id *match;


 struct device_node *of_target_node;
 u32 max_speed_arduino = 0;


 const char *of_compt_str = kcalloc(sizeof(char), 255, GFP_KERNEL);


 __spi_device_internal = spi;
 default_values.speed_hz = spi->max_speed_hz;
 default_values.mode = spi->mode;
 default_values.bits_per_word = spi->bits_per_word;


 debug_printk("spi-protocol-generic: default speed is %d Hz\n",
 default_values.speed_hz);


 // check and read data from of_device_id...
 match = of_match_device(spi_protocol_generic_of_match, >dev);
 if (!match) {
 debug_printk("device not found in device tree...\n");
 return -1;
 }
 of_target_node = of_find_compatible_node(NULL, NULL, match->compatible);
 if (!of_target_node) {
 of_node_put(of_target_node);
 debug_printk("no compatible devices in DT!\n");
 }


 // Here we can use of_get_property, but I prefer more readable
 // code insted of mire obvious
 ret = of_property_read_u32(of_target_node, "spi-max-frequency",
   _speed_arduino);


 if (ret) {
 debug_printk("cannot find property in DT node, status %d\n",
 ret);
 return ret;
 } else {
 debug_printk("freq is %x Hz\n", max_speed_arduino);
 }


 spi->bits_per_word = 8;
 spi->mode = SPI_MODE_0;
 spi->max_speed_hz = max_speed_arduino;
 err = spi_setup(spi);


 if (err < 0) {
 printk(KERN_DEBUG "spi-protocol-generic: spi_setup failed!\n");
 return err;
 } else {
 printk(KERN_DEBUG "spi-protocol-generic: now speed is %d Hz\n",
   spi->max_speed_hz);
 }
// ... and so on ...
}

I can access other properties such as reg and compatible. But even if I am 
trying to get the property of DT from sysfs, this property seems to have 
invalid value.
For example, if I set spi-max-frequency to 100 (1 MHz), value from 
sysfs will be invalid and it won't equal 100. This value is not 
depending from my value in DT overlay.

How can I set this property correctly?

-- 
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/e29e5808-3311-43e6-8ed2-d28af5e7fdc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

2017-05-29 Thread Robert Nelson

On Mon, May 29, 2017 at 12:02 AM, Migue Fonseca 
wrote:

> Hey my friend, thanks for your quick reply. I retested everything with the
> new image, same result:
> [image: Imágenes integradas 1]
>
> Could this be a driver issue? Let me know what you think.
>

Please run version.sh:

debian@test-bbbw-11:/opt/scripts/tools$ sudo ./version.sh
git:/opt/scripts/:[0e222d4aeb4f1c06dcdd025e0b1e1835404e1551]
eeprom:[A335BNLTBWA0*]
dogtag:[BeagleBoard.org Debian Image 2016-10-23]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2017.05-2-g962663a0e0]
kernel:[4.4.62-ti-rt-r105]
nodejs:[v0.12.18]

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/CAOCHtYiyS2%3DG1PEsv-ZZGtgW9XzLUtt4msY%2B1503M7L9uSrj3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Getting a servo up and running...

2017-05-29 Thread Aaron

You can power the servo from an external 6V source, but you'd have to
connect the ground of the power source to your BBBlue or the servo will not
work right.  ie.  The ground going to the servo, still needs to connect to
the ground pin on the BBBlue servo output header.

You can see an example wiring in this picture ( Yes, it is a picture of an
Arduino, but the idea is the same ) :
https://camo.githubusercontent.com/1762dcd6217476edace78913d66cbd8d976a6690/68747470733a2f2f646c2e64726f70626f7875736572636f6e74656e742e636f6d2f752f333533313935382f65787465726e616c2d736572766f2d706f7765722e706e67



On 29 May 2017 at 06:13, Niels Jakob Buch  wrote:

> Would it be possible to wire a Powerout with 6V from a power-socket
> directly to the servo, and not connect the middle pin to the
> servo-connector?
>
> On Friday, 26 May 2017 23:44:41 UTC+2, Niels Jakob Buch wrote:
>>
>> Just took a look at the schematics... https://github.com/beagleboard
>> /beaglebone-blue/blob/master/BeagleBone_Blue_sch.pdf
>>
>> Seems that the servos are powered by the batteries, which might make
>> sense to supply enough amps.
>>
>> Anyway, is there a way to power the servos with another source?
>>
>> --
> 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/c98b47a1-dc19-4fe4-93c4-b136747e2635%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/CALw-AjP9FoCwaCvQZV9YHz%2B1sN_1mT1piSQzRaYPo%2BVNNtz6mA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: I²C reads on broken out bus #1 always return 0

2017-05-29 Thread Graham Haddock

Torsten:
Great job.
--- Graham

==

On Mon, May 29, 2017 at 9:32 AM, 'Torsten K.' via BeagleBoard <
beagleboard@googlegroups.com> wrote:

> FYI: It's working now. The PIC code that came with the motor controller
> was not I²C re-start aware.
>
> I re-implemented the ISR to accept both stop/start and re-start sequences
> before reading the slave's output. That did the trick.
>
> Best,
> Torsten
>
> --
> 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/-cVwfP40L0M/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/24021d75-eb84-40c6-98e1-05dd27972d70%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/CANN_KV6b49tf4q5aki2jJjrTe_WUfm6akar%3Dzi4rMXeKA4hQXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: I²C reads on broken out bus #1 always return 0

2017-05-29 Thread 'Torsten K.' via BeagleBoard

FYI: It's working now. The PIC code that came with the motor controller was 
not I²C re-start aware.

I re-implemented the ISR to accept both stop/start and re-start sequences 
before reading the slave's output. That did the trick.

Best,
Torsten

-- 
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/24021d75-eb84-40c6-98e1-05dd27972d70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Can't get properly spi-max-frequency from custom SPI driver

2017-05-29 Thread Георгий Одишария

Hello!
I am trying to make custom SPI protocol driver for custom device (based on 
FPGA, target for us is LOGI-Bone). Now I have a prototype of FPGA device, 
this prototype is Arduino Pro Mini 3.3V.

I am trying to make custom overlay for device tree which has appropriate 
compatible field for my driver.

Here is my overlay:

/dts-v1/;
/plugin/;
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";


/* identification */
part-number = "BB-ARDUINO-ECHO";
version = "00A0";

fragment@0 {
target = <_pinmux>;
__overlay__ {
spi0_pins_s0: spi0_pins_s0 {
pinctrl-single,pins = <
0x150 0x30  /* mcasp0_aclkx.spi0_sclk, 
INPUT_PULLUP  | MODE0 */
0x154 0x30  /* mcasp0_fsx.spi0_d0, 
INPUT_PULLUP  | MODE0 */
0x158 0x10  /* mcasp0_axr0.spi0_d1,   
 OUTPUT_PULLUP | MODE0 */
0x15c 0x10  /* mcasp0_ahclkr.spi0_cs0, 
OUTPUT_PULLUP | MODE0 */
>;
};
};
};
fragment@1 {
target = <>;
__overlay__ {
#address-cells = <1>;
#size-cells = <0>;
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <_pins_s0>;
ardiuno_echo@0 {
compatible = "arduino,pro-mini-spi-generic";
reg = <0>;
spi-max-frequency = <10>;
};
};
};
};

And here is my code for getting info from device tree:

static int spi_protocol_generic_probe(struct spi_device *spi)
{
int err, ret;
 int devData = 0;
 const struct of_device_id *match;


 struct device_node *of_target_node;
 u32 max_speed_arduino = 0;


 const char *of_compt_str = kcalloc(sizeof(char), 255, GFP_KERNEL);


 __spi_device_internal = spi;
 default_values.speed_hz = spi->max_speed_hz;
 default_values.mode = spi->mode;
 default_values.bits_per_word = spi->bits_per_word;


 debug_printk("spi-protocol-generic: default speed is %d Hz\n",
 default_values.speed_hz);


 // check and read data from of_device_id...
 match = of_match_device(spi_protocol_generic_of_match, >dev);
 if (!match) {
 debug_printk("device not found in device tree...\n");
 return -1;
 }
 of_target_node = of_find_compatible_node(NULL, NULL, match->compatible);
 if (!of_target_node) {
 of_node_put(of_target_node);
 debug_printk("no compatible devices in DT!\n");
 }


 // Here we can use of_get_property, but I prefer more readable
 // code insted of mire obvious
// ret = of_property_read_u32(of_target_node, "spi-max-frequency",
//   _speed_arduino);
 max_speed_arduino = *(u32 *)of_get_property(of_target_node, 
"spi-max-frequency", NULL); 


 if (ret) {
 debug_printk("cannot find property in DT node, status %d\n",
 ret);
 return ret;
 } else {
 debug_printk("freq is %x Hz\n", max_speed_arduino);
 }


 spi->bits_per_word = 8;
 spi->mode = SPI_MODE_0;
 spi->max_speed_hz = max_speed_arduino;
 err = spi_setup(spi);


 if (err < 0) {
 printk(KERN_DEBUG "spi-protocol-generic: spi_setup failed!\n");
 return err;
 } else {
 printk(KERN_DEBUG "spi-protocol-generic: now speed is %d Hz\n",
   spi->max_speed_hz);
 }
// ... and so on
}



I can access to every field of my DT node, but every time I set any 
spi-max-freqency in device tree overlay, I cannot read it properly! Even 
from sysfs:


-- 
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/558551a3-d32a-4e41-9cca-1df5cf6a32e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beagleboard - x15 can run Beaglebone Black's PRUSS code?

2017-05-29 Thread namjagun

Hi recently I bought a Beaglebone Black.

And I need to use GPI read with PRU.

I found some examples how to use PRUSS like am335x_pru_package.(the link 
below)

https://github.com/beagleboard/am335x_pru_package/blob/master/pru_sw/app_loader/interface/__prussdrv.h

There are some defined values to use AM33XX's PRUSS.


But I need to run that code in BeagleBoard-X15 to use PRUSS in AM5728.

I read about migration guide from the link below.

http://processors.wiki.ti.com/index.php/PRU-ICSS_Migration_Guide:_AM335x_to_AM57x

But I think it's hard to change am335x_pru_package's code for migration.
 
Is there any support for migration AM33XX PRU to AM5728 PRU?

It's hard to find about PRUSS migration code from internet.

Please let me know if there is any support like this case.

Thank you very much.


-- 
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/ff71b0f4-8a4b-4c2b-88c7-f9bc1f7e99ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Getting a servo up and running...

2017-05-29 Thread Niels Jakob Buch

Would it be possible to wire a Powerout with 6V from a power-socket 
directly to the servo, and not connect the middle pin to the 
servo-connector?

On Friday, 26 May 2017 23:44:41 UTC+2, Niels Jakob Buch wrote:
>
> Just took a look at the schematics... 
> https://github.com/beagleboard/beaglebone-blue/blob/master/BeagleBone_Blue_sch.pdf
>
> Seems that the servos are powered by the batteries, which might make sense 
> to supply enough amps. 
>
> Anyway, is there a way to power the servos with another source?
>
>

-- 
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/c98b47a1-dc19-4fe4-93c4-b136747e2635%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] setting Beagle Bone pinmux directly

2017-05-29 Thread William Hermans

That's /boot/uEnv.txt, typo above.

On Sun, May 28, 2017 at 11:57 PM, William Hermans  wrote:

> First, you disable universal IO, second, if you do not need hdmi, you
> disable hdmi video, and audio at boot. Through /boot.uEnv.txt. This will
> free up any pin that's not related to I2C-0, I2C-2, the eMMC, and possibly
> a few others I'm not thinking of off the top of my head.
>
> On Sun, May 28, 2017 at 8:35 PM, jmelson  wrote:
>
>> Charles Steinkuehler says the new kernels use memory management to lock
>> access to the pinmux registers.  This certainly matches the symptoms I am
>> getting.  Hopefully, he can tell me how to use config-pin to set it up.
>>
>> Jon
>>
>> --
>> 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/ms
>> gid/beagleboard/5365e3af-9f87-4632-8bc4-41371dc5be89%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/CALHSORpKsSC5xKBXYQD%3DGjO33pRmwXqFx5_it9kJG7UQDh6ROw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] setting Beagle Bone pinmux directly

2017-05-29 Thread William Hermans

First, you disable universal IO, second, if you do not need hdmi, you
disable hdmi video, and audio at boot. Through /boot.uEnv.txt. This will
free up any pin that's not related to I2C-0, I2C-2, the eMMC, and possibly
a few others I'm not thinking of off the top of my head.

On Sun, May 28, 2017 at 8:35 PM, jmelson  wrote:

> Charles Steinkuehler says the new kernels use memory management to lock
> access to the pinmux registers.  This certainly matches the symptoms I am
> getting.  Hopefully, he can tell me how to use config-pin to set it up.
>
> Jon
>
> --
> 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/5365e3af-9f87-4632-8bc4-41371dc5be89%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/CALHSORr6ZP5UuVXhofQZV7SaDLPxGYonKEb%2B_yRRLh8NjLKtUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] recording audio not working on BBB deb 8.7?

2017-05-29 Thread hussainali0935

Hi everyone!

I'm using beagle bone black and I want to use "Audio cape Rev B" for 
playing and recording audio.

I installed debian 8.7 image on BBB and changed the uEnv.txt and added 
proper entry in it to load the Audio cape.

Now, audio cape is loaded and i can play audio with aplay utility 
successfully. But recording is not working.

issuing arecord command results the below error message:

*arecord: set_params:1297: Unable to install hw params*

dmesg messages is as below:
*davinci-mcasp 48038000.mcasp: Too fast reference clock(24576000)*
*davinci-mcasp 48038000.mcasp: stream has more channels (2) than are 
enabled in mcasp (0)*
*davinci-mcasp 48038000.mcasp: Asoc: can't set 48038000.mcasp hw params: 
-22*

where is the source of the problem?

-- 
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/ff1ccdfb-8c91-4a90-ad97-9ece4ebf2737%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Problems with BBB USB serial communication and Windows 10

2017-05-29 Thread 'Satz Klauer' via BeagleBoard



Hi,


I'm running a StarterWare 2 based application on an BBB which makes use of 
a USB serial interface implementation based on the StarterWare example and 
by using a .inf-File which is similar to "usb_dev_serial.inf" which was 
provided by TI in same StarterWare package. Of course VID and PID have been 
changed according to my own USB serial interface implementation.


This works well with all Windows-versions up to 7 (8.x was never tested) 
and also with all Linux variants. But now with Windows 10 there is a 
problem which was reported by different users of this application:

   - opening of the serial interface often fails, simple repeating of the 
   procedure then is successful latest after 10 tries
   - sometimes an already opened connection seem to be corrupted, means 
   there is no more communication possible, host application needs to be 
   closed, device needs to be restarted - but after this, the same COM-port is 
   available again, Windows does not change numbering

So: is anything known about such problems in Windows 10 ? Perhaps are there 
any changes necessary in an INF-file or in USB serial interface code to 
make it work with Windows 10? Is there anything similar known from the 
Linux Kernel of the BBB?


Any hint or idea is welcome!



-- 
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/2647b45a-ff11-42e4-91ed-084f90d7e69c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Serial Debug Header access query

[beagleboard] Re: Windows 10 Bone_D64.exe Failing

[beagleboard] help pru allocating 320mb

Re: [beagleboard] Multiple USB Cameras on BBB

Re: [beagleboard] setting Beagle Bone pinmux directly

[beagleboard] Multiple USB Cameras on BBB

[beagleboard] Re: Serial Debug Header access query

[beagleboard] Re: how delete or uninstall a software

Re: [beagleboard] Serial Debug Header access query

Re: [beagleboard] Serial Debug Header access query

[beagleboard] Serial Debug Header access query

[beagleboard] MikroBus Cape quick-start with drivers?

[beagleboard] Re: Custom SPI protocol kernel module and device tree

[beagleboard] how delete or uninstall a software

[beagleboard] Custom SPI protocol kernel module and device tree

Re: [beagleboard] Re: bbgw wlan0 users

Re: [beagleboard] Re: Getting a servo up and running...

Re: [beagleboard] Re: I²C reads on broken out bus #1 always return 0

[beagleboard] Re: I²C reads on broken out bus #1 always return 0

[beagleboard] Can't get properly spi-max-frequency from custom SPI driver

[beagleboard] Beagleboard - x15 can run Beaglebone Black's PRUSS code?

[beagleboard] Re: Getting a servo up and running...

Re: [beagleboard] setting Beagle Bone pinmux directly

Re: [beagleboard] setting Beagle Bone pinmux directly

[beagleboard] recording audio not working on BBB deb 8.7?

[beagleboard] Problems with BBB USB serial communication and Windows 10

26 matches

Site Navigation

Mail list logo

Footer information