UART sample code on LPC5526JBD64E MCU

[carter_wang]

Hi,

I have two boards, one is LPC55S28-EVK, the other has LPC5526JBD64E on it.

I downloaded SDK_2_7_0_LPCXpresso55S28, then imported the hello world demo application.

I try to develop more functions based on the demo application.

I found the output debug message from the UART port(PIO0_29/PIO0_30) on LPC55S28-EVK, however, no message on my board with LPC5526JBD64E MCU...

I was wondering could you tell me how I should modify the demo application to make it run successfully on LPC5526JBD64E?

It is my way to download the image into MCU on-chip flash.

• Enter ISP mode.
• Download the image by tool Flash Magic.
• Change to passive mode.
• Power on the board.

BR,

carter

[EdwinHz]

The problem might be due to the differences in pin assignments. I believe the LPC55S28-EVK comes with a LPC55S28JBD100 (please confirm this on your board) which is a 100 terminal package. The LPC5526JBD64, however, is a 64 pin package. Please make sure the pin assignments match the UART port of the LPC5526 as well, and that you are reading the UART port accordingly for the correct pins of this part number.

Best regards,

Edwin.

[carter_wang]

Hi Edwin,

Thanks for your information.

I checked the UART pins definition(PIO0_29, PIO0_30) is the same between these two boards.

I tried to use LPC-Link 2 to debug it, but got another issue...

BR,

carter

[EdwinHz · Accepted solution]

Hi Carter,

Are you using the LPC-Link 2 to debug the LPC5526 or the LPC55S28-EVK? Either way, I believe you should check out these posts in hopes of regaining debug access to your MCU:

https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/Regaining-debug-access-to-target-MCU/m-p/473923

https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/ISP-Reset-over-debug/m-p/470945

With respect to the demo application, I would recommend creating a new project for the LPC5526 with the necessary drivers and copying the source files only, instead of importing the whole project. This is because the project often comes with chip or board specific configurations and can cause problems.

I hope this helps,

Edwin.

[carter_wang]

Hi Edwin,

Thanks for your information.

It is workable now.

BR,

carter