Friday, March 10, 2006
Tips for the week: Mar 10 2006
Q: I hear there’s a way to tell OSE to boot with debug capability enabled, but not actually running. I.e. ose_dbgserver, ose_sdm, and ose_ldm are not actually running until a “debug” shell command is invoked. But when I enter that command in my shell it isn’t recognized. How do I get it?
A: The “debug” shell command can be enabled in refsys builds only. You must make sure you’ve got refsys build capability for your binary. If you do (OSE4.6 and up) you can enable it by adding the following:
rtose.mk : add “USE_DEBUG = yes”
rtose4.conf : set debug option to “debug=enable:no”
Then “make all” in the refsys target directory and your rtose.elf binary will have “debug” command enabled.
NOTE: In OSE4.5.2 the rtose.mk file is actually Makefile instead. (But I haven’t been able to test refsys with 4.5.2 yet.)
Q: I am trying to connect to my already-running target using powerpc-ose-gdb, but when I type “info ose targets” it just returns nothing. What is wrong?
A: If you’ve waited a bit already (at least 15 secs), then sounds like your host cannot communicate with the target. Possible reasons include
- incorrect inet configuration (rtose*.conf)
- inet/default_gw is incorrect (try leaving it blank for static IP)
- ose_dbgserver not running (“ps ose_d*”)
- binary not compiled with proper gcc flavor (different target flavors in 5.1)
- network card or cable malfunction (can host/target ping each other? Can Illuminator System Browser see the target?)
- misc. software interference (VMWare, VPN etc)
Q: I’m compiling with GHS MULTI and got this error:
[elxr] (error) cannot find library –lc
A: Alas, you are trying to compile MULTI on OSE5.x which isn’t yet supported. Stick with 4.x for now.
Q: I’m new to this RTOS and I have no idea to find out which version of OSE I’m running currently, and I only have a shell to work with.
A: The built-in version shell command is different in 4.x and 5.x .
OSE4.x : “ver”
OSE5.x : “build_info”
Failing that, when the system boots check the console at boot time.
Q: I’m booting with POLO and I noticed that POLO reports it only downloaded 2MB of binary, which doesn’t sound right – I know the binary is at least 10MB. However it appears to boot and run without problems.
A: POLO may or may not accurately report the actual total downloadable size of the binary image, based on the compiler used. Some compilers are better than others at giving POLO correct information. Others will simply report the size of the stripped elf (rtose_s.elf) rather than the full-blown size of a release or debug elf. It’s confusing but not a big cause for concern.
A: The “debug” shell command can be enabled in refsys builds only. You must make sure you’ve got refsys build capability for your binary. If you do (OSE4.6 and up) you can enable it by adding the following:
rtose.mk : add “USE_DEBUG = yes”
rtose4.conf : set debug option to “debug=enable:no”
Then “make all” in the refsys target directory and your rtose.elf binary will have “debug” command enabled.
NOTE: In OSE4.5.2 the rtose.mk file is actually Makefile instead. (But I haven’t been able to test refsys with 4.5.2 yet.)
Q: I am trying to connect to my already-running target using powerpc-ose-gdb, but when I type “info ose targets” it just returns nothing. What is wrong?
A: If you’ve waited a bit already (at least 15 secs), then sounds like your host cannot communicate with the target. Possible reasons include
- incorrect inet configuration (rtose*.conf)
- inet/default_gw is incorrect (try leaving it blank for static IP)
- ose_dbgserver not running (“ps ose_d*”)
- binary not compiled with proper gcc flavor (different target flavors in 5.1)
- network card or cable malfunction (can host/target ping each other? Can Illuminator System Browser see the target?)
- misc. software interference (VMWare, VPN etc)
Q: I’m compiling with GHS MULTI and got this error:
[elxr] (error) cannot find library –lc
A: Alas, you are trying to compile MULTI on OSE5.x which isn’t yet supported. Stick with 4.x for now.
Q: I’m new to this RTOS and I have no idea to find out which version of OSE I’m running currently, and I only have a shell to work with.
A: The built-in version shell command is different in 4.x and 5.x .
OSE4.x : “ver”
OSE5.x : “build_info”
Failing that, when the system boots check the console at boot time.
Q: I’m booting with POLO and I noticed that POLO reports it only downloaded 2MB of binary, which doesn’t sound right – I know the binary is at least 10MB. However it appears to boot and run without problems.
A: POLO may or may not accurately report the actual total downloadable size of the binary image, based on the compiler used. Some compilers are better than others at giving POLO correct information. Others will simply report the size of the stripped elf (rtose_s.elf) rather than the full-blown size of a release or debug elf. It’s confusing but not a big cause for concern.
free invisible web counter
