#--------------------------------------------------------------------------
# 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        hep6a           0               0
# BD HEPC6A    160
BD API hep9a 0 0

# 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 HERON-ID  filename(s)
#-----------------------------------------------------------------------
  c6    0    HERON1   ROOT     (0)   00000003  heron4.out
  pcif  0    HOST     NORMAL         5

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

#------------------------------------------------
# Number of the link connected to the host system
# HOSTLINK  PORT
#------------------------------------------------
  TOHOST    0
  FROMHOST  0

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

#------------------------------------------------
# Program heart
#        from     fifo  to       fifo   timeslots
#------------------------------------------------
heart    HOST     0     HERON1   0      1
heart    HERON1   0     HOST     0      1

