 | | Re: Fwd: Robotics - Stolen Life (fwd)
|
|
Ted, Looks interesting indeed. You could contact the editors of THE NXT STEP blog ((URL) or of the nxtasy.org forum ((URL) Matthias Zitat von Ted Pawlicki <lego-robotics@crynwr.com>: (...) ---...--- This message was sent using IMP, the Internet (...) (19 years ago, 16-Jul-07, to lugnet.robotics)
|
| |
| | Messing with memory pool
|
|
I'm working on a custom firmware with a new VM. I'm currently trying to reuse the NXT-G memory pool to hold data for the new VM, but I'm running into problems. Apparently, doing a memset to set all of the pool to 0x00 causes the firmware to crash. (...) (19 years ago, 16-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Possible bug? Simple light sensor condition checking.
|
|
(...) It looks to me like the c compiler optimized the assignment to the variable away, since there is no external method call (shutdown_requested() is just a macro). (...) You should make this volatile int offonpad = 0; (...) You should also put an (...) (19 years ago, 16-Jul-07, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Possible bug? Simple light sensor condition checking.
|
|
I use BrickOS (LegOS) but I'm not expert in the inner workings. The code you have here appears fine to me. So, it may be a bug in BrickOS, or a problem elsewhere in your code. I will say I've ran into some interesting things when using tasks. (...) (19 years ago, 16-Jul-07, to lugnet.robotics.rcx.legos)
|
| |
| | Possible bug? Simple light sensor condition checking.
|
|
I tried my own skill on writing a program for the included lego test pad (RIS 2.0), and I discovered something weird. The following code does set the conditions right, but the following code doesn't set the conditions right if I comment out the (...) (19 years ago, 16-Jul-07, to lugnet.robotics.rcx.legos)
|
