topic Re: variable watch not update in the freemaster 3.2.2.2 in FreeMASTER

variable watch not update in the freemaster 3.2.2.2

Panasonic_Kevin_Yang — Thu, 07 Mar 2024 13:44:22 GMT

the target hardware is S32K388 and the behavior is same on NXP S32K388 EVB and our own designed HW.

The test code on the target is incrementing the test_counter to 100 then back to 0.

I tested with debugger, the code runs OK.

I tried to define the variable as static volatile or just static.

But the value never change in the freemaster.

And by checking the log, I can see there is error code 0x80000081

please help to provide some ideas what is going wrong.

I’m using JLink plugin as the communication method.

Re: variable watch not update in the freemaster 3.2.2.2

MichalH — Thu, 07 Mar 2024 06:54:54 GMT

Hello,

please send a screenshot of your Project Options dialog "Comm" tab (where the plug-in is selected) and send also a screenshot of the JLink plug-in configuration dialog.

Also, please describe your hardware platform (what MCU, board etc.).

Thank you,
Michal

Re: variable watch not update in the freemaster 3.2.2.2

Panasonic_Kevin_Yang — Thu, 07 Mar 2024 13:45:40 GMT

Hi Michal,

I uploaded to the original post, please help to check it. Thanks.

Re: variable watch not update in the freemaster 3.2.2.2

MichalH — Thu, 07 Mar 2024 15:50:41 GMT

Thank you,

the error code 0x80000081 is not applicable here, this is just an intermediate error returned for old protocol command probed by FreeMASTER for backward compatibility. The overall result is OK (0x0), which means the JLink plug-in "thinks" it is returning a valid data.

We will need to do some experiments to find out what is wrong. I suspect the FreeMASTER reads the correct memory, but the CPU is halted. Is there any other way how you can find out if the application is running (e.g. any LED blinking)? It sometimes happens that during JTAG connect/disconnect process, the core gets reset and/or halted.

Please do these experiments:

Make your FreeMASTER variable modifiable and change it from variable watch grid to some other value. Will it work? If my theory is correct, the variable will change, but will remain constant after that.
If you use IAR toolchain, please attach the debugger and see if you will be able to pause/resume application execution. FYI: the IAR debugger session shall be able to share the JLink connection with FreeMASTER.
If IAR is attached, press the software reset button.

Similar to IAR, you can also use Segger Ozone debugger. This is also able to co-exist with FreeMASTER on the same JLink connection.

I will ask my colleagues to replicate the same HW setup and to try to replicate the issue locally.

Thanks,
Michal

Re: variable watch not update in the freemaster 3.2.2.2

Panasonic_Kevin_Yang — Thu, 07 Mar 2024 18:16:07 GMT

Hi Michal,

Thanks for the advice.

I just confirmed, when power-on the MCU and its SW running OK.

the mcu halt when I click on the Go button in freemaster. do you have any idea why the freemaster halt the mcu execution?

Re: variable watch not update in the freemaster 3.2.2.2

iulian_stan — Wed, 20 Mar 2024 09:10:38 GMT

Hi @Panasonic_Kevin_Yang,

I tried to reproduce your issue, unfortunately, v7.94a was no longer available for download.
I checked latest version (v7.96q), but run into other issues. Eventually, I downgrade to V7.92q and was able to use FreeMASTER with no issue.

Could you check this workaround and let us know if it works for you ?

Kind regards,
Iulian

Re: variable watch not update in the freemaster 3.2.2.2

pasa_kevin_y — Wed, 20 Mar 2024 21:51:25 GMT

Thank you for trying on your side,

But the behavior remain the same after I re-installed to 7.92q

Re: variable watch not update in the freemaster 3.2.2.2

iulian_stan — Thu, 21 Mar 2024 08:16:58 GMT

Just to confirm what toolchain you are using - is it NXP's GCC, IAR, DIAB or GHS ?

Re: variable watch not update in the freemaster 3.2.2.2

pasa_kevin_y — Thu, 21 Mar 2024 15:39:59 GMT

we are using NXP GCC currently.

回复： variable watch not update in the freemaster 3.2.2.2

DouDou1 — Mon, 08 Apr 2024 02:15:23 GMT

Hi,@Panasonic_Kevin_Yang,

Maybe I have the same problem with you. Have you solved it? If so, can you tell me how it was solved?

