Hello,
I'm currently trying to setup my MCU-Link probe.
But it dosen' show up in the MCUxpresso IDE.
When i try to update the MCU-Link via LinkServer the probe is unlisted (jumpers are open an the LED is off).
When i try to update via ISP (J3 is closed and the LED is red) the MCU-Link is not found.
Is there any other way to update the MCU Link?
Hello,
Could you help us confirm that when installing the Linkserver, you select "Associate with existing MCUXpresso IDE installations" and associate the MCUXpresso IDE installations, please refer to photos.
Could you help us share what it shows your device manager for the debugger?
Probably you need to update your MCU-Link driver. Please help us following these steps:
- With J3 open in MCU-Link probe.
- In device Manager, Right Click on the debugger and select "update driver"
- Select "Browse my computer for drivers" and search for the driver in the location: "C:\nxp\LinkServer_25.12.83\MCU-LINK_installer\drivers:"
- After updating the driver, please retry to update the debugger via ISP mode (with J3 closed) by running "program_CMSIS.cmd" script in [C:\nxp\LinkServer_25.12.83\MCU-LINK_installer\scripts]
Please let me know if that work for you.
Best Regards, Luis
Hello Luis,
I reinstalled my LinkServer 25.12.83 to make sure that the right boxes are checked.
However after updating the driver again, i still couldn't update the MCU LInk via ISP.
Here is a Picture of the Devicemanger for the Link in ISP Mode
And one in normal Mode
Hello,
There is a method for update using Link Server without the jumper for entering ISP
Jumper-less Update with Linkserver
Could you help us trying this method:
- Open in cmd the LinkServer path location:
- Enter the command: "LinkServer probe #1 update auto"
Please let me know if that work for you.
Also, could you help us confirm which firmware version you have currently?
Best Regards, Luis
since my MCU Link is flagged as unlisted i'm unable to update via LinkServer. I also tried #0 udate auto and #update auto and update auto.
I have no way to update the MCU Link and i would like to know why. Clearly the problem with "unlisted MCU Link" must have happend before. I can't be that NXP doesn't know how it can happen that the MCU Link is unlisted and not able to be updated.
Hi @Ebner ,
I had such an 'unlisted' probe in one case where I had accidentally set the 'SWD disable' jumper.
Can you check this?
See https://mcuoneclipse.com/wp-content/uploads/2020/11/mcu-link-board-top-side.jpg
I hope this help,
Erich
Hello Erich,
Thank you for your reply.
There is no Jumper at J5. And i measured if ther is a shortcut inside the PCB between the two pins. There is none.
We tested it on the PC of an colleague an there was the same behaiver.
Ok, I believe it might be a problem with your host OS caching mechanism.
Could you follow the extra steps below which collect some extra information which could be helpful to pinpoint the problem?
The process is the following:
a) dump some registry keys so I can see what are your current values. Please provide these values.
b) next, apply a workaround which forces a USB device enumeration
c) run again a script to dump the new registry file content. Please provide that information.
Step a):
I have attached some registry keys in the attached paths.txt file. Save the file locally, then execute the command below to export registry content:
for /f "usebackq delims=" %P in ("paths.txt") do reg query "%P" /s >> reg_dump_before.txt
This exports some registry keys to that reg_dump_before.txt for diagnostics. It would be great if you could share that content.
Step b):
run the following to force a re-enumeration:
- Have the probe unplugged
- Set jumper for VCOM disabled. On the MCU-Link this is J4 or the middle jumper)
- Plug-in probe to PC
- Remove jumper for VCOM disabled (so enable back VCOM)
- Re-plug the probe to PC
This forces Windows to re-enumerate the USB device with the current configuration and hopefully solves the problem.
Step c):
it would be very helpful to see that are the registry keys after that. So can you run the following line to export the values to a different file:
for /f "usebackq delims=" %P in ("paths.txt") do reg query "%P" /s >> reg_dump_after.txt
Then it would be very helpful if you could provide the content too.
I hope this help,
Erich
Hello,
Thank you for help.
Unfortunatly it didn't solve the Problem.
Attached are the dump filed before and after.
I hope this brings you closer to the solution.
Hi @Ebner,
Somehow community notifications did not work for me, seeing the log files only now :-(.
Erich