This is because unless I'm mistaken AIN7 is configured as a touchscreen PIN
by default. Either way only AIN0-AIN6 are configured as general purpose
ADC's. Passed that, I', not sure of the ramifications of setting AIN7 as a
general purpose ADC either. Read the AM335x TRM before jumping in.
http://elinux.org/images/6/65/Spruh73c.pdf
debian@beaglebone:~$ sudo cp /lib/firmware/BB-ADC-00A0.dtbo .
debian@beaglebone:~$ dtc -I dtb -O dts BB-ADC-00A0.dtbo > BB-ADC-00A0.dts
debian@beaglebone:~$ nano BB-ADC-00A0.dts
/dts-v1/;
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black",
"ti,beaglebone-green";
part-number = "BB-ADC";
version = "00A0";
exclusive-use = "P9.31", "P9.40", "P9.37", "P9.38", "P9.33",
"P9.36", "P9.35", "tscadc";
fragment@0 {
target = <0xdeadbeef>;
__overlay__ {
status = "okay";
adc {
ti,adc-channels = <0x0 0x1 0x2 0x3 0x4 0x5
0x6>;
};
};
};
__fixups__ {
tscadc = "/fragment@0:target:0";
};
};
On Mon, Oct 12, 2015 at 3:49 PM, Nikos <[email protected]> wrote:
> Hello, I have installed 4.1.10-bone16 from RCN's git on my custom board.
> All digital I/Os have been configured via device tree, but I cannot access
> AIN7 as I used to with pre-dtb kernels. All suggestions about going through
> */sys/devices/bone_capemgr.*/slots* seem to not apply, as there is no
> such path on my installation. Any ideas on what I might be missing?
>
> Thanks
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
