• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 995 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.

help about dm385 hardware problem

shuo wang54923
Intellectual 300 points

Other Parts Discussed in Thread: DM385

Dear,
We're testing our new dm385 board, the main chip is DM385AAARD2IF,
and we have strange problem with the board:

1) When power on, the board can output "CCCCC" from UART0.
2) We measure all of the power supply pins, and the voltage values of which meet the requiremnets in the datasheet.
3) 20MHz DEV_CLKIN is ok.

========================================================================
But, when we connect the board with jtag, firstly, it gives the error:
Error connecting to the target:
(Error -241 @ 0x0) A router subpath could not be accessed.
A security error has probably occurred.
(Emulation package 5.1.232.0)

and when we retry, it gives the error:

Error connecting to the target:
(Error -1265 @ 0x0)
Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver.
(Emulation package 5.1.232.0)

We check the jtag pins, and find that input/output data exist on the pin of TMS/TDI/TDO/TCK/RTCK,
but we don't know what's mean for these input/output data.

========================================================================
After many time tries, we give up jtag, and try to use UART boot to download the bootloader.

We can download the min uboot to the board using Tera Term, but after finish the downloading,
the board still output "CCC", and not execute the min uboot

To compare with the new design board, We download the same min uboot to our other design board by UART boot, after finish the downloading,
the other board execute the min uboot successfully.

==============================================
The above is the current status of our new dm385 board.
Can anyone give us some hint about how & where to Identify the problem?

Thank you!

Wang Shuo

  • 0
    TI__Guru**** 170625 points

    Hi Shuo,

    shuo wang54923 said:
    But, when we connect the board with jtag

    Which JTAG emulator/debugger you are using? Have you checked if it support DM385?

    shuo wang54923 said:
    Error connecting to the target:
    (Error -1265 @ 0x0)
    Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver.
    (Emulation package 5.1.232.0)

    See if the below wiki page will be in help:

    shuo wang54923 said:

    Error connecting to the target:
    (Error -241 @ 0x0) A router subpath could not be accessed.
    A security error has probably occurred.
    (Emulation package 5.1.232.0)

    This kind of issues are discussed in the CCStudio forum.

    Also we have something similar in the below e2e thread:

    shuo wang54923 said:

    After many time tries, we give up jtag, and try to use UART boot to download the bootloader.

    We can download the min uboot to the board using Tera Term, but after finish the downloading,
    the board still output "CCC", and not execute the min uboot

    Have you configured the sysboot pins for UART boot?

    shuo wang54923 said:
    To compare with the new design board, We download the same min uboot to our other design board by UART boot, after finish the downloading,
    the other board execute the min uboot successfully.

    Do you mean that u-boot.min.uart is working fine on your old DM385 based board? What is the difference between old DM385 custom board and new DM385 custom board?

    See if the below wiki pages will be in help:

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Intellectual 300 points
    Hi Pavel,
    For these days we have dig the bug and finally we found the power supply sequence of CVDD, CVDD_ARM, CVDD_HDVICP may not meet the requirements in the datasheet. it seems the CVDD_ARM is prior to CVDD. So we connect the CVDD, CVDD_ARM, CVDD_HDVICP with the same power supply, and which should meet the requirement.
    We test and get the result as below:
    1) for 1 piece of board, which mounted with DM385AAR01 chip, it can download u-boot.min.uart and runs ok, also we can use jtag to connect it and run program.
    2) for the other several piece of boards, which mounted with DM385AAARD2IF, nothing changes, that is , it can output CCC from uart, and we can download u-boot.min.uart but can not run it, and also we can not connect it with jtag.
    3) the PCBs is same, only the main chips are different.

    //-------------------------------------------------------------------------------------------------------------------------
    for the board with DM385AAR01, we test again and find:
    4) we firstly download u-boot.min.uart by uart, and when it run, we download u-boot.bin(2nd uboot for nand) by uart again and run it.
    then we download u-boot.min.nand and u-boot.bin (2nd uboot for nand) by uart and flash it to nand.
    5) but when we power off and power on, it can't run from nand flash and only output CCC from uart.
    6) If we download u-boot.min.nand by uart, it runs and then load u-boot.bin from nand flash and run load u-boot.bin ok.

    and our BOOTMODE config as below:
    BOOTMODE[4:0] = 10011
    BOOTMODE[6:5] = 00
    BOOTMODE[7] = 0
    BOOTMODE[9:8] = 10
    BOOTMODE[10] = 1
    BOOTMODE[11] = 0
    BOOTMODE[12] = 1
    BOOTMODE[14:13] = 00
    BOOTMODE[15] = 0

    the above is confirmed when we read control status, the value of which is 0x03010313.

    So our question is:
    a) why the DM385AAARD2IF not work?
    b) why the u-boot.min.nand in the flash not run when power on?


    Thank you!
    Wang Shuo
  • 0 in reply to shuo wang54923
    TI__Guru**** 170625 points

    Wang,

    shuo wang54923 said:
    2) for the other several piece of boards, which mounted with DM385AAARD2IF, nothing changes, that is , it can output CCC from uart, and we can download u-boot.min.uart but can not run it, and also we can not connect it with jtag.

    shuo wang54923 said:
    a) why the DM385AAARD2IF not work?

    This is silicon revision 1.1 device. Can you try with the latest IPNC RDK u-boot (link below)?

    Or if you are using pure PSP (with no IPNC SDK above), you can try with the below u-boot:

    Can you provide me the steps you are using to build, download and run u-boot.min.uart? And the console log also (for run u-boot.min.uart).

    Not able to connect with JTAG - this seems like HW issue. Can you provide me the steps you are doing in your attempt to connect with JTAG to your board?

    shuo wang54923 said:
    4) we firstly download u-boot.min.uart by uart, and when it run, we download u-boot.bin(2nd uboot for nand) by uart again and run it.
    then we download u-boot.min.nand and u-boot.bin (2nd uboot for nand) by uart and flash it to nand.
    5) but when we power off and power on, it can't run from nand flash and only output CCC from uart.

    shuo wang54923 said:
    b) why the u-boot.min.nand in the flash not run when power on?

    May be you are not flashing your NAND correct, I can not say without seeing your steps and logs. May be your NAND flash is not suitable for booting, I can not say without knowing which NAND chip you are using. May be your NAND flash is not aligned with the ROM Code, check DM38x TRM, section 4.7.3 NAND


    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Intellectual 300 points

    Hi, Pavel,

    Thank you!

    It seems we have bought fake chips, and as we use a new batch of chips, all boards are ok!

    Wang Shuo