Hi,
I am using BB Black RevC. It is offered by Element 14; its OS is Debian.
The BBB is used to collect some sensor data and forward it to a server
through WiFi interface; the WiFi dongle used is TP-Link TL-WN821N.
The BBB is required to function at 7/24 basis. So I run a script inside BBB
to
Hi Guys,
Thank you all for your replies.
I found after issuing command: echo cape-bone-iio
/sys/devices/bone_capemgr.9/slots
The ADC can be read from /sys/devices/ocp.3/helper.15/AIN* files just as
pointed out
in http://hipstercircuits.com/reading-analog-adc-values-on-beaglebone-black/
--
.
On Tuesday, March 3, 2015 at 2:04:34 AM UTC+8, sven.n...@gmail.com wrote:
One more thing to check is that the firmware is available and gets loaded.
Then it has worked for me.
/Sven
Den måndag 2 mars 2015 kl. 11:17:05 UTC+1 skrev Dajiang He:
Hi,
I have a BB Black RevC with its original Debian OS
Hi,
by issuing command: echo cape-bone-iio /sys/devices/bone_capemgr.9/slots,
now i can see iio:device0.
However, when I ran
echo 1 /sys/bus/iio/devices/iio\:device0/scan_elements/in_voltage0_en
echo 256 /sys/bus/iio/devices/iio\:device0/buffer/length
echo 1
Hi
following ur guide, it almost worked.
However, when issuing command
echo 1 /sys/bus/iio/devices/iio\:device0/buffer/enable
System gives me error: echo: wrrite error: Invalid argument
I already use root to issue to command, and strangely echo 1
Hi,
How come in my system, there is no /sys/bus/iio/devices/iio:device0?
Under /sys/bus/iio/devices/, there is only one file iio_sysfs_trigger,
which is a symbolic link to some other directory.
Is there any configuration I need to do?
I am using the latest BB black Rev C by Element14. It is OS
