 | | 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. (...) (18 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 (...) (18 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 (...) (18 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 (...) (18 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 (...) (18 years ago, 27-Jun-07, to lugnet.robotics.nxt)
|
