[beagleboard] xenomai boot on beaglebone debian 2015 image SD card: how ?

Hi guys I try to send again this topic , so if this is a duplicate I apologize I am following this guide: installing-xenomai-on-beaglebone-using-debian-distribution

Re: [beagleboard] xenomai boot on beaglebone debian 2015 image SD card: how ?

$ sudo apt-get update $ sudo apt-cache search linux-image |grep xenomai . . . linux-image-3.8.13-xenomai-r67 - Linux kernel, version 3.8.13-xenomai-r67 linux-image-3.8.13-xenomai-r69 - Linux kernel, version 3.8.13-xenomai-r69 linux-image-3.8.13-xenomai-r70 - Linux kernel, version 3.8.13-xenomai-r70

Re: [beagleboard] xenomai boot on beaglebone debian 2015 image SD card: how ?

Oh, and right, once installed, reboot the board ;) On Sun, Oct 18, 2015 at 8:27 AM, William Hermans wrote: > $ sudo apt-get update > $ sudo apt-cache search linux-image |grep xenomai > . . . > linux-image-3.8.13-xenomai-r67 - Linux kernel, version 3.8.13-xenomai-r67 > linux-image-3.8.13-xenomai-

Re: [beagleboard] xenomai boot on beaglebone debian 2015 image SD card: how ?

On Oct 18, 2015 10:08 AM, "Matteo Loda" wrote: > > Hi guys > > I try to send again this topic , so if this is a duplicate I apologize > > I am following this guide: installing-xenomai-on-beaglebone-using-debian-distribution > > They use a bone-debian-7.5-2014-05-14-2gb.img.xz. > > So they have two

Re: [beagleboard] BeagleBone Green Grove i2c issues

Hi Ben, Have you resolved your issue yet ? Personally I have not used I2C on any Beaglebone yet. However I thought I might mention that for most ( perhaps all ) devices of this nature on the Beaglebone's you need to load a device tree file, which in turn often loads needed kernel module drivers, s

Re: [beagleboard] xenomai boot on beaglebone debian 2015 image SD card: how ?

Thank you very much William ! Robert you are more real time than a real time kernel ^^ I will try both the way and I will tell you the results Have a nice Sunday Evening :) Matt 2015-10-18 19:13 GMT+02:00 Robert Nelson : > > On Oct 18, 2015 10:08 AM, "Matteo Loda" wrote: > > > > Hi guys

Re: [beagleboard] BeagleBone Green Grove i2c issues

Hi William, Thanks for writing back. I haven't resolved it, no. I can't find any info about the proper device tree in the BBG documentation. Do you know where I could find one that includes the grove connector busses? Ben On Sunday, October 18, 2015 at 12:10:59 PM UTC-6, William Hermans wro

[beagleboard] barematel assembly level programming with jtag

Hi How to do barematel assembly level programming with jtag? In the webpage i see it built in jtag, but can't find further information. thanks from Peter (cmk...@hotmail.com) -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to

Re: [beagleboard] BeagleBone Green Grove i2c issues

> *Hi William,* > > *Thanks for writing back. I haven't resolved it, no. * > *I can't find any info about the proper device tree in the BBG > documentation. Do you know where I could find one that includes the grove > connector busses? * > > *Ben* > Well, not exactly but . . . First, you need to b

Re: [beagleboard] xenomai boot on beaglebone debian 2015 image SD card: how ?

Matteo, Robert's method will get you the whole thing installed, including xenomai "specific" rootfs. Which I'm not all that familiar with, but I've been told this contains xenomai utilities, examples, test suites, and what not. On Sun, Oct 18, 2015 at 12:25 PM, Matteo Loda wrote: > Thank you ve

Re: [beagleboard] BeagleBone Green Grove i2c issues

> > *$ ls /lib/firmware/ | grep I2C* > *BB-I2C1-00A0.dtbo* > *BB-I2C1-PCA9685-00A0.dtbo* > > *Looks like, at least for me, I have two I2C device tree overlays which I > can load. One generic I2C, and another which is unfamiliar to me, but seems > to be for a specific device.* > So thinking about

Re: [beagleboard] BeagleBone Green Grove i2c issues

Sadly, there does not seem to be a BBG-specific image. On Sunday, October 18, 2015 at 3:29:16 PM UTC-6, William Hermans wrote: > > *$ ls /lib/firmware/ | grep I2C* >> *BB-I2C1-00A0.dtbo* >> *BB-I2C1-PCA9685-00A0.dtbo* >> >> *Looks like, at least for me, I have two I2C device tree overlays which

Re: [beagleboard] BeagleBone Green Grove i2c issues

My best guess is that I2C1 is brought out to the I2C connector, so enabling BB-I2C1-00A0.dtbo should work for you. On Sun, Oct 18, 2015 at 2:43 PM, Ben Shapiro wrote: > Sadly, there does not seem to be a BBG-specific image. > > > > On Sunday, October 18, 2015 at 3:29:16 PM UTC-6, William Hermans

