#--------------------------------------------------------------------------
# Board description
# For raw board handling, use:
# BD Board_type Board_address
# For HUNT ENGINEERING's Device Driver API use:
# BD API        Board_type      Board_Id        Device_Id 
#--------------------------------------------------------------------------
# Raw board handling:
# BD HEPC2M     150
# BD PCV404     e000
# Using API
# BD API hep2e          0               0
BD API hep3b           0               0
# BD HEPC2EA    200

# When using Code Composer Studio, a node must be given a CC-id. This
# id tells the Server/Loader where the node is located in the JTAG
# chain. If e.g. you have 3 processors, the node at the end of the
# chain is CC-id 0, the middle one is CC-id 1, and the node closest
# to the board interface (usually in slot 0) has CC-id 2. The reason
# for all this is that the JTAG scan path is not mapped one-to-one
# to the communication network.
#-----------------------------------------------------------------------
# Nodes description
# ND  BD_nb ND_NAME ND_Type CC-id GBCW      LBCW      IACK      filename(s)
#-----------------------------------------------------------------------
  ND  0     NODE0   ROOT    (1)   00000000  00000000  002ff800 idrom.out hepc3.out

#---------------------------------------
# Bootpath description.
# BOOTLINK  ND_NAME  PORT  ND_NAME  PORT
#---------------------------------------


#------------------------------------------------
# Number of the link connected to the host system
# HOSTLINK  PORT
#------------------------------------------------
  HOSTLINK  3

#------------------------------------------------
# Number of the link connected to the flash system
# FLASHLINK  PORT
#------------------------------------------------
# FLASHLINK  3

