Wednesday, November 20, 2013
Issues with launching sfk-linux for OSE5.5.1 on Optima 2.8
Q: Trying to debug launch sfk-linux on Optima 2.8 with Fedora FC9. The sfk-linux does not start within the debugger, complaining about flash.mem. When Optima2.8 was started on the command line earlier, this error is seen in the console:
$ ./eclipse -clean
Gtk-Message: Failed to load module "gnomebreakpad":
libgnomebreakpad.so: cannot open shared object file: No such file or directory
(eclipse:6953): Gtk-WARNING **: Unable to locate theme engine in
module_path: "nodoka",
(eclipse:6953): Gtk-WARNING **: Unable to locate theme engine in
module_path: "nodoka",
Exception occurred in monitor receiver thread: java.io.EOFException java.io.EOFException
at java.io.DataInputStream.readInt(Unknown Source)
at com.ose.gateway.Command.readHeader(Command.java:91)
at com.ose.gateway.CommandReceive.readReply(CommandReceive.java:74)
at com.ose.gateway.Gateway.receive(Gateway.java:937)
at com.ose.gateway.Gateway.receive(Gateway.java:830)
at com.ose.system.service.monitor.Monitor$ReceiverThread.run(Monitor.java:4709)
Monitor disconnect request failed.
Error disconnecting sender gateway.
Detaching from monitor failed.
A: If you are using sfk-linux from BSP_SFK_OSE5.5.1 with an OSE5.5.1 delivery, there may be issues debugging it a newer version of Optima e.g. 2.8. This setup will generally work fine on Optima 2.7, but there were some changes to Optima 2.8 that cause problems. Migrate the same BSP to use OSE5.5.3 instead of 5.5.1 (just repointing it within environment.mk), rebuild, and most of these problems will go away.
$ ./eclipse -clean
Gtk-Message: Failed to load module "gnomebreakpad":
libgnomebreakpad.so: cannot open shared object file: No such file or directory
(eclipse:6953): Gtk-WARNING **: Unable to locate theme engine in
module_path: "nodoka",
(eclipse:6953): Gtk-WARNING **: Unable to locate theme engine in
module_path: "nodoka",
Exception occurred in monitor receiver thread: java.io.EOFException java.io.EOFException
at java.io.DataInputStream.readInt(Unknown Source)
at com.ose.gateway.Command.readHeader(Command.java:91)
at com.ose.gateway.CommandReceive.readReply(CommandReceive.java:74)
at com.ose.gateway.Gateway.receive(Gateway.java:937)
at com.ose.gateway.Gateway.receive(Gateway.java:830)
at com.ose.system.service.monitor.Monitor$ReceiverThread.run(Monitor.java:4709)
Monitor disconnect request failed.
Error disconnecting sender gateway.
Detaching from monitor failed.
A: If you are using sfk-linux from BSP_SFK_OSE5.5.1 with an OSE5.5.1 delivery, there may be issues debugging it a newer version of Optima e.g. 2.8. This setup will generally work fine on Optima 2.7, but there were some changes to Optima 2.8 that cause problems. Migrate the same BSP to use OSE5.5.3 instead of 5.5.1 (just repointing it within environment.mk), rebuild, and most of these problems will go away.
Labels: Fedora, Optima, OSE5.5.1, sfk-linux
Friday, September 27, 2013
Optima launch error: "Unable to read workbench state"
Q: I tried launching Optima 2.7 and for some reason it thought my C/C++ source view was stale so it requested a refresh of the C/C++ view. Afterward, I am not able to bring up System Browser or System Profiler, or any other Optima tools due to this error:
A: The metadata needs cleaning up. Find optima_win32/eclipse (or wherever the executable is for your case) and run it from the command line once as "./eclipse -clean" to remove any spoiled caches for eclipse. They may have been disordered after refreshing the source view (sometimes happens if you switch between different versions of eclipse). After Optima comes up, shut it down in orderly fashion and relaunch it (without clean) once more. This should resolve whatever cache or plugin inconsistencies cause Optima to forget where the perspective is. If that doesn't help, find your workspace directory and delete .metadata/.plugins/org.eclipse.ui.workbench/workbench.xml to force Optima to revert to the default perspective on startup.
Labels: eclipse, Optima, workbench
Friday, June 21, 2013
Optima for "non-standard" Linux systems
Q: I'm trying out Optima on Linux, but i've already got a working system running Fedora / Ubuntu / x86_64 / VMWare / $ODD_JAVA ... etc.... which isn't among the list of things specifically supported by the documentation. Is there any guarantee that Optima will be able to work on any of those?
A: Well, yes and no. The answer to that question ultimately is determined by how much time you have available to spend to get things working.
By way of real-life examples, here are some obstacles you may encounter.
x86_64 systems: Optima for Linux is inherently a 32-bit application. If you installed everything, or upgraded everything, exclusively for x86_64 bit usage, you're going to have problems.
- The java installation is the key to everything; if you have 64-bit java only, you'll find quickly the 32-bit run-time JVM unzipped by the installation program won't proceed. (To verify this, run the native Eclipse that came with your x86_64 system to make sure at least that much works.) Uninstall the 64-bit version and/or rename the path to /usr/bin/java, install a compatible jdk for i386 or i686, and relink to that version just to get past the installation.
- The next problem is... everything else you've got for 64-bit operation that needs a 32-bit library. You should install at a minimum libgtk* for 32-bit, otherwise you'll start seeing errors for that library.
- The symptom of 32-bit problems is typically that "optima_linux/eclipse" appears to start, but does nothing, and uneventfully returns to the prompt. Add "-debug" tells you nothing interesting; look for clues instead in the configuration/*.log files.
VMWare: Much of the usefulness of VMWare draws on the ability to mount shared file systems, so you can avoid reading DVDs or doing large network transfers to get access to your installation software. There's known problems however getting /hgfs to mount in VMWare, when the kernel level of Linux as a guest is >3.3 or so. The root cause is that the vmware Toolset that handles this task hasn't been smoothly migrated for newer kernels. If you can run a VM that's got a slightly older kernel, you'll have much better luck.
Labels: 64-bit, installation, Linux, Optima, VMWare
Tuesday, June 18, 2013
Optima Log Manager Linux - saving events and notifications in XML format
Q: I've got the Optima Log Manager running and producing traces on my console. I want to save this as something readable by external tools that can process XML or text. The Linux version of Optima saves the trace data always into a .pmd file. How can I get the trace data in a more readable form?
A: In the Linux Optima Log Manager, when you save a file, there is an option to "Browse for other folders." What isn't obvious in this choice is that you can also browse other options for saving your file, namely the format to save it in. The default looks like this:
If you expand "Browse", you'll see this:
Note the lower right corner, where the file extension listbox now appears. If you save in ".event" format, you'll get an XML file as a result.
A: In the Linux Optima Log Manager, when you save a file, there is an option to "Browse for other folders." What isn't obvious in this choice is that you can also browse other options for saving your file, namely the format to save it in. The default looks like this:
If you expand "Browse", you'll see this:
Note the lower right corner, where the file extension listbox now appears. If you save in ".event" format, you'll get an XML file as a result.
Labels: Log Manager, Optima, Tools, XML
Monday, November 19, 2012
libz.so.1: cannot open shared object file
Q: On a new linux system, trying to run gdb for the first time and get:
./powerpc-ose-gdb: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
When I run "locate libz.so.1" it is found in /usr/lib64, so what is the problem?
Labels: debugger, gdb, Linux, Optima
Monday, June 11, 2012
Cannot connect to Gateway and/or Optima from SFK
Q: Trying to connect to Optima 2.4 from a soft kernel running OSE5.4.x on a Window host. I'm getting errors from the OSE Gateway and indications that it can't connect . I have WinPCap running and Optima and the SFK seem to be working otherwise.
A: Whenever using WinPCap , it's very important that you disable hardware check
summing in your Windows network device driver. (Refer to the section "Network Access on Windows"in the OSE Core User's Guide
for more information on this.) Troubleshoot this on both ends of the connection, from both the host command line and also the SFK using the gateway command:
C:/OSE/OSE5.4.1_PPC/bin/win32/osegwcmd -s tcp://177.77.7.77:21768 -e100,100
replacing the IP "177..." with your the remote address in question. If one of the connection returns errors, then on your Windows system check in
Control panel -> system -> device manager -> (local area network) -> Properties......
and look for something called "checksum" or "checksum offload" or "Rx Checksum Offload" or similar. If it is set "on" , flip it to "off", restart the SFK and Optima and try again. Generally hardware checksumming only needs to be disabled if the soft kernel and the other software (e.g. Optima) that communicates with the soft kernel via TCP/IP is running on the same machine. If you run the two across different systems, then this most likely isn't the problem.
Labels: Optima, osegw, sfk, win32, winxp
Monday, December 05, 2011
Optima error: "Unsupported color depth"
Q: I was trying to start the System Profiler feature in the Optima environment, and got an error about "Unsupported color depth" instead of the functionality I needed. What causes this and how can I get around it?
A: The underlying cause isn't clear, but typically it's seen when trying to access Optima running on a server through a remote windowing client such as Citrix, X or NX. The error is seen when trying to open the CPU Profiler or System Profiler and has been seen on both Linux and Solaris servers and with all types of client hosts. There isn't a fix for it, other than perhaps trying a different remote client type. The error is never seen when accessing Optima on the local server, and that's really the only use fully supported.
A: The underlying cause isn't clear, but typically it's seen when trying to access Optima running on a server through a remote windowing client such as Citrix, X or NX. The error is seen when trying to open the CPU Profiler or System Profiler and has been seen on both Linux and Solaris servers and with all types of client hosts. There isn't a fix for it, other than perhaps trying a different remote client type. The error is never seen when accessing Optima on the local server, and that's really the only use fully supported.
Wednesday, September 14, 2011
gdb: unknown target exception
Q: I launched a debug configuration in Optima 2.4 and got this error:
gdb: unknown target exception 0xc0000135 at 0x7c9666c6
You can't do that without a process to debug.
I have followed everything in the Optima UG docs section 6 exactly as written. Why does gdb think there is isn't a program?
A: Sometimes when you create a new debug/run config there is weirdness with launching it right away. Close and restart the eclipse tool and it should launch correctly afterward.
Q: A similar problem with Optima 2.5 - looking in the debug configuration and supposed to see a special OSE tab to configure OSE kernel-awareness, but the tab isn't there.
A: Custom configuration tabs (such as the new custom tab in the Optima 2.5 release) might have the same problem - eclipse may get confused the first time you try to access it via the debug config, or when trying to access it within a project created in an earlier eclipse/Optima release. Try switching to a different workspace and restarting Optima. The OSE tab should now appear when entering the debug configuration menu.
gdb: unknown target exception 0xc0000135 at 0x7c9666c6
You can't do that without a process to debug.
I have followed everything in the Optima UG docs section 6 exactly as written. Why does gdb think there is isn't a program?
A: Sometimes when you create a new debug/run config there is weirdness with launching it right away. Close and restart the eclipse tool and it should launch correctly afterward.
Q: A similar problem with Optima 2.5 - looking in the debug configuration and supposed to see a special OSE tab to configure OSE kernel-awareness, but the tab isn't there.
A: Custom configuration tabs (such as the new custom tab in the Optima 2.5 release) might have the same problem - eclipse may get confused the first time you try to access it via the debug config, or when trying to access it within a project created in an earlier eclipse/Optima release. Try switching to a different workspace and restarting Optima. The OSE tab should now appear when entering the debug configuration menu.
Labels: debugger, Optima, optima2.4, optima2.5
Wednesday, July 07, 2010
FLEXlm error: UNSUPPORTED: "softose_win32"
Q: I am using a local FLEXlm license server, whose license expired recently. I just updated it with my new license file, and tried to start the soft kernel. But I get this error:
10:42:37 (osedaemon) UNSUPPORTED: "softose_win32" (PORT_AT_HOST_PLUS ) jmir@jenshostname (License server system does not support this feature. (-18,327:10054 ""))
Why am I getting this even though I updated the license file to the new one?
A: Most likely because the license manager was not restarted. Just copying the license file over in the correct place is not enough. You must stop the license manager and restart it (with lmgrd -z) so that it picks up the new license. Here is a console output of a successful license acquisition:
10:42:51 (lmgrd)
10:42:51 (lmgrd) pid 1740
10:42:51 (lmgrd) Done rereading
10:42:51 (lmgrd) FLEXnet Licensing (v11.4.100.0 build 50818 i86_n3) started on jenshostname (IBM PC) (7/7/2010)
10:42:51 (lmgrd) Copyright (c) 1988-2007 Macrovision Europe Ltd. and/or Macrovision Corporation. All Rights Reserved.
10:42:51 (lmgrd) US Patents 5,390,297 and 5,671,412.
10:42:51 (lmgrd) World Wide Web: http://www.macrovision.com
10:42:51 (lmgrd) License file(s): c:/flexlm/license.dat
10:42:51 (lmgrd) lmgrd tcp-port 744
10:42:51 (lmgrd) Starting vendor daemons ...
10:42:51 (lmgrd) Started osedaemon (pid 6108)
10:42:51 (osedaemon) FLEXnet Licensing version v11.4.100.0 build 50818 i86_n3
10:42:51 (osedaemon) Server started on jenshostname for: softose
10:42:51 (osedaemon) softose softose_win32 com.ose.cdt.launch
10:42:51 (osedaemon) com.ose.system.ui com.ose.ck.system.ui com.ose.pmd
10:42:51 (osedaemon) com.ose.event.ui com.ose.prof.ui com.zealcore.se.core
10:42:51 (osedaemon) EXTERNAL FILTERS are OFF
10:42:51 (lmgrd) osedaemon using TCP-port 1996
10:42:59 (osedaemon) TCP_NODELAY NOT enabled
10:42:59 (osedaemon) OUT: "softose_win32" jmir@jenshostname
Q: I did that, but i'm still getting the same error.
A: You should also check that your settings in the license file for OSEDAEMON and SERVER are up-to-date as well. Sometimes admins copy a new license file over but forget to fix these. When we ship them, they have default settings and each time you get a new one you should customize them to your server. Example of a correct configuration of a license.dat file:
SERVER jenshostname 001641e67507 744
DAEMON osedaemon c:/OSE/OSE5.4.1_PPC/bin/win32/osedaemon.exe
USE_SERVER
10:42:37 (osedaemon) UNSUPPORTED: "softose_win32" (PORT_AT_HOST_PLUS ) jmir@jenshostname (License server system does not support this feature. (-18,327:10054 ""))
Why am I getting this even though I updated the license file to the new one?
A: Most likely because the license manager was not restarted. Just copying the license file over in the correct place is not enough. You must stop the license manager and restart it (with lmgrd -z) so that it picks up the new license. Here is a console output of a successful license acquisition:
10:42:51 (lmgrd)
10:42:51 (lmgrd) pid 1740
10:42:51 (lmgrd) Done rereading
10:42:51 (lmgrd) FLEXnet Licensing (v11.4.100.0 build 50818 i86_n3) started on jenshostname (IBM PC) (7/7/2010)
10:42:51 (lmgrd) Copyright (c) 1988-2007 Macrovision Europe Ltd. and/or Macrovision Corporation. All Rights Reserved.
10:42:51 (lmgrd) US Patents 5,390,297 and 5,671,412.
10:42:51 (lmgrd) World Wide Web: http://www.macrovision.com
10:42:51 (lmgrd) License file(s): c:/flexlm/license.dat
10:42:51 (lmgrd) lmgrd tcp-port 744
10:42:51 (lmgrd) Starting vendor daemons ...
10:42:51 (lmgrd) Started osedaemon (pid 6108)
10:42:51 (osedaemon) FLEXnet Licensing version v11.4.100.0 build 50818 i86_n3
10:42:51 (osedaemon) Server started on jenshostname for: softose
10:42:51 (osedaemon) softose softose_win32 com.ose.cdt.launch
10:42:51 (osedaemon) com.ose.system.ui com.ose.ck.system.ui com.ose.pmd
10:42:51 (osedaemon) com.ose.event.ui com.ose.prof.ui com.zealcore.se.core
10:42:51 (osedaemon) EXTERNAL FILTERS are OFF
10:42:51 (lmgrd) osedaemon using TCP-port 1996
10:42:59 (osedaemon) TCP_NODELAY NOT enabled
10:42:59 (osedaemon) OUT: "softose_win32" jmir@jenshostname
Q: I did that, but i'm still getting the same error.
A: You should also check that your settings in the license file for OSEDAEMON and SERVER are up-to-date as well. Sometimes admins copy a new license file over but forget to fix these. When we ship them, they have default settings and each time you get a new one you should customize them to your server. Example of a correct configuration of a license.dat file:
SERVER jenshostname 001641e67507 744
DAEMON osedaemon c:/OSE/OSE5.4.1_PPC/bin/win32/osedaemon.exe
USE_SERVER
Labels: flexlm, Optima, OSE4, OSE5, sfk
Wednesday, April 21, 2010
Optima debugger in softkernel halts before starting
Q: I am trying to get the debugger in the soft kernel for OSE5.4.1 going on Optima 2.x. I've followed the instructions in the Optima User Guide to the letter, and the soft kernel builds and runs, but when I try to debug it in Optima I get no further than this error:
Can't find a source file at "/cygdrive/c/OSE/ose5.4.1_ppc/src/osemain.c"
Locate the file or edit the source lookup path to include its location.
I thought I did everything right. Why is Optima complaining now?
Can't find a source file at "/cygdrive/c/OSE/ose5.4.1_ppc/src/osemain.c"
Locate the file or edit the source lookup path to include its location.
I thought I did everything right. Why is Optima complaining now?
A: The docs for Optima need a small amount of updating, mainly to account for the fact that they were written before the big split-off of the BSP products from the "mainline" OSE stream. Beginning in OSE5.3, BSPs were no longer delivered with the main OSE5 delivery and were purchased - and delivered - separately. Our BSP delivery docs advise users to install a directory heirarchy that co-locates the BSP at the save level with the OSE5 directory, rather than underneath it.
And now, the Optima tool runs in a completely different area of the product - within the BSP delivery, e.g. under C:/BSP_SFK_OSE5.4.1/refsys/rtose/sfk-win32. The config doc wasn't updated for this subtlety, which requires for Windows users adding a Path Mapping (under Eclipse C/C++ view in Debug -> Debug Configurations...). Hence the Optima tool's failure to find the source paths for osemain.c, which is located under the OSE5 mainline directory under C:/OSE/OSE5.4.1_PPC/src .
The simplest solution is to follow the button titled "Locate File..." as shown above in the pic. Using the standard windows file dialogue, just add the full path to the osemain.c in OSE5.4.1_PPC mainline area. You'll also have to add this for hello.c if you continue following the doc example (when it tells you to step over the hello.c breakpoint). This will automagically add the desired Path Mapping entries in your Debug Configuration for this debug run, where it can be found later under the Source tab.
Labels: debugger, gdb, Optima, OSE5, OSE5.3, OSE5.4
Friday, March 26, 2010
Install errors on non-supported Linux distros
Q: I'm trying to install OSE5.x/Optima products from CD on a Linux system. I got the following error during installation looking for a missing lib:
[root@localhost OSE5.4.2_PPC]# ./install.sh Welcome to the Enea Installation Program!
Creating the temporary directory...
Unzipping the Java Runtime Environment...
Launching the Enea Installation Program on display :0.0...
Exception in thread "main" java.lang.UnsatisfiedLinkError:
/tmp/ose_J6UME4/jre_linux/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at sun.security.action.LoadLibraryAction.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.awt.NativeLibLoader.loadLibraries(Unknown Source)
at sun.awt.DebugHelper.(Unknown Source)
at java.awt.Component.(Unknown Source) Removing the temporary directory...
A: This error only occurs for the Linux distributions that are not officially support for OSE and Optima. Currently, the officially supported Linux distributions are:
* Suse Linux Enterprise Server 10
* Suse Linux Enterprise Desktop 10
The X11 shared library libXp.so.6 is required by JRE (Java RuntimeEnvironment) 1.4.2 used by the Enea installation program. If that library is missing you can try one of the three following things:
1. Make sure libXp.so.6 is installed.
2. If you have a newer version of libXp.so, try to create a link in that directory that is called libXp.so.6 and points to the newer version of libXp.so.
3. Use another JRE (1.4.2 or newer) that is installed on the Linux machine when starting the Enea installation program, e.g. "install.sh -j /usr/local/bin/java".
Option 3 is generally the most effective.
[root@localhost OSE5.4.2_PPC]# ./install.sh Welcome to the Enea Installation Program!
Creating the temporary directory...
Unzipping the Java Runtime Environment...
Launching the Enea Installation Program on display :0.0...
Exception in thread "main" java.lang.UnsatisfiedLinkError:
/tmp/ose_J6UME4/jre_linux/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at sun.security.action.LoadLibraryAction.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.awt.NativeLibLoader.loadLibraries(Unknown Source)
at sun.awt.DebugHelper.
at java.awt.Component.
A: This error only occurs for the Linux distributions that are not officially support for OSE and Optima. Currently, the officially supported Linux distributions are:
* Suse Linux Enterprise Server 10
* Suse Linux Enterprise Desktop 10
The X11 shared library libXp.so.6 is required by JRE (Java RuntimeEnvironment) 1.4.2 used by the Enea installation program. If that library is missing you can try one of the three following things:
1. Make sure libXp.so.6 is installed.
2. If you have a newer version of libXp.so, try to create a link in that directory that is called libXp.so.6 and points to the newer version of libXp.so.
3. Use another JRE (1.4.2 or newer) that is installed on the Linux machine when starting the Enea installation program, e.g. "install.sh -j /usr/local/bin/java".
Option 3 is generally the most effective.
Labels: installation, Linux, Optima, OSE5
Tuesday, September 02, 2008
Startup errors in Optima 1.5
Q: I'm firing up Optima 1.5 for the first time and getting this error:
Could not check out a FLEXlm license for OSE Events plugin (com.ose.event.ui)
Reason:
No such feature exists(-5,116)
Also a similar error follows for OSE Profiler plugin (com.ose.prof.ui). What gives?
A: Like most releases, the Optima tools have their own license per release. If you forgot to replace your Optima 1.4 (a.k.a. Tools 1.4) license with the 1.5 version, then you'll get errors related to missing license keys for these new features for 1.5. The errors are harmless if you don't need those features, and Optima will proceed to start without them.
Q: Okay, now I've done that and when I restart Optima 1.5 again, it's complaining that I need to select a new workspace. What is wrong now?
A: There is a minor "quirk" with this release of Eclipse that does not fully shut down the Eclipse process in Windows XP when you back out of an Eclipse launch, like you may have done previously if you canceled it (after seeing an error, for instance). Go to the Windows Task Manager and check if the Eclipse process is still up. If so, just kill it there and start up again.
Could not check out a FLEXlm license for OSE Events plugin (com.ose.event.ui)
Reason:
No such feature exists(-5,116)
Also a similar error follows for OSE Profiler plugin (com.ose.prof.ui). What gives?
A: Like most releases, the Optima tools have their own license per release. If you forgot to replace your Optima 1.4 (a.k.a. Tools 1.4) license with the 1.5 version, then you'll get errors related to missing license keys for these new features for 1.5. The errors are harmless if you don't need those features, and Optima will proceed to start without them.
Q: Okay, now I've done that and when I restart Optima 1.5 again, it's complaining that I need to select a new workspace. What is wrong now?
A: There is a minor "quirk" with this release of Eclipse that does not fully shut down the Eclipse process in Windows XP when you back out of an Eclipse launch, like you may have done previously if you canceled it (after seeing an error, for instance). Go to the Windows Task Manager and check if the Eclipse process is still up. If so, just kill it there and start up again.
Wednesday, March 28, 2007
Tips for March 2007
Q: I'm using Optima Tools (Eclipse) to debug an Interrupt Service Routine (ISR). I can step up close to the ISR but when I try to step into or run a breakpoint into it, my system crashes. What is wrong?
A: Unfortunately, stepping through ISRs is not supported with our toolset. You can try it without Eclipse and see if that works, but it might depend on the target. The powerpc-ose-gdb can be used on the command line to accomplish this - tedious, but works.
Q: Okay... I tried using powerpc-ose-gdb on the cygwin command line with the latest Optima Tools release of 1.3 (gdb 6.3 for OSE), and got this error:
$ cd OSETOOLS1.3/gdb_win32_powerpc_6.3/bin
$ ./powerpc-ose-gdb
241 [main] ? (2472) c:\OSE\OSETOOLS1.3\gdb_win32_powerpc_6.3\bin\powerpc-ose
-gdb.exe: *** fatal error - proc magic mismatch detected - 0x8B3C/0xC87757A7.
This problem is probably due to using incompatible versions of the cygwin DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version. The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution. Rebooting is also suggested if you
are unable to find another cygwin DLL.
A: Oops, you are using Tools 1.3 version of gdb with the older version of cygwin. We shipped cygwin 1.3 with OSE5.1 and OSE5.1.1, but upgraded to cygwin 1.5 with OSE5.2 . So match your cygwin version to your OSE release before attempting this. Otherwise nothing works, including builds under refsys.
Q: Right, I'm running Tools 1.2 release of powerpc-ose-gdb. What's the command sequence to find out if the connection to the target is okay and to connect to it?
A: cd OSETOOLS1.2/gdb_win32_powerpc_5.2.1/bin
./powerpc-ose-gdb
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-cygwin --target=powerpc-ose".
(gdb) info ose targets
Hostname Port Id
192.168.3.201 1024 0
Above indicates you're good to go. After first starting gdb, you might have to wait 10-20 secs for this - hit return every 10-20 secs until you see the target info appear. Then you can "target ose 192.168.3.201:1024" followed by "info ose processes" to verify everything is cool with the target.
Q: Wait a minute, I'm running Tools 1.3 version of gdb instead and that doesn't work! I get:
Undefined info ose command: "targets". Try "help info ose".
A: For reasons unknown, this command changed in this tools release. Try "info ose gates" instead, then rinse, cycle, repeat as above. Sorry this isn't better documented.
Q: I was able to see my OSE4.6 target with the Tools 1.2 gdb version, but my Tools 1.3 version doesn't see it. Why?
A: Appears to be a known problem with the newer Tools release. Stick with OSE5 when using Tools 1.3 release version of powerpc-ose-gdb.
A: Unfortunately, stepping through ISRs is not supported with our toolset. You can try it without Eclipse and see if that works, but it might depend on the target. The powerpc-ose-gdb can be used on the command line to accomplish this - tedious, but works.
Q: Okay... I tried using powerpc-ose-gdb on the cygwin command line with the latest Optima Tools release of 1.3 (gdb 6.3 for OSE), and got this error:
$ cd OSETOOLS1.3/gdb_win32_powerpc_6.3/bin
$ ./powerpc-ose-gdb
241 [main] ? (2472) c:\OSE\OSETOOLS1.3\gdb_win32_powerpc_6.3\bin\powerpc-ose
-gdb.exe: *** fatal error - proc magic mismatch detected - 0x8B3C/0xC87757A7.
This problem is probably due to using incompatible versions of the cygwin DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version. The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution. Rebooting is also suggested if you
are unable to find another cygwin DLL.
A: Oops, you are using Tools 1.3 version of gdb with the older version of cygwin. We shipped cygwin 1.3 with OSE5.1 and OSE5.1.1, but upgraded to cygwin 1.5 with OSE5.2 . So match your cygwin version to your OSE release before attempting this. Otherwise nothing works, including builds under refsys.
Q: Right, I'm running Tools 1.2 release of powerpc-ose-gdb. What's the command sequence to find out if the connection to the target is okay and to connect to it?
A: cd OSETOOLS1.2/gdb_win32_powerpc_5.2.1/bin
./powerpc-ose-gdb
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-cygwin --target=powerpc-ose".
(gdb) info ose targets
Hostname Port Id
192.168.3.201 1024 0
Above indicates you're good to go. After first starting gdb, you might have to wait 10-20 secs for this - hit return every 10-20 secs until you see the target info appear. Then you can "target ose 192.168.3.201:1024" followed by "info ose processes" to verify everything is cool with the target.
Q: Wait a minute, I'm running Tools 1.3 version of gdb instead and that doesn't work! I get:
Undefined info ose command: "targets". Try "help info ose".
A: For reasons unknown, this command changed in this tools release. Try "info ose gates" instead, then rinse, cycle, repeat as above. Sorry this isn't better documented.
Q: I was able to see my OSE4.6 target with the Tools 1.2 gdb version, but my Tools 1.3 version doesn't see it. Why?
A: Appears to be a known problem with the newer Tools release. Stick with OSE5 when using Tools 1.3 release version of powerpc-ose-gdb.
free invisible web counter
