[beagleboard] Re: Select timeout error when running video streaming code

Is anyone out there to assist? I'm stuck On Monday, 4 April 2016 09:09:32 UTC+2, Tinashe Mudavanhu wrote: > > Hi, > > I am testing an opencv video capture code on my BBB (running Debian > Wheezy: Linux beaglebone 3.8.13-bone79 #1 SMP Tue Oct 13 20:44:55 UTC 2015 > armv7l GNU/Linux) but getting a

[beagleboard] Corintech Dataloggers

Hi all! Did anybody connect a Corintech Datalogger to a BB or any other Linux system yet? I don't want to use the cloud feature, just fetch the data packages from a BBB over local WLAN. There's no software for Linux from the manufacturer and I coul

[beagleboard] Re: Troubleshooting one-wire DS18B20 detection on BBB, debian, kernel: 3.8.13-bone70

Hi Matt! A year ago I started with those sensors and I didn't have trouble to connect them by the w1 kernel driver. But I don't remember what I did that time, because I dropped that solution. The kernel driver doesn't support broadcast messages and the sensors are triggered one after the other.

Re: [beagleboard] Re: How to write a data file to Beaglebone from Python

> > *Here's some of my code. Hopefully you'll see something newbie-wrong that > I've done. It's been a while since I have done file I/O, so it's likely > that I have some syntax error(s).* > So, I would reduce the code you have, at least in a test file, and use only the absolute minimum code for p

Re: [beagleboard] Re: How to write a data file to Beaglebone from Python

You're also not writing a new line character after your value into the file, which may or may not cause a problem. On Wed, Apr 6, 2016 at 1:32 AM, William Hermans wrote: > *Here's some of my code. Hopefully you'll see something newbie-wrong that >> I've done. It's been a while since I have done

Re: [beagleboard] eMMC gets timeout when I put on cape

