• State Resolved
  • Locked Locked
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 103 subscribers
  • Views 426 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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:

AM3352: ADC detection ability

AM3354: Inquiry about ADC (Linux SDK)

Takayuki Miyazaki
Genius 10120 points
Part Number: AM3354

Hi Experts,

Our customer developed their system with AM3354BZCZA100 for a long time ago. Customer is using internal ADC, they are checking the voltage with built-in ADC. Recently, customer noticed that,  ADC’s value shows “0” Occasionally even though the voltage is output normally when checking voltage repeatedly. Customer is using TI Processor SDK 1.0.0.3 (very old version). Customer mentioned, this issue occurs with STEPDELAY (default value 0x098) in linux-driver, and it seems this issue was resolved with 0xFFF. Customer would like to know the reason why this issue was resolved with STEPDELAY (large value configuration). Therefore, customer is asking following inquiries.

  1. Customer is storing ADC data into FIFO (inside the CPU). When customer set large value to STEPDELAYxx(Open Delay bits), does it extend the effective period of the data written from the ADC to the FIFO?
  2. Or does it extend the validity period of the data that the user reads from the FIFO?
  3. According to TRM, customer is considering It seems to extend the validity period of the data written from the ADC to the FIFO. Is that correct?

Customer would like to know the reason why this issue was resolved with STEPDELAY (large value), as well. Sorry, I just translated customer’s inquiries.

I’ll really appreciate if you will share expert’s advice/comments on their inquiries.

Best regards,

Miyazaki