How to retrieve the variable which is defined in the SOC Encounter configure file ?

It looks like the variable defined in the .conf file are only available locally (ie, within the .conf file). If you want to be able to refer to variables set in the .conf file you could defined them as globals:

design.conf:
set rda_Input(ui_gen_footprint) {1}
global bob
set bob test

encounter> loadConfig design.conf
encounter> puts $bob
test

There may be other ways to retrieve some of the things you'd like to extract from the .conf file via FE db commands. For example CDMA200 might be the name of the top cell in your design so you could query that with an FE TCL command:

encounter> dbgDesignName
CDMA200

Hope this helps,
Bob

Thanks Bob, It works well.

moreover, I have another question.
This is related to our golen.conf

in the config fie there is this lines
set rda_Input(ui_netlist) "$NETLIST"


in our user defined tcl scripts, I write this:
loadConfig golden.conf

Now the question is, Is there is a way I can set the variable *NETLIST* in the user defined scipts. so that I don't need to copy the golden.conf and modified it.

I tried the golbal thing you give to me,
global NETLIST
set NETLIST /path/to/verilog_file
loadConfig golden.conf

It failed to retrieve the $NETLIST


encounter 6> loadconfig ../spc/tcl/golden.conf
Reading config file - ../spc/tcl/golden.conf
can't read "NETLIST": no such variable


Anyway, I just try to setup more efficient design flow.
Thank you in advance.

Ah yes- I follow what you're trying to do. I think it's fairly common that you want to keep almost everything in a project/golden conf file, but you want to change just a couple of things (like the netlist or timing constraints or whatever).

I usually do that this way:

set NETLIST /path/to/verilog_file
loadConfig golden.conf 0
set rda_Input(ui_netlist) "$NETLIST"
commitConfig

The key is the "0" after loadConfig which is conceptually the same as what happens when you load a conf file via the GUI. Then clicking "OK" on the Design Import is the same as commitConfig.

Do you think that will suit your needs?

Yes, This is what I am looking for. Thank your for your support. You really explained it clearly. Thank you again.