To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.nxtOpen lugnet.robotics.nxt in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / NXT / 262
261  |  263
Subject: 
Re: NXT Firmware source code
Newsgroups: 
lugnet.robotics.nxt
Date: 
Fri, 15 Dec 2006 15:40:48 GMT
Viewed: 
12181 times
  
In lugnet.robotics.nxt, Chris Phillips wrote:

Still, writing any type of file onto the NXT will eventually wear out the flash
memory and lead to failure.  If you were to download 30 programs onto your NXT
every day, it would start to have problems after about a year, assuming that
these specs are correct.  Running a data-logging application continuously on
your NXT could burn it out even faster.

If this limitation had applied to the rcx, I'd have suggested this. Because you
can control the outputs and read the inputs direct from a pc you could run an
emulation of the rcx firmware running your program on the pc. The rcx would then
behave in the same way as if you had downloaded the program onto it. You would
have course have the transmission delay caused by the IR link. But whether that
was a problem would depend on your application. I suspect the same could be
applied to the NXT.



Message has 2 Replies:
  Re: NXT Firmware source code
 
(...) Now that's a cool idea. I've been messing around with remote-controlling the NXT via Bluetooth from a PC application, and it seems pretty solid. You'd definitely have some timing issues running a remote emulation like you describe, but this (...) (17 years ago, 15-Dec-06, to lugnet.robotics.nxt)
  Re: NXT Firmware source code
 
"Steve Lane yahoo.co.uk>" <stevenrobertlane@<n...pamplease> wrote in message news:JABnK0.15z@lugnet.com... (...) Fortunately the most common failure mode is a reduction in the "longevity" of storage. Out of box, the Atmel ARM flash is specified to (...) (17 years ago, 18-Dec-06, to lugnet.robotics.nxt)

Message is in Reply To:
  Re: NXT Firmware source code
 
(...) Flash memories all have a limited number of write cycles before they become unreliable. Usually, the on-chip write controller will "load-balance" the writes so that different memory locations all get used the same number of times, (...) (17 years ago, 12-Dec-06, to lugnet.robotics.nxt)

16 Messages in This Thread:








Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR