• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 524 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.

Hardware Testing for BlackhawkUSB100V2

Aniketh Chepuri
Intellectual 530 points
Other Parts Discussed in Thread: UNIFLASH

Hello, 

I have been posting my problems with Blackhawk USB100V2, but nothing workd. I want somebody to suggest me how could I check my BlackhawkUSB 100V2 hardware is working fine when not connected to the any of the PCB boards ???

Thank you. 

Regards,

Aniketh Chepuri.

  • 0
    TI__Genius 11645 points
    Could you explain the issue with little more details ?
  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    Intellectual 530 points

    Hello Karthi,

    I have problem with my blackhawk for the past one month. While I flash the code into my TMS570 it give the "error 242" and when I use Nowflash it shows "Ërror 199". I perfomed the Scan test and it says 

    --------------------------------------------------------------------------------------------------------------------------

    [Start]

     

    Execute the command:

     

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

     

    [Result]

     

     

    -----[Print the board config pathname(s)]------------------------------------

     

    C:\Users\achepuri\AppData\Local\.TI\693494126\

        0\0\BrdDat\testBoard.dat

     

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

     

    This utility has selected a 100- or 510-class product.

    This utility will load the adapter 'jioserdesusb.dll'.

    The library build date was 'Oct  3 2012'.

    The library build time was '21:58:41'.

    The library package version is '5.0.872.0'.

    The library component version is '35.34.40.0'.

    The controller does not use a programmable FPGA.

    The controller has a version number of '4' (0x00000004).

    The controller has an insertion length of '0' (0x00000000).

    This utility will 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 controller is the FTDI FT2232 with USB interface.

    The link from controller to target is direct (without cable).

    The software is configured for FTDI FT2232 features.

    The controller cannot monitor the value on the EMU[0] pin.

    The controller cannot monitor the value on the EMU[1] pin.

    The controller cannot control the timing on output pins.

    The controller cannot control the timing on input pins.

    The scan-path link-delay has been set to exactly '0' (0x0000).

     

    -----[The log-file for the JTAG TCLK output generated from the PLL]----------

     

    There is no hardware for programming the JTAG TCLK frequency.

     

    -----[Measure the source and frequency of the final JTAG TCLKR input]--------

     

    There is no hardware for measuring the JTAG TCLK frequency.

     

    -----[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.

     

    [End

    -------------------------------------------------------------------------------------------

    Now I tried to check the out put from the BlackhawkUSB100V2 and I dont get any out put from the PINS TCLK TDI TnRST,

    Is there any way to check that the Hardware is ok >??

    regards,

    aniketh.

  • 0 in reply to Aniketh Chepuri
    TI__Genius 11645 points
    Sorry Aniketh, somehow this thread got missed.

    From the message above, I see the emulator is detecting the device through Scan properly.

    Its something to do with your Flashing, btw please use UNIFLASH as we do not support NowFlash anymore.

    If you still see some issue because of bad code holding you from connecting to your CPU(for example you flashed a code with MPU set to disable access to all the required memory regions by MISTAKE, then once reset is released then CPU starts executing that code and debugger doesn't connect anymore/flashing is not possible anymore).

    If you are experiencing similar problems, then pls follow the below procedure

    1. Hold the reset pin nRST active low (So CPU doesn't start executing the code that already exists in flash)
    2. Start erase operation using the Flash programming tool (Say UNIFLASH) while holding the Reset pin
    3. While your uniflash keeps waiting since the device is still in reset, try releasing the reset randomly after a couple of sec's

    If it doesn't work the first time, then follow the same procedure again from step-1 until you get lucky to get UNIFLASH halting the target before CPU starts execution.