• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 456 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.

IPNC 8127 bootup problem(2)

Ravikiran HV
Mastermind 8715 points

M trying to bringup IPNC 8127 using TFTP.

Have couple of problems listed here ..:)

1).

      system is able to pick uImage over TFTP and filesystem over NFS.

      after executing finish.sh, it goes for a continuous loop with below logs on console.....................
   

             Phy Addr : 0x4818050c Data : 0x00007b02
             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

I have to do a ^C interrupt to  get the login prompt on console....!!

What could be the reason?

I am using u-boot & uImage of version  DM8127_IPNC_3.00.00

2)

Whenever I try to stop @ the 2nd stage u-boot and give bootcmd, I observe the below msg.

Auto negotitation failed
Using cpsw device

What does it mean??

Thanks you very much ......:)



  • 0
    TI__Expert 8780 points

    Hi Ravikiran,

    For (1) can you check the bootcmd that was saved in the uboot environment variables. It seems that you may have flashed the binaries or low_power mode, but the bootcmd is for full_feature mode or vice versa.

    Regards

    Rajat

  • 0 in reply to Rajat Sagar
    Mastermind 8715 points

    Hi Rajat,

    I have Enabled Full feature mode in Rules.make as below

    IPNC_CONFIG := FULL_FEATURE

    Now build with make sysall.

    Flashed the generated u-boot.bin & u-boot.nand.(These binaries must be of full feature according to Rules.make !!)

    Saved bootcmd using this cmd. : setenv bootcmd 'ipnc_ff_init 1;tftpboot 0x81000000 uImage;bootm';saveenv

    I hope my complete setup is FULL_FEATURE setup now.!!

    But still m Facing the Issue <1> as mentioned above...!!

    Regards

    Ravikiran

  • 0 in reply to Ravikiran HV
    TI__Expert 8780 points

    Ravikiran,

    This is not expected! It seems that either environment variable is not taking affect or there could be an internal supply problem.

    Could you try the low power mode as well?

    Also, please do a 'nand scrub' and reflash the nand again with uboot, uImage and filesystem when you test.

    Regards

    Rajat

  • 0 in reply to Rajat Sagar
    Mastermind 8715 points

    Hi Rajat,

                Thank you for the support...!!

    Now I just re-flashed my u-boot.nand, u-boot.bin &  uImage to nand &  tried working with filesys over NFS. Really nice to See IPNC is up .. :)

    Earlier I flashed only u-boot.nand & u-boot.bin to IPNC & was trying uImage over TFTP and filesys over NFS, is that the problem?

    But I don't understand why kernel boot over TFTP should cause such problem? Amazed !!

    Regarding

    Ravikiran