Can't find import

[a-n-d-i]

Hi,

I love the idea to finally have decent debugging in micropython, thank you so much for your effort!

Sadly, I can't get it running, after following the docs for install on a esp32, flashing, ... it can't find the import. And I can't find it either, not in this repo and not in the linked repo. Can you give me a hint?

ImportError: no module named 'debugpy'

[Josverl]

Currently this requires a custom build;

And I notice that I did not clearly document that😬

It should be something like

cd ports/esp32 
make submodules 
make clean
make CFLAGS_EXTRA="-DMICROPY_PY_SYS_SETTRACE"

Let me verify and fix that

[a-n-d-i]

I used this binary, it sort of sounds like it should be included?

https://github.com/Josverl/mp_debugpy/blob/main/firmware/esp32_settrace_save_names/firmware.bin

[Josverl]

yes it should , but apparently does not, and could do with an update to 1.27.0

Im currently away from home on vacation. but i promise Ill try to repro between hiking , swimming and the occasional cold-one .

[a-n-d-i]

Enjoy your vacation and thank you!

That would be very much appreciated. I managed to make a build but the problem persists and I haven't figured out yet why...

[a-n-d-i]

I finally figured it out, the python-ecosys/debugpy stuff does not get backed into the image bc

• there's two micropython-lib dirs, one gets fetched from this repo, one from the external micropython repo. The build process only looks at the first one.
• the ESP32_GENERIC board has no manifest / mpconfigboard.cmake to actually include the code

[Josverl]

indeed - in the vscode configuration it gets copied by one of the vscode
debug configurations --> tasks --> launch/start_debug_***.py scripts
but that is rather complex / hard to follow / fragile - so definitely up for improvement

you should have something like this n the device:

$ mpremote tree
tree :
:/
├── lib
│   ├── dap_monitor.mpy
│   └── debugpy
│       ├── __init__.mpy
│       ├── common
│       │   ├── __init__.mpy
│       │   ├── constants.mpy
│       │   └── messaging.mpy
│       ├── public_api.mpy
│       └── server
│           ├── __init__.mpy
│           ├── debug_session.mpy
│           └── pdb_adapter.mpy
└── target.py

Im adding package.json files to allow the module to be installed using mpremote mip install rather than copying
and some additional documentation

One other thing - you need to have the target device connected to a shared LAN / WiFi network.
Probably simplest to do that in a main.py or through a mpremote run start_wifi.py approach

[a-n-d-i]

Thanks for the explanation! Yeah, that's not very intuitive, especially for folks who don't use vscode.

Could you add like a sentence or two on the "why" of things? I find it pretty hard to get a grasp of what this project is actually doing bc it's spread over different repos and the commit messages are not very telling.

Something like "We bake a custom firmware to enable xy flag for functionality xy which is located someplace. Then we got the libs repo bc ?" Like one sentence for every place where stuff is happening and why it is there.