47 of 54
2022-25-04
User Guide for XENSIV™ KIT PAS CO2
Hardware description
Possible solution
•
Open the debug serial interface in your laptop / PC and press “RST_BTN” in Rapid IoT connect developer kit
to reset the node. The live connection status is established. Mostly, it may solve the problem.
•
Click on the Ellipsis icon at the end of the devices list
and select “Edit” from the dropdown menu. This will
open Quick IoT experience wizard with all data entered earlier. Verify the entered Kit Serial Number, Wi-Fi
SSID, Wi-Fi Password, etc. are correct. If not, update the same and try with the updated Quick IoT
experience.
•
Open the debug serial interface in your laptop / PC and press “RST_BTN” in Rapid IoT connect developer kit
to reset the node.
In the “DHM resetting the node” an error message appears on the log, it implies that the
device is not having internet access. Create a hotspot with username “IFX_Sensor” and password
“S66M14022021”
from your mobile network and verify the same. . Check if your Wi-Fi network has internet
access from some other connected device, then resolve the firewall settings.
•
Open the debug serial interface in your laptop / PC and press “RST_BTN” in Rapid IoT connect developer kit
to reset the node. If the messa
ge “Unable to connect” appears, it implies that the device is not getting
sufficient power from the USB port. Connect the node to a USB 3.0 port or to a USB charger with at least 1A
output power and retry the connection.
•
User blinking while booting up / after reset. This indicates the device build has issues. Reflash the node by
running the script again. If problem prevails, rebuild the package by restarting the Quick IoT experience.
Please refer to the 2
nd
point for steps to restart the Quick IoT experience and contact Infineon® team if the
issue is still not resolved.
9.
Sensor not found
Possible cause:
Applications other than “Thermistor” are selected in Sensor_solution attributes without any
Infineon® XENSIV
PAS CO2 wing board or Infineon® XENSIV BGT60TR13 Radar wing board
Possible solution:
Select “Thermistor” from the dropdown menu of Sensor_Solution under Attributes tab to resolve the same.
10.
Scrambled logs
Possible cause
:
Observe scrambling of logs on the debug UART port. The CM4 and CM0+ use the same UART port for printing
debug logs. When both cores CM4 and CM0+ access the debug UART port at the same time, the logs get
scrambled.
Possible solution:
This is not an issue with the CYSBSYSKIT-DEV-01 Rapid IoT connect developer Kit or the Rapid IoT connect
system-on-module. For simplicity, we have chosen a single debug UART port so that the user can view the
debug logs from both cores on the same port. In a final product, the customer can choose dedicated debug
ports for each core.
11.
Node not appearing in the fleet monitoring
Possible cause:
“
unable to obtain semaphore for wifi-scan for CP
”
messages seen rarely on the UART
terminal. Be aware that when enabling the location service feature on the cloud, the software on the node may
rarely fail to get a semaphore lock for the Wi-Fi scan. CP stands for Customer Processor and the software is
