As the summary says:

A batch of micro servos (uServo) was created where write protect (WP) is always asserted


...due to short supply, some of these uServo devices may be distributed and put in use.  This bug is to track the issue so we can try not to get confused later when someone comes to us with one of these devices and says "all the tests are failing!"

---

Description: 

> A chip has been flipped, so the cables do not disable write protect as they should
> ...
> in addition to not disabling WP, we've also found that it will actually enable WP when plugged in.

---

> In general, [...] pre-production devices should not have their
> software write-protect programmed, so even if the hardware pin is
> asserted [people] should still be able to write the whole flash. But if
> someone accidentally enables their software write-protect, they may
> have a hard time to recover. If the device doesn't boot with the
> firmware that was write-protected on it, it is bricked until you get a
> non-broken Servo cable (or possibly a SuzyQ) to it.