Subject:
|
Setting LNP host address
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Mon, 20 May 2002 21:26:01 GMT
|
Viewed:
|
2746 times
|
| |
|
|
I've experimented with a couple of choices which were relatively easy to
implement. Let me know if we should keep any these:
1. You can choose to set the host address at build time with a command-line
option to make.
Example: make LNP_HOSTADDR=2
will create an output image file (legos.srec) with the LNP host address set
to 2. Default is 0 for RCX and 8 for PC. The range is 0..15
2. I have added a new protocol message to program.c and added a new command
to dll that will dynamically change the RCX host address when invoked. [A
bit dangerous?]
Example: dll -n3 (or dll --node=3)
will set the RCX LNP host address to 3. And yes, the following works:
"dll -r3 -n0" will reset the RCX, currently addressed as node 3, to be 0.
This will override any setting made during compile-time.
A user program can query "extern unsigned char lnp_hostaddr" (lnp.h) to find
out what address you are running under - if such things matter to you.
Do you all think it is still important to be able to set the LNP host
address during system image download (firmdl3)? These features seem to fit
the need and modifying firmdl3 to modify the image is a bit messy.
/ted
|
|
Message has 1 Reply:
 | | Re: Setting LNP host address
|
| (...) Joe Woolley prototyped the firmdl3 mods, I think, and has now a user program which can change the Id. This now makes 4 approaches we have to consider ;-) My thinking on firmdl3 use was that it is a direct replacement for compile time set that (...) (22 years ago, 23-May-02, to lugnet.robotics.rcx.legos)
|
4 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
