Possible Cause:

The CH347 device driver is not installed on the host PC.

Solutions:

· Check the hardware configuration according to Section 4.1 of the MRS2xx mmWare Sensor Demo Guide Manual.

· Install the corresponding device driver as prompted by the PC. There is a ch347driver.zip file in the MRS2xx_DemoTool.zip folder; simply extract and install it.

……

Possible Cause:

1.The host software's programming mode does not match the hardware configuration.

2.The device has not entered programming mode.

Solution:

……

Please refer to the following table for details on firmware selection:

Firmware naming rules:

(1) MRS261 firmware: 

There is only a single firmware, which only supports the "Motion Detection Setting" Demo. The firmware is named according to the scene;

(2)MRS261Lfirmware:

module model + interface +sram/xp+motion_detection/np/full_spec + configuration.

……

Host MCU UART Communication Troubleshooting Flow

• UART Communication Checklist

1. Verify TX Output: Disconnect the physical connection between the Host MCU and the sensor. Using a logic analyzer, verify that the data write interface (as specified in Section 2.4 of the MRS2xx mmWare Radar Sensor Host Development Manual) outputs the expected data of LEN length at the correct baud rate.

2. After confirming the data in Step 1 is correct, connect the Host MCU TX pin to the sensor RX pin. Have the Host MCU continuously send 0x7E. Use a logic analyzer to monitor whether the sensor TX pin outputs 0x79.

3. Fully connect the Host MCU and the sensor (Host MCU RX pin to sensor TX pin). Use a logic analyzer to simultaneously monitor the system communication pins to verify if the Host MCU RX pin receives 0x79 after the Host MCU TX pin outputs 0x7E.

……

Please ensure that developers have completed the checks outlined in Section 6.1 of the MRS2xx  mmWave Radar Sensor Host Development Manual to guarantee proper communication.

  • Sync Timeout During Firmware Download.

  • Failure at the Last Packet During Firmware Download.

  • Unsupported Error Codes or Checksum Errors During Firmware Download.

  • Sensor Fails to Start/Stop After a Successful Firmware Download.

  • Considerations for Software I²C.

Dynamic Parameter Configuration

The HOST_DRIVER maintains a parameter configuration structure that maps directly to the parameter types available in the GUI tool. Developers can achieve dynamic parameter configuration at runtime by modifying the members of this structure.

Assuming you need to modify the Detection Sensitivity parameter, follow these specific steps:

……

• Prerequisites

When using adaptive learning, the device must operate exclusively in single Mode 3, and the environment must be unoccupied. The specific processing flow for environment learning is: Host MCU Acquires Spectrum -> Parses Spectrum -> Updates Threshold -> Dispatches Threshold.

• Spectrum Acquisition

Method 1: Actively acquire the spectrum using the 0x61 command (Recommended, supports UART/I2C).

Method 2: Acquire the spectrum via TLV configuration for active reporting (Supports UART only).

……

· HOST_DRIVER: Utilizes the DOUT state mode. At the application level, the sensor target data is read only when the DOUT state toggles.

· GUI: Utilizes thread polling for data reading, so the tool continuously refreshes the distance;

……

If an error pop-up containing ".NET xxx" appears when running the GUI tool in a Windows environment, please install the Windows .NET Framework 4.7.2. The installation package can be downloaded from the "Technical Resources" section on this page or via the official link: .NET Framework 4.7.2. 

Yes. Application solutions without a master control (sensor only), as well as application solutions where the master control does not support OTA/firmware downloading, can adopt the external Flash approach.

No special requirements. Mainstream Flash chips on the market are supported, provided they have a minimum capacity of 1Mb.