How do you use the solo1 monitor to see debug print statements #613
Replies: 1 comment
-
I figured something out. After building the custom firmware with make firmware-debug-1 ... I tried to use solo key update which just updates the key to the latest secure version and the USB Serial COM port is not created. After updating the key with the firmware I built (using solo program bootloader solo.hex ) a USB Serial Device (COM3) was created. I connected Tera Term to that port and there are output messages (Baud = 115200 ; Data 8bit;no parity; Stop bits 1 ; Flow Control none). The solo monitor.py specifies a baud rate of 115200; I just am guessing on the other parameters. Because this is a USB connection under the hood, the extra serial port parameters may not matter. |
Beta Was this translation helpful? Give feedback.
-
I was able to create a debug build using make firmware-debug-1.
I was also able to program my solo hacker with this build using the solo1 tool.
However, I do not understand how view the debug messages. Documentation says you can use
solo1 monitor However I do not see a virtual com port created when the device is plugged into the PC.
I run the command as follows
c:\devtree\solo\targets\stm32l432>solo1 monitor COM12
reconnecting COM12...
I would assume that this command would create a virtual serial port.?. However no such port is created.
Is there some additional details on how to set up serial port monitoring with the solo hacker key. I am running Windows 11.
Beta Was this translation helpful? Give feedback.
All reactions