 | | pbLua Fun at OSX
|
|
Hello World, pbLua-Beta2 is out and 90% of my wishes are true now :D Running pbLua with OSX worked out of the box... 1. Flashing NXT and reboot the box once 2. checking for new NXT-Device (ls -la /dev/tty.usb*) 3. connecting with screen to NXT (...) (19 years ago, 21-Mar-07, to lugnet.robotics.nxt)
|
| |
| | 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)
|
| |
| | Re: Adding syscalls/opcodes to NXT-G
|
|
(...) Can you flesh this out a bit? What do you have in mind when you say "create from it a new program clump"? The current version of the firmware limits the size of this buffer to 64 bytes. I increased that limit in my recent changes to be 800 (...) (19 years ago, 21-Mar-07, to lugnet.robotics.nxt)
|
| |
| | Adding syscalls/opcodes to NXT-G
|
|
One of the biggest problems with extending the current FW is that the NI compiler for NXT-G/NXTToolkit is not so flexible. In particular, one can't add new syscalls. Here's a suggestion I would be happy to hear your ideas on - the NXT-G compiler has (...) (19 years ago, 21-Mar-07, to lugnet.robotics.nxt)
|
