I was using the dev board just fine and was able to flash firmware without issue from mcuexpresso. Now, I get the above error when trying to flash new firmware or even just trying to perform a mass erase. The firmware I flashed just before becoming unable to interact with the board was one of the i2c examples that I had modified by a couple of lines in main. Pressing the reset button on the board doesn't help.
The P7 and P8 headers are in the correct position for SWD.
I have split the board in two and soldered wires across P6 and P5 but I have just checked all the connections with a multimeter and I don't find any shorts or disconnections.
Hello @TheOrangeTeaFrog
If CRP is not the issue, please try updating the debugger firmware on the board as follows:
Connect P2 with a jumper, then repower the board. Click the "Boot Debug Probe" button on MCUXpresso IDE.
After a successful update, import a simple GPIO demo under SDK and try debugging again.
BR
Alice
Hi @Alice_Yang
I think I might have removed the P2 header before powering off, or not unmounted correctly. Anyways, today I have been able to flash the new debugger firmware to the device and, after removing P2 and power cycling, it is recognised by the PC. I am now back to the situation at the start of my post: "Cannot provide power to DAP bus" when trying to flash or mass erase.
I am using Linux but also tried this on a Windows machine to see how it shows in the device manager and noticed some interesting things. First, the device (after being flashed with new debugger firmware) does not appear in the device manager in the same way as your screenshot. Rather than showing "NXP LPC11Uxx VCOM" it just shows "USB Serial Device". I installed the windows driver for the board which was downloaded as part of the same .zip file as firmware.bin. I also installed mcuexpresso on the machine and installed the relevant SDK. After this, I restarted the Windows machine and the device still shows as "USB Serial Device". I know this is the correct device since it disappears/reappears as I unplug and replug the device.
Next, I tried to flash some example code as well as performing a mass erase from mcuexpresso on Windows. This produces the same result as on Linux: "Cannot provide power to DAP bus" but gives a little more context. After clicking on the gui flash button, it searches for debug probes and finds my device. Then it brings up a dialog that allows me to select between performing an erase or flashing some firmware I have built. After this, I get a new dialog called "SWD Configuration" which shows "0 available SWD Devices detected. Connect a device and try again". I then get the usual "Cannot provide power to DAP bus" error.
I am not sure why the "SWD Configuration" dialog only appear on Windows. I have checked the SWD header pins again and they are definitely all correctly placed to enable SWD. I have also performed another continuity test with a multimeter and found no issues. It seems that there is still something wrong.
I was also able to attach a logic probe to the SWCLK, SWDIO and NFC_RESET pins as I attempt to perform a mass erase from MCUexpresso
From top to bottom: SWDIO, SWCLK, RFC_RESET
I don't know enough about SWD to determine if there is an issue here
I cannot see the connection very clearly. Please connect the pins on P5 with those on P6, and do not connect them to the small pad on the left.
Thank you.
BR
Alice
Hi Alice
Apologies if the first photo wasn't clear. The wires are soldered into the holes in the board.
As far as I can tell, my wiring is the same as your diagram.
Additionally, the board was functioning correctly for quite some time with this exact wiring.
I have check for continutity/shorts by placing multimeter probes across the 10 pin debug connector to the solder points on p6 and all seems fine.
Hi @Alice_Yang
I order a new at your recommendation board and I am having the exact same issue again.
Here is exactly what has happened with the new board:
- I took the board out of the packaging.
- I soldered 4 header pins to P4 pins 1 (SCL), 3 (SDA), 5 (VCC), 7 (GND)
- I connected the board via usb to my PC
- I saw that the example code that is preloaded on the board was running: the LED array on the back was lighting up.
- I moved the jumpers on P7 and P8 to the SWD position
- I loaded up the i2c_polling_transfer_master example and flashed this onto the board
- I saw the LED go dark which suggested this worked. I got no errors in MCUExpresso when doing this.
- I connected my logic debug probe and pull up resistors to the I2C pins in the hopes of seeing the I2C signal. I put a 30k resistor between SDA and VCC and another 30k resistor between SCL and VCC. I connected my debug probe to SDA and SCL.
- I pressed the reset button the chip while recording logic. I saw no changes to the SDA/SCL logic lines.
- I tried to flash the board again. I now get errors like before
Nothing I do seems to fix these errors. I have tried different USB cables, unplugging and replugging the board, removing and reinserting the SWD headers, resetting the board via the reset button, restarting MCUexpresso.
The thing that seems most likely to have triggered this would be connecting the pull up resistors but I do not see how this would have fried the chip.
Please check what CRP value do you setting. If it is CRP2 or CRP3 as below, SWD access is disabled.
Please check the CRP value you are setting. If it is CRP2 or CRP3 as shown below, SWD access will be disabled.
BR
Alice
