Post Reply 
How to do combined debugging of my HP-41 projects
01-30-2022, 11:35 PM (This post was last modified: 01-31-2022 06:52 PM by hth.)
Post: #1
How to do combined debugging of my HP-41 projects
I have a couple of HP-41 modules that I suspect are a bit underused.

To make it easier to try them out with my Calypsi HP-41 tools out I have created an umbrella project that allows for debugging the HP-41 system with my main MCODE modules plugged in.

This project should be cloned recursively as it has the other projects as submodules using:

Code:
git clone https://github.com/hth313/hp41-OS4-interopability.git --recurse

To try it out you will also need to install my Calypsi tools for the HP-41 Nut target and the VS Code IDE.

Launch VS Code and open the folder of the cloned hp41-OS4-interopability project. The build task can be used to build all the sub-projects together as a single module which contains the HP-41 mainframe operating system, the OS4 operating system extension, Ladybug (HP-16C clone) and my Boost41 module. Both Ladybug and Boost41 are OS4 aware.

Running the project will start an instance of my HP-41 debugger. Open the /usr/local/lib/calypsi-nut/dbnut-ui/hp41.html (UNIX style path, it will be elsewhere on a Windows system) page in a browser to display an HP-41 calculator user interface for the debugged instance.

In the debugger you can set breakpoints (also conditional ones) step around and when stopped you can study how the internal CPU registers change as you move around. And yes, you will step around in the actual HP-41 source code and study see how it works.

Happy MCODE programming!

References:
https://www.hpmuseum.org/forum/thread-17897.html
https://code.visualstudio.com/
https://github.com/hth313/hp41-OS4-interopability.git
https://github.com/hth313/ladybug.git
https://github.com/hth313/boost41.git
https://github.com/hth313/OS4.git
https://github.com/hth313/mainframe.git

Troubleshooting:
In case VS Code does not allow setting breakpoints in assembly files, try Command-K M (use Ctrl on Linux, Command on macOS), then select C as the language mode. For some reason VS Code does not think it is possible to debug assembly projects at source level out of the box.
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: 1 Guest(s)