topic Re: T1024 lauterbach missmatch id code in T-Series

T1024 lauterbach missmatch id code

CarlosV85 — Wed, 15 Jan 2025 16:33:03 GMT

Hello

I just trying to update the RCW for a T1024NXN7MQA using lauterbach.

When the lauterbach tries to prepare the debugger shows a debug configuration error indicating that the IDCODE is incorrect.

Warning: SYStem.CPU setting does not match the detected CPU (IDCODE=0x0682101D).

Any idea about why is this happening?

Thanks in advance.

Re: T1024 lauterbach missmatch id code

Hector_Villarruel — Thu, 16 Jan 2025 03:01:17 GMT

Hello @CarlosV85

Hope this post finds you well,

Could you please provide us with more details about this situation?

Are you able to provide us with a full screenshot of this situation?

Could you please also provide us with your CodeWarrior version and in which OS are u using it?

We will be aware for your kind reply.

Have a great day.

Best regards,

Hector Villarruel S

Re: T1024 lauterbach missmatch id code

CarlosV85 — Thu, 16 Jan 2025 03:46:04 GMT

I am performing a board bring up for a custom board that uses the T1024NXN7MQA. I am not using the code warrior only the lauterbach jtag. At the beggining the lauterbach recognized the T1024 as T1014. We make some changes on the board. The lauterbach recognizes the correct IDCODE but once we try to perform a System.up I am getting a debug port failure indicating that CPU core 0 timeout and RCW cannot be read.

I think that this error is caused due that the HRESET is never asserted to low.

Re: T1024 lauterbach missmatch id code

rweiss — Thu, 16 Jan 2025 10:15:36 GMT

Hi Carlos,

can you please post a screenshot of the AREA window (menu: View - Message Area) after the error occurred?

Did you check that the HRESET signal on your target hardware can actually be pulled to GND? If you don't see HRESET being asserted, it could mean either that the HRESET driver of the debug probe is not working, or that the HRESET signal of the target is tied to VCC.

Best regards,
Reinhard

Re: T1024 lauterbach missmatch id code

CarlosV85 — Thu, 16 Jan 2025 19:26:55 GMT

Hello Reinhard

Sure I attached the current area. I believe the hard coded RCW is not as expected since before this was causing an RESET_REQUEST_B.

Thanks

Carlos V.

Re: T1024 lauterbach missmatch id code

rweiss — Fri, 17 Jan 2025 07:59:26 GMT

Hi Carlos,

I think you are right that the debugger didn't assert HRESET, as the failed access to the cores caused the SYStem.Up sequence to abort very early.

Do you know you can override the RCW with the debugger. There are two examples for NXP evaluation boards, which you can use as template and adopt for the needs of your hardware:

demo\powerpc64bit\hardware\qoriq_t1\t1024qds\demo_set_rcw.cmm
demo\powerpc64bit\hardware\qoriq_t1\t1024rdb\demo_set_rcw.cmm

in your TRACE32 installation folder.

Best regards,
Reinhard

Re: T1024 lauterbach missmatch id code

CarlosV85 — Sat, 18 Jan 2025 00:51:03 GMT

Hi Reinhard

If I understood correctly then the demo example script corresponds to the NXP development board?

if yes I will need to update those scripts to match with my custom board?

At least bit 0 to 387? and I will need to disable the PBI_SRC

Because I noticed that the scripts disable the core but the debug port fail continues.

Thanks

Carlos V.

Re: T1024 lauterbach missmatch id code

CarlosV85 — Wed, 22 Jan 2025 04:11:45 GMT

Hello Hector

I was working with lauterbach but they recomended us to contact nxp.

can you help me to take a look for the following support ticket #00679535?

Thanks in advance

Carlos V.

Re: T1024 lauterbach missmatch id code

CarlosV85 — Wed, 22 Jan 2025 22:32:30 GMT

Now using the Code Warrior with the CODE TAP.

I am having the following issue when I execute the steps from AN12105 6.3 RAMboot process using CodeWarrior

Error launching t1024-core00_RAM_T1024_Download
CCSProtocolPlugin : Failed to reset the target
[CCS last error: T1020: Core not responding ]

Thanks

Carlos V.

Re: T1024 lauterbach missmatch id code

Hector_Villarruel — Sat, 25 Jan 2025 01:04:13 GMT

Hello @CarlosV85

Hope this post finds you well,

This post is to inform you that we are aware of case #00679535.

In order to keep the communication on the same channel, I will close this case and kindly keep the communication on case #00679535.

Have a great day.

BR,

Hector Villarruel