Hi,
For configuration (1), you could try the command setenv bootcmd 'tftpboot'
followed by 'saveenv' and 'reset'. Make sure the tftp server is running on
192.168.1.53 (your server).
I don't really use dhcp and hence, no clues for (2).
-Gijo
2008/3/26 António Silva <[EMAIL PROTECTED]>:
> Hi all
Hi Gijo,
I tried your suggestion and in fact the tftp server is now working, the
result i get is
DM355 EVM # boot
TFTP from server 192.168.1.53; our IP address is 192.168.1.10
Filename 'uImage-dm355'.
Load address: 0x8070
Loading: #
C: (321) 426-6799
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gijo Prems
Sent: Wednesday, March 26, 2008 8:49 AM
To: António Silva
Cc: davinci-linux-open-source@linux.davincidsp.com
Subject: Re: Problem booting dm355 via TFTP
Hi,
For configura
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gijo Prems
Sent: 26 March 2008 12:49
To: António Silva
Cc: davinci-linux-open-source@linux.davincidsp.com
Subject: Re: Problem booting dm355 via TFTP
Hi,
For configuration (1), you could try the command setenv bootcmd 'tftpboot&
Hi Antonio,
You can issue the command 'bootm' with loaded memory location to boot-up the
new kernel. Otherwise you can write it to the NAND and boot from there.
-Gijo
On Wed, Mar 26, 2008 at 2:10 PM, António Silva <[EMAIL PROTECTED]>
wrote:
> Hi Gijo,
>
> I tried your suggestion and in fact the
