Issues while program flash multiple device

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Issues while program flash multiple device

2,116 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by partheepan on Wed Sep 09 06:31:21 MST 2015
Hi,

I am using a couple of lpc824 boards (OM13071).

I have connected them to a single pc and trying to flash program them by selecting the device from the connect to emulator pop up. Whichever device I select the same device is programmed again and again and not the other one by the GUI.

I tried coping the flash command from GUI and got this one

crt_emu_cm_redlink -flash-load-exec "C:\Users\elpk5\Documents\LPCXpresso_7.8.0_426\workspace\i2cTest\Debug\i2cTest.axf" -g -2  -vendor=NXP -pLPC824    -reset=vectreset -flash-driver=LPC800_32.cfx

Where this one is the same for whichever device I select. And this command doesnt specify anywhere that it selects the specific device.

I then moved to the command line and tried to select a particular device but unable to succeed as the hid seems to be similar for both the devices.

I tried using the wire command and tried copying the serial number of the devices but still the same device was programmed again and again. 

The command I used was

For one

C:\Users\elpk5\Documents\LPCXpresso_7.8.0_426\workspace\i2cTest\Debug\i2cTest.ax
f" -g -2  -vendor=NXP -pLPC824  --wire
\\?\hid#vid_0d28&pid_0204&mi_03#8&22e35216&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

For another
C:\Users\elpk5\Documents\LPCXpresso_7.8.0_426\workspace\i2cTest\Debug\i2cTest.ax
f" -g -2  -vendor=NXP -pLPC824  --wire \\?\hid#vid_0d28&pid_0204&mi_03#9&350bb73a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

Could you give me suggestions if I am making any mistake.
I want to connect both the devices to the same pc simultaneously and program them separately by selecting them individually.

I am attaching some of my screen shots.

Thanks in Advance.

0 Kudos
6 Replies

1,956 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Sep 22 07:48:20 MST 2015

You didn't provide enough console output to determine where the trouble might be. For the time being please consider this as unsupported, and we'll investigate a fix in a future release.

Thanks and regards,
LPCXpresso Support
0 Kudos

1,956 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by partheepan on Mon Sep 21 03:48:15 MST 2015
Hi,

I still couldn't resolve this issue. Just wanted to know that are you still working on this issue.

Thanks
0 Kudos

1,956 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by partheepan on Fri Sep 11 04:19:28 MST 2015
Thanks for your reply.

I tried doing the probe list command and got the list. And went back to the flash dialog box and tried adding -ProbeHandle=1 and  -ProbeHandle=2 command to the Extended Additional Options. But it still flashes the same board again and again.

I then went back to command line and tried to do the same adding -ProbeHandle command but still not working.

I have attached all the screen shots for what i did.

Please do help me to solve this problem.

Thanks in advance.
0 Kudos

1,956 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Thu Sep 10 14:58:53 MST 2015
It's really not necessary to use the command-line interface. The Flash Dialog has a list box named "Extended Additional Options" where you can add the parameter I mentioned earlier. As far as determining which is probe 1 and which is probe 2, you can DFU the CMSIS-DAP probe (see boot_link2 script) to each probe in turn, and make note of the HID Path, or the Device Manager Device Instance Path.

To view the connected probes in the Redlink Server using the command-line interface, start the Redlink Server using the command-line below. The ProbeList command will list the enumerated probes. Note in this case, probe 1 has booted the CMSIS-DAP bridge firmware image, and  probe 2 has booted the CMSIS-DAP non-bridge firmware image.

C:\nxp\LPCXpresso_7.9.0_455\lpcxpresso\bin>redlinkserv.exe -commandline
redlink>probelist
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.112
VID:PID = 1FC9:0090
Instance Object:        0
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#8&ff48f8a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

Index = 2
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.112 NB
VID:PID = 1FC9:0090
Instance Object:        0
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#a&13980cf4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030
}

redlink>

Thanks and regards,
LPCXpresso Support
0 Kudos

1,956 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by partheepan on Thu Sep 10 05:01:49 MST 2015
Thanks for your reply.

Could you please let me know where could I find the parameters and could you please give me an example command line as it would be a great help.

Thanks.
0 Kudos

1,956 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Sep 09 14:32:44 MST 2015

The LPCXpresso Flash Dialog does not support multiple probes. If it did, you would see the command line include a '-ProbeHandle=' argument. However, there's no reason why you can't do this from a command shell provided you know the parameter yourself. You can try adding:

-ProbeHandle=1 or -ProbeHandle=2 to the command line


Thanks and regards,
LPCXpresso Support
0 Kudos