Eclipse

Important

This documentation is deprecated and it’s not recommended to be used on new projects.

Visit https://mi-v-ecosystem.github.io/SoftConsole-Documentation/ instead.

Running SoftConsole from command line

If for some reason the SoftConsole needs to be executed from command line then the appropriate launcher scripts need to be used:

• softconsole.sh (Linux OS)

• softconsole.cmd (Windows OS)

Warning

Running eclipse.exe binary directly will not work and cause many issues as the launcher scripts do setup required paths and environment variables for the SoftConsole and Renode to function properly.

The Linux launcher depends on a bash shell, using an alternative shell might cause some paths to be misconfigured and then all depending tools to misbehave.

Glitches, unstable UI and cosmetic issues on Linux

On the Linux SoftConsole 6.1 (and newer) the GTK2 support is removed and it might cause incorrectly rendered UI elements in some cases and on some distributions even unstable UI. Distributions such as RHEL 6.x and CentOS 6.x which provide only GTK2 are not supported anymore. These distributions do not provide GTK3, unless the user is allowed and able to compile and install all dependencies and whole GTK3 subsystem on their RHEL 6.x / CentOS 6.x machines, then they will not be able to use SoftConsole 6.1 without issues. Second workaround is not trivial as well which involves installing Docker 1.7.1 (the highest version which can run on such legacy kernel, unless user wants to recompile the Docker from sources). And installing SoftConsole inside docker container (Debian9 was tested), it is possible to tunnel the X11 application and share the host’s FlashPro5. Running a VM with newer OS can be used only if Renode is targeted, but it will not allow user to interact with real HW as the FlashPro5 driver will not work inside the VM. An upgrade of the OS should be the easiest way to resolve this issue.

Tab with an error message is opened before breaking into the main function

The following error can be observed (with different addresses):

Break at address "0x1000" with no debug information available, or outside of program code.

Before loading the elf to the target it might be executing something which is not resolved. Sometimes it is possible to resolve the issue by specifying the sysroot, but this is not reliable as the target might be executing the previous project. Or in case of Renode no project at all.

http://visualgdb.com/gdbreference/commands/set_sysroot

When the following checkbox:

Is checked then error message/tab can be suppressed.