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.

MSP430F5438A: New type of tool to support MSP430s development

Part Number: MSP430F5438A
Other Parts Discussed in Thread: MSP430F5418A,

I have been recommended by TI's customer support to post this request in this forum.  Here is the problem.

My group is developing a tool that generates uniquely customized hardware monitors for MSP430 processors family.  The customization is for each particular hardware design.  We have  been using previous versions of this tool in several MSP430 designs over several years and now we plan to make it accessible to other designers.  So far we have done the version for MSP4305438A and its variations (MSP430F5418A, 5419A, 5419A, 5435A, 5436A, 5437A, 5438A-EP and 5438A-ET).  Currently we are working on a version for the MSP4301xx/161x but I am not sure if this is the best choice for supporting new designs.

The development of these type of tools for a particular processor family takes considerable effort and expense.  Given the wide variety of the MSP430's we are seeking advice in selecting the next family of processors on which we should work, based on your perceived market needs for new product designs.  Your help on the best way of orienting our efforts will be highly appreciated.

  • 1. Can you tell me how you monitor the MSP430? Using JTAG and MSP430.dll?

    2. The latest MSP430 is MSP430FRxx series.

  • Eason:

    Thanks for your prompt reply...!

    1) It is a command/response tool using any of the USCIA's (TXD & RXD) connected to an ad-hoc external little board that converst to RS232 levels and any terminal emulator (i.e.: hypeterminal, etc.).  If the specific design already has a serial connection it can be used for this purpose also, so no external RS232 converter would be needed.

    2) The software that we put together creates this command-response code that allows exercising all the various I/O and communication devices of the chip (I2C, SPI, IRDA, PWM, input bits, output bits).  All this is based on inputs from the user to describe how the different capabilities of the chip are used (port bits used as inputs, outputs, interrupts or not, etc.).  The command names are also customized for the user specific application  (i.e.: "MOTOR TEMPERATURE", "OVEN DUTY CYCLE", etc., etc.)

  • Hi Jose,

    It seems like a communication protocol based on UART to control the MSP430 peripheral. So customer will use it to monitor the status of MSP430 by combing this part of code into their application.

    I must tell you that we are developing a new platform for MSP. It will be a huge platform and has good compatibility accross different devices. As it is NDA information, I think you can refer to our TI sales to get more about it.

    Eason

  • Jose, don't know if you aware of Mailbox system that support all new msp430 families (F5xx, F6xx and FRAM). It is covered by slaa763 (Interfacing With the MSP430 JTAG Mailbox (JMB) System). Mailbox not need any target setup, leaving all peripherals free. Communication is going by SBW/JTAG interface (even if it is locked by fuse). Here you can see how micro side is simple (my Mailbox - CDC bridge in action)...

    https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/746951/msp430fr2422-pc-software-using-msp-fet-for-communication-via-jtag-mailbox-jmb

    I guess that Eason is right about FRAM popularity.

  • "New platform" sounds intriguing. Can anyone join?

  • Thanks again Eason.  I will follow up with TI sales regarding your tip on the new platform.

    Regarding the tool we are working on, I probably did not explain well the purpose and capabilities of this tool, which has been used already in multiple designs involving MSP430F5438A and we want ot expand to other processors (we like the MSP family so we want to target other processors of this family first).  Perhaps calling this tool "monitor" is not too descriptive and might lead to confusion.  It is not intended to interact with application software at all.  Moreover, it is intended essentially as a hardware testing tool to be used well before any application software might be available.  The idea is to decouple the schedules of the hardware and software development teams.  This hardware test firmware is customized to test each of elementary functions of the product so the hardware design can be validated in all its aspects (waveforms, behavior inside temperature chamber, etc.).  Since it is commanded through a terminal emulator can be automated with text scripts using very intuitive commands adapted to each product in questions, which is something that the test teams appreciate a lot.

  • Thanks for the tips, Zrno.  I was aware of slaa763 and thought that JMB could be more a possible complement than a replacement of the capabilities of our tool but I will definitely take a second look.

  • Hi Jose. OK I think it is a tool for test whether the MSP430 is good or not.

    Actually, I think Zrno's advice is quite good. Internally, we also use JTAG to test the MSP430 in test mode for every device. Then, I think you can handle a whole MSP430 family.

  • Hi Bruce,

    What do you mean join? It is like platform products. A little same like what ST is doing. If you can connect to our TI sales, I think they would like shrare more details.

    Eason

  • Zrmo:

    I understand the benefits that you explain and I see that such tool has a place in the developers armamentarium to help in the actual hardware and software development.  The tool we are working on has quite a different purpose and advantages for the target audience.  It is extremely user friendly for the test group and requires almost no knowledge about the processor or even what the processor does.  The commands are adapted to the specific product and is almost 100% guaranteed that will work the first time, which is especially useful to verify the hardware design.  It is not intended to test the MSP itself (which is assumed good) but all the peripherals surrounding the MSP.

    In fact, if anyone in this forum is currently working in an MSP430F5438A (or similar one from this family, which are the only ones currently supported with our tool) I would like to provide with a version of the tool to seek feedback from you guys.  I would need detail info on the use of I/O bits, USCI's, ADC channels, clocking speed, timers used as PWM, etc. in the form of excel sheets or similar.  In case of interest I can give more details.

    Back to your advice regarding the FR based processors.  Do you have some advice regarding which specific MSP processors (within the FR based ones) might be the most popular for new designs?

    Thanks and regards,

    Jose

  • I would advise the FR235x/FR215x, which is mostly saled recently. It have 4 OPAs and 4 DAC internal, more like a MCU plus some  AFE. It is mostly used in some mix-signal application.

**Attention** This is a public forum