Segmentation Fault in the PTP127A100 example program

[Authorless]

By compiling the sample program for reading and writing analog and digital IOs in your virtual machine,
to run on slimline ARM9 program, the eSetSystemReady (eTRUE) instruction generates a Segmentation Fault.

I thought it was due to the fact that I was testing with only the CPU connected to test the digital IOs present on it. I connected a PCB124B100 module nothing has changed.

[Sergio Bertana]

The module ARM9 Linux CPU comes with a test program launched at startup. Connecting to telnet on the 23 port (with Toolly or PuTTY) and typing the command ps we will have a list of currently running processes here is an excerpt:

root @SlimLine: / # ps
PID USER COMMAND
    1 root init [2]
    ... ...
  1202 root ./ELDevDiscovererD
 1205 root ./ELSLLinuxTester

As you can see, the 1202 process is the program ELDevDiscovererD check for the presence of the module on the network, while process 1205 is the program ELSLLinuxTester that allows you to test the operation of the module. This program uses the library ElSLLinux (The same one included in the example program you use). The simultaneous use by two processes of this library is not possible because the resources (for example the expansion bus) cannot be shared. So to eliminate the problem you need to terminate the ELSLLinuxTester program, use the command kill 1205 (Of course if the PID is like 1205 in my example).

[Sergio Bertana]

The ELSLLinuxTester it is executed by default at startup (See shell file /data/ELStarter.sh). When you have created your application you will have to replace the name of your program in the file ELStarter.sh to allow automatic execution at startup.

This program is listening on port 1000 and allows you to manage a series of tests on the module. By connecting with a telnet (Example Toolly) to the port it is possible to log into the program (Username and Password: admin) and typing ? it is possible to have a list of possible commands (See screenshot).

[Author]

Post