Hello Andrea,
Thank you for your inquiry.
Such an issue is not known to us.
Which target device are you looking to debug?
You seem to be using a J-Link Lite of an eval board. Are you using it with the eval board or custom hardware?
I followed the instruction in the manual to have a JLinkScript to bypass the issue but it seems that it is not executed.
In the J-Link log the script is never called. How are you passing it to the J-Link? More information can be found here: https://wiki.segger.com/Using_J-Link_Script_Files
Another question: does the wrong ROM table value affect the JLink operation? What happens is that after the connection any additional command is not executed. Same behaviour also using the JLink commander: a WriteAP is rejected.
The only base address the J-Link must know is where the core base address is located. All other ROM table entries give additional debug features but are not mandatory.
Best regards,
Nino