A: No. The open-source version of X2C runs with Scilab. If you want to use X2C with Matlab®, you need to get an X2C license.
A: You can download Scilab here.
A: Yes, since nightly build v639, X2C code generation works under Linux. However, some things have to be considered:
ls -l /dev/ttyACM0
gives the ouput
crw-rw---- 1 root dialout 166, 0 Feb 11 08:56 /dev/ttyACM0
With this information, a new device can be created:
sudo mknod /dev/ttyUSB0 c 166 0 sudo chown root:dialout /dev/ttyUSB0 sudo chmod 660 /dev/ttyUSB0
This device should be recognizable by the Communicator.
A: The control scheme is set up in Scilab’s Xcos by dragging the control blocks into the current diagram.
A: You can create the compilation ready c-code representing your control scheme by clicking the create code button in the Communicator GUI.
A: The easiest and fastest way is to use the Communicator GUI. It provides a convenient way to set the communication parameters and connect to the target.
A: To get a connection with the Communicator, an X2C application has to be running on the target. So the target has to be programmed prior to any connection attempts. Also the Interface and Port in the “Setup”-tab have to be selected according to the target’s setup.
A: The new application has to be downloaded with the built-in programming feature of the target’s IDE. With X2C Pro and its bootloader support a new application can be downloaded via the Communicator GUI.
A: Please check the list of supported targets. If your device is not among the listed targets but is a member of either the C28X, ARMV7 or DSPIC series, you can use a generic processor type.
A: Unfortunately, simulation out of the box doesn’t work in Linux yet. However, simulation is possible if these steps are followed: