• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 101 subscribers
  • Views 519 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.

DM8168 uboot boot already ,but nothing to be printed out

Taylor Wang
Prodigy 130 points

   Hi,everyone, I enconter a strange problems about uboot in the DM8168 DVRRDK 4.1.

   I find different cross_compile woud get different u-boot.bin.noxip file and one can boot up from nand flash while the other can't   after  I modified the DDR freq from 796.5 Mhz to 675 Mhz depend on our boards.

   I use the arm-none-linux-gnueabi and arm-arago-linux-gnueabi-  to compile the uboot.

 1、CROSS_COMPILE= arm-none-linux-gnueabi-:  

    The  output file uboot.bin.noxip can boot  from the Nand flash .

2、CROSS_COMPILE= arm-arago-linux-gnueabi-:

    The output file uboot.bin.noxip   boot  from the nand flash but  there is nothing to be printed.When I use CCS debug it ,I find it has configured the DDR and copied itself to OCRAM and DDR .Even though it looks like to run ok ,it prints nothing, Why ?

      Besides,I set the PC register to 0x40400000 and click the RUN by CCS, it runs OK again and prints some informations likes cpu freq .       

      what is the reasons of these ? Can someone explain or give some suggests ? Thank you very much.

     Looking forword to your reply .

     

  • 0
    TI__Guru**** 170625 points

    Hi Taylor,

    Taylor Wang said:

    2、CROSS_COMPILE= arm-arago-linux-gnueabi-:

        The output file uboot.bin.noxip   boot  from the nand flash but  there is nothing to be printed.When I use CCS debug it ,I find it has configured the DDR and copied itself to OCRAM and DDR .Even though it looks like to run ok ,it prints nothing, Why ?

    Are you using the DM816x PSP?

    http://processors.wiki.ti.com/index.php/TI81XX_PSP_UBOOT_User_Guide#Building_2nd_stage_u-boot

    From the wiki above, the recommended toolchain for building the DM816x/TI816x u-boot is:

    $ make CROSS_COMPILE=arm-none-linux-gnueabi-

    The other toolchain (arm-arago-linux-gnueabi-) seems to be used for newer u-boot versions, like for the 
    Sitara AM335x device.

    See the below e2e thread for more info:

    http://e2e.ti.com/support/embedded/linux/f/354/t/261011.aspx


    Regards,
    Pavel


  • 0 in reply to Pavel Botev
    TI__Guru**** 170625 points

    Taylor,

    I am using EZSDK, not DVRRDK, but I think it should be similar with the DVRRDK.

    In EZSDK we use the CodeSourcery ARM GCC Toolchain:

    /home//users/pbotev/CodeSourcery/arm-2009q1/bin/arm-none-linux-gnueabi-*

    Also the toolchain that comes within the DM816x EZSDK is:

    ti-ezsdk_dm816x-evm_5_05_02_00/linux-devkit/arm-none-linux-gnueabi

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 130 points

         Hi, Pavel,Thanks for your rely.

         Befor the DVRRDK version 4.0,the arm-none-linux-gnueabi compiler was installed as part of it. But arm-arago-linux-gnueabi compiler was installed as a part of the DVRRDK 4.1. And now we work on the DVRRDK 4.1.

         We find that the uboot is compiled by arm-arago-linux-gnueabi and will also work well when I modified the DDR freq to the 796.5Mhz (the uboot default  freq).

        But we also need the DDR 675Mhz freq to work well.

        I also find some time a printf function in the  davinci_emac.c file will lead to boot up failly.

        Besides,I also do a following test:

       1、when dm8168 power on,it prints nothing.I connect the CCS. In the CCS debug environment, I find cpu work ok.

       2、In the CCS debug environment,  I set  OCMR (0x40400000~0x40400000+0x40000)  and DDR (0x80700000~0x80700000+0x40000) to 0 to clear memery data.Then I click CPU Reset(HW) to reset the cpu and run again ,it reload the uboot from nand Flash and run ok. The PC terminal capture some information printed by uboot. 

         I think above process is the same as the cpu power up and this can prove the uboot file programed on the nand flash is right . Am I right?

         If so, but one can print something successfully, the other can't.

         I am very confused about this problem. Becase of this I can't ascertain whether the uboot program  is right when I modify the uboot source .

            Can you give me some more advise ?Thank you very much.

  • 0 in reply to Pavel Botev
    Prodigy 130 points

    Hi, recently I encounter the similiar problem again.

    I added some code to the uboot source .After compiling it  didn't work even though the part code added by me didn't start running.

    I am quite confused about this problem. I can't understand the reason.

    Can you help me? I am looking forward to your reply.