All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mehul Gohel <mehul.gohel@einfochips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Detailed documents......
Date: Sat, 18 Mar 2006 11:19:37 +0000	[thread overview]
Message-ID: <441BECC9.10204@einfochips.com> (raw)
In-Reply-To: <20060317210631.DB7F3352B33@atlas.denx.de>

Wolfgang Denk wrote:

>In message <E1FKDWn-00029C-Df@mail.sourceforge.net> you wrote:
>  
>
>>    I am fresh engineer in this field working with DM6446 EVM DAVINCI board
>>which contains DSP as well ARMEJ9. I need to bring that board up. I don't
>>have any experience of how to load the boot loader, how the things goes
>>after boot loader get loaded, so and so. I am working by reading all the
>>document in u-boot source tree and going through the code of u-boot-1.1.3.
>>    
>>
>
>Why are you starting with OLD code? Please use the top of  tree  from
>the git repository instead!
>
>  
>
>>am confused that how to write the image in NAND FLASH, thats why I am using
>>the other option and that is to download the boot image from UART where one
>>host utility will be runing on the host PC that does few handshaking with
>>board's primary boot loader and than downloads secondry boot loader from the
>>host PC.
>>    
>>
>
>You should really start reading the FAQ.
>
>  
>
>>Content-Type: text/html;
>>	charset="us-ascii"
>>Content-Transfer-Encoding: quoted-printable
>>    
>>
>
>And NEVER post HTML!
>
>Best regards,
>
>Wolfgang Denk
>
>  
>
well sorry for posting mail in HTML, I've started compiling uboot and at 
the first instant I am getting error something like

[root at localhost u-boot-1.1.3]# make davinci_config
Configuring for davinci board...
[root at localhost u-boot-1.1.3]# make all
make[1]: Entering directory `/home/mehulgohel/u-boot-1.1.3/tools'
make[1]: `.depend' is up to date.
make[1]: Leaving directory `/home/mehulgohel/u-boot-1.1.3/tools'
make[1]: Entering directory `/home/mehulgohel/u-boot-1.1.3/examples'
make[1]: `.depend' is up to date.
make[1]: Leaving directory `/home/mehulgohel/u-boot-1.1.3/examples'
make[1]: Entering directory `/home/mehulgohel/u-boot-1.1.3/post'
make[1]: `.depend' is up to date.
make[1]: Leaving directory `/home/mehulgohel/u-boot-1.1.3/post'
make[1]: Entering directory `/home/mehulgohel/u-boot-1.1.3/post/cpu'
make[1]: *** No rule to make target `asm.S', needed by `.depend'.  Stop.
make[1]: Leaving directory `/home/mehulgohel/u-boot-1.1.3/post/cpu'
make: *** [depend] Error 2
[root at localhost u-boot-1.1.3]#

Did I went wrong any where, I've not touched anything else not any 
configuration parameter or anything,.

Regards,
    Mehul Gohel  .
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mehul.gohel.vcf
Type: text/x-vcard
Size: 152 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20060318/89150ddf/attachment.vcf 

  reply	other threads:[~2006-03-18 11:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 11:57 [U-Boot-Users] Detailed documents Mehul Gohel
2006-03-17 21:06 ` Wolfgang Denk
2006-03-18 11:19   ` Mehul Gohel [this message]
2006-03-18  9:26     ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2006-03-29 23:45 Truong, Loc
2006-03-30  0:30 ` Wolfgang Denk
2006-03-30 14:55 Truong, Loc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=441BECC9.10204@einfochips.com \
    --to=mehul.gohel@einfochips.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.