EZ-KIT BF 592 Error: 0x80048020

Hello All,

We have purchased the ADZS-BF592-EZLITE. (ez kit board and usb cable) in the package

We have installed the CCES 2.9.2(Cross core Embedded Software) software  and have compiled the example program (Audio loop back) with blackfin settings (ADSP-BF592 EZ-KIT Lite®
Evaluation System Manual)
We were not able to connect the CCES with the hardware emulator with the following settings.
In the Device manager we are able to see ICE 1000 ( PFA device_manager_snap)
I have explored the following steps in the data sheets 
  Using the on-board Debug Agent:
 step 1. Plug one side of the provided USB cable into the USB connector of the debug agent ZP1 (labeled USB).
 step 2. Plug the other side of the cable into a USB port of the PC running CCES.  
 step 3 (if connected through the debug agent): Verify that the yellow USB monitor LED (labeled ZLED2) and the green power LED (labeled ZLED1) on the debug agent are both on. This   
signifies that the board is communicating properly with the host PC and ready to run CCES.
Click Finish to close the wizard. The new debug configuration is created and added to the program(s) to load list.  
>>This step error occurs as 
"Error in launch sequence

[TpsdkServer] Failed to connect to processor.
Error: 0x80048020

Error Description: Selected emulator not detected"
Step 1: 
I have gone through this document also which insists the use of JTAG port.   ICE-1000/ICE-2000 Emulator User’s Guide (Chapter 2 -Connectors)
  There are two connectors on the ICE-1000 used for connecting to a target. J1 is a 0.1" 14-pin connector used for interfacing with legacy targets. This connector only supports debugging via JTAG mode. J2 is a 0.05" 10-pin connector used for JTAG/SWD mode on newer processors.  
Step 2:   
ICE Test Utility fails because of "Determine scan Path Length"
This utility ensures that the JTAG chain is intact; it is used to test your emulation hardware. Before connecting to an emulator session, ensure that each action performed by the ICE Test utility results in a Pass.   
Troubleshooting :
  This step determines the number of JTAG devices located on the target hardware to which the emulator is connected.
We have few queries which I have summarized below.
1. Do we need to connect any emulator hardware has its not mentioned in the document since the Configurator test fails in the step4 
Please reply asap. 
Thanks for the support.