 | | Re: ARM Assembly Language Programming on NXT?
|
|
Hi T.C. (...) aha. I just programmed some startup and interrupt wrapper code (the rest is C), so I didn't get into the higher reaches of macros etc. Jürgen (17 years ago, 16-Oct-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: ARM Assembly Language Programming on NXT?
|
|
(...) Sorry, I found a more recent version, but it's still missing some parts on the ARM architecture: (URL) also found the following Intro guide (which is better than nothing): (URL) (17 years ago, 16-Oct-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: ARM Assembly Language Programming on NXT?
|
|
Hi Juergen, Thanks for replying. (...) Thanks for the info. My goal is to run and debug ARM assembly language programs executing in RAM. I was not familiar with the NXT, so currently I'm looking at the on-board capabilities. I realized after some (...) (17 years ago, 16-Oct-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: ARM Assembly Language Programming on NXT?
|
|
Hi T.C., (...) I have an AT91SAM7S-EK here, it has 4 LEDs and 4 touch buttons. It should also be fairly easy to write a driver for one of the serial ports (polling would suffice for a start). On the NXT the only I/O that is easy to use with the (...) (17 years ago, 14-Oct-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: ARM Assembly Language Programming on NXT?
|
|
(...) Thanks for the tip. I glanced at (URL) previously but I must've missed it thinking it's Java based. (...) Are you referring to the default NXT firmware or the LEJOS NXJ/OSEK firmware? (...) You're right, I've come across several ARM-based SBC (...) (17 years ago, 9-Oct-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: ARM Assembly Language Programming on NXT?
|
|
(...) Thanks Dick for intruducing LEJOS OSEK, When we develolped LEJOS OSEK, Prof. Mizuno wrote several GCC assembly code to port TOPPERS OSEK (an open source OSEK OS) to NXT. Whole assembly code(*.S) is stored in lejos_osek\toppers_o...1sam7s-gnu (...) (17 years ago, 9-Oct-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | RE: ARM Assembly Language Programming on NXT?
|
|
Do a Google on "LEJOS OSEK". I believe this is a solution that has taken the base "OS" from the NXJ JAVA byte code interpreter as the basis for programming the NXT using GCC C++. I assume if you can use the GCC C/C++ tools with the NXT then you (...) (17 years ago, 8-Oct-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | ARM Assembly Language Programming on NXT?
|
|
Hi, I just stumbled on this newsgroup/website while searching for kits for teaching Assembly Language programming to undergraduate students in Comp. Science in an interesting (interactive) manner. I'm primarily interested in the ARM instruction set. (...) (17 years ago, 8-Oct-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: US-Sensor I2C-address
|
|
(...) To my knowledge the LEGO Ultrasonic sensor does not support changing its I2C address. IIRC it is hard-coded to 0x02. I do not think it is ADPA-compliant. John Hansen (17 years ago, 5-Sep-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | US-Sensor I2C-address
|
|
Hello Community, is there currently a known way to change the I2C-Address of the Ultrasonic sensor ? What's the magic with the ADAP ? Thanks for some informations Bye Christian (17 years ago, 4-Sep-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)
|
| |
| | 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
|
|
(...) 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: LEJOS OSEK giving me funky dll errors
|
|
(...) The problem that you have encountered seems to be a common Cygwin problem. (please google cygintl-3.dll). I guess that you need to re-install Cygwin. In my case, I just select make 3.81-1 under Devl and other stuff remains as default during (...) (17 years ago, 19-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | LEJOS OSEK giving me funky dll errors
|
|
I've installed LEJOS OSEK 1.04, but when I try to make all in the helloworld example, I get the error "This application has failed to start because cygintl-3.dll was not found. Re-installing the application may fix this problem." I've tried telling (...) (17 years ago, 17-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Real C/C++ Programming Solution?
|
|
Takashi Chikamasa wrote: LEJOS OSEK also supports the program upload to Flash. However, I intentionally (...) As far as I know, this is from the manufacturers extreme limits of operation. I have personally cycled my NXT through a SAMBA load many (...) (17 years ago, 15-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Real C/C++ Programming Solution?
|
|
(...) LEJOS OSEK also supports the program upload to Flash. However, I intentionally do not describe it in the docs. I am not sure about the life cycle of Flash in the ATMEL ARM7 very well, however, some lugnet discussions told me that the lifecyle (...) (17 years ago, 15-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Real C/C++ Programming Solution?
|
|
(...) The closed-loop features I'd like would be comparable to those implemented in the Charmed Labs Xport Botball Controller (see charmedlabs.com and botball.org) - PID control of velocity, with a "move to position" command and preferably (not (...) (17 years ago, 10-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: NXT memory map
|
|
(...) Strange, for me it is always easy to find with Google: (URL) data sheet is here: (URL) Jürgen Stuber <juergen@jstuber.net> (URL) (17 years ago, 10-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Real C/C++ Programming Solution?
|
|
(...) Actually, implementing a closed-loop motor control in LEJOS OSEK is not difficult. I already have done for NXTway-DS(complex state space feedback) and NXT GT(P control for motor rev. angle). A significant factor to implement a close-loop motor (...) (17 years ago, 8-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Real C/C++ Programming Solution?
|
|
(...) Hmm, how hard would it be to just copy some of those functions from NXTGCC and use them in LEJOS OSEK? Would they require significant modification? Thanks, Jeremy Rand (17 years ago, 8-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Real C/C++ Programming Solution?
|
|
(...) Currently, LEJOS OSEK does not provide abstracted API such as you asked. I agree that LEJOS OSEK should provide more sophisticated API for ease of use. I hope someone will raise his/her hand to write such framework library. Sorry for your (...) (17 years ago, 7-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Real C/C++ Programming Solution?
|
|
Is there a programming solution for the NXT that will allow me to use real C/C++? I've been trying to use NXTGCC (this is for firmware development based on an existing firmware for another controller, which is written in C/C++), but the code seems (...) (17 years ago, 7-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: NXT memory map
|
|
(...) I found everything here (URL) not directly at Atmel... Christian (17 years ago, 7-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | NXT memory map
|
|
Hi, where can I get some more informations about NXT memory map when system is running ? 1. Startaddress of RAM (Range: 0x0000 0000 - 0x0000 FFFF) ??? 2. Startaddress of Flash (Range: 0x0001 0000 - 0x0003 FFFF) ??? Is it true, that the flashmemory (...) (17 years ago, 6-Aug-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Alternate NXT-Firmware flashing tools
|
|
(...) Hi Matt, I think the problem is, that 99% of users using MS and Intel equipment... Minorities, like me, have always problems when using this :D I can't resist... Bye Christian (17 years ago, 29-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Alternate NXT-Firmware flashing tools
|
|
(...) Hi Jürgen, just for information: nxjflash has the same problems at PPC and SPARC ;-( Next week I try to get a little endian machine and try it again... Thanx for your detailed informations Bye Christian (17 years ago, 29-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Alternate NXT-Firmware flashing tools
|
|
Hi all, (...) Recently, we finished a runtime for the RCX, and discovered the awful state of uploading tools for that platform. In particular, there are at least three versions of firmdl running around the net, each capable handling different (...) (17 years ago, 28-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Alternate NXT-Firmware flashing tools
|
|
Hi Christian, (...) if you have an endianness problem it should be visible. The easiest would be to compare it with a little-endian machine. (...) It uses the SAM-BA protocol, which is rather simple and without error checking, more like what a human (...) (17 years ago, 28-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Alternate NXT-Firmware flashing tools
|
|
(...) ReHi Jürgen, yes this is a trivial job, but what should I learn from this packets ? fwflash returns no error back to commandline ... Does this mean fwflash works blindly and returns no protocol or packet errors ? Why is the result "success" (...) (17 years ago, 26-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Alternate NXT-Firmware flashing tools
|
|
Hi Christian, (...) you could add some code in lowlevel.c to dump the USB packets, and then look if you see anything wrong. Jürgen (17 years ago, 26-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Alternate NXT-Firmware flashing tools
|
|
(...) Hi Jürgen, very good idea. Please give me some hints where to start. I haven't found any --verbose command line parameters, yet :D OK, I'm trying to read the source again, expecting ENDIAN problems like every time using PPC and SPARC :-D Bye (...) (17 years ago, 25-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Alternate NXT-Firmware flashing tools
|
|
Hi Christian, (...) how about trying to fix fwflash? Jürgen (17 years ago, 25-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Alternate NXT-Firmware flashing tools
|
|
Hi NXT-Community, I'm searching for an alternate firmware flashing tool for the NXT... Using the Lego Mindstorms Software is an easy way to do this, but not available for my favorite operating systems. I've tried fwflash from libnxt, but without (...) (17 years ago, 25-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Messing with memory pool
|
|
(...) So you have not removed the line from cCmdInitPool where VarsCmd.Pool is set equal to IOMapCmd.MemoryPool, correct? Can you say where "mem" comes from and is it for certain being initialized to zero or nil before cCmdInitPool gets called? Is (...) (17 years ago, 20-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Messing with memory pool
|
|
(...) Okay, thanks for the tip. It was a bit unnecessary for you to spend two paragraphs on that, though; a sentence or two would have sufficed. :-) (...) Code is as follows: if (!mem) mem= (char*)(VarsCmd.Pool); memset(mem, 0, POOL_MAX_SIZE); I'm (...) (17 years ago, 17-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Messing with memory pool
|
|
(...) There is no such thing as an NXT-G memory pool. The standard NXT firmware has nothing to do with the graphical programming language implemented by LEGO and NI which is called NXT-G. (...) Why are you setting it to 0x00 if other parts of the (...) (17 years ago, 17-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | 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. (...) (17 years ago, 16-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | binsert question
|
|
Starting with the original NXTGCC source, if I disable binsert in the makefile, the firmware crashes on boot. The firmware development which I am doing will probably increase the size of the firmware by around 20KB, so I'm wondering if I need to do (...) (17 years ago, 11-Jul-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Custom firmware crashing on boot
|
|
Sorry I didn't have time to reply to your post yesteday; I had limited time available. (...) Hmm, as I said yesterday to Dick, disabling all three binsert calls in the makefile caused my firmware to crash on a blank screen, even after I had done (...) (17 years ago, 29-Jun-07, to lugnet.robotics.nxt.nxthacking)
|
