From: Wolfgang Denk Date: Tue, 13 Jul 2004 09:25:44 +0200 Subject: [U-Boot-Users] Strange Problem Debugging U-Boot In-Reply-To: Your message of "Mon, 12 Jul 2004 17:36:28 PDT." <20040713003628.91372.qmail@web50507.mail.yahoo.com> Message-ID: <20040713072549.1EFF7C109F@atlas.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de In message <20040713003628.91372.qmail@web50507.mail.yahoo.com> you wrote: > > If I single step starting from 0x02000100 (my flash starts @ > 0x02000000) through to function void cpu_init_f (volatile immap_t * > immr) line # 177. It works ok, but if I "Cont" after starting from > 0x02000100, I get SIGABRT at line 177 of file u/mpc8xx/cpu_init.c. This probably means that your BDI2000 config file is not OK. > { line 177 is the actual line from u-boot-1.1.1 tree, line 181 which it > claims below is after I added few lines} Such reports are useless. Always quote the exact lines in text. > Actual line is code: > > /* now restrict to preliminary range */ > memctl->memc_br0 = CFG_BR0_PRELIM; > --->memctl->memc_or0 = CFG_OR0_PRELIM; This is much better. > Any idea what is going on here ? Read the comment in lines 127...141. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de If you fail to plan, plan to fail.