| |
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 its core, strictly ANSI C, we've had no
problems running it on new hardware (eg. the H8300 in the RCX, the
MSP430, and an ARM9 on the Surveyor SRV-1). For this reason, I'm not
overly concerned about having hardware-level debugging. But, I thought
I'd ask.
Cheers,
Matt
|
|
Message has 1 Reply:
 | | 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)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
