Hi,
Win10 can run a subsystem, which is Ubuntu for me, in the powershell environmental. But I can not connect the pca10040 debugger. it show error when I try to erase the board.
ERROR: There is no debugger connected to the PC.
Hi,
Win10 can run a subsystem, which is Ubuntu for me, in the powershell environmental. But I can not connect the pca10040 debugger. it show error when I try to erase the board.
ERROR: There is no debugger connected to the PC.
I assume nrfjprog works only on Windows because it uses SEGGER DLLs and others. These rely on SEGGER J-Link driver which connects J-Link OB (on nRF5x DK) over USB with PC host. Not sure how that would work in Linux subsystem of Win10... But once you have Windows why you don't use that directly? Alternatively follow guide about how to flash on Linux (by using OpenOCD I suppose) without nrfjprog and SEGGER tools.
I assume nrfjprog works only on Windows because it uses SEGGER DLLs and others. These rely on SEGGER J-Link driver which connects J-Link OB (on nRF5x DK) over USB with PC host. Not sure how that would work in Linux subsystem of Win10... But once you have Windows why you don't use that directly? Alternatively follow guide about how to flash on Linux (by using OpenOCD I suppose) without nrfjprog and SEGGER tools.
Excuse me but then I don't understand the point of having Makefile(s) using nrfjprog under nRF5_SDK_12.3.0\examples\peripheral\{PROJECT}\pca10028\s130\armgcc
I'm as well trying to get blinky Makefile working in Bash on Windows 10 and I don't get why it is advised to not use nrfjprog since nrfjprog is already used in the example Makefile.
I installed nrfjprog, gcc-arm-none-eabi, JLink and set up the COM (Windows) to Serial Port (Linux) link and then I find this answer...
KoenigsCould you please open a new devzone case with your question? You can refer to this case if you want to.
Yes that's what I did actually https://devzone.nordicsemi.com/f/nordic-q-a/36986/windows-subsystem-for-linux-wsl---error-there-is-no-debugger-connected-to-the-pc
Thanks