• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 54 subscribers
  • Views 4445 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Error when trying to connect to my 6748 prototype board for the first time

cobsonchael
Mastermind 7930 points
Other Parts Discussed in Thread: TMS320C6748

Hello,

I am using a blackhawk 560BP emulator with a 6748 DSP board.  it is our own board, not an EVM.

i believe i set up the gel file to be something worthwhile, and i set up the target configuration to be 6748. when i try to connect i get

Error connecting to the target: Connect to PRSC failed

every single time.  What does this mean?

  • 0
    TI__Guru* 84110 points

    Which version of CCS are you using?

    Try running the BlackHawk diagnostics. These may vary by CCS version, but they should be able to test the scan chain to validate basic physical connection.

    Do you have an EVM or any known good board to try it on? If this is your first board, then there may be board design or fabrication problems that are preventing the emulator from connecting.

    I have not seen PRSC mentioned before, so we will have to wait for a real CCS expert to say more. But the answers to my questions above might help them help you quicker.

  • 0 in reply to RandyP
    Mastermind 7930 points

    oh, i'm sorry.  I am using CCSv4.2

     

    i have connected to our previous projects using C6421 just fine.  I'm hoping it's some setting i got wrong in CCS4.  I am still a little new to v4 and emulating

  • 0 in reply to cobsonchael
    TI__Guru* 84110 points

    Exactly which target configuration did you choose?

    The GEL file will not come into use until after the emulator makes a valid connection. This means only the target configuration matters from the CCSv4 side of the process.

    The BlackHawk diagnostics are your next easy step to take, to find out what BH can tell you about your emulator and board status.

    But with a new board, the rest of the steps require tracing signals and power supplies through the board and figuring out what may be wrong.

  • 0 in reply to RandyP
    Mastermind 7930 points

    the target configuration is:

    Blackhawk USB560-BP Emulator_0 -> TMS320C6748_0 -> ICEPICK_C -> Subpath_0 -> C674X_0

    as far as i know there are no blackhawk diagnostics that i have found.  on my computer i have the blackhawk control panel which will onyl let me see what Emulator i have connected to the computer and doesn't do any diagnostics, and a BH560v2 config utility which seems to only accept a LAN based emulator because i can't do anything with it unless i enter an IP address. most utilities on the BH website are for CCS3.3. I found BHProbe, though i am not sure if that does everything i want it to do, but from the description it tests emulator-to-target connectivity and all tests passed. either way here is the output from running BHprobe_USB560bp.bat from my CCS4 directory:

    Wed 12/08/2010- 9:03:22.28
    ****************************************************************************************************
    TEST 1 - RESET
    ****************************************************************************************************
    **************************************************
      BHProbe 5.01: Blackhawk USB560bp JTAG Emulator  
    **************************************************
    Wed 12/08/2010- 9:03:22.41          
                 
                 
    bin\XDSProbe.exe -v -F BH560Ubp.out -p0x0 -r -o log\BHprobe_USB560bp.log

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected an XDS560 class product.
    This utility will load the program 'BH560Ubp.out'.
    This utility will operate on port address '0'.
    The controller does use a programmable FPGA.
    The old VHDL code has a version number of '1544' (0x0608).
    The new VHDL code has a version number of '1544' (0x0608).
    The emulator program is named 'BH560Ubp.out'.
    The emulator program is version '35.24.0.3'.
    The controller has a version number of '4' (0x0004).
    The controller has an insertion length of '0' (0x0000).
    The cable+pod has a version number of '3' (0x0003).
    The cable+pod has a capability number of '12' (0x000c).
    The local memory has a base address of '0' (0x000000).
    The local memory has a word capacity of '32768' (0x008000).
    This utility will now attempt to reset the controller.
    This utility has successfully reset the controller.

    -----[Print the reset-command hardware log-file]-----------------------------

    The scan-path will be reset by toggling the JTAG TRST signal.
    The software is configured to use all Nano-TBC VHDL features.
    The controller type is the Nano-TBC VHDL.
    The connection type is a 560-class hybrid cable.
    The controller will be software reset via its configure register.
    The controller will use rising-edge timing on output pins.
    The controller may use rising edge timing on input pins.
    The controller has a logic ONE on its EMU[0] input pin.
    The controller has a logic ONE on its EMU[1] input pin.
    The scan-path link-delay has been set to exactly '3' (0x0003).
    The support logic has not previously detected a power-loss.
      
    Done. 
      
    ****************************************************************************************************
    TEST 2 - SCAN 
    ****************************************************************************************************
    **************************************************
      BHProbe 5.01: Blackhawk USB560bp JTAG Emulator  
    **************************************************
    Wed 12/08/2010- 9:03:26.31          
                 
                 
    bin\XDSProbe.exe -v -F BH560Ubp.out -p0x0 -i -o log\BHprobe_USB560bp.log

    -----[Print the controller-open software log-file]---------------------------

    This utility has selected an XDS560 class product.
    This utility will load the program 'BH560Ubp.out'.
    This utility will operate on port address '0'.
    The controller does use a programmable FPGA.
    The emulator program is named 'BH560Ubp.out'.
    The emulator program is version '35.24.0.3'.
    The controller has a version number of '4' (0x0004).
    The controller has an insertion length of '0' (0x0000).
    The cable+pod has a version number of '3' (0x0003).
    The cable+pod has a capability number of '12' (0x000c).
    The local memory has a base address of '0' (0x000000).
    The local memory has a word capacity of '32768' (0x008000).

    -----[Perform the standard path-length test on the JTAG IR and DR]-----------

    This path-length test uses blocks of 512 32-bit words.

    The test for the JTAG IR instruction path-length succeeded.
    The JTAG IR instruction path-length is 6 bits.

    The test for the JTAG DR bypass path-length succeeded.
    The JTAG DR bypass path-length is 1 bits.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG IR Integrity scan-test has succeeded.

    -----[Perform the Integrity scan-test on the JTAG DR]------------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG DR Integrity scan-test has succeeded.
      
    Done. 
      
    ****************************************************************************************************
    TEST 3 - SCAN2
    ****************************************************************************************************
    **************************************************
      BHProbe 5.01: Blackhawk USB560bp JTAG Emulator  
    **************************************************
    Wed 12/08/2010- 9:03:29.06          
                 
                 
    bin\XDSProbe.exe -v -f bin\bh-noscantest.cfg -F BH560Ubp.out -p0x0 -i -o log\BHprobe_USB560bp.log

    -----[Print the controller-open software log-file]---------------------------

    This utility has selected an XDS560 class product.
    This utility will load the program 'BH560Ubp.out'.
    This utility will operate on port address '0'.
    The controller does use a programmable FPGA.
    The emulator program is named 'BH560Ubp.out'.
    The emulator program is version '35.24.0.3'.
    The controller has a version number of '4' (0x0004).
    The controller has an insertion length of '0' (0x0000).
    The cable+pod has a version number of '3' (0x0003).
    The cable+pod has a capability number of '12' (0x000c).
    The local memory has a base address of '0' (0x000000).
    The local memory has a word capacity of '32768' (0x008000).

    -----[Perform the standard path-length test on the JTAG IR and DR]-----------

    This path-length test uses blocks of 512 32-bit words.

    The test for the JTAG IR instruction path-length succeeded.
    The JTAG IR instruction path-length is 6 bits.

    The test for the JTAG DR bypass path-length succeeded.
    The JTAG DR bypass path-length is 1 bits.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG IR Integrity scan-test has succeeded.

    -----[Perform the Integrity scan-test on the JTAG DR]------------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG DR Integrity scan-test has succeeded.
      
    Done. 
      
    ****************************************************************************************************
    TEST 4 - DATA
    ****************************************************************************************************
    **************************************************
      BHProbe 5.01: Blackhawk USB560bp JTAG Emulator  
    **************************************************
    Wed 12/08/2010- 9:03:31.72          
                 
                 
    bin\XDSProbe.exe -v -F BH560Ubp.out -p0x0 -g -o log\BHprobe_USB560bp.log

    -----[Print the controller-open software log-file]---------------------------

    This utility has selected an XDS560 class product.
    This utility will load the program 'BH560Ubp.out'.
    This utility will operate on port address '0'.
    The controller does use a programmable FPGA.
    The emulator program is named 'BH560Ubp.out'.
    The emulator program is version '35.24.0.3'.
    The controller has a version number of '4' (0x0004).
    The controller has an insertion length of '0' (0x0000).
    The cable+pod has a version number of '3' (0x0003).
    The cable+pod has a capability number of '12' (0x000c).
    The local memory has a base address of '0' (0x000000).
    The local memory has a word capacity of '32768' (0x008000).

    -----[Perform the standard path-length test on the JTAG IR and DR]-----------

    This path-length test uses blocks of 512 32-bit words.

    The test for the JTAG IR instruction path-length succeeded.
    The JTAG IR instruction path-length is 6 bits.

    The test for the JTAG DR bypass path-length succeeded.
    The JTAG DR bypass path-length is 1 bits.

    -----[Perform the Given Data scan-test on the JTAG IR]-----------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.
    It uses the first 1 of the 10 different test-cases.

    Do a test using 0x5533CCAA.
    Scan tests: 1, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG IR Given Data scan-test has succeeded.

    -----[Perform the Given Data scan-test on the JTAG DR]-----------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.
    It uses the first 1 of the 10 different test-cases.

    Do a test using 0x5533CCAA.
    Scan tests: 1, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG DR Given Data scan-test has succeeded.
      
    Done. 
      

  • 0 in reply to cobsonchael
    Prodigy 65 points

    ,

    Did you ever find a solution to this problem, was it a jtag issue.  I am experiencing similiar behavior with a similiar setup.

    Thanks. 

  • 0 in reply to Seth Fowler
    Mastermind 7930 points

    I forgot all about this..

     

    my problem was hardware related and twofold.  first, we had improper resistors loaded for the voltage supervisor circuit so it never released the reset line for the DSP.  second, the reset line to the DSP should be pulled high (even though it says it is internally pulled high we found that it still needs a pullup on it)

  • 0 in reply to cobsonchael
    Prodigy 65 points

    thanks, wasn't sure if you were trying to connect to the arm side first and wakeup DSP.