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.
These are debug prints and will not cause any issues, is there any error you are observing?
Regards,
Raghu
Please mark this reply as Verify Answer on this post if it answers the question.
On console will always print "Phy Addr : 0x4818050c Data : 0x00007f02" . The print will not stop! I think this problem is serious!
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"
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
how do you resolve this problem? thanks.
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
如何按照手册上的步骤来制作jffs2文件系统,u-boot环境变量没搞错的话应该是能启动的。不知道你用的制作命令是否正确。
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. Raghu Kudva suggesting is absolutely right. I encountered the similar problem sometime back and got solved :)
Ravikiran