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
Build environment: Linux on Raspberry Target device: wt32-eth01
Description
@ralphwetzel was investigating an issue for me, and he found out that it is not possible to set a custom port (5004) on xsbug-log via the "-x" parameter. As you can see in his log, xsbug-log keeps listening to the default port (5002):
>> IDF_PYTHON_ENV_PATH: /home/ralph/.espressif/python_env/idf4.4_py3.10_env
>> mcconfig -d -x localhost:5004 -l -m -p esp32/wt32_eth01 -t xsbug
/home/ralph/esp32/esp-idf/tools/idf.py
# starting xsbug
# xsbug-log listening on port 5002. ^C to exit
Steps to Reproduce
Run the above command
See in the log that it starts listening to the default port
Expected behavior
That xsbug-log starts listening at the port specified with the "-x" parameter.
Thanks!!
Bart
The text was updated successfully, but these errors were encountered:
Thanks a lot for your fast support!!!
I can indeed confirm that (after applying your fix) xsbug-log now indeed start listening on port 5004 via Ralph's sidebar.
So you can close this issue!
Build environment: Linux on Raspberry
Target device: wt32-eth01
Description
@ralphwetzel was investigating an issue for me, and he found out that it is not possible to set a custom port (5004) on xsbug-log via the "-x" parameter. As you can see in his log, xsbug-log keeps listening to the default port (5002):
Steps to Reproduce
Expected behavior
That xsbug-log starts listening at the port specified with the "-x" parameter.
Thanks!!
Bart
The text was updated successfully, but these errors were encountered: