 | | 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: 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)
|
