LPC55S66 Rev 0A gives FLASH error with MCUXpresso IDE v11.1.0.3209

[bob_nayar]

I have a Rev 0A LPC55S66 that I am trying to program.

I am using the latest MCUXpresso IDE v11.1.0.3209 with SDK 2.7.0.

When I try to FLASH the device using a PE Micro Multilink Universal(updated drivers), I get these messages on the console:

(Please scroll down to see errors in RED)

P&E GDB Server for Arm(R) devices, Version 7.73.00.00
Copyright 2018, P&E Microcomputer Systems Inc, All rights reserved
Loading library C:\nxp\MCUXpressoIDE_11.1.0_3209\ide\plugins\com.pemicro.debug.gdbjtag.pne.expansion_4.4.1.201911122108\win32\gdi\unit_ngs_arm_internal.dll ... Done.
Command line arguments: -interface=USBMULTILINK -port=USB1 -speed=5000 -flashobjectfile=C:\Users\Admin\Documents\MCUXpressoIDE_11.1.0_3209\workspace\LPC55S66_Project\Debug\LPC55S66_Project.axf -device=NXP_LPC55Sxx_LPC55S66 -programmingtype=0 -runafterprogramming -startserver -singlesession -quitafterprogramming
Device selected is NXP_LPC55Sxx_LPC55S66
User Specified Hardware Selection : Interface=USBMULTILINK and Port=USB1
Connecting to target.
P&E Interface detected - Flash Version 10.36
Device is NXP_LPC55Sxx_LPC55S66.
Mode is In-Circuit Debug.
(C)opyright 2012, P&E Microcomputer Systems, Inc. (www.pemicro.com)
API version is 101
TARGET XML PATH is C:\nxp\MCUXpressoIDE_11.1.0_3209\ide\plugins\com.pemicro.debug.gdbjtag.pne.expansion_4.4.1.201911122108\win32\gdi\P&E\supportFiles_ARM\target_v8m_vfp_se.xml
Creating kernel driver for freertos
Server 1 running on 127.0.0.1:7224
Server 2 running on 127.0.0.1:7226
Server 3 running on 127.0.0.1:7228
Server 4 running on 127.0.0.1:7230
Server 5 running on 127.0.0.1:7232
Server 6 running on 127.0.0.1:7234
Server 7 running on 127.0.0.1:7236
Server 8 running on 127.0.0.1:7238
Server 9 running on 127.0.0.1:7240
Server 10 running on 127.0.0.1:7242
Copyright 2018 P&E Microcomputer Systems,Inc.
Command Line :C:\nxp\MCUXpressoIDE_11.1.0_3209\ide\plugins\com.pemicro.debug.gdbjtag.pne.expansion_4.4.1.201911122108\win32\pegdbserver_console -interface=USBMULTILINK -port=USB1 -speed=5000 -flashobjectfile=C:\Users\Admin\Documents\MCUXpressoIDE_11.1.0_
CMD>RE
Initializing.
Target has been RESET and is active.
CMD>CM C:\nxp\MCUXpressoIDE_11.1.0_3209\ide\plugins\com.pemicro.debug.gdbjtag.pne.expansion_4.4.1.201911122108\win32\gdi\P&E\supportFiles_ARM\NXP\LPC55Sxx\nxp_lpc55s66_1x32x80k.arp
Initializing.
Initialized.
;version 1.04, 11/08/2019, Copyright 2019 P&E Microcomputer Systems, www.pemicro.com [lpc55s66]
;device nxp, lpc55s66, 1x32x80k,
;begin_cs device=$00000000, length=$00048000, ram=$04000000
Loading programming algorithm ...

Programming sequency is : erase, blank check, program, and verify {default}
CMD>VC
Command is inactive for this .ARP file.
VC is not implemented, falling back to VM
CMD>VM
Verifying.
Verify error at address $0000000C.
Byte in module is $4D and should be $89.
Current content of flash does not match application to be programmed
CMD>EM
Erasing.
Module could not be erased.
Error Erasing flash of device
Error occured during Flash programming.
All Servers Running
Target Disconnected.

Is this an issue with Rev 0A?

Please advise.

Thanks.

Bob N

[jeremyzhou]

Hi Bob,

Thanks for your reply.
I don't have the PE Micro Multilink Universal on hand now, otherwise, I'll try to replicate the phenomenon as you mentioned above.
In further, I'll transfer your suggestion to the MCUXpresso IDE team for checking.

Have a great day,
TIC

-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------

[bob_nayar]

Jeremy,

I would rather use MCUXpresso.

Can I use the SEGGER J-LINK EDU in MCUXpresso?

Link: https://www.segger.com/products/debug-probes/j-link/models/j-link-edu/ 

It supports the LPC55S66JBD100.

Please advise.

Thanks.

Bob N

[jeremyzhou]

Hi Bob,

Thanks for your reply.
1) Can I use the SEGGER J-LINK EDU in MCUXpresso?
-- Yes, the MCUXpresso support to work with the J-link.

Have a great day,
TIC

-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------

[bob_nayar]

Thanks, Jeremy.

In response to your earlier suggestion: "I'd like to suggest that you can try using other IDEs likes KEIL MDK, IAR to work with the PE Micro Multilink Universal and using the MCUXpresso work with other debug tool, through the comparing, it can help us to locate the issue.", I went ahead and downloaded the code-limited evaluation version of IAR.

IAR works perfectly with the PE Micro Multlink Universal.

I think you guys need to fix MCUXpresso to get the PE Micro programmer working properly.

Bob N

[jeremyzhou]

Hi Bob,

Thank you for your interest in NXP Semiconductor products and
for the opportunity to serve you.
It seems a bit weird, the PE Micro Multilink Universal should support the LPC55Sxx series, so I'd like to suggest that you can try using other IDEs likes KEIL MDK, IAR to work with the PE Micro Multilink Universal and using the MCUXpresso work with other debug tool, through the comparing, it can help us to locate the issue.

Have a great day,
TIC

-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------