From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
Date: Wed, 2 Feb 2005 12:36:21 -0500
Subject: [U-Boot-Users] debug u-boot with BDI2000
In-Reply-To: <42010953.3010900@iskramedical.si>
References: <42010953.3010900@iskramedical.si>
Message-ID: <42010F95.4070709@smiths-aerospace.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hinko Kocevar wrote:
> Hi,
> 
> After solving early problem with target reset (cable fault) I'm ready to 
> do some real work!
> I order to debug u-boot startup and so on, do I have to enable/provide 
> some additional options when compiling u-boot for my target?
> 
> I've read the Debugging section in dulg manual, but it doesn't mention 
> anything like that - Just to make sure...
> 
> regards,
> hk

Just the standard ones for debugging: -g for symbolic support.

You may want to use -O0 to turn off optimization.  The linux kernel 
won't link when compiled with -O0 because the expected inlining doesn't 
happen (symptom: linking gives missing symbols) -- I don't recall if 
u-boot has that limitation too.

gvb