topic Multiple Link 2 programming in MCUXpresso General

Multiple Link 2 programming

loosecannon — Wed, 05 Sep 2018 19:26:42 GMT

Is there some instruction on using multiple LPC-LINK 2 devices for command line programming? The GUI tool has the capability of selecting a device but the command line seems to try and use the last connected. In this case, the devices are programed with the CMSIS-DAP firmware using LPCScrypt to avoid the problem of booting more than one device at a time.

This is a nice page on using the command line tools

https://community.nxp.com/thread/389139

And this is a nice page on using multiple LPC-Link2 probes

https://community.nxp.com/message/630847

However, I cannot find information on using multiple probes to command line program.

Thank you for your help

Re: Multiple Link 2 programming

driesmoors — Fri, 07 Sep 2018 03:25:58 GMT

Does this thread help you? https://community.nxp.com/thread/456839

Alternatively, have you considered using other tools such as Flash Magic? If Flash Magic supports your IC, it can do precisely what you want.

Re: Multiple Link 2 programming

loosecannon — Fri, 07 Sep 2018 16:27:11 GMT

Thank you for your response. I was trying to use the GUI tools in LPCXpresso V8.2 but it does not report how it selects one debugger over another. I downloaded and installed MCUXpresso and there is a new parameter –ProbeHandle. The order does not seem consistent.

Searching for ProbeHandle with crt_emu_cm_redlink does find a thread about programming but not a way to resolve a ProbeHandle to a serial number.

https://community.nxp.com/thread/459394

Killing all active debug components will also reset the probe handles. The order assigned seams arbitrary so software would not be able to select a probe by serial number. This thread shows what looks to be the same issue I have. There is an example with another program in the bin folder

https://community.nxp.com/message/783775

redlinkserv.exe –commandline

Which lets you execute a command “probelist” to enumerate probes on the console. The problem is when trying to run the crt_emu_cm_redlink.exe to program; it fails to find a probe when supplying a ProbeHandle. It looks like others have tried this and nobody has had any luck.