I'm having trouble with Attach to Running program in Ozone.

I have a jLink Ultra+ and am using Ozone (v 3.36). I’m connecting to a S32K396 chip and Ozone works great when I Download & Reset Program, but
When I Attach to Running Program, it almost always fails with a HardFault exception. My colleague connecting to a S32K388 experiences the same thing.
Weird thing is that sometimes (very rarely) it actually works, but I can't figure out why.

Sorry my original post did not have values in the image.
Here's some more information:
It seems that I am able to attach, but it halts (even though I'm doing Attach to Running Program and not Attach and Halt.
Then I hit step or play and I get the fault which seems to either be an data access violation or instruction access violation with a SysTickException

Some new information: I bypassed my freeRTOS scheduler start with a while(1) loop and I'm able to attach/play/pause/play again without issue. Is it possible this is specific to the freertos plugin?

I confirmed that it WFI=0 at startup and when in Idle task. But I found something that seems to be the answer (although still not working):

Here wiki.segger.com/S32Kxxx at section
Attach to debug session


It says that for S32K chips, you cannot attach out of the box due to the ECC RAM. You must use a JLink Script to alter the normal connection.
So I tried using the File provided and putting in my project file via the BeforeTargetConnect() function.

But I get the following:
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
Connect failed. Resetting via Reset pin and trying again.

Here's the content of that file provided from link above, do I need to alter this somehow?

int InitTarget(void) {
//
// As this script file is only used for attach purposes, no special handling is required.
// Therefore, we override the default connect handled by the J-Link DLL for this device.
// as it would trigger a reset.
//
return 0;
}

Ok, so I've been able to attach by using the SetupTarget function:
int SetupTarget() {
//
// We leave ths function empty here to skip the ECC RAM init for SystemView.
// Otherwise the RTT buffer would be overwritten and SystemView will not start.
//
return 0;
}


Does this sound right?
Any further commentary is much appreciated, thanks!

Yes I can attach now, and the solution was to override the SetupTarget function in JlinkScript in the Ozone project file function: BeforeTargetConnect()