• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 81 subscribers
  • Views 739 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.

Choosing MCU

Lior Barak
Prodigy 40 points

Hello,

 

I need help with selecting MCU for a new medical device. with our older devices we used 8051 but now we want to use ARM Cortex-M.

our needs are:

  1. At least 128K flash memory for code
  2. SPI, I2C, USB build in interfaces
  3. JTAG for code loading and debugging
  4. TIMER/COUNTER I/O - specially to generate PWM signal at 50KHz minimum (as high as possible)at resolution >12bits
  5. No need for internal ADC and DAC
  6. minimal baud rate 9600

 

please offer me the best cost effective complete solution (hardware, software, tools and evaluation board) in order to start the development.

 

your help is much appreciated.

 

Regards,

Lior  

  • 0
    TI__Guru 57255 points

    Hi Lior,

    Everything in your message, except one item, would point me toward having you look at the MSP432* series of TI devices...

    What do you mean by resolution of the PWM as >12bits?  Are your referring to duty cycle resolution?  (ie 12bits of duty cycle resolution when the PWM period is 50kHz? - about 5ns duty cycle steps)


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Prodigy 40 points
    Hi Brett,

    Thanks for your reply.
    You are right regarding the PWM it is illogical request, and we decided to implement the PWM with dedicated component external to the MCU.
    Anyway, the MSP432* still see a bit of an overkill for our application. Here is more specific requirements:
    • 128K FLASH or more for firmware.
    • 16K memory or more for dynamic data.
    • Interface must include: I2C bus, SPI bus, RS232 Bus, USB. (Bluetooth or Wifi are optional)
    • GPIO (General Purpose IO).
    • Counter/Timer.
    • Watch-dog
    • no need for PWM output
    • ~20 ADC Input
    • Evaluation board and developing tools

    A few more questions:
    1. Do you have the ability to generate Drivers automatically?
    2. In one of your MCU we saw that you have channel that support touch screen, this ability could also interest us for future development features of the product. Please provide more information.
    3. Developing tools - What is the minimum environment needed to start working asap?

    Regards,
    Lior
  • 0 in reply to Lior Barak
    TI__Guru 57255 points

    Hi Lior,

    I see two paths:

    1) Use a C2000 MCU - perhaps something like the F28069.  It will meet almost all your needs, including the ability to generate your PWM waveform.  The HRPWM feature of this device enables an ability to edit duty cycle in steps of about 150ps, typically.  The one thing is that it has 16 ADC input channels vs 20.

    2) Use a MSP432 or other TI MCU.  The system that you're starting to think about (with a separate chip for generating the PWM, etc) seems to match with this path and MCU choice.

    This is the C2000 device forum, so you will get good support from the C2000 device here.  If you decide to go with a different TI device family, I would recommend posting to that device's E2E forum for more specific guidance.


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Prodigy 40 points

    Thanks Brett, it is very helpfull.