Skip to main content
Explorer
September 18, 2025
Question

LPS22HH DCR value is 0x00

  • September 18, 2025
  • 3 replies
  • 657 views

I got the DCR form LPS22HH value is 0x00, but the BCR and TPID value all matched the datasheet except the DCR, and the waveforms as follow:

Frankly_0-1758178517338.png

Frankly_1-1758178612419.png

 Based on the feature showed in LPS22HH datasheet, the DCR should be 0x62

Frankly_2-1758178667739.png

but according to the DCR table (details table in MIPI : https://www.mipi.org/MIPI_I3C_device_characteristics_register), all version1.0 device DCR is 0x00.

I don't known what's the current I3C version included in LPS22HH sensor. Can anyone help me clarify it?

Sorry to @Foued_KH again.

    This topic has been closed for replies.

    3 replies

    ST Employee
    September 18, 2025

    Hello @Frankly , 

    For the DCR value, you need to align it with the value in the datasheet of the LPS22HH : 

    Foued_KH_0-1758185090499.png

    There is no need to know the I3C version for this sensor; just follow the commands supported in the datasheet.

    In my opinion, You need to check the decoding parameters for the tool being used.

    Thank you!
    Foued

     

     

    FranklyAuthor
    Explorer
    September 19, 2025

    I don't think the decode tool's parameter is incorrect, before GETDCR,  the host send GETBCR(0x8E) to get the correct BCR(0x07), the correct waveform as follow:

    Frankly_1-1758247061079.png

    according the waveform of GETDCR, the GETDCR Byte is 0 after Target Addr ACK

    Frankly_0-1758246900919.png

    so @Foued_KH could you please show the correct waveform of GETDCT on lps22hh?

     

    FranklyAuthor
    Explorer
    October 13, 2025

    @Foued_KH , could you please help look into the issue?

    FranklyAuthor
    Explorer
    November 26, 2025

    @Federica Bossi  could you please help look into this issue, because I haven't seen Foued online for two months.