Hello JP Miller
Thank you for your response
Do you have some kind of a clue? Has this been seen before?
It is rather inconvenient for us, but we have made a workaround software where we only write within 16 byte blocks, it works but I hate this kind of things with no explanation……
Emne: JP Miller answered you: M24SR64 we can only write to the NDEF file within 16 byte blocks,Why?
Hello again, indeed there are no differences on the CC and only the UIDs are different in the System Files. That is not the reason for a difference in behavior between the failing & passing parts. Next step would be to analyze the I2C commands and traces on the failing & passing parts to determine what is happening. We will contact you to determine how to best address this. Regards
Hello again,
indeed there are no differences on the CC and only the UIDs are different in the System Files. That is not the reason for a difference in behavior between the failing & passing parts.
Next step would be to analyze the I2C commands and traces on the failing & passing parts to determine what is happening. We will contact you to determine how to best address this.
Regards
M24SR64 we can only write to the NDEF file within 16 byte blocks,Why?
We started developing using one of the boards from the MATRIX-M24SR board, connected to our own hardware (via I2C), and got it up and running also with writing to the whole NDEF file, with no problem.
Then we developed a dedicated board including the M24SR64-Y. But for some strange reason, we can only write to the NDEF file within 16 byte blocks. E.g.
Writing from address 0 – 15 works fine.
Writing from address 4 – 14 works fine.
Writing from address 16 – 31 works fine.
Writing from address 10 – 17 don’t work.
Writing from address 0 – 31 don’t work.
I have verified that there is no password on the NDEF, but still, it’s strange that I can write to the memory in small blocks, but no in larger blocks (> 16 byte).
We have tried replacing the onboard M24SR64-Y with one of the chips from a MATRIX-M24SR board, and then we can write with no problems to the whole NDEF file, so this shows that there are no problems with our hardware.
Hello again,
indeed there are no differences on the CC and only the UIDs are different in the System Files. That is not the reason for a difference in behavior between the failing & passing parts.
Next step would be to analyze the I2C commands and traces on the failing & passing parts to determine what is happening. We will contact you to determine how to best address this.
Regards
