Performing source-level debug with hex format, Motorola S format, or binary data format files

2.5.2.4 Performing source-level debug with hex format, Motorola S format, or binary data format files

Even when a file in hex format (*.hex), Motorola S format (*.mot), or binary data format (*.bin) is specified to be the subject file to download, it is possible to do source-level debug by downloading symbol information for the load module file from which the subject file was created, along with the subject file that you download.

In this case, follow the procedure described below as you fill in the Download Files dialog box.

(1)	Clicking the [Add] button

When you click the [Add] button, a blank item ("-") is displayed on the last line in the [Download file list] area.

(2)	Setting the properties of a load module file

In the [Download file property] area, specify for each item as shown below.

File	Specify a load module file from which the file in hex format (.hex), Motorola S format (.mot), or binary data format (*.bin) that you want to download was created. Enter directly from the keyboard, or specify in the Select Download File dialog box that is opened by clicking the […] button.
File type	Specify [Load module file] (default).
Download object	Specify [No].
Download symbol information	Specify [Yes] (default).
Specify the PIC/PID offset	Specify [No] (default)Note.

Note

For files in hex format, Motorola S format, or binary data format, be aware that the destination to which they are downloaded cannot be discriminated between the PIC and PID areas. If you specify PIC/PID offsets in a load module file, the result will be that the specified offsets do not agree with the debug function and the file cannot be debugged.

(3)	Clicking the [OK] button

Settings you've made in this dialog box are enabled, with the specified load module file added as a download file (Only the symbol information included in the load module file becomes the subject to download.).