PC-based QT emulator debugger?

[jickster]

As discussed here, viewtopic.php?f=3&t=1210#p22174 micropython is a ways off from having full debugger functionality.

However, an alternative to having the debugger run on-target is to build micropython for Windows and somehow run a Python debugger on Windows?

Sure you could run the Python script using Pycharm but there'd be inconsistencies between MicroPython and CPython implementation.

In this post viewtopic.php?f=3&t=3840#p22056 user cduran states

Using QT I developed a sort of debugger for python code running on my firmware. For this I used the same build of micropython just so that I have a dublicate of mp that will behave just like the one on my firmware.

I'd LOVE to know how you did it.

[Simsys]

As I see it, there is no concept for debugging uPy scripts today: neither under Windows/Linux nor on an embedded system. I think that's a pity. Micropython claims to be simple, easy to learn. What else does it make sense to offer Micropython for a platform like The Micro Bit?

A good debugger is especially important for beginners. How does my program work? What's happening right now? Where's what going wrong? If you want to use Micropython on an embedded system you have to know how such a system works and on the other hand you have to be able to program (Python).

Of course, this is a difficult task to realize this function. However, the subject does not seem to be of any real interest either. I can imagine that the circle of users would expand enormously with a good debugging solution.

[pfalcon]

There's, and always has been a concept for debugging in MicroPython, it's very simple and obvious one - you debug in any other implementation of Python (CPython or whatever), and then run in MicroPython. As an intermediate step between CPython and baremetal MicroPython you case use Unix MicroPython.

If that doesn't work for you, you're welcome to implement and contribute a native MicroPython debugger. A lot of users will indeed rejoice at your doing that.

[jickster]

As an intermediate step between CPython and baremetal MicroPython you case use Unix MicroPython.

Can you explain why the Unix port is an "intermediate" step and how it helps with debugging?

Thanks

[pythoncoder]

I think he's suggesting you debug the code under CPython. When it's working you run in under Unix MicroPython to ensure that there are no issues resulting from implementation differences between CPython and MicroPython. If it passes this test then you can be confident it will run on baremetal. Barring (possibly) timing issues...

[stijn]

Plus you can debug the Unix port's C code using gdb if needed

[jickster]

I think he's suggesting you debug the code under CPython. When it's working you run in under Unix MicroPython to ensure that there are no issues resulting from implementation differences between CPython and MicroPython. If it passes this test then you can be confident it will run on baremetal. Barring (possibly) timing issues...

Plus you can debug the Unix port's C code using gdb if needed

Got it; thanks!