Troubleshoot Common Issues

This chapter describes ways to fix problems you may encounter when you work with the reference image for the ASRock Beebox. You should also see the release notes for this reference image to check for known issues or limitations. In general, you can look for errors in the slogs. For example, you run the following command to check for errors with the Sensor service:

slog2info -b sensor

Sensor and camera issues

The sensor service doesn't start:
Symptoms: When you restart your board, the sensor service doesn't start. If you run the pidin command, you don't see the sensor service running.
Suggested Resolutions: It 's possible that the configuration for the camera connected to your system is incorrect. Here are some ways you can resolve the problem:
- Check that the type parameter matches the type of camera you are using.
- If you are using a GigE camera, ensure that networking is working and that your cables are properly inserted.
- If you are configuring a file camera, ensure that the video file exists and that the camera service has the proper permissions to read the file.
USB Camera isn't recognized:
Symptoms: You have a camera connected to the ports on your Beebox and run your application using the Camera library, the camera doesn't seem to be recognized. This problem can occur when you call camera_get_supported_cameras() and the numSupported returns a zero, which indicates that no cameras are supported.
Suggested solutions:
- The USB camera might not be properly configured or not supported and therefore, not recognized. Ensure that your camera is configured properly in the sensor configuration file; otherwise, ensure that the USB camera is supported.
  For information about how to supported cameras, see “Supported hardware configurations.”
  
  For information about the sensor configuration file, see “Sensor configuration file” section in the Sensor chapter of the System Services guide.
  
  For information about the supported cameras, see “ Supported hardware configurations”
  .

Networking issues

Static IP address won't work: When you try configure a static IP address for the first time, it won't work.
To check if your Beebox is configured with a MAC Address, connect a USB keyboard to the BeeBox and boot it without a USB storage device connected (e.g., USB stick) and complete these steps:
1. After the Beebox boots, press the F2 key to enter the BIOS settings, navigate to Tool > Internet Flash - DHCP (Auto IP). Auto, select it, wait for "Initializing internet connection" to finish Navigate to Exit, and then select Save Changes and Exit.
If you need to connect to a target using its IP address, you usually connect to the target using a Console connection (e.g., via a serial port) and run the ifconfig command. However, for the Beebox, there isn't a Console port. You can get a Console-like access if you boot the Beebox using the qnx-ifs-NO-SCREEN.ifs IFS image. When you boot using that IFS image, you get use the ifconfig command to determine the IP address. Alternatively, you can use a network protocol analyzer to determine the IP Address that's assigned to the Beebpx. To do this, boot your board and then watch for a request that matches the MAC address of your Beebox. Usually, the MAC address is printed on the bottom of your hardware platform or is available as part of the documentation that came with the hardware platform. For example, you can use the Wireshark Network Analyzer software to filter and look for an DHCP request followed by an ARP request like this:
```
DHCP Discover - Transaction ID 0xadad039
DHCP Request - Transaction ID 0xadad039
Gratuitous ARP for 10.1.22.34.126 (request)
Who as 10.122.34.1? Tell 10.122.34.126
```