Code Debugging Method Sample Clauses

Code Debugging Method. The way Xxxx enters the debug status is to choose the menu ‖Debug‖ ―Start/Stop Debug Session‖ or click the icon on the tool bar. If the Senselock ELsoftware simulator is properly installed and configured, when Xxxx enters the debugging status, there will be the following data input window: There are two parts of data input window. The upper half manages the Senselock ELsimulation file system while the lower half sets the data to be transported to Senselock ELcommunication buffer. Senselock ELsimulator simulates Senselock ELfile system using the file stored in the current project directory called ―vFileSys.dat‖. Click the ―New‖ button in the data input window to create a new simulation file system. It is not necessary to create a simulation file system for Senselock ELapplications that do not call the file system service. Click the ―Modify‖ button in the data input window to modify the simulation file system. In the simulation file system, the file system takes the directory whose ID is ―3F00‖ (namely, MF of SenseLock EL) as a root node and display the information by a tree structure. Designed only for code debugging, the simulation file system supports only one-level directory structure. No sub-directory can be created. Choose ―New File‖ from the right-button menu of the directory node to create a new file in the current directory. The simulation file system supports four types of files: executable files (EXF), data files (DAT), RSA public key files and private key files. For the public key file type, the file shall not be less than 136 bytes while for the private key file type, the file shall not be less than 330 bytes. The internal readable/writable files shall be marked with ―R/W‖ attributes. Double click or choose ―Edit‖ from the right-button menu of any file node to edit its contents as shown in Figure 5-10. You can modify the hexadecimal data directly when editing a file or choose to import data from a disk file or save the data to a disk file. Sometimes executable files need to operate themselves. For example, the internal function _create() can be designed to acquire the information of the current executable file. As the current executable file is not saved to the simulation file system in a real sense, but only debugged in the Xxxx compilation environment, this kind of operation will fail. The solution is to mark an executable file as ―default file‖ in the simulation file system (set this by right clicking the file node). In this way, when the ex...