 | | .lx format
|
| Hi! I am presently helping some PhD students here at my university prepare the labs for a real-time course using LegOS. As part of the course, we want our students to experience a modern development environment for embedded systems, and have (...) (23 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
| | | | | Re: .lx format
|
| (...) Look at legOS makefiles. The lx file is generated from two symbolsrec executables linked to different positions. The files are generated with a special linker script "legOS.lds". Maybe you can do the same with your compiler and use the makelx (...) (23 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
| | | | | Re: .lx format
|
| (...) So in effect, it is dependent on the gcc loader mechanism. Ungh! The idea of using two symbolsrec files: one could be kernel, the other the program. Would make sense for kernel call resolution. (...) I looked at it, and it mainly outputs (...) (23 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
| | | | | Re: .lx format
|
| (...) One other possibility is to not use the lx files at all - just stick to the srec format as (I think) LegOS used to (version 0.1.x?). A bit less efficient downloading the kernel all the time, but removes the need to dabble with lx format at (...) (23 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
| | | | | Re: .lx format
|
| (...) We arrived at that solution independently here... it makes more sense. Also, since only the parts of the kernel we actually use need to be linked in, the result should be much smaller than a full kernel. Furthermore, the compiler we are using (...) (23 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
| | | | | Re: .lx format
|
| (...) We arrived at that solution independently here... it makes more sense. Also, since only the parts of the kernel we actually use need to be linked in, the result should be much smaller than a full kernel. Furthermore, the compiler we are using (...) (23 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
| | | | | Re: .lx format
|
| (...) We are going to use this solution. Seems simpler. /jakob (23 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
| |