Hey :) According to Derek Molloys header pin overview ( http://exploringbeaglebone.com/wp-content/uploads/resources/BBBP9Header.pdf ) some of the pins are used by the HDMI, but I have disabled that. It seems that all the eMMC pins are located on the P8 header. If this was the problem, I should

Re: [beagleboard] Kernel 4.1.10: UART5 overlay can't claim nxp_hdmi_bonelt_pins

Hello! I have kernel version 4.1.10-bone16 with the same issue as pbft. I tried following the "Compatibility issues section". I did the following and rebooted: When I lo

Re: [beagleboard] Release date update?

Hi, Any update on this? On Tuesday, 1 March 2016 15:09:14 UTC, Gerald wrote: > > It will be a while. I hope within a month .But no guarantees based on this > thing passing FCC.. > > Gerald > > > On Tue, Mar 1, 2016 at 4:43 AM, > > wrote: > >> hello, >> >> I just received the newsletter but no

Re: [beagleboard] Release date update?

1. We expect PCBs here in another week. 4/13/2016 2. 1 week for assembly.4/20/2015 3. 1 week for test and bring up. 4/27/2016 4. 1 week for FCC testing 5/4/2016 5. First 500 boards shipping 2 weeks later. 5/18/2016 Gerald On Wed, Apr 6, 2016 at 2:37 AM, Pier wrote: > Hi, > > Any update on this?

Re: [beagleboard] Kernel 4.1.10: UART5 overlay can't claim nxp_hdmi_bonelt_pins

On Wed, Apr 6, 2016 at 1:54 AM, wrote: > Hello! > > I have kernel version 4.1.10-bone16 with the same issue as pbft. I tried > following the "Compatibility issues section". > I did the following and rebooted: > > >

[beagleboard] PRU : which kernel version choice

Hello, I'm currently trying to configure the PRU, I have tried several things. However it was not successful. So I would like to know if the PRU is working on the v4.1.18-bone20 or the v4.1.19-bone20 of the kernel, and if someone have made some successful test on it ? And if not, which (recent

[beagleboard] libbulldog help

Hey all, I have recently posted this question in the libbulldog g group and am just looking to widen the search for help on this topic. https://groups.google.com/forum/#!topic/libbulldog/FgAjrG3zq-c The issue is in regards to compiling the java library from source after modifying it. If anyone

Re: [beagleboard] Ada on the BeagleBone Black

Brent: It is a rare treat to see well documented code, which includes explicit handling of (MKS) units. Your Ada raises the bar for anyone designing maintainable code for the BBB. It, at the very least, serves as pseudo-code for anyone programming in any language. Ada and Jovial before it leave

[beagleboard] Cape no longer working

On the BBB, using Linux beaglebone 4.1.18-ti-r53 (from console flasher image), the CryptoCape no longer appears to load: debian@beaglebone:~$ dmesg | grep CRYPTO [3.607175] bone_capemgr bone_capemgr: slot #3: 'BB-BONE -CRYPTO,00A0,SparkFun,BB-BONE-CRYPTO' [4.617394] bone_capemgr bone_cape

Re: [beagleboard] Cape no longer working

On Wed, Apr 6, 2016 at 11:00 AM, Josh Datko wrote: > On the BBB, using Linux beaglebone 4.1.18-ti-r53 (from console flasher > image), the CryptoCape no longer appears to load: > > > debian@beaglebone:~$ dmesg | grep CRYPTO > [3.607175] bone_capemgr bone_capemgr: slot #3: 'BB-BONE > -CRYPTO,00

Re: [beagleboard] eMMC gets timeout when I put on cape

On Wed, Apr 6, 2016 at 5:09 AM, Martin Wiingaard wrote: > Hey :) > > According to Derek Molloys header pin overview ( > http://exploringbeaglebone.com/wp-content/uploads/resources/BBBP9Header.pdf > ) some of the pins are used by the HDMI, but I have disabled that. It seems > that all the eMMC pin

Re: [beagleboard] Cape no longer working

On Wed, 2016-04-06 at 11:02 -0500, Robert Nelson wrote: > > sudo apt-get update > sudo apt-get install git-core device-tree-compiler > > git clone https://github.com/beagleboard/bb.org-overlays > cd ./bb.org-overlays > > ./install.sh Great! thanks, but now I'm having another problem. It doesn'

Re: [beagleboard] Cape no longer working

On Wed, Apr 6, 2016 at 11:52 AM, Josh Datko wrote: > On Wed, 2016-04-06 at 11:02 -0500, Robert Nelson wrote: > > > > > sudo apt-get update > > sudo apt-get install git-core device-tree-compiler > > > > git clone https://github.com/beagleboard/bb.org-overlays > > cd ./bb.org-overlays > > > > ./ins

[beagleboard] building the linux kernel/making a SD card boot image

Hi, I needed to re-build the Linux kernel (Debian) with the USB power management auto suspend feature turned off. So i followed the instruction to build the Linux kernel and make a boot-able SD card image for my beagle bone black. I followed the instructions at https://eewiki.net/display/linu

Re: [beagleboard] building the linux kernel/making a SD card boot image

On Wed, Apr 6, 2016 at 12:34 PM, Karina wrote: > Hi, > > I needed to re-build the Linux kernel (Debian) with the USB power > management auto suspend feature turned off. So i followed the instruction > to build the Linux kernel and make a boot-able SD card image for my beagle > bone black. I foll

Re: [beagleboard] Cape no longer working

On Wed, Apr 6, 2016 at 12:27 PM, Robert Nelson wrote: > > > On Wed, Apr 6, 2016 at 11:52 AM, Josh Datko wrote: > >> On Wed, 2016-04-06 at 11:02 -0500, Robert Nelson wrote: >> >> > >> > sudo apt-get update >> > sudo apt-get install git-core device-tree-compiler >> > >> > git clone https://github.

[beagleboard] Re: How to write a data file to Beaglebone from Python

Thanks All for your help. It is much appreciated and shows how helpful the BB Forum users are and how valuable the Forum is. John On Wednesday, April 6, 2016 at 5:54:47 AM UTC-7, Dennis Lee Bieber wrote: > > On Tue, 5 Apr 2016 19:11:32 -0700, John Baker > > declaimed the > following: > > > >He

Re: [beagleboard] Cape no longer working

On Wed, Apr 6, 2016 at 1:04 PM, Robert Nelson wrote: > > > On Wed, Apr 6, 2016 at 12:27 PM, Robert Nelson > wrote: > >> >> >> On Wed, Apr 6, 2016 at 11:52 AM, Josh Datko wrote: >> >>> On Wed, 2016-04-06 at 11:02 -0500, Robert Nelson wrote: >>> >>> > >>> > sudo apt-get update >>> > sudo apt-get

Re: [beagleboard] Cape no longer working

On Wed, Apr 6, 2016 at 1:10 PM, Robert Nelson wrote: > > > On Wed, Apr 6, 2016 at 1:04 PM, Robert Nelson > wrote: > >> >> >> On Wed, Apr 6, 2016 at 12:27 PM, Robert Nelson >> wrote: >> >>> >>> >>> On Wed, Apr 6, 2016 at 11:52 AM, Josh Datko wrote: >>> On Wed, 2016-04-06 at 11:02 -0500, Ro

Re: [beagleboard] Cape no longer working

> > > Now it works if we remove: > > - /* TPM - Driver currently only available in > 3.13.x */ > - tpm_i2c_atmel@29 { > - compatible = "tpm_i2c_atmel"; > - reg = <0x29>; > -

Re: [beagleboard] Re: How to write a data file to Beaglebone from Python

Gosh, how did I miss that, that the mode is a string. Well it had to be something simple like that. Quoting the w and r fixed the problem. Very embarrassing. :-[ Thanks, John On 4/5/2016 7:21 PM, Dennis Lee Bieber wrote: On Tue, 5 Apr 2016 13:43:47 -0700 (PDT), John Baker declaimed the follow

Re: [beagleboard] Cape no longer working

On Wed, Apr 6, 2016 at 1:23 PM, Josh Datko wrote: > > > > > > Now it works if we remove: > > > > - /* TPM - Driver currently only available in > > 3.13.x */ > > - tpm_i2c_atmel@29 { > > - compatible = "tpm_i2c_atmel"; > > -

Re: [beagleboard] Cape no longer working

Great! Thanks so much. Sorry about missing that for a while, I need to keep up a bit better :/ Josh -- 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 s

[beagleboard] Getting python Tkinter to recognize display

I am trying to get the python GUI package Tkinter running on the BeagleBone Black (debian Jessie) to connect to the display. I get this error when I run a simple Tkinter test program: root@beaglebone:/boot# python /home/debian/oqy/tktest.pyNo protocol specifiedNo protocol specifiedTraceback

Re: [beagleboard] Cape no longer working

On Wed, Apr 6, 2016 at 1:26 PM, Joshua Datko wrote: > Great! Thanks so much. > > Sorry about missing that for a while, I need to keep up a bit better :/ > I think we could convert gpio1_17 into a led, then you can easily toggle it from userspace. is gpio1_13 and irq source from the TPM? My cry

[beagleboard] Re: PRU : which kernel version choice

I am using 4.1.20-bone-rt-r20, and no chance so far. If you manage to get PRU working, I would be grateful if you inform me. On Wednesday, April 6, 2016 at 5:35:26 PM UTC+3, Le Costaouec Vincent wrote: > > > Hello, > > I'm currently trying to configure the PRU, I have tried several things. > How

[beagleboard] CircuitCo AudioCape and 4.4.6-bone-rt-r7 kernel, not quite there

I decided to try to get the CircuitCo audio cape up and running on 4.4.6-bone-rt-r7, because while similar, my cape has a few differences. My DTB: http://pastebin.com/Wja7ZQRk and DTBO: https://github.com/RobertCNelson/bb.org-overlays/blob/master/src/arm/BB-BONE-AUDI-02-00A0.dts Results of spea

Re: [beagleboard] Cape no longer working

gpio1_17 is tied to the reset line of the ATmega on the cape and is meant to be toggled from userspace to allow for, well, resetting. Besides the obvious this allows users to reset the ATmega to upload sketches with avrdude (using UART4). So, while it sounds odd to make it an LED, if that makes it

[beagleboard] What is the difference between output pull-up, output pull-down, and output no pull?

On the BeagleBone Black GPIOs, what is the difference between output pull-up, output pull-down, and output no pull? In other MCUs I have worked with, pull-up and pull-down are only applied to inputs. But I have found nothing to specifically say that is the case with the Beaglebone, and so

Re: [beagleboard] What is the difference between output pull-up, output pull-down, and output no pull?

You might try reading the datasheet for the AM3358 MCU. http://www.ti.com/product/AM3358 Gerald On Wed, Apr 6, 2016 at 4:38 PM, wrote: > > On the BeagleBone Black GPIOs, what is the difference between output > pull-up, output pull-down, and output no pull? > > > In other MCUs I have worked wi

[beagleboard] Source-level single-stepping kernel code on BBB?

What would I need to get/do to enable me to single-step through kernel code on BBB/G? JTAG header, some kind of interface, and a bunch of software installed on Ubuntu? Can anyone make specific recommendations? Is it even possible? Thanks, -- Rick Mann rm...@latencyzero.com -- For more optio

[beagleboard] On the BBB, what is the difference between output pull-up, output pull-down, and output no pull?

On the BeagleBone Black GPIOs, what is the difference between output pull-up, output pull-down, and output no pull? In other MCUs I have worked with, pull-up and pull-down are only applied to inputs. But I have found nothing to specifically say that is the case with the Beaglebone, and som

[beagleboard] Fwd: Us congress hearing of maan alsaan Money laundry قضية الكونغجرس لغسيل الأموال للمليادير معن الصانع

YouTube videos of U.S. Congress money laundering hearing of Saudi Billionaire " Maan Al sanea" with *bank of America* and The owner of Saad Hospital and Schools in the Eastern Province in *Saudi Arabia* and the Chairman of the Board of Directors of Awal Bank in *Bahrain* Wit

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

You can do this with CCSV6 with a USB200 JTAG adapter, but CCSV6 is no longer kernel aware. CCSV4 was kernel aware, but won’t work with the current kernels. You can still debug with single stepping, software and hardware breakpoints, read/write memory, etc. Trying to debug a kernel module withou

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

Thanks, John. I've tried printk and other logging, but it's virtually impossible to trace something like audio, which spans many modules. I'll look into Lauterbach. > On Apr 6, 2016, at 15:31 , John Syne wrote: > > You can do this with CCSV6 with a USB200 JTAG adapter, but CCSV6 is no longer

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

For audio, your best solution is ftrace. If you use function_graph option, then you can see the hierarchy of the call sequence. You can also use trace_printk to display variables at specific locations. BTW, Lauterbach is about $5K investment for the base tool with USB3 connection. You might be

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

On 04/06/2016 02:56 PM, Rick Mann wrote: > What would I need to get/do to enable me to single-step through > kernel code on BBB/G? JTAG header, some kind of interface, and a > bunch of software installed on Ubuntu? Can anyone make specific > recommendations? Is it even possible? On 04/06/2016 03:3

Re: [beagleboard] Ada on the BeagleBone Black

The compiler and IDE are in the Debian repository. I used aptitude to get them, but once can probably get them from the command line using apt get. There is lots of information and documentation at adacore.com. The problem that I've found is that there are plenty of resources that tell you h

Re: [beagleboard] Kernel 4.1.10: UART5 overlay can't claim nxp_hdmi_bonelt_pins

Thank you very much for the response! The problem is solved now. I am going to post here to help whoever might have a similar issue. My situation was that I had a flasher image with an old 3.8.13 kernel. Then I would update the kernel to a version 4.1.x. It seems like a big leap like that might

Re: [beagleboard] Ada on the BeagleBone Black

Thank! Today I decided to strip out all of the unit definitions and move them into one common package. Unfortunately, this makes the BBS-BBB repository dependent on the BBS repository. But it will allow all of my projects to see the same units, conversion routines, and functions. Should any

[beagleboard] Python Tkinter text flickers

Below is the code for displaying data on a monitor using Python and Tkinter on BeagleBone. It works great, but the text which displays the data flickers. Any ideas why? #!/usr/bin/python import alsaaudio as aa import audioop import Tkinter as tk import tkFont import threading import Queue st

[beagleboard] What is the difference between output pull-up, output pull-down, and output no pull?

On the BeagleBone Black GPIOs, what is the difference between output pull-up, output pull-down, and output no pull? In other MCUs I have worked with, pull-up and pull-down are only applied to inputs. But I have found nothing to specifically say that is the case with the Beaglebone, and some

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

> On Apr 6, 2016, at 4:53 PM, Peter Hurley wrote: > > On 04/06/2016 02:56 PM, Rick Mann wrote: >> What would I need to get/do to enable me to single-step through >> kernel code on BBB/G? JTAG header, some kind of interface, and a >> bunch of software installed on Ubuntu? Can anyone make specific

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

If it's a company project the Lauterbach is well worth the money  Sent from Yahoo Mail on Android On Wed, Apr 6, 2016 at 5:56 PM, Rick Mann wrote: What would I need to get/do to enable me to single-step through kernel code on BBB/G? JTAG header, some kind of interface, and a bunch of soft

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

> On Apr 6, 2016, at 5:27 PM, 'Mark Lazarewicz' via BeagleBoard > wrote: > > If it's a company project the Lauterbach is well worth the money Definitely. Lauterbach is one of my favorite tools and I cannot imagine doing some work without it. It is a difficult tool to learn, but it is very pow

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

> On Apr 6, 2016, at 16:53 , Peter Hurley wrote: > > If this is a latency problem, ftrace is probably your best bet, but > function_graph and the other tracers can induce even more latency. Nothing so esoteric. I'm just trying to get the damn thing to work at all. It's worked in previous kerne

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

OK, so you have to rebuild the entire ALSA library and tools with debug symbols. Also, your Kernel must have debug symbols turned on. You will need to enable various ftrace features with make config. Here is a typical script I use to capture program flow. === #!/bin/bash set -x pause() { lo

Re: [beagleboard] Re: Release date update?

Yes indeed. Gerald On Wed, Apr 6, 2016 at 7:51 PM, Dennis Lee Bieber wrote: > On Wed, 6 Apr 2016 08:54:24 -0500, Gerald Coley > declaimed the following: > > >1. We expect PCBs here in another week. 4/13/2016 > >2. 1 week for assembly.4/20/2015 > >3. 1 week for test and bring up. 4/27/2016 > >

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

That looks like something that would be useful to figure out how to do. The only part that's not immediately clear is "rebuild the entire ALSA library and tools with debug symbols. Also, your Kernel must have debug symbols turned on." Can I do this with RCN's kernel build script setup? Thanks.

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

On Wed, Apr 6, 2016 at 8:44 PM, Rick Mann wrote: > That looks like something that would be useful to figure out how to do. > The only part that's not immediately clear is "rebuild the entire ALSA > library and tools with debug symbols. Also, your Kernel must have debug > symbols turned on." > > C

Re: [beagleboard] Ada on the BeagleBone Black

> > *The compiler and IDE are in the Debian repository. I used aptitude to > get them, but once can probably get them from the command line using apt > get. There is lots of information and documentation at adacore.com > . The problem that I've found is that there are plenty

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

I did this years ago. From what I can find, I believe this is how you get this done: sudo apt-get build-dep libasound2 apt-get source libasound2 cd alsa-lib-1.0.22/ export DEB_BUILD_OPTIONS=nostrip,noopt dpkg-buildpackage -rfakeroot -uc -us After that, you will have some *.deb files created, whi

Re: [beagleboard] End of Life or wildly popular?

After very careful research it seems that resetting using the BBB on a hard hang would be best accomplished by resetting the PMIC pin 44. I misspoke about the SYS_RESETn is brought on the p9 ( LOL ) I Meant to say PMIC_PGOOD for a hard reset of processor. But its not an open drain signal so Wir

Re: [beagleboard] Source-level single-stepping kernel code on BBB?

Reviewing my previous work, the two package you need are: alsa-lib alsa-utils apt-get source alsa-utils cd alsa-utils-1.0.25 export DEB_BUILD_OPTIONS=“nostrip noopt debug" dpkg-buildpackage -rfakeroot -uc -us make make install or dpkg -i libasound2*.deb or apt-get install libasound2-dbg apt-g