LPC Link2 Programming

[sayanjit]

Hi there, 

I am an LPC enthusiast, currently trying my hand on the LPC-Link2 board (OM13054) where I am trying access the ADC peripheral. My goal is to log high-speed (preferably in the range of 60-80 MHz) analog data using the LPC4370 microcontroller of the LPC board to my PC which I can use for further analysis. I have developed the firmware and successfully generated the .bin file from it using the MCUExpresso tool. But, at this stage, I am not being able to flash the firmware onto the LPC board so that I can use it according to my need.

Therefore, any help regarding the flashing process of the firmware or configuring the board with my customize firmware would be very helpful. 

OM13054  

[Omar_Anguiano]

To flash the binary it is needed to use another probe connected to J2 to the OM13054 that is the target.
Specifically, which issues are you experiencing?

Best regards,
Omar

[sayanjit]

The scenario is that I only have the LPC Link2 board excluding the LabTool Analog board (equipped with analog supply through BNC connectors), where I am using my own analog connectors through signal generators. The goal is to access the analog peripheral through my custom Python script (using libusb-win32 driver via Zadig) and log analog data to my PC. I have written the LPC firmware in such a way it should be accessible by sending custom commands with custom headers through Python script. Now I have generated the binary file (fimrware.bin) which I need to flash onto the board.

Firstly, I had tried flashing the binary file using LPCScrypt which is loading the firmware onto SPIFI. It is flashing the SPIFI correctly and the SPIFI starting address verifies the firmware location. 

However, connecting the board to PC, the board is going to DFU Runtime Boot mode (VID_1FC9 & PID_000C) inherently where I cannot access the firmware. While accessing the board through Python script, it is showing 'no interfaces' since the board is in DFU Runtime Boot bode. I have also tried dfu-util to flash my firmware in DFU mode but failed since its in DFU runtime mode. Next I tried to debug the board with MCUExpresso IDE by connecting the board directly to the PC (installing LPC driver back onto the board instead of libusb-win32) which is although detecting the correct LinkServer Debug probe but failing citing reason that target is not connected. Hence, I am at a stall.

Now my questions are:
1. Since I have only one LPC Link2 board, can I flash my firmware onto it by directly connecting it to my PC? 
2. How to access the SPIFI at the start and prevent the board go to DFU Runtime boot mode?
2. For debugging through MCUExpresso, what configurations and connections do I need?
3. I have seen the LabTool application is working fine on the board which specifically places their firmware in the installation folder and to my knowledge, loads it every time on RAM to access the firmware. Can I also follow the same approach since I have only one board and can access it through RAM? (I am okay to re-run the Python script every time)

OM13054  LPCOPEN-SOFTWARE-FOR-LPC43XX 


Your help would be highly appreciated.

[Omar_Anguiano]

LPC Link2 board can be used as evaluation board for LPC4370 with LPCScrypt.
To boot from USB0: JP1 not fitted
To boot from SPIFI: JP1 fitted

Solved: Can I use a single LPC-Link2 and program the LPC4370 on it? - NXP Community

You can load firmware on it however it cannot debug itself, you will need another debug probe.

Best regards,
Omar