• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 52 subscribers
  • Views 494 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.

Recommendation for MCU selection to collect DDC232 ADC data

Khoi Ly10
Intellectual 620 points

Other Parts Discussed in Thread: DDC232, TMS320F280049, TMS320F28378D

Hi Ti,

I was talking to the ADC forum and I was recommended to use the DDC232 ADC chip. This BGA chip supports 20-bit resolution sampling of 32 ADC channels continuously upto 6kHz. My plan is to daisy chain 4 of these ADC's to an MCU that is fast enough to collect 128 channels data at the rate of 500Hz.

Is an MCU sufficient or do I need an FPGA? I have not proprammed FPGA before, so I would like to have a very powerful MCU or an FPGA that is simple enough to learn. If I could get a few options to select from, it is great.

Thank you,

Khoi Ly

  • 0
    TI__Guru 62975 points

    Khoi,

    Given your numbers, the minimal throughput needed to read the samples would be 128 ch x 20b x 500Hz = 1.28Mbps.  C2000 MCUs should be able to handle this bit rate just fine.

    A good starting point would be the 100MHz TMS320F280049 device from the Piccolo series. There are lesser and greater options in Piccolo series in terms of price and performance in case F28004x doesn't fit.

    The Delfino series of devices provide higher performance of up to 200MHz dual-core TMS320F28378D in case you are in need of more processing power than the Piccolo series.

    We can offer more suggestions based on your feedback.

    -Tommy

  • 0 in reply to tlee
    Intellectual 620 points

    Thank you for your reply.

    Is there a module that also incorporates wifi/ bluetooth/ZigBee capability? I was supposed to include this in the MCU selection as well but I forgot. If I have to add a WIFI/Bluetooth/ZigBee transceiver, which should I pick that can expedite my prototyping speed the fastest in terms of supports, reference designs, example codes, documentations, etc.

    Which one do you think is popular in terms of documentations, supports, and community.

    Khoi Ly

  • 0 in reply to Khoi Ly10
    TI__Guru 62975 points

    Khoi,

    For wireless connectivity, you would want to look at the SimpleLink MCUs and wireless modules. I will move your post to the Wireless Connectivity Forum.

    -Tommy

  • 0 in reply to tlee
    Intellectual 620 points
    Hi Tommy,

    I have not received any notification regarding my post being moved to a new forum.

    Sincerely,

    Khoi Ly
  • 0 in reply to Khoi Ly10
    TI__Guru 62975 points
    Khoi,

    I can confirm that this post is in the Bluetooth forum from the URL and site navigation cues. However, it looks like we have not attracted the attention of the experts to weigh in on device recommendations.

    Can you start a new post in here with your 1.28Mbps serial port and wireless connectivity requirements? That should get the ball rolling again.

    -Tommy
  • 0 in reply to tlee
    Intellectual 620 points
    Thanks for your reply.

    I wonder if it is better to get a microcontroller with built-in bluetooth/wifi to collect data from DDC232 and send the data to a PC wirelessly, or it is better to collect the data using Piccolo/Delfino and send the data over SPI to a wifi capable microcontroller (ESP32 is the one I am using) which can then send the data over the network?

    Thanks,

    Khoi Ly
  • 0 in reply to Khoi Ly10
    TI__Guru 62975 points
    Khoi,

    I think you would need to determine the optimal solution for yourself based on your own weighting of costs and requirements.

    For example, if you have a short deadline and are already familiar with a particular family of devices, it might be better for you to continue using what you know and extend the capabilities with a few additional components. Or if cost is a concern, you can pick the solution that uses the cheapest parts.

    A good way to narrow down options is to eliminate options that do you not meet your throughput and processing requirements. It is also easy to eliminate components that may have incompatible (or at least inconvenient) support parameters like recommended supply voltages.

    -Tommy