From: Joe Steeve <joe@sliceware.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] environment problem with new board
Date: Thu, 23 Nov 2006 00:37:26 +0530 [thread overview]
Message-ID: <45649FEE.6030107@sliceware.com> (raw)
In-Reply-To: <20061122175836.A78A6353A56@atlas.denx.de>
Wolfgang Denk wrote:
>> that works apart from 'help' is 'version' :P I think I screwed something
>> with the cmdtbl. I've a slightly messed up u-boot.lds where all input
>> sections (.text, .data, .rodata*, . u_boot_cmd,..) in one huge section.
> You're meddling with a lot of pretty critical places all at once. I
> wouldn't do that, if I were you. I see no reason to mess with the
> linker script, for example.
I had to do that because., the boot code starts executing at 0x40000000
which is a ROM., and the DRAM is at 0x90000000. So., the startup
relocation code is linked at 0x40000000 while the relocatable code (the
rest of u-boot) is linked at 0x90000000. In the startup code., i move
u-boot out to the DRAM and transfer control to 'start_armboot' in
lib_arm/board.c
All existing linker scripts start at one constant address., and so have
no issues. Anywayz., I figured the problem is not with the linker
script., but something weird with the macros.
For example., I checked using #error messages and found that the
following '#if' in common/cmd_mem.c is failing.,
#if (CONFIG_COMMANDS & (CFG_CMD_MEMORY | \
CFG_CMD_I2C | \
CFG_CMD_ITEST | \
CFG_CMD_PCI | \
CMD_CMD_PORTIO ) )
I have '#define CONFIG_COMMANDS CFG_CMD_ALL' in my configs/myboard.h.
I'm quite confused how the compiler did not throw an error. When
compiling common/cmd_mem.c, the first header to be included is the
config.h, in which CFG_CMD_ALL is used but not defined. I found that it
is defined in include/cmd_confdefs.h. Should I be including this header
in the configs/myboard.h?
--
Joe Steeve
Sliceware Private Limited
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20061123/04761734/attachment.pgp
next prev parent reply other threads:[~2006-11-22 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 4:01 [U-Boot-Users] environment problem with new board Joe Steeve
2006-11-22 8:34 ` Wolfgang Denk
2006-11-22 14:08 ` Joe Steeve
2006-11-22 17:58 ` Wolfgang Denk
2006-11-22 19:07 ` Joe Steeve [this message]
2006-11-22 20:04 ` Wolfgang Denk
2006-11-23 0:23 ` [U-Boot-Users] PCI Initialization for AMCC440EP Pras
2006-11-23 1:41 ` Wolfgang Denk
2006-11-23 1:10 ` [U-Boot-Users] environment problem with new board Joe Steeve
2006-11-23 1:16 ` Joe Steeve
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=45649FEE.6030107@sliceware.com \
--to=joe@sliceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox