RemoteMCU - Troubleshooting Page

Troubleshooting Page

Note: There are no guarantees about the work with Python 3 for now. We recommend to use Python 2 with REMCU Lib.

If remcu_connect2OpenOCD(...) or remcu_connect2GDB(...) can not connect to debug server:

  1. Check that the debug server is running and functioning perfectly. Try to flash a firmware into chip and and debug it.
  2. Verify all input arguments:
    • Debug server ip.
      In Windows OS case, use "127.0.0.1" instead of "localhost" if debug server is running on local host.
    • Port of debug server
    • Timeout is not negative

If remcu_getErrorCount() function returns value greater than zero:

  1. Make sure that you have right REMCU Library for your MCU/SoC. For example: you should remcu-STM32F10X_HD-... version of the library for STM32F103RC chip or other STM32 of high-density performance line family. You can get version with help remcu_getVersion() function.
  2. Check debug server connection. You can use remcu_isConnected() function for this.
  3. Verify that the debug server is running and functioning perfectly. Try to flash a firmware into chip and and debug it.
  4. See Issue

If remcu_debuggerTest() function returns non-null. First, replace your debug server(OpenOCD, ST-link GDB server, Jlink GDB server etc.) and then try to change your debug adapter.

If bugs are not discovered and the chip don't responds to driver function call or the result of work was not what you expected, you try the suggestions listed below:

  1. Make sure that you have right REMCU Library for your MCU/SoC. For example: you should remcu-STM32F10X_HD-... version of the library for STM32F103RC chip or other STM32 of high-density performance line family. You can get version with help remcu_getVersion() function.
  2. Verify that the debug server is running and functioning perfectly. Try to flash a firmware into chip and debug it.
  3. Get another Openocd version (later or equal v0.10.0-11-20190118)
  4. Use ST-link GDB server (from Atollic IDE) instead of Openocd and vice-versa
  5. Use Jlink with Jlink GDB server if you have it.
  6. Check your device. Is the MCU board in good condition?
  7. Verify work of these functions by running firmware with that code on the chip. Make sure that the work is correct.
  8. See Issue

If you use REMCU Lib on Raspberry Pi Board (see examples) and you were faced with some problems:

  • Verify wire connection
  • Check GPIO pins of Raspberry. Is they in working order? Try to toggle theirs . Snippet
    • Show scheme (click here)
  • Check your device. Is the MCU board in good condition?