Hi Viral sachde, Phil.

Thanks for your reply.

1) The printenv , was the cut and paste error.
Now I tried again, this time, the badmagic error is not, but stull its not
getting bootup

DM6467 EVM # printenv
bootdelay=3
baudrate=115200
ipaddr=192.168.1.201
setenv=bootcmd nboot 80700000 0 a0000
serverip=10.65.102.67
bootfile=/tftpboot/uImage
bootcmd=nboot 80700000 0 a0000
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:0e:99:02:b3:47
nfshost=10.65.102.67
rootpath=/home/Ramesh/workdir6467/filesys
bootargs=console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs
nfsroot=10.65.102.67:/home/Ramesh/workdir6467/filesys, nolock mem=120M
///////////////////////////////////

Now the result after the boot up is ,

DM6467 EVM # boot
Loading from NAND 128MiB 3,3V 8-bit, offset 0xa0000
   Image Name:   Linux-2.6.10_mvl401-davinci_evm
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1390892 Bytes =  1.3 MB
   Load Address: 80008000
   Entry Point:  80008000    // After this , the DM6467 EVM# prompt came.
DM6467 EVM #
//////////////////////////////////////////////////////////////////////////

Hi Phil,

I have done the 'saveenv' command before.  But I didnot understand your
word  "Given that the expansion is done prior to the 'saveenv' you might as
well just set bootargs statically." I m sorry for that.

What should be in bootcmd ?

Thanks
Ramesh.


On 9/29/08, Phil Quiney <[EMAIL PROTECTED]> wrote:
>
>  Hi,
>
> Actually, on giivng it a second thought, I think the lines
>
> setenv nfshost 10.65.103.160
>
> setenv rootpath /home/Ramesh/workdir6467/filesys
>
> setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs
> nfsroot=$(nfshost):$(rootpath), nolock mem=120M
>
>  ..will work if you keep typing them in each time as the 'setenv bootargs'
> will expand the current $nfshost & $rootpath. It would not work if you did a
> 'saveenv' and later tried to change 'nfshost' or 'rootpath' as the
> 'bootargs' variable has no variable part left. Given that the expansion is
> done prior to the 'saveenv' you might as well just set bootargs statically.
>
> Regards
>
> Phil Q
>
>
> Phil Quiney, Senior Software Engineer
> Trinity Convergence
> Cambridge Business Park
> Cowley Road
> Cambridge CB4 0WZ, UK
> T: +44(0)1223-435536
> F: +44(0)1223-435560
> www.trinityconvergence.com
>
>
>  ------------------------------
> *From:* davinci-linux-open-source-bounces+pquiney=trinityconvergence.com@
> linux.davincidsp.com 
> [mailto:davinci-linux-open-source-bounces+pquiney<davinci-linux-open-source-bounces%2Bpquiney>
> [EMAIL PROTECTED] *On Behalf Of *Phil Quiney
> *Sent:* 29 September 2008 08:56
> *To:* Viral Sachde; Ramesh
> *Cc:* [email protected]
> *Subject:* RE: EVM 6467 board doesnot bootup
>
>  Hi,
>
> Your u-boot parameters are truly broken.
>
> You have a 'setenv=bootcmd nboot 80700000 0 a0000' which is nonsense. I
> think that should have been bootcmd=nboot 80700000 0 a0000
>
> The reason it does not boot is because you have set 'bootcmd=bootm' As
> there is nothing in memory you get the bad magic number.
>
> If you set the bootcmd to nboot 80700000 0 a0000, I think it should at
> least try to boot.
>
> You then need to sort out the bootargs, as previously posted
> 'nfsroot=10.65M' is not right, it should be an IP address & path to the NFS
> root filesystem on your server.
>
> I guess this is either a cut'n'paste issue, or perhaps the terminal
> emulator is not wrapping long lines.
>
> Also you cannot put u-boot variables into the bootargs variable, they do
> not get expanded and the kernel will not know how to handle $(nfsroot) and
> $(rootpath). There is a 'trick' to do this that has been used on the
> DM6446.....
>
> bootcmd=setenv setboot setenv bootargs $(bootargs)
> video=dm64xxfb:output=$(videostd):format=component
> davinci-vpfe.device_type=1;run setboot;bootm 0x2200000
> All this did was allow the $(videostd) variable to be picked up at boot
> time - the 'run setboot' was the trick that caused bootargs to be reset with
> the expanded variables.
>
> So, you should now understand that your lines....
>
> setenv nfshost 10.65.103.160
>
> setenv rootpath /home/Ramesh/workdir6467/filesys
>
> setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs
> nfsroot=$(nfshost):$(rootpath), nolock mem=120M
>
> ...will not work.
>
>
>
> Regards
>
> Phil Q
>
> Phil Quiney, Senior Software Engineer
> Trinity Convergence
> Cambridge Business Park
> Cowley Road
> Cambridge CB4 0WZ, UK
> T: +44(0)1223-435536
> F: +44(0)1223-435560
> www.trinityconvergence.com
>
>
>  ------------------------------
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Viral
> Sachde
> *Sent:* 29 September 2008 07:14
> *To:* Ramesh
> *Cc:* [email protected]
> *Subject:* Re: EVM 6467 board doesnot bootup
>
>
>
> 2008/9/29 Ramesh <[EMAIL PROTECTED]>
>
>> Hi ,
>>
>> After I tried to run one demo code on DM6467, I am not able to boot up the
>> DM6467.
>>
>> ###########################################################
>> DM6467 EVM # printenv
>> bootdelay=3
>> baudrate=115200
>> ipaddr=192.168.1.201
>> setenv=bootcmd nboot 80700000 0 a0000
>> serverip=10.65.103.160
>> bootfile=uImage
>> nfshost=10.65.102.67
>> rootpath=/home/Ramesh/workdir6467/filesys
>> bootargs=console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs *
>> nfsroot=10.65Mstdin=serial*
>> stdout=serial
>> stderr=serial
>> ethaddr=00:0e:99:02:b3:47
>> bootcmd=bootm
>>
>>
>> DM6467 EVM # boot
>> ## Booting image at 80700000 ...
>> Bad Magic Number
>> DM6467 EVM # <INTERRUPT>
>>
>> ##########################################################
>> Board envirmental setup is
>>
>> setenv nfshost 10.65.103.160
>>
>> setenv rootpath /home/Ramesh/workdir6467/filesys
>>
>> setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs
>> nfsroot=$(nfshost):$(rootpath), nolock mem=120M
>> #########################################################################
>>
>> Please give me some idea to recover the board.
>>
>> Thanks
>> Ramesh.
>
>
>
> Check you bootargs, nfsroot parameter does not look correct.  "*
> nfsroot=10.65Mstdin=serial"
>
> *rgrds*
> *
> Viral
>
>
>>
>>
>>
>> _______________________________________________
>> Davinci-linux-open-source mailing list
>> [email protected]
>> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>>
>>
>
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to