I'm having an issue with the nDRDY pin not going low after every conversion. I'm taking a single sample at the 2.5 SPS interval (~406ms for the sample). It seems that sometimes my firmware doesn't detect a low nDRDY signal within 800ms, at which time I timeout and report an error. I can verify this behavior on a scope. I have a few questions:
1) Is there an errata for this chip that may describe something like this? I wasn't able to find one.
2) I'm using the START command (the START/SYNC pin is tied to ground) to kick off a conversion. How do I tell if the conversion actually started? I can check to see if nDRDY is high after the START command but that doesn't really tell me much because nDRDY is also high after startup.
3) My application requires very very low power so I have the whole chip on switched power so I'm cutting power to it between conversion cycles. After I apply power, the firmware waits for the the power supply to settle, then waits 5ms for the ADS124S08 to boot, then sends a WAKEUP followed right away by a RESET command, then waits 5ms, then sets ups up the registers for my conversion (and reads back to verify) and starts the conversion with a START command. Is there anything wrong with this sequence?
4) Is the nDRDY pin a push-pull output? Or should I use a pull-up or pull-down on the line?
Incidentally I'm also seeing the same behavior in continuous mode. Not sure if this is relavent or not.