Hello,
We have designed a watch using the Chronos demo and MSP430f6723.
Driver lib is MSP430ware_1_40_00_24.
The LCD is based on and ordered from the same manufacturer/supplier as is used in EZ430-Chronos watch.
We have received the following complaint from a few customers:
- Watch FW is updated using the BSL_Scripter over a CP210 UART-COM bridge
- After watch is reset, certain LCD segments (which previously had been displaying fine) don't display.
- Updating with the same FW a few more times, the LCD segments seem to improve each time.
- After 4-6 updates, LCD returns to normal
- After the LCD returned to normal functioning, the customer plugged the watch into his PC (same one used for FW BSL update) in order to charge it. After charging, the LCD was again corrupted.
Some more clarifications:
- So far this phenomenon has happened on PC Win8 and on MAC (we have a BSL-scripter program written for the MAC).
- We have not been able to reproduce this "bug" - even though we've tried on over 10 other watches.
- Many other customers have successfully updated their watch's FW without experiencing such a "bug".
- All of our FW versions have undergone much QA and testing.
- Watches aren't released to a customer before the LCDs are thoroughly checked.
We have requested that one of the watches that this "bug" was found on be returned. The other watch where this was experienced is behaving nicely sine and the problem can't be reproduced.
What is the connection between the BSL and the LCD segments? Even without burning the FW, the BSL TX/RX when he charged the watch's battery did something to the LCD segments.
Why would a few times burning the FW improve the situation?
Please let me know if you have any ideas.
Thanks,
Mechi