Watch this spot for updates in the next few days on this issue. We're told that LEGO is very close to releasing a patch (final testing phase), and as soon as we know where to send you folks we'll post it here. Hopefully in a few more days, the patch will be out...
--
Brian Davis
9 comments:
Brain,
The next dilemma (for those of us who suffered "clicking brick syndrome" and then got our bricks up and running) will be: should we install the patch or not?
If the patch resolves the BT connectivity issues (as well as the other stuff), then I'm in!
I'll try to get an answer from the folks in-the-know by the time the patch is released. I *suspect* that you will ultimately still need the patch (for the nxt time you need to update the firmware)... it seems that whatever is going wrong sometimes, occassionally, goes right, and you get a successful firmware download. If that's the case, those of you who have had the problem are likely to run into it on the next firmware download. Worse yet, those who *successfully* updated their firmware on the first attempt may still have the CBS problem, they just don't know it yet. But with a patch availible, we'll have a solution handy if we need it.
--
Brian Davis
So what's the difference between version 1.1 and 1.3 anyway?
Good work, Brian!
I bricked mine and fixed it. All I did was plug my USB cable into a port right on the motherboard, then reflashed in the NXT software.
Before the upgrade, my bluetooth ports would only connect one at a time. Now they both connect at once. Not sure what that means to the user, but hey.
The 1.03 version gives users more memory to store programs. I don't see any reason *not* to upgrade. Just don't try it over bluetooth.
-norcalbarney
So did we ever determine that a upgrade via USB is 100% safe or is it hit-or-miss as well?
Actually, the *only* way to upgrade the firmware is via USB. And yes, in some bricks it has resulted in the brick getting stuck in a despondant clicking forever mode. Hopefully very soon LEGO will release a patch and we will announce it here (&, for that matter, everywhere else we can possibly think of).
The clicking is caused by the brick being in its 'recovery mode' firmware. This firmware is write protected and only contains the code needed to download new firmware. You can get to it by pressing the button in a hole on the same side as the battery holder.
The 'recovery mode' firmware also has instructions for making the speakers click, as a way of telling the user the device is turned on.
Post a Comment