| |
In lugnet.robotics.nxt.nxthacking, Juergen Stuber wrote:
> Hi Christian,
>
> "Christian Mock" <chrimo-@-moccy.xdsnet.de> writes:
> >
> > Please give me some hints where to start.
> > I haven't found any --verbose command line parameters, yet :D
>
> you could add some code in lowlevel.c to dump the USB packets,
> and then look if you see anything wrong.
>
>
> Jürgen
ReHi Jürgen,
yes this is a trivial job, but what should I learn from this packets ?
fwflash returns no error back to commandline ...
Does this mean fwflash works blindly and returns no protocol or packet errors ?
Why is the result "success" ???
Questions over questions :D
My problem is, I did not understand exactly the lower level protocol and
handling of the flashroutines...
How can I debug it ?
I hoped that anybody of the "creators" have done this before, or is nobody using
fwflash with the NXT ?
Moin Moin :D
Christian
|
|
Message has 1 Reply:
 | | 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)
|
Message is in Reply To:
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
|
|
|
|
