Hi Pietro,
sorry for delay, I'm very busy now.
I can see there were some changes between cut1 and cut2. There was boot ROM on cut1. After reset, some code has been executed from address 0x1C0001CC. Even if the flash was completely erased, this code was executed and no reset was triggered. This functionality has been removed on cut2 and the program counter is loaded directly with the reset vector from address 0x04. So, if the flash is erased, program counter is loaded with value 0xFFFF_FFFE. Once the execution is started, bus error is triggered. I can see that the device is periodically reset each about 120us (I can see the same waveform as on your screenshot).
So, it's seems to be related to your debugger. It works as expected if I use Lauterbach debugger and also if I use OpenSDA on S32K EVB together with S32 Design Studio - I'm able to establish the communication even if the flash is erased.
Regards,
Lukas