This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/PROCESSOR-SDK-AM437X: ADC1 support for am437x-gp-evm

Part Number: PROCESSOR-SDK-AM437X
Other Parts Discussed in Thread: AM4372

Tool/software: Linux

Hi all,

I am using custom board based on am437x-gp-evm. There I need to check the adc1 output, But there is no "ADC1" support  in am4372.dtsi file.

I am using latest ti-linux-sdk-4.00.00.04, how can I configure ADC1.

is  there any driver for adc1 which i can use for ADC1.

any help regarding this.

Thank you.

  • We're looking into this. Feedback will be posted here.
  • Vimal,

    The Linux Processor SDK still does not support ADC1 on the AM437x device out of the box. This support is planned for a future release but it is unclear how long it will be until it is there.

    Here is a patch that was made for v3.2.0.5 of the Linux Processor SDK that enables ADC1 on the AM437x device: e2e.ti.com/.../2082260

    For now you'll either have to forward port that patch to your current SDK or revert back to the 3.2.0.5 SDK to use the patch as-is.

    Jason Reeder
  • Thank you.

    I will try to forward port this patch. Let's see if i can get it working on newer sdk. 

  • Hi jason,

    I applied your patch to newer sdk and build it. Building was proper but I am not finding any devices in "/sys/bus/iio/devices/" .

    Previously I can read the adc0 values from /sys/bus/iio/device/*device0/....... But not there is no such devices.

    dmesg | grep adc shows nothing. You have changed a lot " in adc0 driver also "drivers/iio/adc/ti_am335x_adc.c". 

    Now from where i can read the values. Where these device will be registered?

    thanks.

  • Vimal,

    I just spent some time trying to manually apply the patch to the latest SDK as well. It appears like there are too many changes (especially in the drivers/mfd/ti_am335x_tscadc.c file) for the older patch to be usable.

    It looks like you will either need to move back to the 3.2.0.5 version of the SDK to apply that patch or wait for the official support to show up in an upcoming SDK release.

    Jason Reeder