"Couldn't find Zephyr root" both SEGGER and VsCode

[Mr.Newlove]

Hello all,

Lost my VM that had a working installation and just setting everything back up.

After installing SDK 1.8.0 and all of the extensions for VsCode. Now both SEGGER and VSCode cannoot find the Zephry root and I cannot find it on disk?

This was not a problem in the past, any ideas?

Thanks

Edit: Another problem... like all of the examples are missing?? searched for serial_lte_modem and it comes up with nothing. Even just searching serial, or application comes up with nothing useful?

Edit2: I installed the most recent 3 releases and none have a zephyr folder anymore?!?!?

[Albrecht Markus Schellenberger]

Hello Kyle,

Mr.Newlove said:

And the nrf9160 is not talking, but if I flash using the Programmer v2.1.1 desktop app from the SDK it works fine?

Well this is strange. But I’m not able to get the attached file to run on my DK neither. Could you try the following in a bash with your nRF9160 DK?

cd ncs/nrf/applications/serial_lte_modem/

west build -b nrf9160dk_nrf9160_ns -p

west flash --erase

Does this work?

Regards,

Markus

[Mr.Newlove]

Albrecht Markus Schellenberger said:

Well this is strange. But I’m not able to get the attached file to run on my DK neither. Could you try the following in a bash with your nRF9160 DK?

Odd, as I said it works fine if I use the standalone loader. Keep in mind I am using different Rx/Tx pins so it wont talk on the standard DK

Mr.Newlove said:

Yes, that would be great. I have tested to create a custom board based on the nRF9160 non-secure myself with the wizard in VS Code. I stored it in my_root_application\boards and it seems to work fine, so no ”The system cannot find the file specified” here. I get build errors for sure, but they are expected without any modifications of the board files itself.

Odd thing, went to test this again after updating the SDK and I am getting different errors now to do with the kconf, but I think those are all solvable. Think its because I didn't actually configure the serial port pins for the new board so it doesn't know what to do.

Albrecht Markus Schellenberger said:

Does this work?

Peculiar, yes that works, but not from within VSCode using the SDK tools

From bash:

$ west flash --erase
-- west flash: rebuilding
[0/21] Performing build step for 'spm_subimage'
ninja: no work to do.
[1/5] Performing build step for 'mcuboot_subimage'
ninja: no work to do.
-- west flash: using runner nrfjprog
-- runners.nrfjprog: mass erase requested
Using board 960031669
-- runners.nrfjprog: Flashing file: C:\ncs\MyApps\serial_lte_modem_uart0_gps\build\zephyr\merged.hex
Parsing image file.
Verified OK.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 960031669 flashed successfully.

From VSCode:

Executing task: nRF Connect: Flash serial_lte_modem_uart0_gps/build (active) <

Flashing build to undefined
west flash -d c:\ncs\MyApps\serial_lte_modem_uart0_gps\build --skip-rebuild -r nrfjprog --snr 960031669 --erase

-- west flash: using runner nrfjprog
-- runners.nrfjprog: mass erase requested
-- runners.nrfjprog: Flashing file: C:\ncs\MyApps\serial_lte_modem_uart0_gps\build\zephyr\merged.hex
Parsing image file.
Verified OK.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 960031669 flashed successfully.

Edit: I have no idea why, but now it works, I didnt change anything, maybe updating the SDK the other day fixed it?