• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 80 subscribers
  • Views 1280 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.

CCS/MSP432P401R: systick_interrupt_gpio_blink Example Only Works After Reset

Hunter Long61
Prodigy 225 points

Part Number: MSP432P401R

Tool/software: Code Composer Studio

Hello Everyone,


The systick_interrupt_gpio_blink example project found under the Driver Library examples in MSP432Ware works great for me with the Launchpad development board. The little LED blinks as it should.

However, we have a board we designed with the MSP432 on it that we are debugging with a MSP-FET. With this board, the same program doesn't work. For some reason the SysTick_Handler() function never gets called.
I found that if I click software reset during debugging it begins to work however. I tried going to Properties/Debug and checking Reset the target on a program load or restart and this also works. Now when I debug into the board it works the first time without having to click software reset.

My question is, why do the two boards behave differently, with our custom board requiring this extra step and the Launchpad not?  Also, why isn't reset the target on a program load or restart enabled by default if the ISR won't work without it?

Thanks!

Hunter

  • 0
    TI__Guru 63851 points

    Hunter,
    How does the reset/jtag lines compare with your board and he Launchpad and/or the target board, www.ti.com/.../slau571a.pdf ? I am looking into the differences between the XDS110 (launchpad) and the MSPFET+ARM Adapter.

    Chris

  • 0 in reply to Chris Sterzik
    Prodigy 225 points

    Thanks!

    We aren't using an ARM adapter exactly, we are going from the MSP-FET to a Tag-Connect cable as shown here http://www.tag-connect.com/Materials/TC2050-IDC-430-NL%20Datasheet.pdf. The Tag-Connect cable then connects to the MSP432 as shown in this image.

  • 0
    Guru 92251 points

    Hunter Long61 said:
    The systick_interrupt_gpio_blink example project found under the Driver Library examples in MSP432Ware works great for me with the Launchpad development board. The little LED blinks as it should.

    However, we have a board we designed with the MSP432 on it that we are debugging with a MSP-FET. With this board, the same program doesn't work. For some reason the SysTick_Handler() function never gets called.

    I tried to repeat this, using a MSP-EXP432P401R Rev 2.0 using a MSP-FET and MSP-FET-432ADPTR. I couldn't repeat the problem, in that when debugging with a MSP-FET the systick_interrupt_gpio_blink example is toggling the LED when SysTick_Handler() is called.

    When using the MSP-FET one difference I noticed is that the msp432p401r.gel script isn't reporting any output, whereas when using a XDS110 the msp432p401r.gel script reports output to the CCS console. Looking at the msp432p401r.gel script it takes different behavior when a MSP-FET is being used.

    E.g. when a MSP-FET is used the msp432p401r.gel doesn't perform a System Reset in OnPreFileLoaded(). Maybe this is why you found checking "Reset the target on a program load or restart" made a difference.

    Also, what software are you using?

    I was using CCS 7.0.0.00042 with MSP Debug Probe drivers 7.0.5 (which includes MSPDebugStack 3.9.1.2)

  • 0 in reply to Chester Gillon
    Prodigy 225 points

    Thanks Chester,


    I think I was using CCS 6.1.3 or something like that, I'm trying updating to CCS7 now to see if that helps.

  • 0 in reply to Chester Gillon
    Prodigy 225 points
    Ok, it looks like it is working fine now after updating to CCS 7. Thanks for the help!

**Attention** This is a public forum