insight/317: Target selection problems

[hepler at vlsi-concepts dot com]

>Number:         317
>Category:       insight
>Synopsis:       Target selection problems
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jul 05 04:23:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator:     Ed Hepler
>Release:        6.6
>Organization:
>Environment:
Cygwin
>Description:
I have added a new target (custom jtag interface to a mips equivalent synthesizable core) to GDB.   
 
I have this working with GDB (using my own, modified version of remote-mips.c) in normal, text mode.  To get into the appropriate target mode, I use the command:
target vr2000
This invokes code in my modified remote-mips.c to use the
jtag interface, etc.

When I run insight, I can see that "_initialize_remote_mips" is executed and the Tk Source Window pops up.

If I select the File -> Target Settings menu item, an error occurs and I get the following stack trace:

can't read "PREFS_state(gdb/load/default-portname value)". no such element in array
  while executing
"return $PREFS_state([list $name_value])"
  (procedure "PREFS_cmd_get" line 3)
  invoked from within
"PREFS_cmd_get gdb/load/default-portname"
  ("eval" body line 1)
  invoked from within
"eval PREFS_cmd_$dispatch $args"
  (procedure "pref" line 6)
  invoked from within
"pref get gdb/load/default-portname"
  ("default" arm line 8)
  invoked from within
"switch -regexp -- $gdb_target_name {
  sim|ice {
    set targ $gdb_target_name
    set targ_opts [pref getd gdb/load/${gdb_target_name}-opts]"
  ...
  (procedure "set_target_name" line 28)
  invoked from within
"set_target_name"
  (menu invoke)errorCode is NONE

I suspect that I need to add some code to targetselection.itb to add the appropriate "vr2000" selection, but I was surprised by the error (before
I changed anything).    I looked through targetselection.itb and didn't see anywhere that the
array item gdb/load/default-portname was set (although
I did see gdb/load/default-port being set).

I also tried creating an initialization file (.gdbinit) that contains the command:
target vr2000
and I see evidence that the target is set when executing
gdb (some jtag commands are sent), but I don't see this
when executing insight.

To add my new target, is there anything else that needs to be done beyond setting the appropriate gdb_target() array items?

Is there any documentation on what must be modified within insight to add a new target? 

Thanks... 
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: