Friday, November 18, 2005
Schedule for next 2 weeks
I will be out of the office and away from hardware not on the laptop.
Nov 21-23 (Mon-Wed) : Gone for Thanksgiving. Occasional email checking.
Nov 28-Dec 1 (Mon-Thu) : In Nashua, NH for Elements training. Should have full access to email but might not respond right away.
Nashua contacts:
Sheraton Nashua: 603 . 888 . 9970
Nov 21-23 (Mon-Wed) : Gone for Thanksgiving. Occasional email checking.
Nov 28-Dec 1 (Mon-Thu) : In Nashua, NH for Elements training. Should have full access to email but might not respond right away.
Nashua contacts:
Sheraton Nashua: 603 . 888 . 9970
Tipsheet for Nov 18
-------------------------------------
Question: Why does my Illuminator version say 3.4.1 ? I thought we are on release 5.1 now.
Answer: You are running the Tools 1.1 release of Illuminator. Prior to OSE 5.1, the Illuminator product was bundled with the OSE distribution. Starting in 5.1 however the Illuminator is shipped separately with the Tools distribution. At some point the decision was made to divert Illuminator into its own stream, which is why it now has a different number.
Problem: Unable to build rtose image in Eclipse
Symptom:
"make: makefile: line xx: Error -- Expecting macro or rule defn, found neither"
Solution:
The cryptic error really means your system is confused about which cygwin installation is needed here. Since you need $OSE_ROOT/cygwin/bin from OSE to be used here, put that in your PATH environment variable first. Do this is both /cygwin.bat and also Windows System settings, just to be sure it's the same for both.
Problem: Unable to debug rtose.exe for OSE 5.1 soft kernel in Eclipse
Symptom:
Trying to debug this as a local C/C++ application, during setting up the debug configuration Eclipse says that rtose.exe is not a valid image. You may also see that it Eclipse does not allow you to select this as the image in the debug configuration.
Solution:
Make sure one or more of the correct binary parser checkbox is selected (project->properties->c/c++make project->binary parser) "PE Windows Parser" and/or "Cygwin PEParser" are appropriate for most users. This has to be correct to make Eclipse CDT recognize the files as executable. If it does the file will show up in the "Binaries" folder under the project.
Question: Why does my Illuminator version say 3.4.1 ? I thought we are on release 5.1 now.
Answer: You are running the Tools 1.1 release of Illuminator. Prior to OSE 5.1, the Illuminator product was bundled with the OSE distribution. Starting in 5.1 however the Illuminator is shipped separately with the Tools distribution. At some point the decision was made to divert Illuminator into its own stream, which is why it now has a different number.
Problem: Unable to build rtose image in Eclipse
Symptom:
"make: makefile: line xx: Error -- Expecting macro or rule defn, found neither"
Solution:
The cryptic error really means your system is confused about which cygwin installation is needed here. Since you need $OSE_ROOT/cygwin/bin from OSE to be used here, put that in your PATH environment variable first. Do this is both /cygwin.bat and also Windows System settings, just to be sure it's the same for both.
Problem: Unable to debug rtose.exe for OSE 5.1 soft kernel in Eclipse
Symptom:
Trying to debug this as a local C/C++ application, during setting up the debug configuration Eclipse says that rtose.exe is not a valid image. You may also see that it Eclipse does not allow you to select this as the image in the debug configuration.
Solution:
Make sure one or more of the correct binary parser checkbox is selected (project->properties->c/c++make project->binary parser) "PE Windows Parser" and/or "Cygwin PEParser" are appropriate for most users. This has to be correct to make Eclipse CDT recognize the files as executable. If it does the file will show up in the "Binaries" folder under the project.
Thursday, November 10, 2005
Tipsheet
-------------------------------------
Problem: Finding Emanate & Emanate Lite SNMP in 4.x Release docs
Symptom:
Unable to find release notes and OSE-specific info for SNMP product.
Solution:
Starting in 4.5, the 3part directory subtree for emanate_full
and emanate_lite contains a /doc directory. One might expect to see the
release notes there, however the specific release notes for this version
are not there. Look for the release notes for each release in:
$OSE_ROOT//doc/emanate_*.txt
Note that for 4.6, the only architectures that have emanate_*.txt are
for sfk-win32 and powerpc.
In 5.x, the SNMP product was ported to the IPNET stack, so the corresponding
release notes file is in:
$OSE_ROOT/refsys/modules/emanate_src/ipemanate/doc
Problem: Finding Emanate & Emanate Lite SNMP in 4.x Release docs
Symptom:
Unable to find release notes and OSE-specific info for SNMP product.
Solution:
Starting in 4.5, the 3part directory subtree for emanate_full
and emanate_lite contains a /doc directory. One might expect to see the
release notes there, however the specific release notes for this version
are not there. Look for the release notes for each release in:
$OSE_ROOT/
Note that for 4.6, the only architectures that have emanate_*.txt are
for sfk-win32 and powerpc.
In 5.x, the SNMP product was ported to the IPNET stack, so the corresponding
release notes file is in:
$OSE_ROOT/refsys/modules/emanate_src/ipemanate/doc
Tasks
I have a lot of stuff on my plate right now, although much of it is not directly related to a customer issue. I'm still getting my parts environment set up, self-training and trying to make progress on my hardware.
- iSystem: I have a real need now to get freeze-mode debugging. I am trying to get the emanate_lite example running in 4.5.2 to see how our SNMP works, and it boots fine as long as I don't change anything. But the host (agent) doesn't communicate with the target (manager). (The command to test this out is "getmany" in the SNMP delivery.) So I have to change the IP settings in userconf.mk to get it to match what I currently have: host=10.11.1.11 and target=10.11.1.20 . Of course after I change that one little thing, the emanate_lite example doesn't even boot. So I need to get to the bottom of this.
- Gateway: need to get a Gateway example going as well.
- VPN is fixed and the VPN licenses are working for compiles but not for debug. The VPN is interefering somehow with the communication between host and target. They cannot ping each other, unless the VPN is taken down first. (inetutil example in 4.5.2)
- RVCT compiler: have 2.2 installed, will downoad 2.1 from extranet also.
- GHS temp license: received a new one so I'm set with a local GHS license for a little while.
Now (finally ) customer-related stuff.
-------------------------------------
- SNMP questions about the MIB object snmpEnableAuthenTraps and customer wants to be able to change that setting on the fly. After some dialog with the vendor it seems that the customer has to change this on their own - there is no API for it. The struct that the object is in is a global so they can change it anytime, anywhere it is externed. Vendor also said a "set" request can be sent to change it, but it's not real clear from the 600 page document and examples how to do that using the existing MIB object.
- NTP TSG written by HQ support is almost ready for publishing, need to review final draft and send any comments back.
- [elxr] link warning ose_confd.o from ghs4.07 : HQ Support wants customer to use ghs3.x instead. Case will stay as is but shift to minor priority.
- OSEck sfk-linux with simulator app: Not sure what status of this is, someone from outside has become involved. Are they going to bring in a consultant to deal with this?
- iSystem: I have a real need now to get freeze-mode debugging. I am trying to get the emanate_lite example running in 4.5.2 to see how our SNMP works, and it boots fine as long as I don't change anything. But the host (agent) doesn't communicate with the target (manager). (The command to test this out is "getmany" in the SNMP delivery.) So I have to change the IP settings in userconf.mk to get it to match what I currently have: host=10.11.1.11 and target=10.11.1.20 . Of course after I change that one little thing, the emanate_lite example doesn't even boot. So I need to get to the bottom of this.
- Gateway: need to get a Gateway example going as well.
- VPN is fixed and the VPN licenses are working for compiles but not for debug. The VPN is interefering somehow with the communication between host and target. They cannot ping each other, unless the VPN is taken down first. (inetutil example in 4.5.2)
- RVCT compiler: have 2.2 installed, will downoad 2.1 from extranet also.
- GHS temp license: received a new one so I'm set with a local GHS license for a little while.
Now (finally ) customer-related stuff.
-------------------------------------
- SNMP questions about the MIB object snmpEnableAuthenTraps and customer wants to be able to change that setting on the fly. After some dialog with the vendor it seems that the customer has to change this on their own - there is no API for it. The struct that the object is in is a global so they can change it anytime, anywhere it is externed. Vendor also said a "set" request can be sent to change it, but it's not real clear from the 600 page document and examples how to do that using the existing MIB object.
- NTP TSG written by HQ support is almost ready for publishing, need to review final draft and send any comments back.
- [elxr] link warning ose_confd.o from ghs4.07 : HQ Support wants customer to use ghs3.x instead. Case will stay as is but shift to minor priority.
- OSEck sfk-linux with simulator app: Not sure what status of this is, someone from outside has become involved. Are they going to bring in a consultant to deal with this?
Friday, November 04, 2005
Elements training schedule
Elements training is set for Nashua, NH for Nov 29, 30 and Dec 1. My plan is to leave early Nov 28 and return evening of Dec 1.
Thursday, November 03, 2005
Weekly tips
Problem: OSEck 3.1 and Illuminator require different license files
Symptom:
One of the products displays "unable to get license" error on launch, because LM_LICENSE_FILE and/or the Illuminator configuration are pointing to an incorrect file.
Solution:
Set environment variable LM_LICENSE_FILE to point to the license.dat for OSEck. Then start Illuminator. Enter "File" menu and select "Preferences", followed by "License" tab. Set the license to point to the Illuminator license.dat . They can be different files in different places.
------------------------------------------------------
Problem: Soft Kernel compiling for 5.1 : cannot use ARCH=sfk-win32
Symptom:
make lm ARCH=sfk-win32
Error: module X does not build as a load module
Solution:
The soft kernel compile for refsys in 5.1 cannot use ARCH as
sfk-win32 or any other sfk designation. Need to use x86, solaris or similar.
See: $OSE_ROOT/refsys/modules/modules.mk for rules used by make
to determine.
--------------------------------------------------------
Problem: unable to get license for Illum. 1.1 tools release
Symptom:
Fire up Tools 1.1 Illum. and get "could not get the license" error window.
Solution:
The Illuminator release for Tools 1.1 (shipped apart from 5.1)
requires the tools flexlm license.dat rather than the one for 5.1 soft kernel.
Use the tools 1.1 license to get Illuminator functionality for this release.
--------------------------------------------
Problem: Unable to compile on 4.4.1 using gcc
Symptom: varies but usually see output like:
C:\OSE\common\src\startefs
.c /cygdrive/c/DOCUME~1/NSHEVC~1/LOCALS~1/Temp/cc4eHC5U.i
powerpc-eabi-gcc: Internal compiler error: program cpp got fatal signal
11
dmake.exe: Error code 129, while making '..\obj\\startefs.o'
Solution:
Add to your root /cygwin.bat for OSE 4.4.1 the following define:
GCC_EXEC_PREFIX=/cygdrive/c/OSE/OSE4.4.1/win32/lib/gcc-lib/
--------------------------------
Symptom:
One of the products displays "unable to get license" error on launch, because LM_LICENSE_FILE and/or the Illuminator configuration are pointing to an incorrect file.
Solution:
Set environment variable LM_LICENSE_FILE to point to the license.dat for OSEck. Then start Illuminator. Enter "File" menu and select "Preferences", followed by "License" tab. Set the license to point to the Illuminator license.dat . They can be different files in different places.
------------------------------------------------------
Problem: Soft Kernel compiling for 5.1 : cannot use ARCH=sfk-win32
Symptom:
make lm ARCH=sfk-win32
Error: module X does not build as a load module
Solution:
The soft kernel compile for refsys in 5.1 cannot use ARCH as
sfk-win32 or any other sfk designation. Need to use x86, solaris or similar.
See: $OSE_ROOT/refsys/modules/modules.mk for rules used by make
to determine.
--------------------------------------------------------
Problem: unable to get license for Illum. 1.1 tools release
Symptom:
Fire up Tools 1.1 Illum. and get "could not get the license" error window.
Solution:
The Illuminator release for Tools 1.1 (shipped apart from 5.1)
requires the tools flexlm license.dat rather than the one for 5.1 soft kernel.
Use the tools 1.1 license to get Illuminator functionality for this release.
--------------------------------------------
Problem: Unable to compile on 4.4.1 using gcc
Symptom: varies but usually see output like:
C:\OSE\common\src\startefs
.c /cygdrive/c/DOCUME~1/NSHEVC~1/LOCALS~1/Temp/cc4eHC5U.i
powerpc-eabi-gcc: Internal compiler error: program cpp got fatal signal
11
dmake.exe: Error code 129, while making '..\obj\\startefs.o'
Solution:
Add to your root /cygwin.bat for OSE 4.4.1 the following define:
GCC_EXEC_PREFIX=/cygdrive/c/OSE/OSE4.4.1/win32/lib/gcc-lib/
--------------------------------
free invisible web counter
