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.

ADS8330/ SPI interface

Other Parts Discussed in Thread: ADS8330, OMAP-L137

I'm trying to get the OMAP-L137 to drive the ADS8330 via the SPI1 interface.

I need to transmit slower than the SPI-provided XEVT event. Ideally, I'd like the INT output of the chip to trigger an EDMA event that will transmit the 16-bit word.

I'm not having any success because I do not see INT driven low coming out of the chip. I'm writing a control word of 0xe4bd. I can see the SCLKs and the MOSI data. It is correct. I had expected to see INT drop low as per Figure 2 on the data sheet. When I put a scope on it, it never drops low.

CONVST is high all the time. Chip select brackets the clocks. I've added the smallest delay front and back of chip select because I was not able to read the configuration register with out some delay. Now I can read the configuration register back and it looks good. Anybody have a clue why INT is not changing?

  • The Configuration Register (CFR) Map table (Table 4 of the datasheet) references Pin 10 repeatedly when I think it means Pin 4 (EOC/INT). At least the pinout of the chip suggests that. Could someone at TI verify that the table means Pin 4?

  • Hi,

    I'd recommend to reset the converter after power up first by sending a 0xE4BC in your case. The next transfer would be your 0xE4BD. Please let me know if this helps.

    Regarding the pinout: Dependent on the chip package you are using EOC/INT# is pin 4 for the QFN package and pin 10 for the TSSOP package (data sheet page 10). The description in table 4 refers to the TSSOP package.

    Regards,
    Lars