From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Steeve Date: Wed, 22 Nov 2006 19:38:28 +0530 Subject: [U-Boot-Users] environment problem with new board In-Reply-To: <20061122083448.CE392353A56@atlas.denx.de> References: <20061122083448.CE392353A56@atlas.denx.de> Message-ID: <456459DC.7020905@sliceware.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Wolfgang Denk wrote: >> I managed to get u-boot to the prompt :) However., a 'printenv' >> dumps garbage on the console. I've been slightly clueless as to >> where to look > > Is anything else working? Does "md" work as expected? Can you "cp" > data fromone part of the RAM to the other, and verify that it gets > copied ok? When i try those commands i get an 'unknown command'. The only thing 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. So., maybe something is going wrong with it. I'm going to split up the sections like on the other boards and see if that makes a difference. The following is the relevant part of the map file (the whole thing is a part of the .text section of the output file..). 0x9100abb0 __u_boot_cmd_start = . *(.u_boot_cmd) .u_boot_cmd 0x9100abb0 0x30 common/libcommon.a(cmd_boot.o) 0x9100abb0 __u_boot_cmd_reset 0x9100abc8 __u_boot_cmd_go .u_boot_cmd 0x9100abe0 0x18 common/libcommon.a(cmd_bootm.o) 0x9100abe0 __u_boot_cmd_bootm .u_boot_cmd 0x9100abf8 0x48 common/libcommon.a(cmd_nvedit.o) 0x9100abf8 __u_boot_cmd_saveenv 0x9100ac28 __u_boot_cmd_printenv 0x9100ac10 __u_boot_cmd_setenv .u_boot_cmd 0x9100ac40 0x48 common/libcommon.a(command.o) 0x9100ac40 __u_boot_cmd_question_mark 0x9100ac70 __u_boot_cmd_version 0x9100ac58 __u_boot_cmd_help 0x9100ac88 __u_boot_cmd_end = . >> in the sources. Any pointers would be of help. I'm defining >> 'CFG_ENV_IS_NOWHERE'. > > Why are you doing this? Basically., I just want a default environment which was defined at compile time (for starters). I thought I'll get the basic functionality working before getting all the features to work. Finally the bootloader is going to sit inside an SPI-EPROM (SST25). >> Is this right?? > > No. You don't provide much information, but my first guess is that > you have RAM problems. [Yes, that's always my first guess. But I > know that this is the cause of 99% of all initial problems.] Hmm., right now I already have a proprietary bootloader sitting in the EPROM. I'm making that bootloader load the u-boot image in the right place and transfer control to it. So., I dont see how the RAM could be a problem. However., I dont do a 'dram memory test yet' in the code., I think I should do that to verify things are actually fine. -- 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/20061122/abd00b93/attachment.pgp