Codewarrior/LS1043A memory access error

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Codewarrior/LS1043A memory access error

5,052 Views
yoshida08
Contributor I

I am debugging a our designed board on which LS1043A is mounted.
I'm using code warrior to debug, but I get an error like the attachment.
What is the cause? 

0 Kudos
Reply
7 Replies

4,813 Views
yoshida08
Contributor I

Thank you for your reply.

I'm sorry, I reply late.

0 Kudos
Reply

4,973 Views
yoshida08
Contributor I

We solved problem of the JTAG hardware interface design.

We send new log.

This problem remain yet. 

0 Kudos
Reply

4,952 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please configure the switch setting on your custom board to configure it as hard-coded RCW, then try whether CCS still failed at reset_to_debug.

If the problem remain, further investigating about JTAG interface hardware design is needed.

0 Kudos
Reply

4,988 Views
yoshida08
Contributor I

Thank you for your reply.

This problem remain yet. We checked our JTAG hardware interface design.

"nRESET" signal is connected to TRST direct. 

Is this connection a problem?

0 Kudos
Reply

5,017 Views
yipingwang
NXP TechSupport
NXP TechSupport

When you execute the Connection Diagnostics action, then CodeWarrior Connection Server(CCS) will be popped up automatically on the right bottom of the Windows task bar.

Please open CCS console, type "log v", then execute Connection Diagnostics again, the low level CCS log will be printed out, please capture the log to me to do more investigation.

0 Kudos
Reply

5,010 Views
yoshida08
Contributor I

Thank you for your reply.

we got the log.

Please check the attached file.

0 Kudos
Reply

5,000 Views
yipingwang
NXP TechSupport
NXP TechSupport

In your CCS log, it failed at "reset_to_debug".

Please make sure SERDES REF CLK is set to 100 MHz, set rcw_src to the hard-coded RCW option matching the board's DIP SW regarding SYSCLK and differential/single-ended clock source

If this problem remains, please check your JTAG hardware interface design.

Please refer to "Figure 18. JTAG interface connection" in the attached application note.

Please refer to "5.28 JTAG pin termination recommendations" in the attached app note.

0 Kudos
Reply