June 1, 2015 8:11 AM CEST
Hi,
I have four SBricks, two of them were immediately unpacked and used to various success, so they got a couple of firmware upgradres over the first weeks after release. After having to stop Lego in general for a couple of weeks, I have now connected them again successfully with my Android Tablet and subsequently upgraded to the latest firmware without problems, they work very nicely with my Sony Xperia Tab Z3 Compact ;-)
Then I unpacked my other two ones and they were found by the tablet and upgraded (LED was not blinking during the process; I associated this behaviour with the initial LED behaviour that was a bit strange). After the app confirmed successful flash, the SBricks are not working. Reenabling bluetooth, rebooting the tab and of course rebooting the Bricks is not successful. The Bricks can be found in the app, but neither LED identification or port checking works (LED stays on, no movement on connected motors). The first two units that were in-between updated continue to work nicely. Strangely, when I try to re-flash the nonworking pair via the OTA functionality in the app, a motor connected to port D spins wildly while the app reports flashing progress, but actually nothing else seems to happen as the LED does not flash.
I suspect something was done in some of the older firmware upgrades that is missing from the ones that were from the initial run and that never got updated until now. How can I fix this? As I said the bricks can still be found via bluetooth, so not all is lost I guess...
Thanks,
Tobias
This post was edited by Tobias Knostmann at June 1, 2015 8:11 AM CEST