locked
Cannot Telnet to port 2342 to see debug output after side load. RRS feed

  • Question

  • We are trying to follow these instructions to see debug output on 192.168.35.2 port 2342 via Telnet after sideloading an application with --debug option.  However we keep getting connection refused.  However, we can connect to 192.168.35.2 port 2345 via Telnet, but it is gdb.  Please advise.

    https://docs.microsoft.com/en-us/azure-sphere/install/qs-blink-cli  

    Tuesday, April 14, 2020 9:39 PM

All replies

  • Hello,

    Welcome to MSDN forums!
    Ensure that you have updated the latest version of SDK and OS in your Azure Sphere device.

    If your PC can connect to the Azure Sphere device, but often drops the connection, you may have a conflict in the IP subnet.

    Azure Sphere uses subnet 192.168.35.*. If you have other software that uses the same subnet, either disable that software or limit the range of IP addresses that it uses.

    For high-level application, you can see the port 2342 with gdb. Please refer Build, deploy, and debug a high-level application from the Windows command line

    "Open a command prompt and use any Windows terminal client to read the output stream from the process. Specify 192.168.35.2 as the IP address and 2342 as the port."

    For more information about debugging with gdb, see GDB: The GNU Project Debugger

    Wednesday, April 15, 2020 2:45 PM
  • Hello,

    Just checking in to see if the above answer helped. If this answers your query, do click “Mark as Answer” and Up-Vote for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.

    Monday, April 20, 2020 4:56 AM