To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.nxt.nxthackingOpen lugnet.robotics.nxt.nxthacking in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / NXT / NXT Firmware Hacking / 81
80  |  82
Subject: 
Re: Alternate NXT-Firmware flashing tools
Newsgroups: 
lugnet.robotics.nxt.nxthacking
Date: 
Sat, 28 Jul 2007 11:44:43 GMT
Viewed: 
17944 times
  
Hi all,

On 7/28/07, Juergen Stuber <juergen@jstuber.net> wrote:

As far as I remember there is no error checking,
which explains why error sometimes go undetected
and the NXT doesn't boot.
Error checking could be added, though.

I hoped that anybody of the "creators" have done this
before, or is nobody using fwflash with the NXT ?

I used the version in NXJ successfully both for the NXT and
for an AT91SAM7S-EK evaluation board, which uses the same processor.

Recently, we finished a runtime for the RCX, and discovered the awful
state of uploading tools for that platform. In particular, there are
at least three versions of firmdl running around the net, each capable
handling different platforms (Win/Linux/Mac) and different towers
(serial/USB) with differing levels of ability.

In the end, we solved part of our problem by dropping our bytecode
into an srec, as opposed to inventing a new format for
upload-over-the-air. This allowed us to leverage the most (existing)
code, and required only minimal changes in our runtime. We still,
however, must collect up the various versions of firmdl and go through
them all, combining and pruning code, to make sure we end up with one
that actually works on all platforms equally well.

However, this thread makes me wonder: how many versions of fwflash are
there already for the NXT? Is there more than one? And, as a hacking
community, is there a good excuse/reason for this? The uploading tools
are a critical part of every (independent) runtime project, and having
them be ad-hoc and per-runtime strikes me as a sad way for the
community to go. Is that the road we're already on, or are people
collaborating with each-other across projects to make sure that we
have one uploading tool to rule them all, and in darkness, to bind
them?

(Apologies to J.R.R.T.).

Cheers,
M



Message has 1 Reply:
  Re: Alternate NXT-Firmware flashing tools
 
(...) Hi Matt, I think the problem is, that 99% of users using MS and Intel equipment... Minorities, like me, have always problems when using this :D I can't resist... Bye Christian (17 years ago, 29-Jul-07, to lugnet.robotics.nxt.nxthacking)

Message is in Reply To:
  Re: Alternate NXT-Firmware flashing tools
 
Hi Christian, (...) if you have an endianness problem it should be visible. The easiest would be to compare it with a little-endian machine. (...) It uses the SAM-BA protocol, which is rather simple and without error checking, more like what a human (...) (17 years ago, 28-Jul-07, to lugnet.robotics.nxt.nxthacking)

9 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