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
Launching sfk-linux aborts with "Resetting soft kernel" error
Q: Launching an sfk-linux for the first time on Ubuntu, and getting this error:
Welcome to RTOSE; an OSE reference system.
Type 'help' for a list of available commands.rtose@softlin> Resetting soft kernel!
Aborted
Type 'help' for a list of available commands.rtose@softlin> Resetting soft kernel!
Aborted
A: There are several causes, but the first thing to check is ramlog.mem. You may find, especially in the case of using VMs, that the surfer aborts ungracefully:
SEH: Information about current process "ose_surfer"
SEH: Pid 0x0001003c bid 0x00010008 progpid 0x00000000
SEH: File & line: surfer.c 7072
SEH: Extra text: "ose_surfer error: bind failed (errno: 13 file: ../../modules/surfer/src/surfer.c line:7723)"
SEH: Pid 0x0001003c bid 0x00010008 progpid 0x00000000
SEH: File & line: surfer.c 7072
SEH: Extra text: "ose_surfer error: bind failed (errno: 13 file: ../../modules/surfer/src/surfer.c line:7723)"
Just comment out the "surfer" references in rtose5.conf to get around this for now; you can also remove the module manually from rtose.mk with an "override -= surfer" entry. Then "make clean cleanall cleanobj" and rebuild.
The next problem is that you're probably not user "root." There is a long-standing anomoly that the Linux soft kernel requires the user to be running as "root". If you're not logged in as root, e.g. you're using Ubuntu or other quick-use Linux distros that don't set up a root account, run the soft kernel with sudo:
jmir@ubuntu:~/OSE/BSP_SFK_OSE5.5.1/refsys/rtose/sfk-linux$ sudo ./obj/rtose_debug/rtose -c rtose5.conf
This should be enough to get your soft kernel going.
RTOSE(debug) for sfk-1 built 130618 12:06 by jmir
Copyright 2003-2010 Enea Embedded Technology AB. All rights reserved.
Copyright 2003-2010 Enea Embedded Technology AB. All rights reserved.
Changing directory to /host//home/jmir/OSE/BSP_SFK_OSE5.5.1/refsys/rtose/sfk-linux
Welcome to RTOSE; an OSE reference system.
Type 'help' for a list of available commands.
rtose@softlin
Type 'help' for a list of available commands.
rtose@softlin
Labels: Linux, rtose, sfk-linux, surfer
free invisible web counter
