From mboxrd@z Thu Jan 1 00:00:00 1970 From: Clemens Koller Date: Wed, 04 Jul 2007 11:37:11 +0200 Subject: [U-Boot-Users] U-Boot-NG ? In-Reply-To: <20070703230932.GA11529@ld0162-tx32.am.freescale.net> References: <20070630020850.22A711B2CB9@mercury.denx.de> <20070702164755.GC3361@leda.ptxnet.pengutronix.de> <1183402971.3393.2.camel@loki> <1183406087.3393.11.camel@loki> <20070703110242.GG3361@leda.ptxnet.pengutronix.de> <46597312D56D2A47A3A6E9C1D0D9B7AEB0C4F2@kpladc0001.konzeptpark.intra> <20070703230932.GA11529@ld0162-tx32.am.freescale.net> Message-ID: <468B6A47.7030404@anagramm.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Scott Wood wrote: > 4. Include full console functionality in the wrapper, but only for debug > builds. A simple printf() really shouldn't be that big, anyway. This > also eliminates the need to get console information from the environment, > since you can hardcode it for debugging purposes. IMHO for board bring up, the very first thing a bootloader should do is some pin toggling! (ideally there is a LED connected to a pin...) to see if the board at least comes out of reset and starts at our code. And then to put out a counter, every time some initialization was finished until a console is initialized. I guess most of you came in contact with the Port 0x80 and beep POST codes: http://en.wikipedia.org/wiki/Power-on_self-test This would help all those without hardware debuggers connected to their board. Best regards, -- Clemens Koller __________________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Stra?e 45/1 Linhof Werksgel?nde D-81379 M?nchen Tel.089-741518-50 Fax 089-741518-19 http://www.anagramm-technology.com