 | | Re: Alternate NXT-Firmware flashing tools
|
|
(...) 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" (...) (19 years ago, 26-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Alternate NXT-Firmware flashing tools
|
|
Hi Christian, (...) you could add some code in lowlevel.c to dump the USB packets, and then look if you see anything wrong. Jürgen (19 years ago, 26-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Alternate NXT-Firmware flashing tools
|
|
(...) Hi Jürgen, very good idea. Please give me some hints where to start. I haven't found any --verbose command line parameters, yet :D OK, I'm trying to read the source again, expecting ENDIAN problems like every time using PPC and SPARC :-D Bye (...) (19 years ago, 25-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Alternate NXT-Firmware flashing tools
|
|
Hi Christian, (...) how about trying to fix fwflash? Jürgen (19 years ago, 25-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: stop task
|
|
(...) It hasn't, Elizabeth - I'm not upset at John, and he knows *far* more about programming than I do. I just wanted to point out that there are process where abruptly "killing" a thread was one of the best solutions I ever found, due to the speed (...) (19 years ago, 25-Jul-07, to lugnet.robotics.nxt)
|
