 | | IRPD sensors and LegOS (long)
|
|
Well, after much frustration and a great deal of help from the very wise Rossz, I was finally able to get up and running w/ DJGPP and LegOS 0.2.4 The first thing I did was write a program to use with Pete Sevcik's IRPD proximity detectors that he (...) (24 years ago, 30-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Linking failure when 'making' an lx file
|
|
(...) Sorry about the extra stuff, the linking problem was due to the compiler trying to find the above link "___ucmpsi2". When I used h8300-hitachi-hms-nm I could see all the methods and links in my code, and this was the only strange looking one. (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Linking failure when 'making' an lx file
|
|
Hi Can anyone tell me why I'm getting a linking failure when trying to compile my C code, in the standard way. The linker is failing to find a fucntion I have defined in my source: /usr/local/crossgcc/...chi-hms-ld -T ../boot/legOS.lds -relax (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blockin LNP calls
|
|
(...) I guess I'm using lnp_logical_write then? That is, I include the standard lib_lnp.h file into my code and then link my app with liblnp.so.....does this answer your question? Is there a way in which I can call lnp_logical_write directly to test (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blockin LNP calls
|
|
(...) No, I meant lnp_logical_write, which is called from lnp_addressing_write. lnp_logical_write is not within the file lnp.c, which I guess you link into your app. This function is supposed to actually write to the serial device communicating with (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blockin LNP calls
|
|
(...) Sorry, I was using an unsigned char variable, this was just a remnant of some testing I did..... I tried a lot of variations ;-) (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blockin LNP calls
|
|
(...) Yes, the problem is on the host PC (running Red Hat 6.2). What I cant figure out is how identical code works fine if I instantiate the wrapper class in a simple demo app, but once I try calling it form within my CORBA server, it blocks on (...) (24 years ago, 28-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blockin LNP calls
|
|
(...) From the statement "data is received by the RCX" I assume you have this problem on the host system. What OS are you using? Also, how does your lnp_logical_write() routine look like? Eddie C. Dost ecd@skynet.be (24 years ago, 27-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blockin LNP calls
|
|
(...) ,testaddress, 8); It shouldn't be the real problem, but are you sure about the port paramenter? How about: result = lnp_addressing_write...estbuffer, testlen ,testaddress, testport); Bye, Paolo. --- Maier's Law: If the facts do not conform to (...) (24 years ago, 27-Aug-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Blockin LNP calls
|
|
HELP! I'll ellaborate a little on the details of my previous posting: My code (removing some CORBA detail) looks like this: I have a class "nanOrbDemo_i" which has the following constructor: inline nanOrbDemo_i(){ if ( lnp_init(0,0,0,0,0) ){ cout << (...) (24 years ago, 27-Aug-00, to lugnet.robotics.rcx.legos)
|
