LPC55S69_IF and MCUXpresso

Hallo!
I look and “play” with DAPlink – develop, because I am interesting into LPC55S69 for DAPlink. (for private study project).

I want to gib some issue.
I hope ist not ebnouch :).

(1) In your readme.md develop is an issues:
(1a) in “**Step 1.** Initial setup.” does not work “git checkout develop” on Windows10
(1b) typing mistake: “ ## Activate virtual environment / **Step 2.**”
`$ venv/Scripts/activate.bat (For Windows) ` TO `venv\Scripts\activate.bat (For Windows)`

(2) LPC55S69_IF and MCUXpresso
I try your develop in my develop system (Win 10, VM (Win10) for generate project)
I make Eclipe project in MCUXpresso of LPC55S69_BL and _IF.
Both can compile very well. Then the firmware (BL) was programmed to MCU-LINK hardware.
I want to use DAPLink-develop LPC55C69 with MCUXpresso.

But MCUXpresso will connect the daplink always with JTAG.

I have also tried with your firmware "0256_lpc55s69__0x10000.bin" from "firmware-0256-3406476e.zip"

I have also tried to disable JTAG in DAP_config.h:
```
/// Indicate that JTAG communication mode is available at the Debug Port.
/// This information is returned by the command \ref DAP_Info as part of Capabilities.
#define DAP_JTAG 0 // [RS 2021.07.08] 1 ///< JTAG Mode: 1 = available, 0 = not available.

/// Configure maximum number of JTAG devices on the scan chain connected to the Debug Access Port.
/// This setting impacts the RAM requirements of the Debug Unit. Valid range is 1 .. 255.
#define DAP_JTAG_DEV_CNT 0 // [RS 2021.07.08] 4 ///< Maximum number of JTAG devices on scan chain

/// Default communication mode on the Debug Access Port.
/// Used for the command \ref DAP_Connect when Port Default mode is selected.
#define DAP_DEFAULT_PORT 1 ///< Default JTAG/SWJ Port Mode: 1 = SWD, 2 = JTAG.
```

TERMINAL:
```
MCUXpresso IDE RedlinkMulti Driver v11.3 (Mar 30 2021 16:50:12 - crt_emu_cm_redlink build 18)
Found chip XML file in C:/Users/XXXX/OneDrive/_Projekte_XXXXXXX/MCUXpresso_demos/WS_LPC1549_SWO_demo/Z_LPCopen_test_SWO_001/Debug\LPC1519.xml
Reconnected to existing LinkServer process.
Connecting to probe 1 core 0 (using server started externally) reports:
'Ee(42). Could not connect to core.'
Retrying...
Reconnected to existing LinkServer process.
Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core.
============= SCRIPT: LPC15RunBootRomConnect.scp =============
Error: Hardware interface transfer error
Error: Wire not connected
Error: Wire not connected
Error: Wire not connected
Error: Wire not connected
Halt on reset vector catch
Error: Wire not connected
Error: Wire not connected
Error: Wire not connected
Error: Wire not connected
Error: Wire not connected
Halt on watchpoint write of ROMWSCTRL register
Error: Wire not connected
Error: Wire not connected
============= END SCRIPT =====================================
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port
```

CONSOLE – REDLINK:
```
[Closed]

[Started server]
[Connected on port 3025]
redlink> ProbeList
Index = 1
Manufacturer = Arm
Description = CMSIS-DAP v1
Serial Number = 00000080f73f9e125231fe3851580eaa3016cc084c504355
VID:PID = 0D28:0204
Path = \\?\hid#vid_0d28&pid_0204&mi_02#9&23a6fe2b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink> ProbeStatus
Index = 1
Manufacturer = Arm
Description = CMSIS-DAP v1
Serial Number = 00000080f73f9e125231fe3851580eaa3016cc084c504355
VID:PID = 0D28:0204
Path = \\?\hid#vid_0d28&pid_0204&mi_02#9&23a6fe2b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE ** BY DAPlink256 - LPC4322_IF : _WireInitialized = TRUE_**
WireProtocol = JTAG ** BY DAPlink256 - LPC4322_IF : _WireProtocol = SWD_**
CoresConfigured = FALSE
PacketSize = 64
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink> ProbeIsOpen 1
FALSE
redlink> ProbeOpenByIndex 1
Probe Handle 1 Open
redlink> WireIsConnected 1
FALSE
redlink> WireSwdConnect 1
Error reading from server (redlinkserv.exe):
Read timed out
Error reading from server (redlinkserv.exe):
Read timed out
[Closed]

[Connected on port 3050]
[Closed]

[Closed]

[Connected on port 3075]
[Closed]

[Closed]
```

pictures available

(3) Asserfile wenn jump to bootloader again wich jumper
If I jump to bootloader again, with jumper on “Short To Disbale VCOM”, a file is apperars:

Content:
```
Assert
File: ../source/daplink/drag-n-drop/vfs_manager.c
Line: 360
Source: Application
```

My contribution is probably a very small one, but when I use something, I want to give my gratitude back with a few reminders in order to make a project perfect. I would like to say again a big thank you for this project.

best regards
Robert

Start by separating the README.md corrections from the LPC55S69/MCUXpresso connection report and the bootloader assertion. Read DAP_config.h and source/daplink/drag-n-drop/vfs_manager.c around line 360, then reproduce the reported JTAG/SWD and bootloader behavior if the hardware is available. Done should mean each problem has a confirmed scope, reproduction details, and either a focused fix or a separate issue.

Written by the indexing model from the issue text.