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

OMAP35x EVM bootup

Annie Zhang
Intellectual 460 points


Hi,

I changed the uboot delay to 0 and I can not stopped in uBoot any more, so I reset my uboot envrionment variable to all zeros by doing the following: dd if=/dev/zero of=/dev/mtdblock2’. Now I try to set my boot environment variables to be able to boot up with 2 choices: 1) boot up from flash, 2) bootup to my Host via NFS using tftp, but neither of them were succeed. Boot up using TFTP to my host could not get the correct ip address: it shouwed the TFTP from server 0.10.17.100 which is wrong, but target IP address is 10.17.100.56 is correct, and boot up to flash got the folloiwng before Kernel PANIC:

List of all partitions:
1f00 512 mtdblock0 (driver?)
1f01 1792 mtdblock1 (driver?)
1f02 256 mtdblock2 (driver?)
1f03 5120 mtdblock3 (driver?)
1f04 254464 mtdblock4 (driver?)
No filesystem could mount root, tried: ext3 ext2 vfat msdos

I have the following environment varaibles set for uboot, did I miss any setups?

bootdelay=10                                                                                                             
baudrate=115200                                                                                                          
netmask=255.255.254.0                                                                                                    
bootfile="uImage"                                                                                                        
nfshost="10.17.100.173"                                                                                                  
get_kernel=run nand_kernel                                                                                               
nand_kernel=nand read.i 0x80000000 280000 220000                                                                         
myBootArgs="console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=10.17.100.173:/home/azhang/nfsdir/timeSysNfs,
nolock mem=99M mpurate=600 omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y"                      
serverip="10.17.100.173"                                                                                                 
myBoot=setenv bootargs $(myBootArgs);dhcp;bootm                                                                          
ethaddr=00:50:C2:7E:90:C6                                                                                                
bootargs_fs=mem=99M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootstype=jffs2 mpurate=600                   
boot_fs=run get_kernel;setenv bootargs $(bootargs_fs); bootm                                                             
bootcmd=run boot_fs                                                                                                      
ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:on                                                     
stdin=serial                                                                                                             
stdout=serial                                                                                                            
stderr=serial                

  • 0
    TI__Mastermind 41665 points

    Annie Zhang said:
    I changed the uboot delay to 0 and I can not stopped in uBoot any more, so I reset my uboot envrionment variable to all zeros by doing the following: dd if=/dev/zero of=/dev/mtdblock2’.

    Just a small comment on this, often U-Boot will let you interrupt the boot sequence by using a CTRL-C, if you get it before it actually branches into the Linux kernel (like while it is loading from TFTP or from NAND) you should be able to get the command prompt back with a delay of 0.

    Annie Zhang said:
    I have the following environment varaibles set for uboot, did I miss any setups?

    I think the problem is the double quotes " " that you have around some of the variables, if you do a printenv in U-Boot you should not see those quotes in the output. Essentially I would recommend going through with setenv and setting the values you have " " around without the " " to see if that helps.

  • 0 in reply to Bernie Thompson TI
    Intellectual 460 points

    Thanks. That was my problem - no " around the uboot environment variables. Thanks.

     

    Annie