Hi All
Have only owned and played with the BBB for one week.
The uSD has been configured with
bone-debian-8-11-lxqt-4gb-armhf-2019-01-07-4gb.img
The on board eMMC has been wiped completely.(interferes with Libpruio)
Installed the development environment on the uSD and can compile and run
the
Run it from the plug in card?
Plug in the size you need.
Expand the installed image to make the whole card available to you.
--- Graham
==
On Saturday, February 23, 2019 at 2:22:13 PM UTC-6, aa...@cnccraft.co.uk
wrote:
>
> Yes you were right. I now finally have a debian jessie system on my
OK sorry I thought you were referring to config pin on I2C.
On Sunday, February 24, 2019, 1:08:56 PM EST, Adrian Godwin
wrote:
I2C uses clock stretching but I'm not aware of any SPI interfaces that do it.
However, it may be that the hardware is shared.
On Sun, Feb 24, 2019 at 5:22
I2C uses clock stretching but I'm not aware of any SPI interfaces that do
it. However, it may be that the hardware is shared.
On Sun, Feb 24, 2019 at 5:22 PM 'Bruce Snyder' via BeagleBoard <
beagleboard@googlegroups.com> wrote:
> It's probably for clock-stretching. Both pins clock and data
Thanks for that. I've done something similar for another Melexis device,
the MLX90640 32x24 sensor.
However, I've used a rather bizarre interface : an arduino that does the
I2C operations remotely via the usual USB-serial interface.
It also handles a couple of ST vl53l1x distance sensors. This
In case it's useful for anyone else, I have ported code for the
MLX90621 (4x16 pixel remote IR temperature sensor) from the RPi (talks
directly to the BCM hardware) to use standard Linux I2C devices (eg:
/dev/i2c1) so it works on the 'Bone and other boards with standard
Linux I2C support.
Tested
It's probably for clock-stretching. Both pins clock and data need to go
both ways.
On Thursday, February 21, 2019 at 9:58:12 AM UTC-5, waplu...@gmail.com
wrote:
>
> Thanks - you saved my day! I just ran into the same quirk. Truly bizzare
> that the SPI_CLK pinmux has to be set as an input
