You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have built TNC on a breadboard (version with STM32L432KC). Uploaded firmware (firmware.bin) and tried to connect with tnc1-python-config. It allows to connect to device, the button Connect changes to Disconnect, but in the upper left corner it still says "Not connected" and all fields seem to be set to default values (e.g. TNC Information shows "Uknown" and "Unsupported").
Rebuilt firmware from source and started debugging with gdb. It seems to be initializing normally, then getting into a loop analyzing audio. I enabled define KISS_LOGGING and got some meaningful debug output on the serial console. This is the start of it:
Tried to place breakpoints in all serial port callbacks, but they don't fire neither using tnc1-python-config nor when connecting with serial console and trying to send keystrokes.
Operating system: Linux (Ubuntu 18.04 LTS)
Thanks in advance!
The text was updated successfully, but these errors were encountered:
I have built TNC on a breadboard (version with STM32L432KC). Uploaded firmware (firmware.bin) and tried to connect with tnc1-python-config. It allows to connect to device, the button Connect changes to Disconnect, but in the upper left corner it still says "Not connected" and all fields seem to be set to default values (e.g. TNC Information shows "Uknown" and "Unsupported").
Rebuilt firmware from source and started debugging with gdb. It seems to be initializing normally, then getting into a loop analyzing audio. I enabled define KISS_LOGGING and got some meaningful debug output on the serial console. This is the start of it:
Tried to place breakpoints in all serial port callbacks, but they don't fire neither using tnc1-python-config nor when connecting with serial console and trying to send keystrokes.
Operating system: Linux (Ubuntu 18.04 LTS)
Thanks in advance!
The text was updated successfully, but these errors were encountered: