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.

DM3730's power management unit(TPS65910) can not work

Other Parts Discussed in Thread: TPS65910, DM3730

I am using the TPS65910 to manager DM3730's power,but it does not work.

the i2c address of TPS65910 is 0x2D,and I find that DM3730 try to communicate with a address of 0x49.

I think that is the reason.

and someone know h ow to fix it.

Thank you!

  • I wish someone can help me to fix it.

    Thank you!

  • Hello,

    As I read in the TPS65910x Integrated Power Management Unit Top Specification document at the link below:

    http://www.ti.com/lit/ds/swcs046t/swcs046t.pdf

    You are right about the I2C address of TPS65910. The general-purpose I2C module using one slave hard-coded address (ID1 = 2Dh). Therefore the decision is to change the address for I2C communication in the sources code but could you specify what software you are using. Is it some official TI's release or it is a custom build?

    BR

    Tsvetolin Shulev

  • Cvetolin Shulev-XID

    Thanks for your reply.

    This problem is occur,when I want to boot dm3730 from MMC,No external code is involved in this process.
    That is to say OCM_ROM codes set the I2C slave address(I2C_SA).I confirm it by JTAG debugger.

    How to change this I2C_SA in booting?

    whao

  • Hi Whao,

    The ROM code is hard coded and could not be changed. The earliest place where the I2C_SA could be changed is the x-loader. I only could suggest you to make this setting in the board file where are made the most of the hardware modules initializations .

    BR

    Tsvetolin Shulev

  • Hi Tsvetolin Shulev,

    Follow your suggestion,I try to load x-load.bin to DM3730's OCM_RAM using JTAG,and it can work correctly.

    Thefile of x-load.bin can load u-boot.bin to DDR and excute it correctly.

    JTAG booting is troublesome,so I want to boot it from UART3,

    when I try this idea using Flash v1.6.

    Unfortunately, This app output :

        -stdout
        -omap 3
        -no_force_package_alignment
        -com 3
        -t 60
        -p CUSTOM_AM37XX_BOARD
        -2
        chip_erase NANDINFO1BITBOOT 0
    Leaving parameter file:temp_script.txt
    @temp_script.txt
    Looking for device (omap com3)
    Please turn off device, then turn it on again
    Awaiting ASIC id
    AsicId items 04
    AsicId id        	01 05  01  36 30 07 07 
    AsicId secure_mode	13 02  01  00 
    AsicId public_id 	12 15  01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
    AsicId root_key_hash	14 15  01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
    Searching 2nd for: CUSTOM_AM37XX_BOARD 363007 07 GP 
    Loading second file Targets\2nd-Downloaders\dnld_startup_omap3_gp_512m.2nd
    Entering parameter file:omapflash2nd.txt at line: 9
        -pheriphalboot_reopen
    Reading board configuration file Targets\Configurations\configuration_custom_am37xx.txt
    Reading definition file .\targets\definitions\definitions_omap3.txt
        -board_config Targets\Configurations\configuration_custom_am37xx.txt
    Leaving parameter file:omapflash2nd.txt
    Sending size of second file (0x00006804 bytes)
    Transferring second file to target (0x6804 bytes)
    Closing boot connection
    Found device (omap com3)
    Waiting for 2nd
    Reception failed - timeout after 60 s during peripheral boot (waiting for 2nd)
    
    Console program failed, exit code: 2

    I think, there are some wrongs in this .2nd file,Can I debug this file and find why it cannot be excuted.

    Thanks

    whao

  • Hi Whao,

    A possible reason for the error could be if there is no enough space in the NAND for the second file. If this is not the reason for the error you can the Flash v1.6 User guide feedback section at the link:

    http://processors.wiki.ti.com/index.php/Flash_v1.6_User_Guide#Feedback

    for more advanced support.

    BR

    Tsvetolin Shulev

  • Hi Tsvetolin Shulev,

    I solved this problem by a tool named pserial.

    Thanks.

    whao