S32G-VNP-RDB2 Lauterbach

[NP1]

Can someone tell which debugger will support in S32G-VNP-RDB2 board. Will Debugger LA-3000 will support in this board? 

[NP1]

We are trying load  LwIP example on S32G-VNP-RDB2 board and the Lauterbach we use is LA-3500 (debug module) with LA-3255 and LA-7844x (debugger for ARM A/R [arm8/9] with extension to cortex M series).

But we were getting the above error (bus error at  address 0x34500000).  Is there any restriction to write to this memory location? or ho to resolve this error

[Daniel-Aguirre]

Hi,

We assume you are trying to run the LWIP example that comes with the TCP/IP stack (non PFE). If so, have you installed HSE-FW? This is a requisite for the example to be able to run. There is a workaround talked in the following thread which explains the modifications needed if HSE-FW is not available:

Solved: Ethernet Bring up - NXP Community

As for the memory space, we see that it is defined on the linker file, which means it should be available:

Is this same problem happening with a blink example?

Please, let us know.

[NP1]

Yes it is the LWIP example that comes with the TCP/IP stack . Same is happening with LED blink one as well.

[Daniel-Aguirre]

Hi,

Thanks for your feedback.

Which *.cmm files are you using for your setup?

Please, let us know.

[NP1]

I have attached the same S32G2_load.txt (note: just changed the extension for uploading purpose) 

[Daniel-Aguirre]

Hi,

We have received the following update from our internal team:

"0x34500000 is the start address of non-cacheable memory in LwIP example, the customer used the incorrect trace script which caused this issue, the script to be used should be "s32g2_connect_m7_0". This script can found in T32\demo\arm_obsolete\hardware\s32g2\scripts"

If you cannot find this script, help us opening a ticket on the NXP online services, for us to be able to share more information on regards of this topic.

Please, let us know.

[NP1]

When I open s32g2_connect_m7_0.cmm script , we were getting stopped at vector catch error . ST:3400020 [
\\User\Global\_ResetVector ]

[rweiss]

Hi @NP1,

perfect, the core is now stopped right at it's reset vector. This is the expected result after runing this script.

Regards,
Reinhard

[NP1]

Okay. So after that I just need to load the elf right ?

[rweiss]

demo\arm_obsolete\hardware\s32g2\scripts is not part of the official TRACE32 installation. The actual path is demo\arm\hardware\s32g2\scripts

Regards,
Reinhard

[Daniel-Aguirre]

Hi,

Thanks for your feedback. We will ask the internal team if they have seen this behavior before.

Please, let us know.

[Daniel-Aguirre]

Hi,

For S32G, we have the following information on regards of Lauterbach tools:

For which we are not seeing the specific P/N you are mentioning.

Still, we recommend sending the inquiry to Lauterbach support itself, since they will provide more information on regards of their platform.

Please, let us know.

[rweiss]

Hi @Daniel-Aguirre,

the debugger setup is suitable for S32G. Some order numbers changed since these pages were created.The pages show the recommended configuration at that time, but usually older hardware will also support newer processors, by updating the debugger software.

Best regards
Reinhard

[viswa_kondapall]

Hi ,

I think any licensed one will support. But u need .cmm scripts to debug. Those are available with most of the nxp SW bundles. Most of the projects has this .cmm files. goldvip binaries etc. folders search. please let me know. not able to find.

regards,

Viswa.