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

8127 RDK(V2.0.0) jffs2 starting problem

bo guo1
Prodigy 35 points

Hi,

I meet a error with DM8127 SDK.

#make jffs2

I can get jffs2_ipnc.bin, burn flash. When DM8127 starting form reset, it will always print "Phy Addr : 0x4818050c Data : 0x00007f02" .

the picture is

:

Thanks,

bo guo.

  • 0
    TI__Genius 11000 points

    Hi,

    These are debug prints and will not cause any issues, is there any error you are observing?

    Regards,

    Raghu

  • 0 in reply to Raghu Kudva
    Prodigy 35 points

    On console  will always print "Phy Addr : 0x4818050c Data : 0x00007f02" . The print will not stop! I think this problem is serious!

  • 0 in reply to bo guo1
    TI__Genius 11000 points

    Hi,

    This can only happen if the uboot is for "lowpower" and you running "fullfeature" mode or viceversa.

    Please ensure to run same uboot with same mode build for "low power" or "full feature"

    Regards,

    Raghu

  • 0 in reply to Raghu Kudva
    Prodigy 200 points

    hello : today ,i have met a same issue to you with DM8127 SDK

    data 173209

    BW Phy Addr : 0x4d0000e4 Data : 0x00173209

    AW Phy Addr : 0x4d0000e4 Data : 0x00173209 DDR IOs RX is shutdown data 1

    BW Phy Addr : 0x48180400 Data : 0x00000001

    AW Phy Addr : 0x48180400 Data : 0x00000001 data 0

    BW Phy Addr : 0x48180a00 Data : 0x00030000

    AW Phy Addr : 0x48180a00 Data : 0x00030000

    Phy Addr : 0x48180a04 Data : 0x00000000 PRCM for TPPSS Initialization in Progress data fd

    BW Phy Addr : 0x48180b10 Data : 0x0000009f AW Phy Addr : 0x48180b10 Data : 0x000000fd data 2

    BW Phy Addr : 0x4818050c Data : 0x00000001 AW Phy Addr : 0x4818050c Data : 0x00000002 data 2

    BW Phy Addr : 0x48180554 Data : 0x00070000 AW Phy Addr : 0x48180554 Data : 0x00070002

    Phy Addr : 0x4818050c Data : 0x00007f02 Phy Addr : 0x4818050c Data : 0x00007f02

    Phy Addr : 0x4818050c Data : 0x00007f02 Phy Addr : 0x4818050c Data : 0x00007f02

    Phy Addr : 0x4818050c Data : 0x00007f02 Phy Addr : 0x4818050c Data : 0x00007f02

    how do you resolve this problem? thanks.

  • 0 in reply to jianfa zhou
    Prodigy 35 points

    Hi zhou,

    I running "fullfeature" mode is ok. Please ensure to run same uboot with same mode build for "full feature". When i running "low power" always have the issue, i dont know the reason.

    Regards

  • 0 in reply to bo guo1
    Intellectual 320 points

    如何按照手册上的步骤来制作jffs2文件系统，u-boot环境变量没搞错的话应该是能启动的。不知道你用的制作命令是否正确。

  • 0 in reply to bo guo1
    Mastermind 8715 points

    Hi bo guo,

               U need to ensure that full-feature u-boot is used to Run Ful-feature  RDK, & lowpower mode u-boot is used to run low-power mode Enabled RDK(SW).

    any kind of mismatch in the modes of u-boot & ur RDK build cause this problem.

    Waht Mr. suggesting is absolutely right. I encountered the similar problem sometime back and got solved :)

    Regards

    Ravikiran

  • 0
    Prodigy 165 points

    Today, I meet this problem. You should chang  bootcmd

    setenv bootcmd 'ipnc_ff_init 1;nboot 0x81000000 0 0x280000;bootm';saveenv

    (this is for full feature)

    to

    setenv bootcmd 'ipnc_ff_init 0;tftpboot 0x81000000 0 0x280000;bootm';saveenv

    (this is for lowpower)

    there will be no such printed information.

     

    if you can only see all black picture, you should delete old configuration files on camera. In console type :     rm  /mnt/nand/*   , then reboot.