MMA9555L PEDOMETER.STEPCOALESCE register not updated

[aminekechouindi]

Hello,

We are developing a project based on MMA9555L pedometer. 

The STEPCOALESCE register is not updeted. 

Following pedometer application configuration after power on:

x00 x00 x00 x00 x00 x01 x00 x00 xaf x50 x04 x03 x05 x01 x00 x00 x00

Following our requested pedometer application configuration:

x00 x00 x00 x00 x00 x01 x80 x00 xb4 x64 x04 x83 x05 x82 x00 x00 x01

Following the read back of pedometer application configuration (Note that CONFIG bit is reset correctly):

x00 x00 x00 x00 x00 x01 x00 x00 xb4 x64 x04 x83 x05 x82 x00 x00 x00

All parameters are updated correctly except STEPCOALESCE.

We have also tried a single register update with offset  = 0x10 without success.

Question 1: Why the power on configuration do not match default defined on data sheet (0x01)?

Question 2: Why the update is not working?

[JackITB]

Hello Amine,
Which hardware are you using ?

I did some investigation with an KITMMA9555LEVM but cannot reproduce your issue.

See Slave port transaction log below:

IIC COMMAND TRANSACTION :: Starting MB = 00, No. bytes to read = 21
Write : 15 10 00 11 // query pedometer settings
Read : 15 80 11 11 00 00 00 00 00 01 00 00 AF 50 04 03 05 82 00 00 01

IIC WRITE TRANSACTION :: Starting MB = 00
Write : 15 20 00 11 00 00 00 00 00 01 80 00 B4 64 04 83 05 82 00 00 01 // write custom pedometer settings

IIC COMMAND TRANSACTION :: Starting MB = 00, No. bytes to read = 21
Write : 15 10 00 11 // query pedometer settings
Read : 15 80 11 11 00 00 00 00 00 01 00 00 B4 64 04 83 05 82 00 00 01

STEPCOALESCE register default content is 0x01 as expected.

For the record, there was a typo in Datasheet rev2.2: STEPCOALESCE register offset address erroneously declared as 0xF. It was subsequently corrected (to 0x10) in Datasheet rev2.3.

Regards,   Jacques.

[aminekechouindi]

Hello Jacques,

1/ Concerning the HW, it is 263 9555 BWL module purchased from DIGIKEY and mounted on our proprietary hardware prototype.

|MMA9555L| chip_info = {.device_id = x12a274d8, .rom_ver = x0101, .fw_ver = x0202, .hw_ver = x0106, .build_ver = x0341}
|MMA9555L| pedometer.status = {.ver = x01}

We note that we are on R1.33 version of pedometer application not the latest R1.34 (is it possible that there is a fix between these versions, we were not able to find anywhere a release note related to these versions).

2/ Concerning your test; We can’t confirm that STEPCOALESCE is correctly updated, before update the STEPCOALESCE is already = 0x01) please try to change it to 0x02 or 0x03 to confirm.

We note also another difference between your and our sequence related to Actual number of bytes of the response; it is not matching Requested number of bytes (there is one byte missing and it is corresponding to STEPCOALESCE reg). How we can explain that.

|MMA9555L| mma9555l_get_pedometer_configuration >>

|MMA9555L| command header = x15 x10 x00 x11

|MMA9555L| response header  = x15 x80 x10 x11

|MMA9555L| raw_data = x00 x00 x00 x00 x00 x01 x00 x00 xaf x50 x04 x03 x05 x01 x00 x00 x00

|MMA9555L| mma9555l_get_pedometer_configuration <<

Br,

Amine.

[JackITB]

Hello Amine,
I'm using FW revision 1.34, not sure if this could explain the differences.

Yes, I can successfully change STEPCOALESCE to any value.

Ok, I see in your communication log that only 0x10 bytes have been returned instead of the 0x11 requested. This would explain why you can't access/update STEPCOALESCE register.

Please contact me directly (at jacques.trichet@nxp.com) to discuss how to equip your parts with latest FW.

Regards,   Jacques.