I have a BBB that sometimes fails to have a useable network interface at
power up. Removing power and reapplying power does resolve the issue. Is
there a fix for this issue? Would an upgrrade to Rev C fix this?
...
--
For more options, visit http://beagleboard.org/discuss
---
You
The enumeration and thus the mapping of I2C devices is confusing. Bus 1
uses /dev/I2c-2 etc. Is there any way to fix this so that the hardware
matches the software? Could this be hardcoded in the OS?
The current mapping of devices is most disturbing.
--
For more options, visit
I think that the issue stems from older versions of debian based linux and
the newer version that use a device tree.
If the echo statement fails then:
To enable the I2c-1 on the BeagleBone Black Rev A, B and C:
1. Rev A/B: Open the file /media/BEAGLEBONE/uEnv.txt in an editor
add the following to rc.local
echo BB-I2C1 /sys/devices/bone_capemgr.9/slots
On Thursday, November 13, 2014 9:13:51 PM UTC-6, ngocta...@gmail.com wrote:
I use I2C-Tools to detect the i2c like:
root@android:/ # i2cdetect
-l
to the receiver via the RS232 port.
Without a way to get the status of the TV set, that makes the BBB unusable
in this case.
On Thursday, December 25, 2014 11:47:37 AM UTC-6, Charles Steinkuehler
wrote:
On 12/25/2014 9:36 AM, Richard-tx wrote:
I just installed cec-client and cec-client
12:16 PM, Richard-tx rich.a...@gmail.com
javascript: wrote:
Since the cec library and utils packages do not work, maybe those
packages should be removed from the list of installable packages.
Um that's not how Debian works... Just because one device doesn't
support
I just installed cec-client and cec-client reports that there are no
devices available. Is there some trick to getting cec-client to work?
# cec-client -l
DEBUG: [ 2] trying to autodetect all CEC adapters
Found devices: NONE
--
For more options, visit
Sorry, I forgot to mention that this is on a BBB- B and I am running
Ubuntu 13. I can certainly use another OS if necessary.
On Thursday, December 25, 2014 9:36:06 AM UTC-6, Richard-tx wrote:
I just installed cec-client and cec-client reports that there are no
devices available
I also tried debian and cec-client does not work with that either.
On Thursday, December 25, 2014 9:36:06 AM UTC-6, Richard-tx wrote:
I just installed cec-client and cec-client reports that there are no
devices available. Is there some trick to getting cec-client to work?
# cec-client
I want to read the power status of the HDMI connected TV or monitor. I can
do this use a Rpi and cec-client but it appears the cec-client is not
supported on the BBB.
What would be the easy way to determine if the connected TV or monitor is
powered on or off?
richard
--
For more options,
I just flashed Ubuntu 13.10 and the performance is back to normal. Compile
time of 42m38s.
I will flash Ubuntu 14 again and retest.
On Tuesday, September 16, 2014 10:13:20 AM UTC-5, Richard-tx wrote:
Unles I flashed it wrong twice in a row. I can't see how I could have
botched the job
The issue isn't Ubuntu but the libwxgtk3.0-dev package vs the
libwxgtk2.8-dev package. 3.0 apparantly has a bunch more stuff.
Sorry for the false alarm.
On Monday, September 22, 2014 11:15:37 AM UTC-5, Richard-tx wrote:
I just flashed Ubuntu 13.10 and the performance is back to normal
back to Debian . .
.
On Mon, Sep 15, 2014 at 10:00 AM, Richard-tx rich.a...@gmail.com
javascript: wrote:
Here is pstree -A
pstree -A
init-+-acpid
|-avahi-daemon---avahi-daemon
|-cron
|-dbus-daemon
|-dhclient
|-7*[getty]
|-rsyslogd---3*[{rsyslogd
javascript::
From: Richard-tx rich.a...@gmail.com javascript:
Reply-To: beagl...@googlegroups.com javascript:
beagl...@googlegroups.com javascript:
Date: Sunday, September 14, 2014 at 5:05 AM
To: beagl...@googlegroups.com javascript: beagl...@googlegroups.com
javascript:
Subject: [beagleboard
.
On Mon, Sep 15, 2014 at 12:38 AM, Richard-tx rich.a...@gmail.com
javascript: wrote:
Here is the output from vmstat 2
You can see where I start the build.
# vmstat 2
procs ---memory-- ---swap-- -io -system--
--cpu-
r b swpd free buff cache
I just installed Ubuntu 14.04 (eMMC flashed) and something seems wrong. I
have a software package that I compile. When I compile it under Debian,
it takes about 45 minutes to complete. Now with Ubuntu 14 it has takes
76-78 minutes. Is there something that I should look at or do? I did add
I forgot to mention that this is on a BBB.
On Sunday, September 14, 2014 7:02:17 AM UTC-5, Richard-tx wrote:
I just installed Ubuntu 14.04 (eMMC flashed) and something seems wrong. I
have a software package that I compile. When I compile it under Debian,
it takes about 45 minutes
On Friday, May 30, 2014 10:30:00 AM UTC-5, William Hermans wrote:
If a person can not figure this out on their own, they probably deserve to
get rooted, or whatever else happens to them. Some would also argue
removing root.
--
For more options, visit http://beagleboard.org/discuss
Removing root would certainly make it secure.
usermod -d / root
userdel -r root
will make it absolutely secure. Not terribly useful but very secure.
That also brings up the #1 dumbest idea in computer security.
#1) Default Permit
Read more at:
I need to create a transparent rs-232 connection from my pc to a remote
device. I thought that the BBB would be a good solution.
I need to connect the serial port to a BBB which then connects to a remore
BBB over wifi and then out the BBB serial port. I need to do this without
logging into
I am using ttyO0 as a serial console for another linux machine. When the
BBB boots, it sends out messages out ttyO0 which is connected to another
machines console. Since a getty is running and the messages get echo'd
back, uboot reacts to those messages which stops the boot process..
So the
The OS is Wheezy.
On Friday, May 2, 2014 9:40:31 PM UTC-5, Richard-tx wrote:
I am using ttyO0 as a serial console for another linux machine. When the
BBB boots, it sends out messages out ttyO0 which is connected to another
machines console. Since a getty is running and the messages get
The way my BBB works is like this:
To power up the BBB from OFF when powered from the 5 v jack, I have to
press the power button.
To power up using the mini-usb connector, all I have to do is turn on the
USB power.
My question is this. Is there a way to have the BBB automatically power up
Have you created a partition and a file system on the USB stick?
On Monday, April 21, 2014 5:27:30 AM UTC-5, Sanghyuk Lee wrote:
hello
I installed ubuntu 12.04 in emmc memory. because I need sdio interface
for another device.
But BBK cannot mount usb stick memory.
When
I see nothing wrong with your interfaces file. I can't think of a thing
that would prevent it from reconnecting on reboot. What does dmesg say?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
There are a few ways to alleviate the congestion.
1 - remove unwanted packages The X windows stuff takes up a lot of space
for example.
2 - move various dirs to a USB drive or SD card. /opt and /var are two
good candidates. /usr could be done but that requires some
experimentation. If
When it comes to wifi and ARM devices and debian, there is one interfaces
file that I use. So far it has worked every single time.
auto lo
iface lo inet loopback
iface eth0 inet static
address 10.232.1.81
netmask 255.255.255.0
gateway 10.232.1.1
auto wlan0
allow-hotplug wlan0
iface wlan0
WHen it comes to wifi and ARP devices and debian, there is one interfaces
file that I use. So far it has worked every single time.
auto lo
iface lo inet loopback
iface eth0 inet static
address 10.232.1.81
netmask 255.255.255.0
gateway 10.232.1.1
auto wlan0
allow-hotplug wlan0
iface wlan0
me (Richard-tx change)
9:31 AM (less than a minute ago)
When it comes to wifi and ARM devices and debian, there is one interfaces
file that I use. So far it has worked every single time.
auto lo
iface lo inet loopback
iface eth0 inet static
address 10.232.1.81
netmask 255.255.255.0
As far as I am concerned the BBB is inapproprite as a firewall To keep
performance up as high as possible, two high speed (1 gig) NIC cards are
needed. USB is not high speed.
On Tuesday, April 1, 2014 4:25:05 PM UTC-5, Mike Bell wrote:
On 04/01/2014 05:02 PM, vignesh murali wrote:
I just
I have a strange one.
I am using a Dell U2410 monitor. It just so happens that I have the same
monitor described at http://elinux.org/Beagleboard:BeagleBoneBlack_HDMI
I loaded the image
https://rcn-ee.net/deb/microsd/wheezy/bbxm-debian-7.4-2014-03-27-2gb.img.xz
on my BBB
When the HDMI
X desktop.
We can mark this solved..
Richard
On Friday, March 28, 2014 8:42:34 AM UTC-5, RobertCNelson wrote:
On Fri, Mar 28, 2014 at 8:32 AM, Richard-tx
rich.a...@gmail.comjavascript:
wrote:
I have a strange one.
I am using a Dell U2410 monitor. It just so happens that I have
Google got tired of me searching for debian lde x11 display problem I
finally tried setting the video mode to auto using xrandr and that fixed
it. Go figure.
Richard
On 28 March 2014 14:42, Robert Nelson robert...@gmail.com
javascript:wrote:
On Fri, Mar 28, 2014 at 8:32 AM, Richard-tx
Yes, I am on the Rpi site as well.
I decided to try a BBB. The BBB has certain features the RPI does not;
like multiple UARTs. I have a terminal server that died on me so I am
making one from a BBB.
The only thing I wish is that this forum were hosted on something like
phpBB3. Google
I bought a BBB about 3 weeks ago. Was impressed enough that I bought two
more. I have a few Rpis is use around the house as well so I have a little
experience with SBCs Anyway. all three BBB has been flawless. No problems
at all.
I did discover one thing. Of all the Linux distros out
This is one of those things that should be documented a little better.
Assuming you are using ubuntu or debian, here is the command.
echo BB-I2C1 /sys/devices/bone_capemgr.*/slots
That should do it.
On Friday, January 10, 2014 5:45:17 AM UTC-6, Jyotirmaya Joon wrote:
i2c2 file is not
I am porting a piece of software to the BBB. To make my life easy, I would
like to know if there is some predefined compiler macros that would
identify the compilation platform which in this case is a Beaglebone Black.
I know that __arm__ is defined but that isn't good enough. I am porting
I see all manner of topics referenceing ttyO0 as the console device, but I
don't want the boot messages to spew out the RS232 port. I would prefer
that the boot messages appear on the screen or be logged to a
fileanything but have those boot messages go to the serial port.
If this is
This issue is very reminiscent of a serial port issue that occurred in the
early days of SYSV rel 3 on Intel. What would happen was if the baud rate
was high enough, the interrupts would occur so frequently that the kernel
would be preempted which would cause the OS to hang. The fix at the
the answer is to use tty0 tty0 is the screen (hdmi display)
On Thursday, March 20, 2014 6:58:52 AM UTC-5, Charles Steinkuehler wrote:
On 03/20/14 02:39, Richard-tx wrote:
I see all manner of topics referenceing ttyO0 as the console device, but
I
don't want the boot messages to spew
I think you are going about it wrong. I would start by adding a device to
the bus and them with the basic commands like i2cdump, i2cget, etc, control
it.
If you want to learn Linux internals, that is great, but start at the
device driver. assuming you know how the kernal works.
richard
On
41 matches
Mail list logo
