Other Parts Discussed in Thread: SEGGER, SYSCONFIG
Tool/software:
Hello,
we are evaluating MSPM0G3507 on 2 custom PCBs and are running into problems with debugging/programming these parts.
As IDE we are using CCS 12.7.1 with MSPM0 SDK 2.02.00.05.
As Progammer we are using Segger JLink Plus connected to SWD (PA19/PA20).
I noticed that MSPM0G3507 might lock up and not be accessible by JLink sometimes.
There are several methods though to unlock MSPM0G again, which are discussed in other Threads on E2E Forum.
Method 0: Enter BSL -> While writing our software, we were fine by pulling PA18 to VCC and forcing MSPM0G into BSL Mode.
On our Board, we need to use PA18 as Analog Input and we do not want to enter BSL Mode on each power cycle, so I tried to disable BSL Invoke Pin Check in Sysconfig.
In Configuration NVM -> Accept configuration risks is set.
In BSL GPIO Invoke Configuration -> Enable BSL Invoke Pin Check is unchecked.
All other options in Configuration NVM were not changed.
This worked fine for a day. We could reprogram MSPM0G many times with power cycling in between and we did not run into any problems.
When I tried to upload to MSPM0G today, I was unable to connect again.
CCS shows only the following error: CORTEX_M0P: Error connecting to the target: Could not connect to target.
The Connection between JLink and MSPM0G seems to be correct. I can also confirm, that supply voltage is stable.
I tried unlocking MSPM0G through other discussed methods:
Method 1: DSSM Mass Erase -> After launching the project configuration and showing all cores, it does not show any non-debuggable devices in CCS. Therefore i cannot connect to CS_DAP_0 and force a mass erase. Could there be some settings, that I have overlooked, that would hide CS_DAP_0?
Method 2: BSL Unlock -> This Method does seem to only work with XDS110, since it uses MSPM0_BSL_GUE.exe. Is this correct, or can we also use JLink here?
Are there any other Methods that we could try or is the MSPM0G bricked?
Thank you!
