HI ALL,
v2.8.0, nrf54l15, using the "periphral_uart" demo without any modifications
I downloaded nrf52840 using v2.8.0 and it runs normally, but nrf54l15 has issues.
The steps are as follows:
1.build
2.flash
3.Then
Thanks
HI ALL,
v2.8.0, nrf54l15, using the "periphral_uart" demo without any modifications
I downloaded nrf52840 using v2.8.0 and it runs normally, but nrf54l15 has issues.
The steps are as follows:
1.build
2.flash
3.Then
Thanks
Ubuntu
nano ~/.bashrc
and add a line to the eof with full path to nrfutil location
export PATH=$PATH:/home/nrfutil_location
then apply changes
exec bash
Adding nrfutill to PATH doesn't work for me because... nrfutil is already in PATH.
`west` command fails to find nrfutil when executed from VSCode GUI (ACTIONS->Flash, but works just fine when executed manually from Toolchain shell (Manage Toolchains->Open Terminal Profile).
So I classify it as a bug in vscode plugin - it likely runs `west` command (the one that flashes) in wrong shell env or sth.
I modified `west` script to dump environmrnt and it seems NRF Connect VSCode plugin actively removes any PATH overrides from user's .bashrc and instead tries to construct PATH manually from system + toolchain + SDK.
So if nrfutil is NOT installed system-wide, but for instance in ~/.nrfutil/bin, it will never be located by VSCode.
Where do I report this bug?
I modified `west` script to dump environmrnt and it seems NRF Connect VSCode plugin actively removes any PATH overrides from user's .bashrc and instead tries to construct PATH manually from system + toolchain + SDK.
So if nrfutil is NOT installed system-wide, but for instance in ~/.nrfutil/bin, it will never be located by VSCode.
Where do I report this bug?