But it’s NG.
STM32F401 - UART(PA2/PA3) - STLink(on NUCLEO-F401RE) - STLink Virtual COM Port - VisualStudio
Looking for a device on transport 'Serial'.
Found device port 'Serial' with ID '3dca2ecd-b447-4599-893f-6f025836bbe5' for transport 'Serial'.
Starting device deployment.
Attempting to connect to device 'Serial:COM11': iteration 0.
Opening port '\\.\COM11'.
Attaching debugger engine.
Cannot attach debugger engine!
I checked UART signal used Saleae Logic, STLink send data is parity added.
Then I test original application, parity is none.
Original App -> STLink Virtual COM Port - STLink(on NUCLEO-F401RE)
This sequence is fine.
1.Connect PC and NUCLEO-F401RE.(UART debug firmware in NUCLEO)
2.Deploy apps on VisualStudio … ERROR
3.Run original windows app. (Set Parity none to COM)
4.Retry to deploy apps on VisualStudio … fine!
So I can understand correctly, you’re asking for this because the STLink serial port sets the parity on the PC to something not “None” and this conflicts with what the debugger on the device expects?
and this way maybe can include inside vsix onto vs2017 so when we select serial to have ability to change also parity mode to none (or play with other modes too for serials) to debug/upload.
but only as mentioned @matsujirushi above which parts
1.TinyCLR OS Firmware communicate 115200,8,1,N by UART.
2.vsix communicate 115200,8,1,?. (Not explicitly specified parity setting. use default setting.)
3.Some device’s default is none-parity. It worked nomally.
4.But STLink Virtual COM default is NOT none-parity. Don’t communicate between device and vsix.
Run original windows app to set none-parity after connecting the device. and immediately close application and UART port.
vsix communicate 115200,8.1.N.