Re: [beagleboard] BeagleBone Green Grove i2c issues

No luck yet ? I'm doing more investigating . . . so what is the output of the command: $ cat /etc/dogtag ? If your Linux image predates Aug 11 this year, and you've not recently updated your device tree file binaries. Then loading the current BB-I2C1-00A0.dtbo may not work. If we notice the diff

Re: [beagleboard] BeagleBone Green Grove i2c issues

On 10/18/2015 05:59 PM, William Hermans wrote: My best guess is that I2C1 is brought out to the I2C connector, so enabling BB-I2C1-00A0.dtbo should work for you. On Sun, Oct 18, 2015 at 2:43 PM, Ben Shapiro > wrote: Sadly, there does not seem to be a BBG-s

Re: [beagleboard] BeagleBone Green Grove i2c issues

Make sure you have it connected to the correct Grove connector, one is i2c2 (same bus as the "cape eeprom") the other is usart2... Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed t

Re: [beagleboard] BeagleBone Green Grove i2c issues

On Sun, Oct 18, 2015 at 6:47 PM, Robert Nelson wrote: > Make sure you have it connected to the correct Grove connector, one is > i2c2 (same bus as the "cape eeprom") the other is usart2... I should also mention... Full support for the Green is with these images: http://elinux.org/Beagleboard:Bea

[beagleboard] Status of pruss in 4.1.10-ti-r21/2015-10-11 Debian snapshot?

Pruss is still broken in the 4.1.10-ti-r21 kernel, right? Does anyone know if the new remoteproc thing can be used to download existing firmware that was built with pruss in mind, and how I could modify my code to use that instead? Thanks, -- Rick Mann rm...@latencyzero.com -- For more opt

Re: [beagleboard] Status of pruss in 4.1.10-ti-r21/2015-10-11 Debian snapshot?

On Sun, Oct 18, 2015 at 7:05 PM, Rick Mann wrote: > Pruss is still broken in the 4.1.10-ti-r21 kernel, right? > > Does anyone know if the new remoteproc thing can be used to download existing > firmware that was built with pruss in mind, and how I could modify my code to > use that instead? > a

[beagleboard] Talking to BBB with OS X 10.11 (El Capitan)

Has anyone been able to connect to the BBB running OS X El Cap? The driver provided on the getting started page is long since obsolete (FTDI driver) and http://www.joshuawise.com doesn't seem to exist anymore (404). If I look at the IP address assigned to it and try to SSH in, it just times out.

[beagleboard] BeagleBone GREEN: Can't get grove devices to show up... anyone else?

Hi, I've been having a hell of a time getting the BeagleBone Green to see Grove devices connected to it. Running i2cdetect -r 0 results in the following output regardless of which Grove sensors are connected: # i2cdetect -r 0 WARNING! This program can confuse your I2C bus, cause data loss and

[beagleboard] SPI's Beginner Guide

Hi, testing different kind of sensors/modules provide the change to work with the several buses the BeagleBone Black has. Now, I'm playing with an analog light sensor connected to an ADC which communicate with BBB through SPI bus. So, the first step I need to do is enable the SPI. Then, test S

[beagleboard] long headers for BBB?

I want to attach a BBB to another larger board without cutting a hole in the board for the ethernet module as the capes do. Anyone know of a long header setup that will achieve this? A standard header with 0.1" high black plastic piece and really long pins is not good enough since there is nothi

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

Hi TJF, I am trying to use the example you provided here to sample an analog signal. With the default setting of tmr=5000, I am getting configuration error: config failed: sample rate too big It works with tmr=2 and dumps the data into 2 files. Though the data looks to be in binary format.

Re: [beagleboard] Beaglebone refusing to boot

Hi, I managed to get it to print out a new error, "bad magic", which should be 0x27051956 and is the first 4 bytes of u-boot.img. Modified u-boot to print out what it's actually getting and it varies the first few times it powers up, but then becomes consistently 0xF6EFFADE, which implies it's f

[beagleboard] Installing/booting latest Angstrom build (2015-10) on BBB

