 | | Re: Enhanced standard NXT firmware
|
|
(...) I would have liked to have one permanently, but it seems a little steep. Last summer I got a limited edition (32KB or something) along with the an AT91 evaluation board. (...) Perhaps Section 5.1 is useful: (URL) I just tried to post but it (...) (18 years ago, 17-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Re: Enhanced standard NXT firmware
|
|
(...) It actually was not a very big deal. I was familiar with the firmware source code since I had looked at it quite a bit since it was released, trying to figure out how to get it to compile with GCC. All the RIC bug fixes were things I figured (...) (18 years ago, 17-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Re: Enhanced standard NXT firmware
|
|
(...) <snipped description> Holy crap John! You've been really busy! For anyone poking around in this forum, I can say that what John has done is pretty significant. I have written my own firmware for the brick so I know how much work must have gone (...) (18 years ago, 17-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Enhanced standard NXT firmware
|
|
Over the past couple days I have used the IAR Embedded Workbench to implement some enhancements and bug fixes for the standard NXT firmware. The bug fixes are as follows: 1. RIC drawing code incorrectly checked the size of the OP_LINE structure for (...) (18 years ago, 16-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Re: Brickworld Announcement - Area Attractions and baseball
|
|
(...) Although a robot pitcher and robot hitter would be very very kewl, just a robot pitcher and wireless remote control hitter would be very kewl. Like those old baseball machines at the beach. One would have to anticipate the lag and the speed of (...) (18 years ago, 15-Mar-07, to lugnet.events.brickworld, lugnet.robotics.nxt)
|
| |
| | Re: Brickworld Announcement - Area Attractions and baseball
|
|
(...) Unfortunately the ultrasonic sensor can't even detect the red and blue balls when stationary. (Unless you're REAL close: within an inch or two.) Their surface doesn't reflect much sound (perhaps something to do with the index of refraction), (...) (18 years ago, 15-Mar-07, to lugnet.events.brickworld, lugnet.robotics.nxt)
|
| |
| | re: Baseball
|
|
(...) Yes, that could work. We just need someone to design a "standard" pitching machine that can toss balls a foot or two. Then, we need a "regulation" bat size. We could do the whole base-ball, but I doubt very many people could field a whole (...) (18 years ago, 15-Mar-07, to lugnet.events.brickworld, lugnet.robotics.nxt)
|
| |
| | Re: Brickworld Announcement - Area Attractions and baseball
|
|
(...) Ok, thinking out loud now: Well, what about a home run derby or the like? Maybe a machine that pitches and a machine that hits... We could use those red and blue spheres that come with the nxt... Would ultrasonic sensor work for detecting the (...) (18 years ago, 15-Mar-07, to lugnet.events.brickworld, lugnet.robotics.nxt)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
(...) OK. This is good info!!! It is hard to guess that this was the way to do it. It also makes some sense for LEGO to use their file manager to do this rather than having a second tool replicate a filemanager on the host and insert it at compile (...) (18 years ago, 15-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
(...) Hi Dick Swan, That is a nice flexible way of doing it. I will see if I can figure it out in gcc. Thanks for the idea. (...) Well...I have -=Os on, which are all size reducing features. The actual "problem" can also be this packed stuff that we (...) (18 years ago, 15-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: NeXT-A-Sketch - My second program/first Dave-built NXT 'bot(ish...)
|
|
(...) Or do what I did. Change the program so you only have to tap the button to clear the screen so you can easily reset it while shaking upside down. (18 years ago, 15-Mar-07, to lugnet.org.ca.rtltoronto, lugnet.robotics.nxt)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
(...) LEGO is using a slightly older version of IAR Embedded Workbench. Maybe that explains it. Or maybe its a 1.03 vs 1.04 source code difference. (...) I have been told that the following is the standard operating procedure for generating the (...) (18 years ago, 15-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
Regarrding overwriting the flash system. I encountered the problem of flash file system overwriting user code as well. It's because it is hard coded in the code the starting address of the file system. There's a constant named "STARTOFUSERFLASH" (...) (18 years ago, 14-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
... (...) I have not done that. Well, just a little bit:-). The best one (not surprisingly) is the "-Os" optimization, which does this "Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size." (...) I tried (...) (18 years ago, 14-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
(...) I did not do so. The memory map in LEGO_MINDSTORMS_NXT_..._v1.03.bin is like this for the files: 0x11F000-0x12E99D Actual files like Demo.rxe 0x13FF00-0x13FF37 FILE_HANDLE(s) 0x13FFFC-0c13FFFF FILEVERSION The nxtgcc stuff compiles to 126176 (...) (18 years ago, 14-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
(...) Have you experimented at all with the compiler optimisation flags? I don't know if all of them are supported for the ARM architecture, and some options cause problems on other architectures, but there's a bit of a list here: (URL) removing (...) (18 years ago, 14-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
(...) More precisely, I was told to increase the STARTOFUSERFLASH value if I increased the firmware size beyond the current value. The unmodified source code compiles to 121324 bytes using the current evaluation version of the IAR Embedded Workbench (...) (18 years ago, 14-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: My first(ish) program
|
|
(...) (URL) that I think you need to buy any more LEGO or anything... 8?) ROSCO (18 years ago, 14-Mar-07, to lugnet.org.ca.rtltoronto, lugnet.robotics.nxt)
|
| |
| | Re: GCC vs. IAR compiler: Could GCC be tweaked to generate code as tight as IAR?
|
|
(...) Are you adjusting these values in d_loader.h? #define STARTOFFILETABLE (0x13FF00L) #define STARTOFUSERFLASH (0x11F000L) #define SIZEOFUSERFLASH (STARTOFFILETABLE - STARTOFUSERFLASH) I've been told by folks at LEGO that if I grow the size of (...) (18 years ago, 14-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: My first(ish) program
|
|
(...) LOL... Hand eye coordination is a gift. Although, I'm not doing any better... I had the pleasure of playing Mr. Cowdice's rabbit game last friday, and scored a big fat -2. Dave, Im thinking you need to start scoring on the bell curve. Just saw (...) (18 years ago, 14-Mar-07, to lugnet.org.ca.rtltoronto, lugnet.robotics.nxt)
|
