On Mon, Jan 25, 2016 at 11:00 PM, Soapy Smith wrote:
> I am very confused, is that not one of the
>
> Recommended Debian Images
>
> at the very top of the beagleboard.org web page???
>
> http://beagleboard.org/latest-images
I'm not sure what you are confused about..
You reported some bugs, i rep
Hello all,
Is there a good resource (besides this list! :) that would help me
understand what to remove/disable from the stock Debian Wheezy distro, on a
BeagleBone Black, to arrive at a barest-minimum/rock-solid setup to run a
dedicated app, as an embedded device?
Background:
I've developed
I am very confused, is that not one of the
Recommended Debian Images
at the very top of the beagleboard.org web page???
http://beagleboard.org/latest-images
On Monday, January 25, 2016 at 9:06:27 PM UTC-5, RobertCNelson wrote:
>
> On Mon, Jan 25, 2016 at 6:17 PM, >
> wrote:
> >
> > I can't
I'm very very confused, is that the one of the official working
Recommended Debian Images
On Monday, January 25, 2016 at 9:06:27 PM UTC-5, RobertCNelson wrote:
>
> > Debian 8.2 (BeagleBone, BeagleBone Black, Seeed BeagleBone Green, Arrow
> > BeagleBone Black Industrial - 2GB SD) 2015-11-12
>
He is also using an accompanying 74HC595 8 bit serial shift register in a 4
bit (interface DB4-DB7 configuration).
--
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 t
Newhaven Model: NHD-0216K1Z-NSB-FBW-L.
--
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+u
On Mon, Jan 25, 2016 at 10:09 PM, Dean wrote:
> Interesting. Just reloaded with an updated kernel and this time it did not
> crash. All the same similar problems remain. William all things equal if you
> found the book remedial I would like to challenge you on that. Buy yourself
> an LCD and see i
I'm a programmer, and not an electronics engineer. However, I've already
done bare metal LCD with an MSP430, so I doubt the BBB would present much
of a challenge . . .
On Mon, Jan 25, 2016 at 9:09 PM, Dean wrote:
> Interesting. Just reloaded with an updated kernel and this time it did not
> cras
Interesting. Just reloaded with an updated kernel and this time it did not
crash. All the same similar problems remain. William all things equal if
you found the book remedial I would like to challenge you on that. Buy
yourself an LCD and see if you can replicate what Derek Molloy did there in
Dean,
By the way, I think it's great that you seem to be using a virtual machine
for test development. This is something I do myself too.
In fact I wrote a smallish web server like app in C to display CANBUS data
out over a websocket. Initially this code was developed on an i386 virtual
machine,
>
> *The code came from Derek Molloy's Exploring Beaglebone -Tools and
> Techniques Chapter 9 page 362 Listing 9-10. *
>
Yeah, I own the book too, but to be honest, I've only read a couple pages.
Mostly because most of the material is remedial for me. I've been
programming since the early 90's, an
Thanks Robert. I will give it another whirl.
--
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 beaglebo
On Mon, Jan 25, 2016 at 6:17 PM, wrote:
>
> I can't access 192.168.7.2 after flashing Debian 8.2 to eMMC.
> How do I enable it?
> I loaded up the latest image to an SD card.
> Runs great when booted from SD card, both E:\ and 192.168.7.2 methods work.
> Edited /boot/uEnv.txt to enable flash
> Fla
I saw the same behavior and accidently found a workaround which may help. I
was testing wireless drivers on the BBB at the time.
I run my BBB attached to a powered USB hub which is plugged into the host PC
running either Windows 7 or 10; or Ubuntu Linux 14.04.3. Delian 8.2 is
running dns
The code came from Derek Molloy's Exploring Beaglebone -Tools and
Techniques Chapter 9 page 362 Listing 9-10. Regarding a decent book on how
to spidev have you any recommendations? I am the first to admit I am a
novice and it goes without saying that we all started somewhere as
frustrating as t
On Mon, Jan 25, 2016 at 6:57 PM, Dean wrote:
> apt-get install build-essential
>
>
> In 3.8.x spidev2.0 could be used on spi1, but with 4.1.x+ the "first"
> is spidev1 (even if spi1 over spi0..) >
>
>
> SPIDevice *busDevice = new SPIDevice(2,0); //Using second SPI bus (both
> loaded)
>
> The code
- I can't access 192.168.7.2 after flashing Debian 8.2 to eMMC.
- How do I enable it?
- I loaded up the latest image to an SD card.
- Runs great when booted from SD card, both E:\ and 192.168.7.2 methods
work.
- Edited /boot/uEnv.txt to enable flash
- Flashed to eMMC.
- B
Thanks Bit Pusher. Interesting read, appreciate it.
On Thursday, 21 January 2016 01:30:46 UTC, Bit Pusher wrote:
>
> Robert, after many many hours I was able to get almost everything working
> (well enough) in Debian 8.2; most of the details are described at:
>
> https://groups.google.com/forum/
Ok, so without seeing any code no one can really answer a question related
to your problem. However, I will say that errors in the realm of "invalid
argument" or "file not found" are development 101 type problems. Also, if
your code is not exiting with an error on these problems I will say that
you
We will look into it.
Gerald
On Jan 25, 2016 6:03 PM, "Kjetil Haarbye" wrote:
> Observation on the BB-X15 schematic:
> P3 ball is shown connected to GPIO2_17 in schematic.
> GPIO2_17 in AM5728 (SoC) DS is at ball H5.
> P3 ball in AM5728 (SoC) DS is connected to GPIO2_7.
> Ergo, by utilizing comm
We will look into it.
Gerald
On Jan 25, 2016 5:51 PM, "Kjetil Haarbye" wrote:
> Observation on the BB-X15 schematic:
> P3 ball is shown connected to GPIO2_17 in schematic.
> GPIO2_17 in AM5728 (SoC) DS is at ball H5.
> P3 ball in AM5728 (SoC) DS is connected to GPIO2_7.
> Ergo, it's simply missp
*pt-get install build-essential *
*In 3.8.x spidev2.0 could be used on spi1, but with 4.1.x+ the "first" is
spidev1 (even if spi1 over spi0..) > *
* SPIDevice *busDevice = new SPIDevice(2,0); //Using second SPI bus (both
loaded)*
*The code is trying to open /dev/spidev2.0, but it's not
*apt-get install build-essential *
*In 3.8.x spidev2.0 could be used on spi1, but with 4.1.x+ the "first" is
spidev1 (even if spi1 over spi0..) > *
* SPIDevice *busDevice = new SPIDevice(2,0); //Using second SPI bus (both
loaded)*
*The code is trying to open /dev/spidev2.0, but it's no
Thanks William and Brian for your help.
Mesh point is added to the supported interface modes list and worked
without problem after changing the kernel from 3.8 to 4.1.
Utku
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to th
Observation on the BB-X15 schematic:
P3 ball is shown connected to GPIO2_17 in schematic.
GPIO2_17 in AM5728 (SoC) DS is at ball H5.
P3 ball in AM5728 (SoC) DS is connected to GPIO2_7.
Ergo, by utilizing common sense, we can conclude it's simply misspelled and
*should
be renamed from GPIO2_17 to
Thanks Bit Pusher your post is interesting. I think I'm going stick with
the previous version of the linux kernel for now. I can see me having the
plough hours of my time into Debian 8.2 which I don't currently have at the
moment, not to mention my lack of Linux knowledge!
On Thursday, 21 Janu
Observation on the BB-X15 schematic:
P3 ball is shown connected to GPIO2_17 in schematic.
GPIO2_17 in AM5728 (SoC) DS is at ball H5.
P3 ball in AM5728 (SoC) DS is connected to GPIO2_7.
Ergo, it's simply misspelled and *should be renamed from GPIO2_17 to
GPIO2_7*.
Best regards,
Kjetil Haarbye
--
Thanks RobertCNelson, appreciate your input. Downgrading certainly works.
It's a shame the adafruit library won't work with Debian 8.2.
On Tuesday, 19 January 2016 23:57:28 UTC, RobertCNelson wrote:
>
> On Tue, Jan 19, 2016 at 5:54 PM, Robert Hurd > wrote:
> > I upgraded my BeagleBone Black ima
Great answer!
It came a little late for the project that I was working lol.
But even so, it was a good explanation and will still help many people.
Thanks,
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
My mistake, I wasn't clear at all. Allow me to restate...
There is one line return after issuing the command sudo dhclient eth2, and
then the shell locks up.
There is no message returned. Only a blinking cursor and nothing further
happens.
Let's see if I can paste in what it looks like:
user@
On Mon, Jan 25, 2016 at 12:42 PM, Soapy Smith wrote:
> sudo dhclient eth2 (or whatever is obviously the BBG from looking at
> ifconfig)
>
> There is one line return and then nothing happens (after entering password
> due to sudo).
"nothing happens"... on success, yes "nothing happens"..
check:
sudo dhclient eth2 (or whatever is obviously the BBG from looking at
ifconfig)
There is one line return and then nothing happens (after entering password
due to sudo).
On a healthy board, at the first "sudo dhclient ethX", there is a quick
line feed and no messages.
The second time, I get
RTN
On Mon, Jan 25, 2016 at 12:14 PM, Robert Nelson wrote:
> On Mon, Jan 25, 2016 at 12:05 PM, Soapy Smith wrote:
>> I've always seen marginal success in USB connectivity with BBB. I recently
>> acquired a couple of BBG, at first I thought these were solid, but now I am
>> seeing problems.
>>
>> The
On Mon, Jan 25, 2016 at 12:05 PM, Soapy Smith wrote:
> I've always seen marginal success in USB connectivity with BBB. I recently
> acquired a couple of BBG, at first I thought these were solid, but now I am
> seeing problems.
>
> There is a difference seen in the host computer from the shell com
I've always seen marginal success in USB connectivity with BBB. I recently
acquired a couple of BBG, at first I thought these were solid, but now I am
seeing problems.
There is a difference seen in the host computer from the shell command
ifconfig -a.
Here is ifconfig -a for a working BBG:
et
You can run X server on the tablet, and display X applications from
BBB to the tablet using TCP transport over USB. The touch input works
as a mouse, but is a little strange (touches vs mouseclicks).
On Fri, Jan 22, 2016 at 5:23 AM, wrote:
> Hello. I was wondering if it's possible to use a table
I have had wireless working on a 3.8 BBB for quite some time and I wanted
to move to a v4 kernel in the hope that the "lagginess" of the wifi
connection would be reduced. I loaded another board with the LTS RT v4
kernel, did apt-get install wireless-tools wireless-regdb crda, and put my
ssid an
On Mon, Jan 25, 2016 at 10:37 AM, Lindsay Lohan wrote:
> On the image downloads page it says..
>
> To turn these images into eMMC flasher images, edit the /boot/uEnv.txt file
> on the Linux partition on the microSD card and remove the '#' on the line
> with 'cmdline=init=/opt/scripts/tools/eMMC/in
On the image downloads page it says..
To turn these images into eMMC flasher images, edit the /boot/uEnv.txt file
on the Linux partition on the microSD card and remove the '#' on the line
with 'cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh'
but "Debian 8.2 (BeagleBone, BeagleBone
I am running the Ubuntu 14.04.3 image from Dec 11, 2015, on a Beaglebone
Black, with updated packages and updated kernel. System details below. When
I insert an SD card with 2 Linux partitions (and formatted ext4
filesystems) on it after boot, it fails to be recognized. The following
message a
It's nice to see that we were in the right path. Thank you!
On Monday, January 25, 2016 at 2:56:24 PM UTC+1, RobertCNelson wrote:
>
> On Mon, Jan 25, 2016 at 7:02 AM, Iñigo Martínez > wrote:
> > Since we started working with several BeagleBone Black boards we have
> been
> > facing some weird
Hi,
I have replicated the PRU cape board EEPROM device and created another
circuit board for my application.
In order to make it work with the Beagle Bone Black, i need a way to copy
the 78 byte file from the EEPROM of a PRU cape board.
Is there anyway i can do reads and writes to this EEPROM de
We had a image of debian in BeagleBone Black. it was giving *no space issue*
on installation of OpenCV. upon looking we found we must use SDCard
storage. inserting SD Card didn;t resolved issue, we formatted SD Card via
Disk Utility, while SD Card was still in BBB. Now BBB was not starting up
We had a image of debian in BeagleBone Black. it was giving *no space issue*
on installation of OpenCV. upon looking we found we must use SDCard
storage. inserting SD Card didn;t resolved issue, we formatted SD Card via
Disk Utility, while SD Card was still in BBB. Now BBB was not starting upo
I am not sure about this but I think I read somewhere that QT 5.3.x does
not support the "qws" anymore. I run QT 5.3.1 with -platform linuxfb
only and it works. I did compile with eglfs but have not been able to
get that to work either.
-- Original Message --
From: em.ce.kwad...@gmail
On Mon, Jan 25, 2016 at 7:02 AM, Iñigo Martínez wrote:
> Since we started working with several BeagleBone Black boards we have been
> facing some weird problems. Sometimes the board got stuck when it started to
> boot.
>
> There is no much information regarding this problem. This thread has some
>
Since we started working with several BeagleBone Black boards we have been
facing some weird problems. Sometimes the board got stuck when it started
to boot.
There is no much information regarding this problem. This thread has some
information:
https://groups.google.com/forum/#!topic/beagleboa
Hi Robert
You're just the guy I'd like to talk to. Do you have any thoughts on why
the mounting of /dev/mmcblk0p1 to serve as a virtual mass storage partition
might have been disrupted? Does adding a cape - specifically for an LCD
screen - change the set of files that are generated or run durin
48 matches
Mail list logo
