On the PocketBeagle, both I2C-1 and I2C-2 are both brought out to the
headers and both enabled by default.
I don't know that there is any reason to prefer one over the other on the
PocketBeagle.
--- Graham
==
On Sat, Feb 10, 2018 at 7:55 PM, Stuart Longland wrote:
> On 11/02/18 11:43, Graham w
Robert nelson had answered this back in december
I searched this once and must have missed this.
Robert Nelson
12/27/17
Other recipients: simo...@gmail.com
- show quoted text -
We've moved to u-boot overlays, to achieve the same follow:
https://elinux.org/Beagleboard:BeagleBoneBlack
This is the DTB file on the green downloaded yesterday.
I dont understand that if its disabled why is there a /dev/i2c-1 file ?
They fixed the numbering starting with the 9.1 images from what i can read.
If it needs to be enabled how would one go about enabling it ?
On 2/10/2018 6:43 PM, Graham w
On 11/02/18 11:43, Graham wrote:
> I am not an expert at Device Tree stuff, but this is what I think I know.
> I2C-0 is intended for internal board management, so sort of reserved,
> except as a last resort.
> I2C-1 is available, but not enabled, on the BBB and is
> enabled/implemented on the Pocke
Wulfie:
I am not an expert at Device Tree stuff, but this is what I think I know.
I2C-0 is intended for internal board management, so sort of reserved,
except as a last resort.
I2C-1 is available, but not enabled, on the BBB and is enabled/implemented
on the PocketBeagle, so you could always loo
I will keep looking into this.
more infos
I took the current DTB file and decompiled it
I looked at the I2C sections
i2c0 = "/ocp/i2c@44e0b000";
i2c1 = "/ocp/i2c@4802a000";
i2c2 = "/ocp/i2c@4819c000";
i2c@44e0b000 {
compatible = "ti,omap4-i2c";
More infos
after reading a bit and seeing where to look I may have found the error msg.
root@beaglebone:/home/debian# dmesg | grep i2c
[ 0.817817] omap_i2c 44e0b000.i2c: could not find pctldev for node
/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_i2c0_pins, deferring
probe
[ 0.818857]
p8 and p9 pins start at pin number 1
can you try again?
On 2/10/2018 10:33 AM, marrius9...@gmail.com wrote:
> Linux beaglebone 4.9.45-ti-r57 #1 SMP PREEMPT Fri Aug 25 22:58:38 UTC
> 2017 armv7l GNU/Linux
>
> I was trying to add a i2c device to bbb. After several failed
> attempts, I measured the
Linux beaglebone 4.9.45-ti-r57 #1 SMP PREEMPT Fri Aug 25 22:58:38 UTC 2017
armv7l GNU/Linux
I was trying to add a i2c device to bbb. After several failed attempts, I
measured the power on the rail. The voltage
from pin0 to pin 3 shows 2.47v. As well frompin 0 to pin 5 which suppose to
be 5V DD
Can anybody with a green or black verify the odd behavior i am seeing on
my greens and blacks ?
I am using the latest IOT image
root@beaglebone:/home/debian# uname -r
4.9.78-ti-r94
I use i2ctools and issue the commands
root@beaglebone:/home/debian# i2cdetect -r 0
WARNING! This program can conf
Thanks for those suggestions, but that's way too much work. I guess I'll just
design a minimal enclosure for my specific needs.
> On Feb 9, 2018, at 18:58 , ybeag...@rehut.com wrote:
>
> Older versions of Eagle can do 3D exports. The process flow I have used with
> Eagle6 is -
>
> Generate a
11 matches
Mail list logo
