if someone who has the time and know how, could quickly test would be
appreciated;
I have made a quick program, which uses the user LEDs
same behavior; works great when executed from console, does not work when
executed at boot time
main.cpp
//
#include
#include
#include
#include
#i
running BeagleBoard.org Debian Image 2015-03-01
startup (from
https://learn.adafruit.com/adding-a-real-time-clock-to-beaglebone-black/set-rtc-time)
is invoked via;
systemd
bash script has a delay, increased it to 2 min still same non-running of the
PRU.
given the large delay; I have logged
Testing with various Windows SCP utilities fails in a similar way. The
transfer starts out fine and then rapidly throttles down to extinction.
WinSCP, SmarTTY
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Group
Transfer using several Windows utilities (WinSCP and SmarTTY) fail
similarly - the transfer starts out find and then throttles itself to
exinction.
On Thu, Jun 25, 2015 at 4:16 PM, Phil Mills wrote:
> I have a Beaglebone Black with a fresh flash of the 2015-03-01 Debian
> image (bone-debian-7.8
If you fed 3.3V in through the header, that would have been what fried it
for good.
We can replace the processor and anything else that is needed. We can
stipulate that the eMMC be left as is and just boot off of SD to test out
the board..
Gerald
On Thu, Jun 25, 2015 at 4:27 PM, Jonathan Ross
I have a Beaglebone Black with a fresh flash of the 2015-03-01 Debian image
(bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img) that I cannot scp or
rsync large files to.
>From my Wheezy 64-bit host VM, I try to scp a 27MB file to the Beaglebone
via ethernet and the transfer stalls out after <1
I think I fried the PRU (single blip on the PWR LED upon power on then
nada). I tried feeding 3.3v to the board via the header, but still nothing.
Is there a sneaky way to power up a BBB long enough to get data off it?
Cheers,
--
For more options, visit http://beagleboard.org/discuss
---
You re
Hi folks. I previously had some code working that wrote serial out to an
RS485 shield. I'm setting up a new beagle bone and I can't get the same
code to work. When I write, I get an errno of 11 (Resource temporarily
unavailable).
I must have set something up on the previous beagle bone, but I
> I haven't progress much yet. I am hoping that I can copy the audio cape dts
> files to get it hooked up, and then get the uda1380 into the kernel somehow.
> I have seen the code for the > driver in the linux source.
Not sure if you are committed to the UDA part. There is another board (crea
Guys, this solution did not work for me. I updated the
/etc/init.d/led_agng.sh script but it looks like I do not have the
/usr/bin/led_acc program at all. Just wondering if I should remove the
script using update-rc.d as Simon suggests or get a hold of
/usr/bin/led_acc somewhere.
Best regards,
Hi guys
i'm a newbie in embedded system but i would like to make my BeagleBone
Black work with MMA8451 sensor.
Which are the steps to make BBBAndroid work with the sensor?
I recompiled the kernel after i added the sensor driver taken
from
http://www.freescale.com/webapp/sps/site/prod_summary
oh sorry thanks, I was not able to find my post. I thought I forgot to send
my first message.
Ok, I will try, thanks a lot!
Le jeudi 25 juin 2015 09:24:53 UTC-4, RobertCNelson a écrit :
>
> On Thu, Jun 25, 2015 at 6:36 AM, >
> wrote:
> > Hello,
> >
> > Is it possible to have GCC 4.8 on my Be
On Thu, Jun 25, 2015 at 10:23 AM, wrote:
>
>>
>> http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-
>> kernel.git;a=shortlog;h=refs/heads/ti-linux-4.1.y
>>
>> I'm hoping to to backport much of ^^ so v4.1.x will be around for awhile..
>> (until the next lts release next summer)
>>
>
> OK. That
>
> http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-
> kernel.git;a=shortlog;h=refs/heads/ti-linux-4.1.y
>
> I'm hoping to to backport much of ^^ so v4.1.x will be around for awhile..
> (until the next lts release next summer)
>
OK. That sound ideal. I am going to work off your 4.X.
Wh
On Thu, Jun 25, 2015 at 9:58 AM, wrote:
>> > root@arm:~# aplay -l
>> > List of PLAYBACK Hardware Devices card 0: EVM [DA830 EVM],
>> > device 0: AIC3X tlv320aic3x-hifi-0 []
>> > Subdevices: 1/1
>> > Subdevice #0: subdevice #0
>>
>> Sweet! ;)
>
> :) - BYW I assume that device presenc
The signal on the bus is the same.
Just the name is different.
So to talk to the part using Linux, use the address in "7-bit" format,
which for your part is 0x21.
If you are writing in C, you will use i2c-dev and ioctl
If you are writing in Python 2.7, you will use SMbus and something like the
Ad
> > root@arm:~# aplay -l
> > List of PLAYBACK Hardware Devices card 0: EVM [DA830 EVM],
> > device 0: AIC3X tlv320aic3x-hifi-0 []
> > Subdevices: 1/1
> > Subdevice #0: subdevice #0
>
> Sweet! ;)
:) - BYW I assume that device presence means that it really is in place and not
getting
Tushar?
> Does the page @ http://narcissus.angstrom-distribution.org/ open ? I am
> unable to see Narcissus site. Does this site work any more ? Is there an
> alternative to build custom images
> like what was possible on Narcissus earlier ?
There's a repo on Github: https://github.com/Angstr
Le Thursday 25 June 2015, terra a écrit :
> ur lucky day, just did it :)
Thanks! There are a lot of things I still need to understand (mainly about
default interrupt mapping), But your example helps!
Thanks,
--
Frédéric
--
For more options, visit http://beagleboard.org/discuss
---
You r
On Thu, Jun 25, 2015 at 8:43 AM, wrote:
> Hi Robert
>
>> Then from /boot/uEnv.txt:
>>
>> cape_enable=bone_capemgr.enable_partno=BB-BONE-AUDI-02
>
> Cool. Glad to be able to add something to the mix. It looks like it is hooked
> up at boot.
>
> root@arm:~# cat /sys/devices/platform/bone_capemgr/s
Hi Robert
> Then from /boot/uEnv.txt:
>
> cape_enable=bone_capemgr.enable_partno=BB-BONE-AUDI-02
Cool. Glad to be able to add something to the mix. It looks like it is hooked
up at boot.
root@arm:~# cat /sys/devices/platform/bone_capemgr/slots
0: PF -1
1: PF -1
2: PF -1
3:
On Thu, Jun 25, 2015 at 6:36 AM, wrote:
> Hello,
>
> Is it possible to have GCC 4.8 on my BeagleBone Black? I have the Debian
> distribution and I try those 2 commands it's not working
>
> sudo apt-get install gcc (gcc is already the newest version) ==> My current
> GCC version is 4.6.x
> sudo a
Does the page @ http://narcissus.angstrom-distribution.org/ open ? I am
unable to see Narcissus site. Does this site work any more ? Is there an
alternative to build custom images like what was possible on Narcissus
earlier ?
--
For more options, visit http://beagleboard.org/discuss
---
You r
Hello,
Is it possible to have GCC 4.8 on my BeagleBone Black? I have the Debian
distribution and I try those 2 commands it's not working
sudo apt-get install gcc (gcc is already the newest version) ==> My current
GCC version is 4.6.x
sudo apt-get install gcc-4.8 (unable to locate package)
An
Same as is noted on the X15 WIKI. End of September..
http://elinux.org/Beagleboard:BeagleBoard-X15
Gerald
On Wed, Jun 24, 2015 at 2:49 PM, Mathieu Chouinard
wrote:
> Hi,
> I'm wondering what is the current status of the X15?
> Mathieu
>
> --
> A te quaeso, sicut in Aeneidos libro quarto Aenea
On Thu, Jun 25, 2015 at 7:58 AM, Robert Nelson wrote:
> On Thu, Jun 25, 2015 at 6:16 AM, wrote:
>>
>>> I haven't progress much yet. I am hoping that I can copy the audio cape
>>> dts files to get it hooked up, and then get the uda1380 into the kernel
>>> somehow. I have seen the code for the
On Thu, Jun 25, 2015 at 6:16 AM, wrote:
>
>> I haven't progress much yet. I am hoping that I can copy the audio cape dts
>> files to get it hooked up, and then get the uda1380 into the kernel somehow.
>> I have seen the code for the > driver in the linux source.
>
> Not sure if will be of any
Hi,
I wanted to know if the HDMI works well with the BBB and Kernel 4.1 ?
Because, I'm having issue with the Kernel 4.1 and a clone of BBB .
The kernel say :
[7.816539] tda998x 0-0070: set_page 000a err -121
[7.873069] tda998x 0-0070: set_page 000a err -121
[7.933820] tda998x 0-0070:
> I haven't progress much yet. I am hoping that I can copy the audio cape dts
> files to get it hooked up, and then get the uda1380 into the kernel somehow.
> I have seen the code for the > driver in the linux source.
Not sure if will be of any use but I've just opened a PR on the RCN overlay
hii
even am trying to connect 4x4 matrix keypad did you
achieved any result regarding this...please share the information
to connect the keypad
Thanks in advance
Regards
Mallikarjuna G
On Friday, 12 September 2014 11:38:25 UTC+5:30, sv.se...@gmail.com wrote:
>
>
> Hi,
>
> I have connecte
How do you invoke the startupscript? (Maybe it's to early during boot.)
On Thu, Jun 25, 2015 at 10:35 AM, terra ÜÝÜ wrote:
> Hi,
>
> I have a basic application which use PRU1. program works 100% when executes
> as "root" from user space (via putty).
> I have a bash start up script, which synchron
*i2cdetect -r 0*
*i2cdetect -r 1*
*i2cdetect -r 2*
*not possible*
*i2cdetect -r 3*
2015-06-20 13:28 GMT+03:00 Erkan Güzeler :
> Thanks a lot for your reply,
>
> I clearly understand when I reading some paper about beagle board i2c.
> So I changed i2c bus from 4 to 3.
> When I tried to "i2cdetect
Hi,
I have a basic application which use PRU1. program works 100% when executes
as "root" from user space (via putty).
I have a bash start up script, which synchronizes with RTC and executes my
program.
cat /usr/share/rtc_ds3231/clock_init.sh
#!/bin/bash
sleep 15
echo ds3231 0x68 > /sys/class/i
ur lucky day, just did it :)
// This is a nearly-minimal PRU program. It delays for five seconds, then
// notifies the host that it has completed, then halts the PRU.
//
// The idea is to have a program that does something you can see from user
// space, without doing anything comp
34 matches
Mail list logo
