MSP432 Debug Problem with Launchpad and IAR EW-ARM with MSP432 Launchpad

Hi Rene,

You are experiencing this issue because you are still using a black MSP-EXP432P401R LaunchPad with pre-release silicon, the post-release red version is now available to order. You can also try downgrading IAR EW-ARM versions to one that only recognizes the pre-release silicon (7.60).

Regards,
Ryan

Hi Ryan,

I use allready the red MSP-EXP432P401R LauchPad with the Rev C Controller.
The IAR EW-ARM Version works for view days without Problem.

Any Ideas?

Hello Rene,

Understood, thank you for clarifying. This could be a bug involving the newest release of IAR EW for the MSP430 (v7.70), I am trying to loop IAR experts into this thread to investigate and comment on the matter.

Regards,
Ryan

Now I have additional informations.

I have 2 MSP-EXP432P401R LaunchPads. One works and one not.
The Board with the Problem that the Debuger not go online ist, that
the Return Value to the debuger with the Hardware Revision is not right.

Here the wrong Answer in the Debuger LogFile:

[00:00:462] GTI_READMEM_WITH_STAT()
[00:00:462] ==> startAddress = 0x00201010
[00:00:462] ==> page         = 0x00000000
[00:00:462] ==> count        = 0x00000004
[00:00:462] ==> attr         = 0x00000000
[00:00:462] ==> strAttr      = (null)
[00:00:462] ==> waitState    = 0x00000000
[00:00:462] ==> accessSize   = 0x00000004
[00:00:462] ==> mem_access_id   = 0xFFFFFFFF
[00:00:463] <== buf             = 0x000000CF 0x000000A8 0x00000020 0x0000000C
[00:00:463] <== GTI_RETURN_TYPE = 0x00000000

The right Anser should be so:

[00:00:395] GTI_READMEM_WITH_STAT()
[00:00:395] ==> startAddress = 0x00201010
[00:00:395] ==> page         = 0x00000000
[00:00:395] ==> count        = 0x00000004
[00:00:395] ==> attr         = 0x00000000
[00:00:395] ==> strAttr      = (null)
[00:00:395] ==> waitState    = 0x00000000
[00:00:395] ==> accessSize   = 0x00000004
[00:00:395] ==> mem_access_id   = 0xFFFFFFFF
[00:00:395] <== buf             = 0x00000043 0x00000000 0x00000000 0x00000000
[00:00:395] <== GTI_RETURN_TYPE = 0x00000000

The Controller have to answer with a 0x00000043.
The Controller with the Problem returned everytime another value.
But the Answer with the Device ID is on both Controllers right. (0x0000A000)

[00:00:395] GTI_READMEM_WITH_STAT()
[00:00:395] ==> startAddress = 0x0020100C
[00:00:395] ==> page         = 0x00000000
[00:00:395] ==> count        = 0x00000004
[00:00:395] ==> attr         = 0x00000000
[00:00:395] ==> strAttr      = (null)
[00:00:395] ==> waitState    = 0x00000000
[00:00:395] ==> accessSize   = 0x00000004
[00:00:395] ==> mem_access_id   = 0xFFFFFFFF
[00:00:395] <== buf             = 0x00000000 0x000000A0 0x00000000 0x00000000
[00:00:395] <== GTI_RETURN_TYPE = 0x00000000

Only the HW Revision goes wrong.

Now I think the Controller is destroid and I replace them with a new one (Rev C).
But the Problem is the same. The Debugger reads different Hardware Revision Values.

[00:00:772] GTI_READMEM_WITH_STAT()
[00:00:772] ==> startAddress = 0x00201010
[00:00:772] ==> page         = 0x00000000
[00:00:772] ==> count        = 0x00000004
[00:00:772] ==> attr         = 0x00000000
[00:00:772] ==> strAttr      = (null)
[00:00:772] ==> waitState    = 0x00000000
[00:00:772] ==> accessSize   = 0x00000004
[00:00:772] ==> mem_access_id   = 0xFFFFFFFF
[00:00:773] <== buf             = 0x000000C7 0x00000000 0x00000000 0x00000000
[00:00:773] <== GTI_RETURN_TYPE = 0x00000000

[00:00:592] GTI_READMEM_WITH_STAT()
[00:00:592] ==> startAddress = 0x00201010
[00:00:592] ==> page         = 0x00000000
[00:00:592] ==> count        = 0x00000004
[00:00:592] ==> attr         = 0x00000000
[00:00:592] ==> strAttr      = (null)
[00:00:592] ==> waitState    = 0x00000000
[00:00:592] ==> accessSize   = 0x00000004
[00:00:592] ==> mem_access_id   = 0xFFFFFFFF
[00:00:593] <== buf             = 0x00000097 0x00000002 0x00000000 0x00000020
[00:00:593] <== GTI_RETURN_TYPE = 0x00000000

I test it also with an Blackhawk XDS100V2 Debugger. It's the same.

Has anyone an Explanation for that? I cant continuously replace Controller and hope it works.

Hope for Ideas!!!

Rene

So the problem follows the LaunchPad and not the device? This is important for understanding whether it is a hardware problem or not. Are there any physical differences between the two LaunchPads?

Regards,
Ryan

Yes the Problem is only on one LaunchPad.
The 2 Boards are out of the box without changes.
I have measured some Signals around the Controller.
All Looks good.
And the Controller answers right to the debuger with the DEVICE ID 0x0000A000
That means the communication with the debuger is fine.
Only the HW Revision goes wrong.

I have test the last time different Software.
If it possible, that a Software can bring the controller
in a state, that he not correct answer?

Unfortunately I can not delete the Controller. The Erase function reads also
the HW Revision.

You had said in your original post that this LaunchPad sometimes works without issue, and that restarting IAR sometimes helps? Is communication effective if the working LaunchPad's XDS110-ET is wired to the non-working LaunchPad's target MSP432 device? There may still be reason to believe that the XDS110-ET is defective.

Regards,
Ryan

Since 2 Days the second LaunchPad dosn't work anymore. View days before I see this Problem sometimes and
it helps to reconnect or restart the board and the IAR Workbench. But now it dosn't work all the time.
The 2 Board are not wired. All is in original state (stand alone). But I have made test with an external debuger
named Blackhawk XDS100V2 and this do the same. The HW Revision is wrong.

Next I will try an older IAR Workbench. Hoppfully this helps.
But I cant believe it.

Rene,

Could you also try using CCS instead and doing a device factory reset (referred to in SLAU575)? www.ti.com/.../slau575e.pdf

Regards,
Ryan

Hi Ryan,

yesterday I uninstall the newest IAR EWARM and install the Version before.
The Problem is the same.

Then I again swaped the Controller. Now it's working fine.
Unfortunately, I have not solved the Problem, only bypassed.
But I can work now.

In this Moment I don't have the ccs Compiler installed.
But when I have such a Problem again, then I can try this.
Thanks for this Information and for your time.

I hope I do not report me so quickly.

Rene