 | | 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 (...) (18 years ago, 21-Mar-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: The standard NXT firmware & the case of the missing opcodes
|
|
(...) I don't think I ever got around to mentioning this here, but a long time ago I implemented all of the above opcodes in my NBC/NXC enhanced standard NXT firmware. I implemented all of the shift opcodes so that they take 3 parameters rather than (...) (17 years ago, 22-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: The standard NXT firmware & the case of the missing opcodes
|
|
(...) If you download the test_release.zip that I uploaded late last night you will be able to use these new opcodes (after installing the enhanced firmware in lms_arm_jch.zip) in both NBC and NXC programs. Here is some sample NXC code: task goofy() (...) (17 years ago, 23-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: The standard NXT firmware & the case of the missing opcodes
|
|
(...) Could you, please, confirm, that the latest version of NBC then translates the following two commands with three arguments listed in the NBC manual: shr shl to the correct new opcodes of the enhanced firmware (depending on the type of the (...) (17 years ago, 30-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
