msDebug Fails to Be Debugged in the Container Environment and HDK Driver Package Needs to Be Installed

Symptom

The message "msdebug failed to initialize. please install HDK with –debug before debugging." is displayed.

Possible Cause

The HDK driver package is not installed using the --debug option, or the driver device node /dev/drv_debug on which the msDebug tool depends is not mapped to the container environment.

Solution

1. Check whether the host machine uses the --debug option to install the HDK driver package.
   If the command output is the same, the debugging driver has been installed. Otherwise, run the--debug command to install the matching HDK driver package.

   [mindstudio@localhost ~]$ ls /dev/drv_debug     #Check whether the /dev/drv_debug device node exists.
   /dev/drv_debug

2. If the driver package has been installed and the operator operating environment is a container, check whether the container environment meets the following conditions:
   • The device node /dev/drv_debug on which debugging depends can be found.
   • The container environment has permission to access the device node.

   

   You are advised to add the --privileged --device=/dev/drv_debug option to the container startup command to ensure that the device node on which debugging depends is mapped and the container environment can access the node.