• State Resolved
  • Locked Locked
  • Replies 16 replies
  • Subscribers 107 subscribers
  • Views 1474 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Restore UBL on DM365IPNC-MT5

ADC
Intellectual 660 points

Hi,
i have damaged ubl in my DM365IPNC-MT5 and i don't know how to restore it

i have searched around documentations and web to find all the possible way and i concluded there aren't other ways than use Code Composer Studio and a XDS 510 USB emulator or XDS 560 emulator like is described on User_Guide_IPNC_DM365 document.

Am i going wrong?
I am not yet very practical and I do not know what to do, i haven't CCS and emulator ...
Is there any way to use serial flash or sd card? It seems impossible, i can't found any way to change boot mode. Is there?

Can someone help me?
Best regards

  • 0
    TI__Mastermind 19985 points

    Hi,

    As of now, IPNC Reference Design comes with the solution of using CCS and JTAG to program the UBL on NAND. We have not validated the SD boot and programming mode on the IPNC, but ideally it should work smoothly, as it works on DM365 EVM.

    For selecting the SD boot mode, please close jumper JP2 on the debug board. This detail is mentioned in the User Guide of IPNC Ref Design.

    BTW, if you do not have CCS and JTAG, i can recommend you to visit or talk to local TI FAE who can help you with the programming of NAND.

    Regards,

    Anshuman

    PS: Please mark this post as verified, if you think it has answered your question. Thanks.

     

  • 0 in reply to Anshuman Saxena
    Intellectual 660 points

    Thanks Anshuman,
    i have found this detail, i'll try

    Best regards
    Andrea

  • 0 in reply to Anshuman Saxena
    Intellectual 660 points

    Hi Anshuman,
    i have tried SD boot but it seems an invalid procedure.
    when DM365IPNC boot by SD, nothing is shown in terminal

    I' ve read in another thread (http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/100/p/30578/106659.aspx#106659) that the SD bootloader code need to be modified for IPNC Ref Design and SD booting code is configured to work with UART0 than UART1 used by appro. Then is each test useless with the current instrument?

    Anshuman Saxena said:
    We have not validated the SD boot and programming mode on the IPNC, but ideally it should work smoothly, as it works on DM365 EVM.


    Can in practice work smoothly without modify SD bootloader code?
    Does someone plan to do it?

    Best regards
    Andrea

  • 0 in reply to ADC
    TI__Mastermind 19985 points

    Andrea,

    The post your referred to is having all details of SD card booting. We do not have any support of SD card booting on the IPNC Ref Design offering. The hardware supports it and one can modify the SD card boot code for UART1 instead of UART0, and then use it on the IPNC hardware.

    Have you tried taking the approach of contacting your local TI FAE to help you with programming the IPNC again?

    Regards,

    Anshuman

  • 0 in reply to Anshuman Saxena
    Intellectual 660 points

    Hi Anshuman,
    i've modified SD card boot code for install ubl and uboot without wait user intercation then i reload via TFTP uImage and cramfsImage and it seems to be ok.
    Now, i can work with my DM365IPNC-MT5 ... the only strange thing is a lot of "rtc wait time out !!!!!" messages during startup. Do you know what it mean?

    Thanks for your help
    Regards,
    Andrea

  • 0 in reply to ADC
    TI__Mastermind 19985 points

    Andrea,

    This is wonderful. Good to know that you could overcome the bottleneck.

    "rtc wait time out !!!" used to come earlier when the RTC was not correctly enabled in the system. I dont expect it to come with the ver 1.5 software builds. Did you use the UBL and uBoot that we had provided with ver 1.5 release or did you try any other UBL?

    Regards,

    Anshuman

    PS: Please mark this post as verified, if you think it has answered your question. Thanks.

  • 0 in reply to Anshuman Saxena
    Intellectual 660 points

    Yes, i have used the correct versions ... this is the initial output

      DM36x initialization passed!
    TI UBL Version: 1.50
    Booting Catalog Boot Loader
    BootMode = NAND
    Starting NAND Copy...
    Valid magicnum, 0xA1ACED66, found in block 0x00000008.
       DONE
    Jumping to entry point at 0x81080000.

     Reset RTC Fail..
     DM365_IPNC_UBL_V03

    U-Boot 1.3.4 (Aug  5 2009 - 18:21:12) DM365-IPNC-0.6


    Regards,
    Andrea

  • 0 in reply to ADC
    Prodigy 110 points
    Hello, Has anyone solved this issue? I am seeing the same problem with a DM368 IPNC as well and starting to investigate. (UBL version 1.5) Thanks, Rulphie
  • 0 in reply to ADC
    Prodigy 125 points

    ADC,

    Can you please send me modified boot code or tell me whet you had to modify, I'm having the same problem.  I tryed to just change like this (below) in device.h but it's not working.

     

    //#define UART0 ((DEVICE_UartRegs*) 0x01C20000)
    #define UART0 ((DEVICE_UartRegs*) 0x01D06000) //PR UART1

  • 0 in reply to frivas
    TI__Mastermind 19985 points

    Hi,

    For RTC issues, i have got the following response

    "To solve this problem, the customer need power off the IPNC and wait 30 mintues then power on the IPNC.

    This is for discharging the RTC’s battery. "
    Regards,
    Anshuman
  • 0 in reply to Anshuman Saxena
    Prodigy 110 points

    Hi Anshuman,

    Thanks, this solves the problem.

    Rulphie

  • 0 in reply to rulphie
    Prodigy 50 points

    I too had the same issue,  I just short the battery, after that rtc reset fail was not happening, what is the actual cause fro this issue,

    My case is little bit different, we made a IPNC board and during the bopard bring up we found this issue, we initially suspected some RTC (32Khz)clk issue. but clock was ok when we probed.

     

    After see this forum i just shorted the battery. its works fine and we were able to set date an d time.

     

     

     

    Regards

    Joseph george

  • 0 in reply to frivas
    Prodigy 70 points

    Quick patch to change UART0 to UART1 on appro IPNC DM368

     

    (dm3xx_sd_boot-6.1 base)

    1

    flash_utils/DM36x/Common/include/device.h

    //#define UART0 ((DEVICE_UartRegs*) 0x01C20000)
    #define UART0 ((DEVICE_UartRegs*) 0x01D06000)

    2.
    flash_utils/DM36x/Common/src/device.c
    // assign multiplex pins to UART1
    @Uint32 DEVICE_init()
    DEVICE_pinmuxControl(3,0xFFFFFFFF,0x60000000);  // SPI0, SPI1, UART1, I2C, SD0, SD1, McBSP0, CLKOUTs 00180000
    DEVICE_pinmuxControl(4,0xFFFFFFFF,0x5555D555);  // MMC/SD0 instead of MS, SPI0 55555555

    // correct baudrate divider
    @Uint32 DEVICE_UART0Init()
    //UART0->DLL = 0x0d; 
    UART0->DLL = 0x42;               // Set baud rate<< depends on your PLL divider setting at DEVICE_PLL1Init() and the OSC input


  • 0 in reply to RRW
    Expert 1195 points

    Hi Rux,

    I updated the SD card boot utility as described by you. After updating the files, i definitely re-make by 

    sudo make

    but i get the following error in this case:

    make [1] : arm_v5t_le-gcc: command not found

    Can you please re-write the steps of booting dm36x IPNC with SD card. I am facing the similar problem that you faced. 

    Thanks.

  • 0 in reply to umair khan
    Prodigy 70 points

    hi umar,

     

    it looks like that you didn't set the toolchain path.

    try to use

    export PATH=<toolchain build Dir>/bin:$PATH

     

    umair khan said:

    Hi Rux,

    I updated the SD card boot utility as described by you. After updating the files, i definitely re-make by 

    sudo make

    but i get the following error in this case:

    make [1] : arm_v5t_le-gcc: command not found

    Can you please re-write the steps of booting dm36x IPNC with SD card. I am facing the similar problem that you faced. 

    Thanks.

     

  • 0 in reply to Anshuman Saxena
    Intellectual 305 points

    does that mean, we just switch the device off? and turn it back on after 30min?

    Anshuman Saxena said:

    Hi,

    For RTC issues, i have got the following response

    "To solve this problem, the customer need power off the IPNC and wait 30 mintues then power on the IPNC.

    This is for discharging the RTC’s battery. "
    Regards,
    Anshuman