Espruino Advanced Debug - Anyone have the missing jigsaw puzzle piece?

You are reading a single comment by @Robin and its replies. Click here to read the full conversation.

•

Robin

Sat 2021.10.02

Re-read

https://www.espruino.com/AdvancedDebug
https://github.com/espruino/Espruino/blob/master/README_BuildProcess.md

While I'm able to flash both a release and a debug .hex version built from VSCode using nRFConnect, and am able to build and debug the Nordic blinky and blinky_pwm examples using SEGGER embedded studio, I'm not able to understand (yet) the basic process I need to debug a running Espruino snippet.

I see and can navigate the Espruino .c source within VSCode. I am able to see the SEGGER blinky main.c example but not up to speed on where the background (SDK?) files are just yet, and can place breakpoints within SES and single step debug.

What jigsaw piece conceptually am I missing to somehow use either tool to configure the environment to step through from the WebIDE JS command down to the .c source that activates the hardware?

About

Avatar for Robin @Robin started