 | | Re: The standard NXT firmware & the case of the missing opcodes
|
|
(...) I guess what I'm saying is '<<=', 'OP_ASL' and 'OP_LSL' are all the same thing (zero fill). '>>=' means either 'OP_ASR' (smear fill) or 'OP_LSR' (zero fill) depending on whether your target is signed or not. If you wanted direct equivalents (...) (19 years ago, 21-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: The standard NXT firmware & the case of the missing opcodes
|
|
(...) Having used shifts in Z80 assembly before, I can see the uses of the different types. However, I can't see how I'd want anything other than arithmetical in the NBC opcodes. The only times I used logical, rotating, or with-carry-bit shifts was (...) (19 years ago, 21-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | The standard NXT firmware & the case of the missing opcodes
|
|
There are several opcodes defined in c_cmd_bytecodes.h which are missing from the VM implementation in c_cmd.c Here are the ones that are not implemented: //Family: Bit manipulation #define OP_CMNT 0x0A // dest, src #define OP_LSL 0x0B // dest, src (...) (19 years ago, 21-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Enhanced standard NXT firmware
|
|
... (...) Hi John, I just tried to load it and just tested the "Try-me" light sensor. It worked fine. Not so much help, but I can try some more another day. Good work. Rasmus (...) (19 years ago, 19-Mar-07, to lugnet.robotics.nxt.nxthacking, lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Missing links?
|
|
Hi guys, Are there missing any links in the "stable" section (the one with the links to RobotC, pbLua NBC etc) to the left of the forum (most likely since I put them there...)? I don't know if all can edit it but otherwise you can probably write to (...) (19 years ago, 18-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
