Worst case is prior to the chip being powered up, or while the rails are
being sequentially raised.
In that case, internal power can be a low as zero, and ESD diodes on each
pin can conduct at 0.7 Volts.
You damage individual pins or can avalanche the whole chip if you can drive
enough current.
On 17/12/17 00:34, Graham wrote:
> An FTDI 3.3 Volt USB to UART0 connection will not blowup or hurt anything.
> You an hook it up and leave it hooked up, and not have to worry about
> damaging the Pocket Beagle,
> A 10K pullup to +3.3 V is also OK, but not actually required for the
> FTDI cable to
An FTDI 3.3 Volt USB to UART0 connection will not blowup or hurt anything.
You an hook it up and leave it hooked up, and not have to worry about
damaging the Pocket Beagle,
A 10K pullup to +3.3 V is also OK, but not actually required for the FTDI
cable to work.
Something like the
Following your example I'm trying to set 400KHz on my i2c-1 too. I have a
Beaglebone Black WIRELESS that loads am335x-boneblack-uboot.dtb as overlay.
UBOOT: https://pastebin.com/hA4RbNUm
1) Decompilation: dtc -I dtb -O dts -o am335x-boneblack-uboot.dts
am335x-boneblack-uboot.dtb
2) Actually my
Actually seems that the mCciPort (first parameter in LEP_OpenPort) doesn't
stand for the I2C bus but for a user-defined id number for the camera.
So actually the problem moves to "How do tell the SDK to read from I2C-2
instead of I2C-1"?
The SDK uses libmpsse, I think.
In order to test the
