Rev D2 - JP3 Open - normal Boot, Closed DFU LPC link Boot.
https://www.nxp.com/docs/en/supporting-information/LPCXPRESSO-V2-BOARD-FAMILY-SI.pdf
you should close it for LPC link mode. that should be the 3.3V connection to the linker, which then gets priority when booting.
15 minutes ago, Rio said:
Rev D2 - JP3 Open - normal Boot, Closed DFU LPC link Boot.
https://www.nxp.com/docs/en/supporting-information/LPCXPRESSO-V2-BOARD-FAMILY-SI.pdf
you should close it for LPC link mode. that should be the 3.3V connection to the linker, which then gets priority when booting.
Unfortunately I have the same behavior 
try again from the beginning. should normally go now (reboot, reinstall, reconnect etc.) otherwise something went wrong .. or the linker type isn’t supported by 8.2.2 ?? I will take a look later.
In some posts, people get in trouble with CMSIS-DAP. but take a look here:
On the other hand, I read that it probably also worked with 8.2.2 … I can’t test it myself (i have only rev.A B C). Do you have the chance to grab an older revision? Don’t you want to go to the newer CPU sooner if that is so much trouble? But you could still do some research … it’s up to something.
From the document “As supplied, (JP1 - no jumper fitted, JP2 - jumpered across 1-2, JP3 - no jumper fitted), the built in LPC-Link2 based debug probe works as a plug’n’play debug probe with the LPCXpresso IDE. The first time you start an LPCXpresso debug session, a compatible debug firmware image is downloaded to the debug probe allowing you the debug the onboard target MCU.”
JP2 has no pin thus is not jumpered.
rev D should work:
<___base_url___>/topic/20471-new-lpc1769-boards-and-mios/?tab=comments&do=embed&comment=178303&embedComment=178303&embedDo=findComment#comment-178303
I’m not sure what else to do … but maybe try another PC. After that you can find out what’s going on with the current one.
I’ve tried on another compter and I have the same result.
In both cases the board shows up in Blutooth & other devices.
did you try this:
< base_url >/topic/20087-lpc1769-rev-d-board-how-to-load-bootloader/?do=embed
If his guidance on the rev D doesn’t help, you could PM him. at least he managed it.
Edit: Oh, I just checked again at myself: I had actually successfully flashed a Rev D1 via the IDE 8.2.2 in the past. I can’t remember any unusual things now.
Ok, i have found my rev.D1 board again and plugged it in. It’s using CMSIS DAP linker too.
Yes, it is also not found (with closed jumper). So something is still fishy. Have you ever tried to load the host drivers from nxp:
at the bottom:
I think that’s for it ..
Just now, Rio said:
Ok, i have found my rev.D1 board again and plugged it in. It’s using CMSIS DAP linker too.
Yes, it is also not found (with closed jumper). So something is still fishy. Have you ever tried to load the drivers from nxp:
at the bottom:
Host Device Drivers ( 1 )
- Firmware and drivers for LPC11U35 debug probes
I’ve just done so, same result
In the IDE console I have
[Started server] [Connected on port 3025] redlink\>ProbeList No probes found
and did you install LPC11U35 installer before and restart PC?
i found this too:
did you follow these instructions?:
I know tired but it should work at some point.
Just now, Rio said:
and did you install LPC11U35 installer before and restart PC?
Yes…
Just now, Rio said:
i found this too:
did you follow these instructions?:
I know tired but it should work at some point.
The board is different, I cannot get the disk to mount.
The board isn’t different…LPC11U35 is the CMSIS-DAP Debug Probe board name, or not? and it is referred to by the LPC1769 board rev.D on that side.
5 minutes ago, Rio said:
The board isn’t different…LPC11U35 is the CMSIS-DAP Debug Probe board name, or not? and it is referred to by the LPC1769 board rev.D on that side.
That picture is not a REV D.
there are 3 more links at the bottom by ZhangJennie, about that post about 1769 rev.D problems, referred to:
- MBED serial driver
- probe firmware
- Can’t find debug Probe ticket..
I know the picture you posted/shown is related to a lpc8xx but I think it uses the same probe (CMSIS-DAP).
BTW: You have to think of it this way: there are two boards - on the one hand it is the debug / linker probe and on the other hand the LPC1769 board - both are connected. If the jumper is set, the probe has priority.
ok i tried the same steps that you mentioned. And I come to the same conclusion that it does not work under win10 as you described ( with me, however, no drivers are shown in the device manager ). I don’t quite get it - I’m (actually) sure I got it installed in the past - but that was a win7. But when I try to install it in Win7 it doesn’t work either. When installing the mbed driver, the same error message appears. it is really crap right now … maybe gerald.wert has an idea, he also successfully connected it, just didn’t write how.
ok, i have now tested a different usb cable (the cable is short and thicker - it looks more stable ). Everything works now (also with win7 and win10 ). The jumper must be removed , otherwise the linker will not work. no mbed driver needed or anything else…it worked for me without installing anything or without updating the firmware now. but i’m not sure if i ever installed the mbed stuff before i was switching to win10 - that was 2 years ago, but I don’t think so, because I restore a untouched/clean OS once a year.
so either you actually don’t have a really good short cable at hand, or you have an old firmware on the probe.
check out:
better cable
update linker/probe firmware
have a look here:
so, therefore you can hold ‘reset’ button on board or solder a bridge on JP4. I just did the solder solution. that’s working. so you get into the ISP mode and you can copy the newer not mbed-based firmware for the linker board (LPC11U35 debug probe) again. I didn’t do that now, because my board already works, but it should work as described here.
Quote
That year we introduced a new version of the firmware that was not based on mbed…
