• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 46 subscribers
  • Views 154 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

ADS131M08: The technology support need for ADS131M08

ADS131M08: Drivers and support (Linux)

Clark Dunson
Prodigy 20 points
Part Number: ADS131M08
Other Parts Discussed in Thread: ADS131E08

Tool/software:

Hello E2E;

We are on the verge of committing to this part, but I just noticed that my eyes have played tricks on me.

linux/drivers/iio/adc/ti-ads131e08.c

does not say: ti-ads131m08. I see now that ads131e08 is a completely different part than ads131m08. I doubt that the driver is compatible.

We are on Linux Arm64 with Yocto. Raspberry PI is a Broadcom BCM2711. We want 8 channels @1kHz over SPI.

All I see is:

hal.h

hal.c

ads131m0x.h

ads131m0x.c

Have I missed anything?  Seems simple enough. Or have we made the wrong choice? If so, I need to put the brakes on hard, as our schematic is essentially finished.

Thank you!

Clark

  • 0
    TI__Mastermind 45915 points

    Hi Clark,

    The timing requirement for ADS131M08 and ADS131E08 are quite different. I'm not sure if you found these files on Github. If so, you can find more information over there:

    To interface the ADS131M0x devices with a microcontroller (MCU), the firmware or software engineer needs to know how to correctly configure their MCU's serial peripheral, sequence the serial commands, and control the SPI timing of command bytes to the ADC. Provided code examples in hal.c functions utilize the TI SimpleLink SDK and allow for quick integration with TI SimpleLink MCUs.

    You can also find the example code in C on TI.com.

    BR,

    Dale

  • 0 in reply to Dale Li
    Prodigy 20 points

    Thank you very much Dale;

    We'll go over all of this today, We have the GPIOs for DRDY and SYNC/RESET all mapped out, and the four SPI wires, so that is looking good. The DRDY interrupt handler seems to be required, so sorting that is next. Will get back if we have issues

    Clark

  • 0 in reply to Clark Dunson
    TI__Mastermind 45915 points

    Hi Clark,

    Sounds good, let me know if you have any further questions.

    BR,

    Dale

  • 0
    Prodigy 40 points

    Update:

    This is all mostly working now. The hal.h & hal.c files work out well with libpigpio, and the structure of them, and the included notes are spot on. THANK YOU! The only issue I had is that the libpigpio routine: intGpioDetISRFunc() requires the addition of 512 (gpio += 512;) in order to use the deprecated /sys/class/gpio interface, which it does.

  • 0 in reply to Clark Dunson
    TI__Mastermind 45915 points

    Hi Clark,

    Thank you for your update. I do not know what the routine you mentioned is. If you have any trouble to communicate with the ADC, please sharing your timing. I can definitely help you on that.

    BR,

    Dale