DS90UB953-Q1: 953 0x5c & 0x5d & 0x5E & 0x5F will have error when start up, but after 5 minutes, the register will back to 0 and never report error again

Brian Li

Part Number: DS90UB953-Q1

Hi team,

I have asked an E2E before about how to improve the robust of the link:(1) DS90UB953-Q1: Register to improve the robustness - Interface forum - Interface - TI E2E support forums

Customer only had 9530x52[1] error about 50% before. (Other registers all correct)

And customer tried your suggestion and feedback as below:

They changed the 953 0x32=0x12,954 0x41=0x49，And they find the 953 0x52[1]'s error will significate drop to about 10%，but new error about 0x52[5] & 0x52[6] & 0x55 will occur about 2%;
They also find 953 0x5c & 0x5d & 0x5E & 0x5F will have error when start up, but after 5 minutes, the register will back to 0 and never report error again.

Could you please kindly help check the cause?

Thanks,

Brian

over 1 year ago

0 Darrah Merillat over 1 year ago

TI__Mastermind 23390 points

Hi Brian,

Thank you for your questions. How did the customer decide on setting 0x32 = 0x12 on the 953 and 0x41 = 0x49 on the 954? On the 953 0x32 = 0x12 is setting reserved registers, which is not recommended. Register 0x41 of the 954 is the SFILTER configuration but setting 0x41 = 0x49 is setting the maximum value to 4 and the minimum value to 9. The maximum value must be greater than the minimum value. I'd recommend they instead program 0x41 = 0xA9.

Many of these registers listed actually aren't indicating errors. Register 0x52[5] is a reserved register and 0x52[6] is the lock status. Register 0x55 contains the CRC error count, but they were already reporting 0x52[1] which is the CRC error flag, so this is not a new error. Also note that the CRC error specifically does not clear on read, instead register 0x49[3] should be written to. It is also common for some errors to be logged during device initialization. These errors are not a true representation of the system and occur while the devices are powering up. Since most error registers are cleared on read, if they are consistently reading 0 after the initial read that means the system is operating without errors. As long as the errors are not seen consistently during operation after being cleared, the original errors are not indicative of an issue with the system.

Regards,
Darrah