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.

MSP432 IAR Kickstart RAM limitation?

Hi all,

I work with MSP432 evaluation board inside IAR ARM Kickstart version 7.40.3.

When I go over around 2K of RAM and run into debug mode PC does not go into main and debug view not displayed correct.

Any ideas?

Kind regards,

Andrei Zinenko

  • Hi Andrei,

    When you have a lot of variables or arrays in RAM, the c-startup code starts to take longer and longer to run, because it is initializing all of these variables and arrays before main. Because the Watchdog timer is already enabled by default after a reset, if this code takes too long to run before you can reach your first line of main where you are disabling the watchdog, the watchdog can time out and cause your part to reset (basically ending up being in a loop of running c-startup code, wdt timeout, reset, repeat). You can resolve this by overriding __low_level_init(), which is called before the variables are initialized, and having it disable the watchdog there. There are a number of threads detailing this for MSP430 if you search the forum for watchdog and __low_level_init, and for MSP432 the fix should be similar. You should also check the IAR EWARM development guide - it has information about __low_level_init().
    I hope that this helps!
    Regards,
    Katie
  • Thanks Katie,
    I'll definitely check it first thing in the morning.
    Andrei
  • Hi Andrei,

    Did this resolve your issue so we can close out the thread?

    Thanks,
    Katie
  • Hi Katie,

    Yes, it did.

    Thank you very much.

    Kind regards,

    Andrei Zinenko

**Attention** This is a public forum