Mindboards

ronmcrae wrote:I recently had one NXT that was stuck clicking in Samba mode. As far as getting firmware onto that brick, nothing I did worked, and I did at least all of what has been discussed above.

What circumstances did that one fail under?

You could also try installing the LeJOS firmware on the NXT. That uses a really different firmware loader. If BricxCC and NXT-G fail, I kinda doubt that this will work either, but it's worth a try.

~Matt: We were both right and both wrong, I guess. I tested with the EFW and stock firmware , and "! Autorun.rxe" doesn't work. :oops: However, you have to use "! Startup .rxe " . Anything else fails. And yes, the EFW is definitely required. If you are using a custom FW, is it th...

I'm 100% certain that if you name it "! Startup" (don't worry about the extension, but it needs to be a capital "S"), that it will work fine. I have done it a zillion times. :shock: What firmware do you use? It doesn't work for me. (custom firmware build almost identical to stoc...

I don't think so, at least I can't see why it would matter. No matter what lego FW you are using, it should play ! Startup as soon as you turn it on (normally a sound file). Oohhhh, I just realized something: Everyone said "! Startup" , but like you just pointed out, that's a sound file. ...

What firmware does your NXT have? I think this only works with the NBC/NXC enhanced firmware.

Oh... Thanks.
The documentation I looked at was the NXC guide that came with BricxCC.

Well, you've said it yourself, so I'm stating the obvious: Have you checked if joyvals has the correct format? What happens if an empty or a malformed message arrives? Empty / malformed messages shouldn't make a difference, since the program only does some math on the array and stores the result. I...

Hi, I'm having a problem with a NXC program I'm writing. Here's the code: task main() { char BOXNO = 0; int b; short a1, a2, a3, a4, a5, a6, a7, a8; char joyvals[60]; while (1) { ReceiveMessage(BOXNO, true, joyvals); b = (joyvals[0] << 24 | joyvals[1] << 16 | joyvals[2] << 8 | joyvals[3]) - 1; a1 = ...

As far as motion is concerned, I'm not sure a 70hz refresh rate is much better than 10hz, because the pixels respond so slowly. A sprite moving to keep pace with a 70hz refresh will be severely blurred. As Aswin0 said though, that's good for static grayscale.