TL;DR --> How do I boot my BBB (rev C) from a recent 2015 build of Angstrom (ideally one I don't have to compile myself)? The latest Angstrom images for the BBB are dated 2013-06, and I want to get the latest version working on my BBB. I notice that the De

Re: [beagleboard] Re: Beaglebone Black : miss mii.ko and usbnet.ko so no USB to ethernet converter work !

Bingo Robert ! Sorry for time I took but I was very busy the problem was exactly the udev/rules the system recognized the asix mac address but assigned him the eth2 interface the eth1 was assigned to another asix mac address, not the mine. I changed the assignement and now everythi

[beagleboard] problem: 2015 beaglebone images & xenomai boot

Hi guys I am following these guide to install xenomai on my beaglebone SD card system:installing xenomai on beaglebone this guide uses an old image: http://debian.beagleboard.org/im

Re: [beagleboard] Kernel 4.1.9 overlays not working

Robert, I have the same question about the source of DTC 1.4.1-gXYZXYZXYZ - I installed the device-tree-overlay package into a new build (Linux beaglebone 4.1.10-bone-rt-r16 #1 Sun Oct 4 09:05:14 UTC 2015 armv7l GNU/Linux) and checked the version of dtc. It was v1.4.0. I tried running ./dtc_ove

[beagleboard] Reserving memory for writes to DDR from PRUs

For my application, I want to write from the PRU into a large set of circular buffers in the ARM DDR memory. Following various examples, I have gotten this to work for small amounts of data, but when I attempt to write "too much", I crash the Linux. To me, this is not surprising, as I don't s

Re: [beagleboard] Status of pruss in 4.1.10-ti-r21/2015-10-11 Debian snapshot?

> On Oct 18, 2015, at 17:11 , Robert Nelson wrote: > > On Sun, Oct 18, 2015 at 7:05 PM, Rick Mann wrote: >> Pruss is still broken in the 4.1.10-ti-r21 kernel, right? >> >> Does anyone know if the new remoteproc thing can be used to download >> existing firmware that was built with pruss in mi

Re: [beagleboard] Transmit buffer underflow when trying to play audio using an externally attached codec board

I've had the same problem with kernels later than 3.8. On 3.8, I switched to using ti,da830-evm-audio (davinci-evm.c, I think). My DTS (for both types of sound card) call for a 12MHz McASP master clock, but in 4.x kernels, I would actually see a 24MHz signal come off the master clock, and I thin

Re: [beagleboard] Kernel 4.1.9 overlays not working

On Sun, Oct 18, 2015 at 8:42 PM, codemonkey wrote: > Robert, I have the same question about the source of DTC 1.4.1-gXYZXYZXYZ - > I installed the device-tree-overlay package into a new build (Linux > beaglebone 4.1.10-bone-rt-r16 #1 Sun Oct 4 09:05:14 UTC 2015 armv7l > GNU/Linux) and checked the

Re: [beagleboard] Status of pruss in 4.1.10-ti-r21/2015-10-11 Debian snapshot?

On Sun, Oct 18, 2015 at 8:52 PM, Rick Mann wrote: > >> On Oct 18, 2015, at 17:11 , Robert Nelson wrote: >> >> On Sun, Oct 18, 2015 at 7:05 PM, Rick Mann wrote: >>> Pruss is still broken in the 4.1.10-ti-r21 kernel, right? >>> >>> Does anyone know if the new remoteproc thing can be used to downlo

Re: [beagleboard] Talking to BBB with OS X 10.11 (El Capitan)

On Fri, Oct 16, 2015 at 5:18 PM, wrote: > Has anyone been able to connect to the BBB running OS X El Cap? The driver > provided on the getting started page is long since obsolete (FTDI driver) > and http://www.joshuawise.com doesn't seem to exist anymore (404). If I look > at the IP address assig

Re: [beagleboard] Kernel 4.1.9 overlays not working

http://www.embeddedhobbyist.com/2015/09/beaglebone-black-updating-device-tree-files/ On Sun, Oct 18, 2015 at 7:07 PM, Robert Nelson wrote: > On Sun, Oct 18, 2015 at 8:42 PM, codemonkey wrote: > > Robert, I have the same question about the source of DTC > 1.4.1-gXYZXYZXYZ - > > I installed the d

Re: [beagleboard] Transmit buffer underflow when trying to play audio using an externally attached codec board

"buffer underflow", heh sounds a bit like an oxy- moron, . . . On Sun, Oct 18, 2015 at 6:58 PM, Rick Mann wrote: > I've had the same problem with kernels later than 3.8. On 3.8, I switched > to using ti,da830-evm-audio (davinci-evm.c, I think). My DTS (for both > types of sound card) call for a

Re: [beagleboard] Reserving memory for writes to DDR from PRUs

What you need to do. Is understand how "things" are mapped into memory. So from the gist of things, It sounds like you're creeping into memory reserved by "something else". NO one can tell, as you've not given us any code . . . On Sun, Oct 18, 2015 at 6:42 PM, Andrew Szymkowiak wrote: > For my a

Re: [beagleboard] SPI's Beginner Guide

> > *Hi,* > > *testing different kind of sensors/modules provide the change to work with the several buses the BeagleBone Black has.* Irreverent . . . *Now, I'm playing with an analog light sensor connected to an ADC which > communicate with BBB through SPI bus. * > *So, the first step I need to

[beagleboard] Re: Poor Java performance on new BBB

Hallo! Ok, but can I change the Kernel from the slow BBB without reflash the whole system with a new Image? -- 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 gro

Re: [beagleboard] Transmit buffer underflow when trying to play audio using an externally attached codec board

I’m using the v4.1.3-bone15 linux kernel with debian-8.1-minimal-armhf-2015-06-09. So yeah, it seems something broke between 3.8 and 4.1. I did look at the relevant McAsp registers and they all looked properly setup from what I could see. I'm not sure what could be wrong. Looking a the relevan