Known Issues

There are a few known issues with the PTP Cell/B.E. These issues are as follows:

Java API

There is a known bug with the cell simulator's capacity to use the Java API along with the simulator GUI window. In order to enable the use of the Java API with the simulator, you must set the option USE_JAVA_API to true: "USE_JAVA_API=true". This parameter can be found in the file parameters.properties which is located at: eclipse/plugins/org.eclipse.ptp.cell.simulator/org/eclipse/ptp/cell/simulator/conf. If the USE_JAVA_API option is set to true, then the simulator GUI window cannot be used.

Broken GDBServer Connection

If you are debugging a Cell application remotely using gdbserver and the connection to the gdbserver is broken, then the PTP Cell/B.E will try to reconnect automatically. However, this will not be successful even though the gdbserver is still running on the target machine.

Moreover, if you stop this debug session and try to start a new one, the PTP Cell/B.E will issue an error because the gdbserver is still occupying the previous configure port on the target machine and the PTP Cell/B.E will not be able to launch another instance of gdbserver in the same port unless the debug launcher configuration is modified.

The workaround for this is to kill the gdbserver application on the target machine before launching another debug session again.

Remote Launch Directory Needs to be Writable for All Users

The Cell Target Application launcher automatically creates a remote directory for launching the application. By default, this directory is given by following macros: ${system_workspace}/${user_workspace}/${project_name}/${timestamp}. If you are sharing the remote (cell be) machine, then you must be sure that all users can write to the directory given by ${system_workspace}.

The first user that connects to the machine will create ${system_workspace}. The next users will create their directories inside ${system_workspace}. However, if ${system_workspace} was not created will full write privileges, then the next users will not be able to launch.

Proper Configuration for Localhost

While using the Cell Target Application launcher and Local Cell Simulator, the PTP Cell/B.E calls Inet4Address.getLocalHost() for several times. In some cases, this method may fail if your machine is not configured correctly. This failure could result in the PTP Cell/B.E refusing to create new simulator environments and/or causing failures with the Cell Target Application launcher.

If this problem is encountered, check the /etc/hosts file and ensure that the following line is present:

  127.0.0.1 localhost mymachine
where "mymachine" is the name of the machine as given by the environment variable $HOSTNAME.

Valid MAC Addresses for Local Cell Simulator

The local simulator configuration window allows you to choose your own MAC address. If you decide to specify your own MAC address, the following rules apply: