• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 79 subscribers
  • Views 916 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.

MSP432P401R: Is there a document like SLAC710c for MSP432?

David Roberts
Intellectual 350 points

Part Number: MSP432P401R

I have spent 3+ months developing software running on an MSP430FR5994 Launchpad... without using MSP430 DriverLib. Now I want to convert that S/W to the MSP432P401R Launchpad and add new features like floating point, output to graphic displays, etc. that are possible with the new, faster H/W.

I believe that there is a tool that helps the conversion and I will start researching it shortly. But I don't just want to convert my S/W, I also want to add to it. I need something like SLAC710c, but focusing on MSP432 instead of MSP430. I need a bunch of standalone examples... no SDK stuff, no DriverLib stuff, no RTOS stuff, no MSP432 ROM stuff... just standalone C code examples... I haven't found them yet.  I want code that I enter into CCS with my very own fingers. Code that I understand completely.

  • 0
    Genius 3850 points

    you are in luck: 

    it covers a bunch of chips, including msp432.

  • 0 in reply to Danny F
    Intellectual 350 points
    Thanks, Danny; I will examine them. You have quite a selection and I am thankful for what you have provided; not everything is covered (I2C, SPI, ADC, LPM,..) but it's a great place to get my bearings. As I understand it, there needs to be a new interrupt table, when converting to the MSP432; when I glanced at your files, I didn't notice one. Did you use interrupts? Does TI plan to provide examples for non-{SDK/DriverLib/RTOS} users?
  • 0 in reply to David Roberts
    Genius 3850 points

    not sure what you meant by "new interrupt table" so two possible answers:

    1) when the chip was introduced, the start-up files provided by TI does not contain specific names for the ISRs - they are all IntDefaultHandler , aka the Luminary way of doing things. Later releases do have peripheral specific names.

    2) the driverlib way of doing things is to copy the isr to the ram and then "register" your isr. I took the advance of the peripheral specific names and used them directly, no ram-based interrupts.

    for example, you will see this line in ta0_oc.c:

    //tmra0 ccr1..6 isr
void TA0_N_IRQHandler(void) {

    you should find TA0_N_IRQHandler() in the start-up file.

    This approach is consistent with how CMSIS and other vendors handle interrupts, and requires no extra code.

  • 0 in reply to Danny F
    Genius 3850 points
    similar approach exists for the interrupt-based uart (tx-only) routines.
  • 0
    TI__Guru 53575 points
    You can find register level examples in the resource explorer along with the other examples you mention:

    dev.ti.com/.../

    Regards,
    Chris
  • 0 in reply to Chris Sterzik
    Intellectual 350 points

    Thanks to all who replied.

    I have since discovered slac698... exactly what I was looking for, but for some reason couldn't find until today. More than any book or code on the internet, slac710c helped me to understand how the MSP430 worked. I hope that I will be able to say the same about slac698.

    I also discovered

    www.microdigitaled.com/ARM/MSP432_ARM/Code/MSP432_red_codes.htm

**Attention** This is a public forum