Debug Now doesn't recognize app's zephyr.elf file

MikeH

Using Debug Now GUI button generates this line in launch.json:

"${workspaceFolder}/nfed/samples/mqtt/build/circuitdojo_feather_nrf9151@2/mcuboot/zephyr/zephyr.elf"

It should be:

${workspaceFolder}/nfed/samples/mqtt/build/circuitdojo_feather_nrf9151@2/mqtt/zephyr/zephyr.elf"

It is a new project copied from nfed/samples/blinky and located at nfed/samples/mqtt.

Unable to see any differences in folder hierarchy between blinky and my new mqtt folder.

jaredwolff

@MikeH ahh there’s a bug in the .elf discovery. I just pushed version 0.5.11 which should address this

MikeH

I upgraded to version 0.5.11. Why does it want to Run Setup? Getting this output:

git version 2.52.0.windows.1
[SETUP] git installed
[SETUP] Checking python...
[SETUP] Found python: Python 3.10
[SETUP] Python 3.10 meets requirements (>= 3.10)
[SETUP] Using Python: python
python -m venv "C:\Users\mikej\.zephyrtools\env"
[SETUP] unable to setup virtualenv

Everything else was working correctly before the upgrade.

jaredwolff

Can you delete that env folder and try again?

There was a fix pushed related to serial monitor on Windows which required a fresh setup. It’s breaking probably because the env already exists. In my testing usually you can write over it. I guess not on Windows.

jaredwolff

I just pushed v0.5.12 which will do this automatically for the future.

MikeH

Yes, deleting the folder gets passed that error, but then I had to manually reinstall several python packages in the new venv to get sample projects to rebuild.

jaredwolff

Yup since they get deleted. You can do it by running Zephyr Tools: Init Repo on the already existing project. That should get everything you need.