Issue with flashing LPCXpresso54628 EVK board.

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Issue with flashing LPCXpresso54628 EVK board.

1,902件の閲覧回数
a_s
Contributor II

Hello, I am trying to flash the controller via UART port using FLASH MAGIC on LPC54628 evk. Below fig. shows the configuration for flash magic:

Screenshot 2025-02-11 182159.png

During first flashing attempt, I accidently erased the whole chip by checking the erase entire device option in flash magic. After this, the device is not getting either in Flash magic or in MCUxpresso IDE. Looks like erasing the entire chip has erased the bootloader as well. 

I am getting following error in MCUxpresso IDE:

a_s_0-1739278676705.png

Error: 0 available SWD Devices detected.


In what way I can recover the MCU from this stage ? 

 

Thank You


OM13098

ラベル(2)
0 件の賞賛
返信
10 返答(返信)

1,796件の閲覧回数
a_s
Contributor II

I recall the following scenario:

I successfully flashed the GPIO example code from MCUXpresso-SDK  using MCUXpresso-IDE  without any issues.

When I attempted to flash the same .bin file using the Flash Magic Tool, I followed the user manual instructions. I placed the device in UART ISP mode and executed the ISP commands via a serial terminal, receiving the expected responses. I then used the following configurations in Flash Magic:

a_s_0-1739513572563.png

After performing these steps, the device is no longer detected by either Flash Magic or MCUXpresso-IDE .
I am getting following error in MCUXpresso-IDE  :

a_s_1-1739513572465.png

Error: 0 available SWD Devices detected.

 

In what way I can recover the MCU from this stage ? 

Best regards,
Akshay Sidral

0 件の賞賛
返信

1,685件の閲覧回数
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello @a_s

 Have you programmed a GPIO demo without making any changes?

Please put the device back into ISP mode. Then, attempt to perform a full erase using Flash Magic. After that, try debugging again with MCUXpresso IDE. Note that you should switch to a new workspace in MCUXpresso IDE and import a new GPIO demo.

If it still doesn't work, please update the debugger firmware. 

 

BR

Alice

0 件の賞賛
返信

1,643件の閲覧回数
a_s
Contributor II

Hello @Alice_Yang ,
We initially programmed the demo GPIO, and the execution was successful. We also configured the device in ISP mode and attempted to erase the Flash using Flash Magic. However, we encountered the following error:

image.png

Despite trying all the supported baud rates in Flash Magic, the error persists.

Could you kindly guide us on how to proceed with updating the debugger firmware?

Thank you for your assistance, and I look forward to your prompt response.

 

Best regards,
Akshay

0 件の賞賛
返信

1,615件の閲覧回数
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello @a_s 

Please refer to the board user manual -> 4.2 Programming the link2 firmware

https://www.nxp.com/webapp/sps/download/preDownload.jsp?render=true 

update.jpg

 

BR

Alice

0 件の賞賛
返信

1,580件の閲覧回数
a_s
Contributor II

Hello @Alice_Yang,

I have gone through the link which you have attached, but page is not available:image.png

Then I have referred User Manual, the mentioned link is also not available :
http://www.nxp.com/lpcutilities


image.png

Is there any other source for the document? 

Kindly help on this ASAP as we are unable to use the evaluation board. 

 

Best Regards,

Akshay

0 件の賞賛
返信

1,556件の閲覧回数
Alice_Yang
NXP TechSupport
NXP TechSupport
0 件の賞賛
返信

1,857件の閲覧回数
samv
Contributor II

Do you have an LPC-Link2 board available?  That may get you into the chip via the JTAG/SWD port.

If not, might be a worthwhile investment.

Good luck. 

 

0 件の賞賛
返信

1,830件の閲覧回数
a_s
Contributor II

Thank your for the reply.

At the moment, we are getting it in couple of days. Could you pin point the root cause of this problem ? How did the boot ROM got erased ? 

Thank you for your assistance.

 

Best regards,
Akshay Sidral

0 件の賞賛
返信

1,818件の閲覧回数
samv
Contributor II

Remember to follow the procedure for using the external probe in the user manual.

0 件の賞賛
返信

1,819件の閲覧回数
samv
Contributor II

I don't suspect the ROM was erased (ROM = Read Only Memory) but rather the on-board debug probe got corrupted.  I am not an expert in this area but it's my best guess.

Hopefully you will make some progress.

 

 

0 件の賞賛
返信