• State Answer Suggested
  • Locked Locked
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 100 subscribers
  • Views 2123 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.

Linux hangs after Starting kernel ...message

Ashwani
Expert 1365 points 


Hi,

We are using Leopard TMS320DM365 based board. We have downloaded RidgeRun Leopard Board DM365 Evaluation SDK from RidgeRun download centre.
We are able to get u-boot prompt.The serial console is working fine.


Now we want to run Linux from u-boot prompt (using bootm). We have followed the following process:

1. Load the uImage via TFTP transfer uImage to suitable memory location. 

 	DM365_WebCam>tftp 0x82000000 kernel.uImage.root.leopard        

	TFTP from server 192.168.1.25; our IP address is 192.168.1.101                              
	Filename 'kernel.uImage.root.leopard'.                          
	Load address: 0x82000000                                                                   

	Loading: #################################################################
        	 #################################################################
	         #################################################################

        	 #################################################################
	         #################################################################
	         #################################################################

        	 #################################################################
	         #################################################################
	         #################################################################

        	 #################################################################
	         #################################################################
        	 #################################################################

	         #################################################################
        	 ####################
	done
	Bytes transferred = 4427968 (4390c0 hex)

2.  When we execute "bootm 0x82000000" command it gives the "Starting kernel ...". After that nothing is printed in the serial console.


	DM365_WebCam>bootm 0x82000000
	## Booting kernel from Legacy Image at 82000000 ...
	Image Name:   "RR Linux Kernel"
	Image Type:   ARM Linux Kernel Image (uncompressed)

        Data Size:    4427904 Bytes =  4.2 MB
        Load Address: 80008000
        Entry Point:  80008000
        Verifying Checksum ... OK
        Loading Kernel Image ... OK
        OK

Starting kernel ...


Note: I use the following boot arguments:
bootargs=mem=60M console=ttyS0,115200n8 root=/dev/nfs rw nfsroot=192.168.1.25:/home/ashwani/project/dm365_ridgerun/backup/trunk/fs/fs



Pls help me where should I investigate to get Linux serial data.


  • 0
    TI__Expert 6850 points

    Given that you are not using a TI hardware development board or the software associated with such, you would be better served to ask your question over on the Leopard Imaging or RIdge Run support forums.  They should be better equipped to handle your questions.  Thanks.

  • 0
    Genius 5240 points

    I had the same problem when I created my own Linux configuration for our board.  So you may had run into the same problem.  Here's the issue.....

    In u-boot there is a section of code that loads a number that represents the "machine type" in a variation that's passed to the kernel.  It's not in "bootargs".  When I created a new configuration for my board, I also created a new machine type.  But the machine type the kernel was trying to run according to u-boot was the EVM.  So the kernel hangs after the starting message.

    You need to find out if the Leopard board uses a different machine type.  It would be in the kernel source.  Then make sure that u-boot is loading that machine.

    John A

  • 0 in reply to John Anderson
    Expert 1365 points

    Hi John,

    Thanks.


    After changing the machine type; kernel able to booting but stop after some time.

    The last lines of booting message as follows:

    davinci_emac_probe: using random MAC addr: fe:54:c9:7a:42:be                               
    emac-mii: probed                                              
    Looking up port of RPC 100003/2 on 192.168.1.199
    rpcbind: server 192.168.1.199 not responding, timed out
    Root-NFS: Unable to get nfsd port number from server, using default
    Looking up port of RPC 100005/1 on 192.168.1.199
    rpcbind: server 192.168.1.199 not responding, timed out
    Root-NFS: Unable to get mountd port number from server, using default
    Root-NFS: Server returned error -5 while mounting /home/ashwani/project/leopard/filesys
    VFS: Unable to mount root fs via NFS, trying floppy.
    VFS: Cannot open root device "nfs" or unknown-block(2,0)
    Please append a correct "root=" boot option; here are the available partitions:
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
    Backtrace:

    I  checked on host machine, NFS server running properly.

     

    Could you please help me to solve this problem?


     

     

     

     

     

     

     

     

     

     

     

  • 0 in reply to Ashwani
    Genius 5240 points

    The NFS server in the listing doesn't match the bootargs in your initial post.  It appears that you aren't properly specifying your NFS server or the location of the file system.  You need to post your current bootargs.

     

    John A

  • 0 in reply to John Anderson
    Expert 1365 points

    Hi John,

    Below are the bootargs and corresponding boot messages (few last lines)

    bootargs=mem=60M console=ttyS0,115200n8 root=/dev/nfs rw nfsroot=192.168.1.199:/home/ashwani/project/dm365_ridgerun/backup/trunk/fs/fs nolock eth=02:00:10:00
    :00:05

     

    davinci_emac_probe: using random MAC addr: 72:8f:66:09:8e:cb
    emac-mii: probed
    Looking up port of RPC 100003/2 on 192.168.1.199
    rpcbind: server 192.168.1.199 not responding, timed out
    Root-NFS: Unable to get nfsd port number from server, using default
    Looking up port of RPC 100005/1 on 192.168.1.199
    rpcbind: server 192.168.1.199 not responding, timed out
    Root-NFS: Unable to get mountd port number from server, using default
    Root-NFS: Server returned error -5 while mounting /home/ashwani/project/dm365_ridgerun/backup/trunk/fs/fs
    VFS: Unable to mount root fs via NFS, trying floppy.
    VFS: Cannot open root device "nfs" or unknown-block(2,0)
    Please append a correct "root=" boot option; here are the available partitions:
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
    Backtrace:
    [<c002f700>] (dump_backtrace+0x0/0x110) from [<c002f844>] (dump_stack+0x18/0x1c)
     r6:c0025850 r5:c042e5e4 r4:c2029f58
    [<c002f82c>] (dump_stack+0x0/0x1c) from [<c0040a0c>] (panic+0x54/0x134)
    [<c00409b8>] (panic+0x0/0x134) from [<c0008fec>] (mount_block_root+0x1d4/0x21c)
     r3:00000001 r2:c2028000 r1:c2029f58 r0:c0393a64
    [<c0008e18>] (mount_block_root+0x0/0x21c) from [<c00090f8>] (mount_root+0xc4/0xfc)
    [<c0009034>] (mount_root+0x0/0xfc) from [<c000929c>] (prepare_namespace+0x16c/0x1d0)
     r5:c0025808 r4:c042e0b8
    [<c0009130>] (prepare_namespace+0x0/0x1d0) from [<c00087d8>] (kernel_init+0xdc/0x110)
     r5:c002411c r4:c042de98
    [<c00086fc>] (kernel_init+0x0/0x110) from [<c0043c2c>] (do_exit+0x0/0x654)
     r5:00000000 r4:00000000

     

     

    Regards

    Ashwani

  • 0 in reply to Ashwani
    Genius 5240 points

    Did you put the RFS in the /etc/exports file and restart NFS?  It looks like NFS isn't even responding according to your messages. Tthe problem appears to be on your NFS server.

    John A

  • 0 in reply to John Anderson
    Expert 1365 points

    Hi John,

    After reinstalling the NFS server, it start working.

    Thanks for you support.

    But nothing is display on screen.

    Inside Architecture configurations setting as follows:
                  Video Output : Composite
                  Video Default Resolution : NTSC

    and Boot argument:
      video=davincifb:vid0=1280x720x16,5529K:vid1=1280x720x16,5529K:osd0=720x576x16,2025K
      davinci_enc_mngr.ch0_output=COMPOSITE


    Please help me where should I investigate to get display.

  • 0 in reply to Ashwani
    Genius 5240 points

    Ashwani,

    Here is the bootargs for my board....

    setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=192.168.1.5:::255.255.240.0:vcxnexus:eth0:off root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=80M video=davincifb:vid0=OFF:vid1=OFF:osd0=720x576x16,4050K dm365_imp.oper_mode=0 davinci_capture.device_type=4

    I working on our own board now and not the EVM.  Right now I'm only doing encoding and it's on the composite input w/ NTSC standard.  I know previously when I was working on the DM365EVM I was seeing output on the composite out.  My application was sending the captured video to the output.  I eliminated that because I was taking a performance hit.

    When my kernel boots I see the following messages in the listing....

    dw365_afew_hw_init

    ch0 default output "COMPOSITE", mode "NTSC"

    Could the reason nothing is displayed on the screen be that you haven't run any application?

    John A

  • 0 in reply to Ashwani
    Prodigy 50 points

    I have the same problem ,how did you change the "machine type"?

    gdutdongjiu411@hotmail.com

  • 0 in reply to Ashwani
    Prodigy 50 points

    i found the machine type in uboot is the same as in the kernel ,but my kernel still hangs in Starting kernel ... ,  do you know why ?

  • 0 in reply to jim liang59064
    Expert 1365 points

    Hi Jim,

     

    What is ur bootargs?