MSPM0G1107: crash during programming

Hi Holger,

It might be WDT issues if it set too small.

Another issues is that the CCS with J-Link support is not stable, sometimes it enter fault state and need a factory reset to recover (this happens to previous CCS 12.8 version when I debug)

- So I normally use J-Flash to program the firmware and use CCS to start the project-less (only load symbol, not program) to debug.

B.R.

Sal

Hi Sal,

> It might be WDT issues if it set too small.
I thought the WDT is switched of during programming? 

> Another issues is that the CCS with J-Link support is not stable, sometimes it enter fault state 
Is this documented somewhere? Customer uses CCS v20. Does this problem also occure with this version?

Regards, Holger

Hi Holger,

HS FAE Germany said:

> It might be WDT issues if it set too small.
I thought the WDT is switched of during programming? 

Yes, that true. What I am concerning is that before debugger take fully control of device, the WDT might be work and not feed (as debugger are trying to hold MCU). So, too smally WDT has this issues I think. 

HS FAE Germany said:

Is this documented somewhere? Customer uses CCS v20. Does this problem also occure with this version?

No, this just comes from my personal debug experience. And it can not be stably reproduced.

Customer can try this method also, to see if this fix their issues.

B.R.

Sal

Hi Sal,
customer only have problems with J-Link, with XDS110 it is stable. In their company they use a lot of J-Link because they used competition MCU also. 
It would be good if the J-Link stability with CCS would be improved.

Regards, Holger

Hi Holger,

Move the thread to SDTO team to see if there any further comments.

B.R.

Sal

HS FAE Germany said:

It would be good if the J-Link stability with CCS would be improved.

If the issue is specific to J-Link, then it is likely the SEGGER would need to investigate this.

Hi Ki,

Does we support to call the latest standalone J-Link version in the CCS v20.x version?

In the CCS 12.x version, it integrates a default J-link DLL version which is quite old. Not sure how it is in the latest CCS v20.x version.

B.R.

Sal

Yes, CCS does come with J-Link support. We bundle a package provided by Segger. The development and validation of the J-Link debug functionality is from Segger. We simply bundle it so customer can access it out of the box instead of having to download it separately.

Note that the while CCS does periodically update the version of J-Link support it comes with, it typically lags the latest available by a few versions.

Holger,

HS FAE Germany said:

Tools:
- CCS 20.2.0.12__1.8.0

CCS 20.2.0 comes with J-Link support v8.34. It is a fairly old version

CCS 20.4.0 comes with v8.70. I would recommending updating the CCS version and see if that helps.

Thanks

ki

Hi Sal,
can you install the latest J-Link support package and test if you see if that improves stability?

Regards, Holger

Hi Holger,

Sorry for late response. Just come back for anual leave.

As I said this issues used to happen with my debug history, while I do not have method to verify this issues is fixed or not. 

It requires user high frequently debug and see its stability. Please let customer try this.

I will monitor it when I debug with J-Link on CCS.

B.R.

Sal