Can´t start debug session anymore

Mbed Studio
21

Hi @g2as, @hase_berlin, @bikeNomad, @faydrus,

Thank you for reporting the bug with port 49,999. We confirmed that there was a case when an incorrect port was used for debugging in pyOCD. The issue was fixed. Fix for it will be shipped with the upcoming 1.3.1 release. Apologies for the inconvenience.

We also keep working on a solution to improve debugging in Studio and on supporting more development boards.

Thanks,
Arek - Mbed Studio team

22

Is there a way to change the port in the preferences or will we have to wait for the patch? If we have to wait for the patch, is there an ETA on the release?

23

Hi Paul,

Unfortunately, it is impossible at the moment. We are planning to allow soon to modify all pyOCD config in Studio. It won’t however be possible in the upcoming 1.3.1 patch release. It should be released at the beginning of next week.

Thanks,
Arek - Mbed Studio team

24

Is there any news on the 1.3.1 patch release that hopefully was coming this week? Is there a website where we can look at release notes for Mbed Studio or download previous versions?

25

I had the same port issue, and Mbed Studio 1.3.1 still has not been released, so I had the idea of the following workaround on Windows 10, and it works in my case: just run the following command as administrator:

netsh interface portproxy add v4tov4 listenport=49999 listenaddress=localhost connectport=50000 connectaddress=localhost

To verify that the command was applied successfully, run:

netsh interface portproxy show all

To remove this rule:

netsh interface portproxy delete v4tov4 listenport=49999 listenaddress=localhost

26

Hi @pmoen, @bthebaudeau,

Apologies for the delay in 1.3.1 release. There was one other issue on Linux that we wanted to fix also as part of this patch. Unfortunately fixing it took longer than expected. 1.3.1 release is created and we finalize testing. It will be most likely distributed on Tuesday next week.

Release notes for Studio are added in Studio. You can access them using Help->Release Notes from the menu.

Kind Regards,
Arek - Mbed Studio team

1 Like
27

Hi Benoit,
That was a clever work around!
This one earned a place into my bag of tricks!
Thanks for the tip.

28

Hi Guillermo,

You’re very welcome!

29

Thanks to the insight by @bthebaudeau, here is what I did on macOS. I installed nmap via homebrew to accomplish a similar solution. Once nmap is installed, you can use the following to forward the ports used by the debugger and Mbed Studio.

ncat -l 49999 --sh-exec "ncat localhost 50000"

This command needs to be entered in the terminal window after the Background Tasks window reports starting the debugger (In the lower right corner of Mbed Studio). This ensures that the debugger has access to port 50000. The following steps will need to be performed each time the debugger is run.

  1. Press the debug program button
  2. Wait for the message “Starting Debugger” in the lower right part of Mbed Studio window.
  3. Enter the above ncat command in a terminal window.

Great job thinking out of the box @bthebaudeau.

1 Like
30

Thanks!

31

Hi,

Patch for Mbed Studio 1.3.1 has just been released today. It should have a fix for starting a debug session on an incorrect port. Apologies for keeping you waiting. Fixing a different issue on Linux took longer than anticipated.

Thanks,
Arek - Mbed Studio team