 | | NXT & RIC
|
|
A while back I wrote part 1 of a 2 part description of the RIC file format on the Nxtasy blog. I still haven't gotten around to writing part 2 (been busy writing other stuff) but RIC-related things have been hanging around on the edges of my (...) (17 years ago, 29-Jun-07, to lugnet.robotics.nxt)
|
| |
| | Re: Adding a JTAG port?
|
|
(...) I used a JTAG tool in the beginning by glueing a JTAG connector manually. You could do that and perhaps have a look at section 4.3 in (URL) it is easier to use libnxt. I am using it in this project: (URL) can download libnxt source from (or of (...) (17 years ago, 29-Jun-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Adding a JTAG port?
|
|
Hi all, Do I need to add a JTAG port to develop an alternative runtime for the NXT? We did the RCX without this level of debugging, and the NXT is far more open. Is it necessary, nice to have, or simply not necessary at all? Given that our VM is, at (...) (17 years ago, 29-Jun-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Introduction of LEJOS OSEK
|
|
LEJOS OSEK Website has been available at (URL) There has been several updates since the first introduction: - LEJOS OSEK Ver 1.02 supports restart of application program by pressing the triangle button at the left hand side of NXT. (Usability should (...) (17 years ago, 29-Jun-07, to lugnet.robotics.nxt)
|
| |
| | Progressing from RCX to NXT
|
|
SHORT VERSION Can anyone point me in the direction of some simple NXT models, preferably of fun things like vehicles, that a smart rising 4th grader can build on his own, that will inspire him to explore NXT? LONGER VERSION My son is 9 1/2. We gave (...) (17 years ago, 29-Jun-07, to lugnet.robotics.nxt)
|
| |
| | Re: Custom firmware crashing on boot
|
|
(...) The modifications are slightly more complex than simply replacing c_cmd.c, but that's basically the only NXTGCC file that I've modified. The new VM is copied mostly verbatim from another program, and is contained in a new file, pcodesim.c. (...) (17 years ago, 28-Jun-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | RE: Custom firmware crashing on boot
|
|
Here's two things to try since you've only swapped out the VM hich I assume is a replacement for the "c_cmd.c" file. 1. First there is a "#define" that specifies the start address of the file system. If you're 10K larger you're going to need to (...) (17 years ago, 27-Jun-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Custom firmware crashing on boot
|
|
(...) It is nice with some action. (...) OK, that is very good. (...) A quick question: Are you running binsert after you compile? It may be worthwhile to look at lines 50-55 in "Makefile". With some effort and a hex file editor you can check if (...) (17 years ago, 28-Jun-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Custom firmware crashing on boot
|
|
Hey, I'm new here, so if I seem like a n00b, it's probably because I am. Hopefully my question won't be too annoying. I'm trying to use the NXTGCC 0.0.9 package as a starting point for custom firmware. The main point of my custom firmware is to swap (...) (17 years ago, 27-Jun-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Temporarily removing official NXT driver to use SAM-BA
|
|
Hey, I tried to post this message two days ago and it hasn't shown up yet, so I'm trying again (with a different client in case that's why it was eaten). If people receive duplicates, I sincerely apologize. Message follows: Hey, I apologize in (...) (17 years ago, 27-Jun-07, to lugnet.robotics.nxt)
|
