Embedded IDE Link™ MU

info - Information about processor

Syntax

iid = info(id)

Description

iid = info(id) returns property names and property values associated with the debugger and processor referred to by id. iid is a structure containing the information elements and values shown in the following table:

Structure Element	Data Type	Description
`iid.CurBrkPt`	String	When the debugger is stopped at a breakpoint, the field reports the index of the breakpoint. Otherwise, this value is-1.
`iid.File`	String	Name of the current file shown in the debugger source pane.
`iid.Line`	Integer	Line number of the cursor position in the file in the debugger source pane. If no file is open in the source pane, this value is -1
`iid.MultiDir`	String	Full path to your Green Hills^® MULTI^® installation the root directory). For example 'C:\ghs5_01'
`iid.PID`	Double	Process ID from the debug server in MULTI.
`iid.Procedure`	String	Current procedure in the debugger source pane.
`iid.Process`	Double	Program number, defined by MULTI, of the current program.
`iid.Remote`	String	Status of the remote connection, either `Connected` or `Not connected`.
`iid.Selection`	String	The string highlighted in the debugger. If there is no string highlighted, this value is '`null`'.
`iid.State`	String	State of the loaded program. The possible reported states appear in the following list: `About to resume` `Dying` `Just executed` `Just forked` `No child` `Running` `Stopped` `Zombied` For details about the states and their definitions, refer to your Green Hills MULTI debugger documentation.
`iid.Target`	Double	Unique identifier the indicates the processor family and variant.
`iid.TargetOS`	Double	Real-time operating system on the processor if one exists. Provides both the major and minor revision information.
`iid.TargetSeries`	Double	Whether the processor belongs to a series of processors. For details about the processor series, refer to your Green Hills MULTI debugger documentation.

info returns valid information when the IDE debugger is connected to processor hardware or a simulator.

Using info with multiprocessor boards

Method info works with targets that have more than one processor by returning the information for each processor accessed by the id object you created with ghsmulti. The structure of information returned is identical to the single processor case, for every included processor.

Examples

On a PC with a simulator configured in MULTI, info returns the following configuration information after stopping a running simulation:

iid=info(test_obj1)

iid = 

  CurBrkPt: 0
  File: '...\Compute_Sum_and_Diff_multilink\Compute_Sum_and_Diff_main.c'
  Line: 3
  MultiDir: 'C:\ghs5_01'
  PID: 2380
  Procedure: 'main'
  Process: 0
  Remote: 'Connected'
  Selection: '(null)'
  State: 'Stopped'
  Target: 4325392
  TargetOS: [2x1 double]
  TargetSeries: 3

When you create a new ghsmulti object, the response from info looks like the following before you load a project.

iid=info(test_obj2)

test_obj2 = 

        CurBrkPt: []
            File: []
            Line: []
        MultiDir: []
             PID: []
       Procedure: []
         Process: []
          Remote: []
       Selection: []
           State: []
          Target: []
        TargetOS: []
    TargetSeries: []

info - Information about processor

Syntax

Description

Using info with multiprocessor boards

Examples

See Also