• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 98 subscribers
  • Views 352 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.

TDA3XEVM: TDA3XEVM NOT WORK ,

sung woo yong
Prodigy 90 points
Part Number: TDA3XEVM 
tda3x evm board was purchased from spectra digital.

I entered 12v power using the power supply.

The current consumes about 300 ma.

Using tera term, I selected 115200 and uart third serial port for monitoring.

Dip sw is set to qspi or nor mode.


1) 
after power on 

No letters appear after power on.

2) 

I used blackhawk's usb560 v2 system trace and ccs to connect to the mipi60 slot.

If i will connect, message  "power loss"

I bought two evm boards and they all work the same.
  • 0 in reply to sung woo yong
    TI__Genius 13560 points

    Can you double-check your dip sw/sysboot. Refer to section "3.4 Boot Modes" in the Vision SDK TDA3x user guide. Also please try setting it to debug mode.

  • 0 in reply to Alex Bashkov
    Prodigy 90 points

    yes ..

    When connect  jtage emuilator ,   mode set  debug .

    after execute connect  m4_ipu_c0   ,  output following message 

    Error connecting to the target:
    (Error -2172 @ 0xD)
    Unable to communicate with the debug probe. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.
    (Emulation package 8.4.0.00006)

    i have question.

    first  bootloader is  rom boot.  and so second bootloader is qspi or nor or usrt ...

    1) 

    when rom boot  output  message  to serial  ? 

    following datasheet on page3. write  to display "AL" to serial port

    http://www.ti.com/lit/an/spracc3/spracc3.pdf 

  • 0 in reply to sung woo yong
    TI__Genius 13560 points

    If you boot an OS you won't be able to connect via JTAG. Can you try a not flashed EVM? You should first be able to connect to a bare metal board after just ROM execution and gel script initialization. 

  • 0 in reply to Alex Bashkov
    Prodigy 90 points

    evm board is bare board .

    when test jtag emulator , following messsage

    [Start]

    Execute the command:

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

    [Result]


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

    C:\Users\Owner\AppData\Local\TEXASI~1\CCS\
    ccs930\0\0\BrdDat\testBoard.dat

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

    This utility has selected a 560/2xx-class product.
    This utility will load the program 'bh560v2u.out'.
    Loaded FPGA Image: E:\ti\ccs930\ccs\ccs_base\common\uscif\dtc_top.jbc
    The library build date was 'Nov 25 2019'.
    The library build time was '14:08:22'.
    The library package version is '8.4.0.00006'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.

    An error occurred while hard opening the controller.

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    The value is '-180' (0xffffff4c).
    The title is 'SC_ERR_CTL_NO_TRG_POWER'.

    The explanation is:
    The controller has detected a target power loss.
    The user must turn-on or connect the power supply for the target.

    [End]

  • 0 in reply to sung woo yong
    TI__Genius 13560 points

    Is the power LED on? This error means the JTAG debugger is unable to sense the presence of a power supply voltage on the target.

  • 0 in reply to Alex Bashkov
    Prodigy 90 points

    Yes ... Power Led is on state.

    I checked all power and clocks, but that's right.

  • 0 in reply to sung woo yong
    TI__Genius 13560 points

    Here is a suggestion from another thread:

    If you are certain the board is properly powered, the DS5 LED is on, the power rails are correct (check the user's guide) and the JTAG Debug Probe is firmly seated on the MIPI-60 connector (not the MLB/MLBP connector), then there is a possibility something else is going wrong: either the Debug Probe or the board are not working.

    I would isolate the issue by testing each component separately: use a different target board to validate the Debug Probe, then use a different Debug Probe with the first target board. Either one or another combination should show the issue.