MSP432E401Y: Timer Interrupt not triggering

Part Number: MSP432E401Y

Actual part number is MSP432P401R, wasn't able to find it in the part number field. My project uses an LCD screen to display messages to an operator for their input. When the device is turned on there's a startup screen during which everything is initialized and the screen is meant to transition through a timer interrupt. Two times out of roughly eighty power cycles, the startup screen gets stuck and never transitions to the main menu. The device was reflashed with some additional code that is meant to do a marginal read of the flash on startup, we've run 50 more times with that code and haven't seen this issue again. 

Is this an issue with the Interrupt Vector Table being corrupted somehow on startup? What would you recommend us to check?

Thanks,

David 

  • Hi David

    First if you want to check if the timer's interrupt have been triggered, you can use a GPIO toggle event to show this that you can monitor it easily.

    To this issue, it seems some things lead the device to be reset. You can also use a GPIO toggle event to show this.

  • Hey Gary,

    I can include the toggle event but that would only let me check if the timer triggered when a fault occurs right? Unfortunately this seems to be a very rare occurrence, is there anything I should check in my code or a HW issue that could explain this problem? 

    Also I've been trying to access the product page for the MSP432P401R to view some technical documentation, but I no longer see it on the site is there a reason for that?

  • Hi David

    First it is hard to say this stuck issue is related with Timer, it maybe stuck at any initialization part. If you can post the code that will be better.

    Second if it related with timer, here is a note that you can take care about

    At the end, it is better to find a way to reproduce this issue more easily that we can verify the workaround.

  • Hey Gary,

    My problem is that I'm having a difficult time reproducing the issue. I've had a few hundred tests run with power cycling in between and have not had the issue repeat itself. Do you have any recommendations on how we may be able to induce a failure? 

    Thanks,

    David 

  • Make sure your code is followed the note I have mentioned before. I think that may help improve this issue