SensorTile.box PRO: No serial port (/dev/ttyACM0 or /dev/ttyUSB0) on Raspberry Pi

[kj711]

Hello,

I am working with the SensorTile.box PRO and trying to connect it to a Raspberry Pi 4B over USB.
On plugging the board into the Pi, it is detected in lsusb as:

Bus 001 Device 003: ID 0483:5744 STMicroelectronics Sensortile.box_PRO_Multi_Sensor_Streaming

However, Linux does not create a serial device such as /dev/ttyACM0 or /dev/ttyUSB0.
This means I cannot access the device over a standard serial interface (e.g., minicom, screen, or pyserial).

Additional observations:

• I attempted to communicate with the device using PyUSB on the Raspberry Pi.

• The device enumerates with an IN endpoint (0x81) and an OUT endpoint (0x06).

• When I attempt to send data to the OUT endpoint, I consistently get:

usb.core.USBError: [Errno 32] Pipe error

This suggests that the device expects a specific vendor-defined command format and does not accept generic bulk writes.

Questions:

1. Does the SensorTile.box PRO expose a CDC-ACM serial interface over USB, or is the communication handled only via a vendor-specific USB protocol?

2. If it uses a proprietary USB protocol, is there any documentation or SDK available to interpret the USB bulk endpoints directly?

3. Is there a way to configure the board’s firmware so that it enumerates as a standard USB serial device?

My use case is to stream sensor data from the SensorTile.box PRO to a Raspberry Pi gateway and then push it to the cloud.

Thanks in advance for your guidance.

[SimonePradolini · Accepted solution]

Hello @kj711 

Which firmware is running onto SensorTile.box PRO? I guess you are referring to FP-SNS-DATALOG2.

If so, you are searching for STDATALOG-PYSDK, the Python framework designed for capture, processing, and visualization of data from DATALOG2 firmware. Here you'll find all the references for properly download and install it.

Best regards

Simone

[kj711]

Thank you Simone

[kj711]

Hello @SimonePradolini ,

We are working with the STEVAL-MKBOXPRO (SensorTile.box PRO) and the AI-inertial MLC Smart Asset Tracking example firmware provided in the ST AIoT Craft tool. The firmware was successfully built and flashed to the device.

However, when connecting the device to a Raspberry Pi 4B (used as a gateway) and using the PySDK (stdatalog-pysdk) to acquire data, we are facing the following issues:

1. We are not able to retrieve classified data output from the MLC model.

2. The device is detected by the PySDK, but only raw sensor streams are available.

3. No classification events (labels/decisions) appear in the dataframes or logs.

4. Even when acquisition runs successfully, the gateway does not receive classified results — only empty or raw signals are observed.

Our expectation:

• When the AI-inertial MLC Smart Asset example firmware is running, the classified results (MLC output classes) should be exposed via the PySDK interface and retrievable on the Raspberry Pi gateway.

Questions:

1. Does the AI-inertial MLC Smart Asset example firmware currently expose the MLC classification results via the stdatalog-PySDK interface?

2. Is there any additional configuration required (in the firmware or in the PySDK) to enable classified data output?

3. If classification output is not yet supported through PySDK, is there a recommended way to extract MLC results programmatically (e.g., via UART, BLE, or alternative APIs)?

Any guidance or references would be greatly appreciated.

[SimonePradolini]

Hello @kj711 

I asked internally to the colleagues in charge for AIoTCraft support. They'll reply to you with all the needed details to fully support you.

Best regards

Simone