LPC Microcontrollers中的主题 Re: Chip initialisation failure in LPC54608J512BD208

Chip initialisation failure in LPC54608J512BD208

prasannanaik — Tue, 19 Nov 2019 04:46:52 GMT

Hi,

I am unable to debug my custom board having microcontroller LPC54608J512BD208.

I am getting chip initialisation error while downloading the code.

I have attached screenshots of error messages along with firmware. Please help in resolving the issue.

IDE: MCUXpresso v10.3.0_2200

Debug interface: SWD

Also, is there any debug enable pin in LPC54608J512BD208?

Thanks and best regards,

Prasanna

Re: Chip initialisation failure in LPC54608J512BD208

ZhangJennie — Wed, 20 Nov 2019 06:28:51 GMT

Do you use NXP demo board or your own designed PCB?

If NXP demo board, please send me a photo of the board while it is connecting PC. thus I can check status.

If not NXP demo board, send me the SWD schematic, I will check the design.

On SW side, I suggest you use the MCUXpresso SDK demo ( for example, hello world, blink_led,etc) as a connection testing application.

Jun Zhang

Re: Chip initialisation failure in LPC54608J512BD208

prasannanaik — Fri, 22 Nov 2019 06:23:11 GMT

Hi Jun Zhang,

Thanks for your reply!!!

1) I am using LPC54608J512BD208 mounted on PCB designed for my application. I have attached schematic in this reply.

2) While debugging the problem, i had following observations:

a) I can program my board through LPC11U68 xpresso v2(Rev C) development board. I pulled ISP0 pin to ground while programming to get the debug access. Now i can debug using LPC11U68 xpresso v2(Rev C) development board.

b) I am unable to program/debug my board through PE Micro's USB multilink. While connection it shows following error

I have verified the connections between port G of multilink & my custom board.

Thanks & best regards,

Prasanna

Re: Chip initialisation failure in LPC54608J512BD208

ZhangJennie — Fri, 22 Nov 2019 08:40:31 GMT

By checking your schematic, I didn't find issue of SWD design.

As you side, you can connect and download code to target if use LPC11U68 on board debugger? but only has problem if use Multilink.

if my understanding is correct, What is your Multilink version? please send me photo or product link of it. Thanks.

Have a great day,
Jun Zhang

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

Re: Chip initialisation failure in LPC54608J512BD208

prasannanaik — Fri, 22 Nov 2019 10:40:53 GMT

Hi Jun Zhang,

Thanks for your input.

While further debging the issue i have found that conroller is getting programmed when connected with Multilink Universal version D whereas it doesn't work with Multilink Universal version B. I was using Multilink Universal version B earlier.

I have used port G in both the versions for debugging.

I have only 1 device of version D whereas 2 device of version B so it is difficult to manage that 1 device between 3 team members.

Can you please help identifying the solution to connect microcontroller with version B device.

Thanks & best regards,

Prasanna

Re: Chip initialisation failure in LPC54608J512BD208

ZhangJennie — Mon, 25 Nov 2019 02:06:51 GMT

Hi Prasanna

So from our discussion, we can focus the issue on your Multilink Universial Rev B itself.

If your Rev B is not broken, Normally it is because the firmware is old.

As Multilink Universial is P&E product but not NXP's, I suggest you contact P&E directly for this issue. I believe they can help you on it directly.

PEmicro | Experts in Embedded tools for Flash Programming and Development

Have a great day,
Jun Zhang

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!