cancel
Showing results for 
Search instead for 
Did you mean: 

FSM_ODR register settings on LIS2DUXS12

BD651
Associate II

I am suspecting that the ODR setting in my application is not correct. I want to be using 25Hz so according to the datasheet I would set register address 39h to 48h. 25Hz equals 001 which would give 01001000 = 48h.

But all examples and also the Unico tool outputs 4Bh instead of 48h. Am I missing something or should the last two LSB bits always be 1 instead of 0?

fsm_odr_register.png

1 ACCEPTED SOLUTION

Accepted Solutions
Federica Bossi
ST Employee

Ciao @BD651 ,

I didn't realize you were using the FSM tool, we checked and you are right: this is a bug. I have already warned to fix it in the next version. In the meantime you can manually change the value of register 39h from 4B to 48.

Sorry for that.

If this helps you, please mark my answer as "Best Answer" by clicking on the "Accept as Solution" button, this can be helpful for Community users to find this solution faster.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

View solution in original post

3 REPLIES 3
Federica Bossi
ST Employee

Hi @BD651 ,

Welcome to ST Community!

We replicated your test and we read 48 correctly. Can you try again with our same settings?

FedericaBossi_0-1692266507085.png

If this solves your problem, please mark my answer as "Best Answer" by clicking on the "Accept as Solution" button, this can be helpful for Community users to find this solution faster.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
BD651
Associate II

Thank you for the answer. I don't have access to the evaluation kit so I can not read out the values like that. However, I tried the below configuration from the Unico-Gui (using the LIS2DUXS12) and the resulting code when saving the Device Configuration results in 4Bh stored in position 39h.

unico_25Hz.png

The resulting .ucf file:

-- Finite State Machine Tool v9.15.0.0, STEVAL-MKI235KA (LIS2DUXS12)
-- <FSM_OUTS1>FSM1
-- <FSM_OUTS2>FSM2
-- <FSM_OUTS3>FSM3
-- <FSM_OUTS4>FSM4
-- <FSM_OUTS5>FSM5
-- <FSM_OUTS6>FSM6
-- <FSM_OUTS7>FSM7
-- <FSM_OUTS8>FSM8

Ac 14 00
Ac 13 10
WAIT 5
Ac 3F 80
Ac 04 00
Ac 05 00
Ac 39 4B
Ac 1A 01
Ac 0A 00
Ac 0B 01
Ac 0E 00
Ac 0F 00
Ac 17 40
Ac 02 01
Ac 08 54
Ac 09 00
Ac 09 00
Ac 09 01
Ac 09 01
Ac 09 00
Ac 09 02
Ac 02 21
Ac 08 00
Ac 09 51
Ac 09 00
Ac 09 10
Ac 09 00
Ac 09 0C
Ac 09 00
Ac 09 66
Ac 09 2E
Ac 09 10
Ac 09 00
Ac 09 00
Ac 09 06
Ac 09 53
Ac 09 99
Ac 09 50
Ac 09 00
Ac 04 00
Ac 05 01
Ac 17 00
Ac 3F 00
Ac 1F 01
Ac 14 60

Federica Bossi
ST Employee

Ciao @BD651 ,

I didn't realize you were using the FSM tool, we checked and you are right: this is a bug. I have already warned to fix it in the next version. In the meantime you can manually change the value of register 39h from 4B to 48.

Sorry for that.

If this helps you, please mark my answer as "Best Answer" by clicking on the "Accept as Solution" button, this can be helpful for Community users to find this solution faster.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.