Difference between revisions of "Debugging softMC Firmware Linux"
m (→FWCONFIG) |
(→FWCONFIG) |
||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 7: | Line 7: | ||
COM1 of softMC is reserved for Linux shell. | COM1 of softMC is reserved for Linux shell. | ||
| − | Shell is used for editing FWCONFIG and IO.DAT or for solving problems such as:<br /> | + | Shell is used for editing [[FWCONFIG|FWCONFIG]] and IO.DAT or for solving problems such as:<br /> |
*softMC does not boot<br /> | *softMC does not boot<br /> | ||
*softMC does not get IP address<br /> | *softMC does not get IP address<br /> | ||
| Line 22: | Line 22: | ||
== File Locations == | == File Locations == | ||
| − | '''FWCONFIG<br | + | '''[[FWCONFIG|FWCONFIG]]'''<br> |
/FFS0/<br /> | /FFS0/<br /> | ||
'''Programs and Libraries:<br />''' | '''Programs and Libraries:<br />''' | ||
| − | /FFS0/ | + | /FFS0/SSMC/<br /> |
'''Linux Log files'''<br /> | '''Linux Log files'''<br /> | ||
/var/log/<br /> | /var/log/<br /> | ||
| Line 58: | Line 58: | ||
== FWCONFIG == | == FWCONFIG == | ||
| − | FWCONFIG | + | See [[FWCONFIG | FWCONFIG]] |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | ===== TCP/IP keepalive timeouts ===== | |
| − | + | Refer to: | |
| − | ''' | + | *'''[[Socket_keep-alive_timeouts|Socket_keep-alive_timeouts]]''' |
| − | |||
| − | |||
== Troubleshooting a Software Crash == | == Troubleshooting a Software Crash == | ||
Latest revision as of 10:05, 26 October 2017
Contents
Introduction
In some situations, a controller is no longer accessible with terminal of ControlStudio. This occurs when the controller has encountered a serious problem and tasks are suspended or the network stack of the operating system is corrupted. For the core-development it is necessary to collect data when such a situation occurs to collect data and analyze the root-cause to be able to fix/correct it.
This entry presents the controller file system and some useful commands for debugging.
Access to Linux Shell
COM1 of softMC is reserved for Linux shell.
Shell is used for editing FWCONFIG and IO.DAT or for solving problems such as:
- softMC does not boot
- softMC does not get IP address
- File system has overflow of log files or core dumps that need to be deleted manually.
- Autostart (CONFIG.PRG or AUTOEXEC.PRG) makes softMC unresponsive
Important: COM1 should not be used by applications
The shell has input and output by default on COM1.
Automatic login: user name mc, password mc
Also possible to login with ssh or telnet: user mc, password mc
File Locations
FWCONFIG
/FFS0/
Programs and Libraries:
/FFS0/SSMC/
Linux Log files
/var/log/
RAM disk
/RAM/
 | NOTE |
| Access to FWCONFIG file is allowed only under PRIVILEGELEVEL=1. |
Useful Commands
- /sbin/ifconfig - gives IP information
- vi - text editor
- cp - copy files
- rm - delete files
- ls - list directory
- threads - lists linux threads
- df - free space on disk. For example "df /FFS0/ -h" will show free space on the flash disk
- du - space used by directory/files. For example "du /FFS0/ -h" will show usage of softMC libraries and programs
Application Autostart
No local I/O or dedicated DIP-switch for automatic start of application.
DIP-Switch is emulated. Firmware reads DIP-Switch value from file /FFS0/SSMC/IO.DAT
DIP=0x0
INP=0x00
Bit #6 of DIP-Switch is responsible for autostart of application.
IO.DAT is created automatically if it does not exist, values are zeros.
- IO.DAT can be edited either via softMC user interface or directly from Linux shell:
- vi /FFS0/SSMC/IO.DAT
- vi /FFS0/SSMC/IO.DAT
- Simplest way to disable autostart would be deletion of IO.DAT
- rm /FFS0/SSMC/IO.DAT
FWCONFIG
See FWCONFIG
TCP/IP keepalive timeouts
Refer to:
Troubleshooting a Software Crash
In case of software crash operating system creates complete snapshot of crashed process. Firmware saves snapshots to directory /cores.
These snapshots (or "core" files) contain important information and may help to improve software quality.
It is recommended to check contents of /cores upload files to support@servotronix.com and erase contents of /cores.
softMC can be accessed with any SFTP software, such as WinSCP or Bitvise SSH client.
User name and password are given at the top of this page.