Re: variable watch not update in the freemaster 3.2.2.2

iulian_stan — Wed, 10 Apr 2024 08:59:38 GMT

Hi @Panasonic_Kevin_Yang, @DouDou1,

We are looking into this issue. In the meantime could you provide some details about the following:

Are you facing this issue when the application is loaded into Flash or Sram, or both ?
Are you running an active debug session at the same time you use FreeMASTER ?

Re: variable watch not update in the freemaster 3.2.2.2

pasa_kevin_y — Mon, 15 Apr 2024 16:33:48 GMT

I load the application to flash, never tried to load to ram.

I didn't run debug session while using the freemaster

Re: variable watch not update in the freemaster 3.2.2.2

DouDou1 — Sat, 20 Apr 2024 08:01:53 GMT

I found that every S32DS program creates a variable called exit_code and decides if it is equal to 0 in the main loop. When I call freemaster, this variable is changed, and the program is finished

Re: variable watch not update in the freemaster 3.2.2.2

Panasonic_Kevin_Yang — Mon, 22 Apr 2024 14:55:03 GMT

our sw won't run into that loop, so it is not the root cause in our case.

Re: variable watch not update in the freemaster 3.2.2.2

iulian_stan — Thu, 25 Apr 2024 08:57:35 GMT

Hi,

It seems that JLink performs some default operations on connect. Ex: memory initialization - in this case the behavior you observe may depend on your particular application (what is stored in those regions).

Example logs:

SetupTarget() start Initializing ECC RAM... RAMCodeAddr: 0x20000000 RAMInitAddr: 0x20000010 RAMInitSize: 0x00007FF0 InitPattern: 0xDEADBEEF ECC RAM initialized successfully Initializing ECC RAM... RAMCodeAddr: 0x20000000 RAMInitAddr: 0x20400000 RAMInitSize: 0x00004000 InitPattern: 0xDEADBEEF ECC RAM initialized successfully SetupTarget() end - Took 25.3ms

We are yet to confirm whether it's the root cause. If so, this could possibly be disabled with JLink Scripts as described on JLink's Wiki page.

Re: variable watch not update in the freemaster 3.2.2.2

Panasonic_Kevin_Yang — Thu, 25 Apr 2024 16:54:49 GMT

the behavior remains the same, below is the log showing the script has been ran.

03-00000000-00-00000001-01C1: ------J-Link related settings------
J-Link Host interface: USB
J-Link script: **********************************\Example_InitTargetOverride.JLinkScript
J-Link settings file: none
------Target related settings------
Target device: S32K388
Target device parameters: none
Target interface: JTAG
Target interface speed: 4000kHz
Target endian: little

Re: variable watch not update in the freemaster 3.2.2.2

MichalH — Fri, 03 May 2024 06:22:32 GMT

Hello,

what Iulian wrote above is important, the JLink may corrupt a memory by initializing it to the 0xDEADBEEF pattern and causing a HardFault. Using a custom JLinkScript which overrides the SetupTarget might be necessary.

I was observing slightly similar (but still different) behavior on S32K344. It appears that there might be a DebugEvent escalated to a HardFault when FreeMASTER-JLink connects to the application. Regardless the possible HardFault root cause, let's first make an experiment to confirm that it really occurs.

Please locate your vector table (startup_ARMCM7.c) and implement a two different handlers, one for HardFault and one for DebugMon. Implement each handler as a short endless loop which just increment a global variable (countHardFault, countDebugMon). Add the two counters to FreeMASTER watch to see if they will count (meaning the theory was correct) or not.

Thanks,
Michal

Re: variable watch not update in the freemaster 3.2.2.2

DouDou1 — Tue, 07 May 2024 02:13:53 GMT

You can try to see if the variable has changed, and if it has, then the program will not proceed

Re: variable watch not update in the freemaster 3.2.2.2

iulian_stan — Mon, 20 May 2024 11:07:53 GMT

Hi @Panasonic_Kevin_Yang ,

According to my observation JLink re/initializes RAM memory in the target setup phase, thus the content of the JLinkScript file should be:

int SetupTarget (void) { return 0; }

After adding the following script BDM plugin settings:

I noticed that memory regions mentioned before preserved their data, and variables also kept their values in between FreeMASTER connections.

Apologies for a delayed reply.