PDM EEPROM Bitmap Counters JENOS JN5169 / JN516x

jackjl — Wed, 03 Jul 2019 00:10:12 GMT

Does anyone have experience / recommendations regarding the PDM EEPROM Bitmap counters (some assistance from NXP would be greatly appreciated). We are using the PDM_eCreateBitmap functionality as we need large persistent counters (and cannot predict power cycle frequency). Creating the counter and reading the counter works perfectly, but the flags and operation due not appear to match the documentation: JN-UG-3075.

The documentation implies that the "counter" will toggle a bit every count up, which means in a typical segment, approximately 400 bits available for toggling. When a segment is full, it should return a flag of full, but will automatically move to the next segment. Issue 1) The flag is never set to full. We are looking to check the flag to verify that number of "400" before it jumps to the next segment so that we can estimate EEPROM lifetime based on write cycles.

As well, we had expected the pu32InitialValue would increase, and the pu32BitmapValue would go between 0-400 as it moved through filling up one segment. However, the Initial Value stays at 0, and the BitmapValue keeps increasing (into the hundreds of thousands).

The flag not reporting a full segment would be okay if we could validate our expectations of operation, i.e. that it will move from PDM EEPROM segment to segment approximately every 400 counts.

Re: PDM EEPROM Bitmap Counters JENOS JN5169 / JN516x

mario_castaneda — Thu, 11 Jul 2019 00:19:58 GMT

Hi Jack,

Are you aware of the segments available? Are you printing the return status?

Is it possible that you could share your implementation?

Are you getting PDM_E_STATUS_USER_PDM_FULL return value?

Regards,

Mario

topic Re: PDM EEPROM Bitmap Counters JENOS JN5169 / JN516x in Wireless MCU

PDM EEPROM Bitmap Counters JENOS JN5169 / JN516x

Re: PDM EEPROM Bitmap Counters JENOS JN5169 / JN516x