So, i2c_bus=3,100 probably won't work for your case. You'll probably have
replace "3" to reflect the proper I2C bus you're using. But in case you're
using a bus thats already in use ( 0, or 2 ), I'd probably not try the
above.
On Tue, Nov 15, 2016 at 10:45 PM, William Hermans
http://permalink.gmane.org/gmane.linux.distributions.gumstix.general/60029
> The signals on the bus are the same as shown in my previous posted
picture.
> The error is as follows:
> error I2C_RDWR errno=121(Remote I/O error)
Generally, that means that the remote didn't respond properly
tomorrow i can running thermal with i2c in bbb ,therefor im clean one
file.there are file erased.
when i run file again .showed
thermal1= bus.read_byte_data(address, reg1)
IOError: [Errno 121] Remote I/O error
anyone know to fix it?
--
For more options, visit
Can't say I'm interested in the BBGW _at_all_. But I do think the BBG is
pretty nice.
On Tue, Nov 15, 2016 at 10:30 PM, Robert Nelson
wrote:
> On Nov 15, 2016 11:28 PM, "William Hermans" wrote:
> >
> > Jason,
> >
> > What's the compelling reason for
On Nov 15, 2016 11:28 PM, "William Hermans" wrote:
>
> Jason,
>
> What's the compelling reason for those of us who already have well
established images to shift to this one ? Honestly, I can't see one.
Besides . . . apt-get upgrade . . .
It's just the new default 'latest'
Jason,
What's the compelling reason for those of us who already have well
established images to shift to this one ? Honestly, I can't see one.
Besides . . . apt-get upgrade . . .
On Mon, Nov 14, 2016 at 1:54 PM, Jason Kridner wrote:
> Thanks to Robert and the rest of the
4.6.2 is easy to build from source Robert. It just takes a little bit of
time to compile directly on a beaglebone is all. 2-3 hours, is all.
On Tue, Nov 15, 2016 at 8:16 PM, Robert Nelson
wrote:
> Hey Everyone,
>
> Over the weekend, there was a few requests to bump our
9) More useful links
Camera user manual.
http://www.linksprite.com/upload/file/1274419957.pdf
Camera programming python examples
http://learn.linksprite.com/pcduino/arduino-ish-program/uart/taking-pictures-with-a-pcduino-a-linksprite-jpeg-color-camera-ttl-interface/
UART setup
8) Setting up a link sprite LS-Y201 camera continued.
Some searching on the internet lead me to this site(
http://bradsmc.blogspot.com/2013/05/taking-larger-pictures-with-pcduino.html).
I used his work to create two python programs 1st to take pictures and the
2nd to change the picture sizes.
7)Setting up a link sprite LS-Y201 camera I bought.
It took some time to get the UART pins to work on the BBG.
ISSUE FOUND:
The UART pins are not enabled by default as UART pins. I tried several
methods, and ended up following the instructions posted here
A follow up on this. Looking at the uBoot printouts, I thought there was 2
things I could do to speed up the boot time:
- Zero the bootdelay (currently set to 2s)
- Locate uEnv.txt/boot.scr on the root to save .2s (...), since currently
it's looking in 2 different locations
To change bootdelay, I
Hey Everyone,
Over the weekend, there was a few requests to bump our version of nodejs.
So everyone knows, the v0.12.x is going eol shortly:
https://github.com/nodejs/LTS/blob/master/README.md
So i started looking at all our default nodejs packages and started
patching them to support 3
resolved, 100pF cap on SPI0 clock near the grove connector causing
reflections, resulting in double-clocking data. sigh.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe
Remoteproc and RPMsg are kernel modules. Remoteproc/RPMsg live in the
kernel, but they can communicate with user space via character device files
and the sysfs virtual file system.
The PRUSSDRV is totally different, not related to Remoteproc in any way to
my knowledge.
Best introductory page
I understand that bringing up GPIOs low is good practice. I meant when I
set the P8_11 using "config-pin P8_11 pruout" the pin is automatically
pulled high it appears. Is there a way to set it as a "pruout" but as a low
pruout to start. It appears to be defaulting to "HI" mode when set to
Cool, I'll be moving to that image, thanks for the heads up!
Regards,
Greg
On Tuesday, November 15, 2016 at 10:49:41 AM UTC-5, Jason Kridner wrote:
>
> Shouldn't be any deltas, but can you use 2016-11-06 from
> https://beagleboard.org/latest-images because we are standardizing on
> that image
It's generally considered good design practice to bring up GPIOs low. But
there are exceptions. I'm not sure what the PRU will do when it is
disabled.
I did the same thing months ago, and I do remember LEDs being lit or dimly
lit after boot. Ultimately I got past that concern and it didn't
> On Nov 15, 2016, at 8:06 AM, Greg wrote:
>
>
> Just my advice, especially for a newbie PRU person (maybe even an experienced
> one too), don't touch the Device Tree! At least not directly:
>
> https://github.com/cdsteinkuehler/beaglebone-universal-io
>
> (Note
> On Nov 15, 2016, at 6:25 AM, Chris Green wrote:
>
> Jason Kridner wrote:
>> [-- text/plain, encoding quoted-printable, charset: UTF-8, 56 lines --]
>>
>>
>>
>>> On Nov 15, 2016, at 3:16 AM, Lee Armstrong wrote:
>>>
>>> Is there a
Thanks for the detailed response that helped clear up a bit of confusion I
was having. I've also been rereading through your pdf. I got the
remote_proc up and running again. I started playing around with config-pin
and "Universal IO" and was able to successfully toggle the pins how I
wanted.
Just my advice, especially for a newbie PRU person (maybe even an
experienced one too), don't touch the Device Tree! At least not directly:
https://github.com/cdsteinkuehler/beaglebone-universal-io
(Note the path to slots is not the same for 4x kernels)
I've been using the Debian 8.6 IOT
Try this:
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
On Monday, November 14, 2016 at 10:39:58 PM UTC-5, James Strawson wrote:
>
> Excellent! I'm glad the device trees made it in.
>
> Is it possible to have an IOT image (preferably already set to flash) up
> there as well? I see
Jason Kridner wrote:
> [-- text/plain, encoding quoted-printable, charset: UTF-8, 56 lines --]
>
>
>
> > On Nov 15, 2016, at 3:16 AM, Lee Armstrong wrote:
> >
> > Is there a way to update an existing BB to this version without re-flashing
> > at all?
> On Nov 15, 2016, at 3:16 AM, Lee Armstrong wrote:
>
> Is there a way to update an existing BB to this version without re-flashing
> at all?
You can run off of microSD.
You can also, depending on the age of your image, do 'sudo apt-get update; sudo
apt-get upgrade'.
Is there a way to update an existing BB to this version without re-flashing
at all?
On Monday, November 14, 2016 at 8:54:26 PM UTC, Jason Kridner wrote:
>
> Thanks to Robert and the rest of the BeagleBoard.org community!
>
> http://beagleboard.org/latest-images/
>
> The above URL is now updated
25 matches
Mail list logo