From: Wolfgang Denk Date: Fri, 25 Feb 2005 08:51:47 +0100 Subject: [U-Boot-Users] Porting UBoot without UART In-Reply-To: Your message of "Thu, 24 Feb 2005 23:40:51 MST." <528646bc0502242240233e0d7f@mail.gmail.com> Message-ID: <20050225075152.8240FC1430@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 Dear Grant, in message <528646bc0502242240233e0d7f@mail.gmail.com> you wrote: > > > > Provide our own console functions. See common/console.c and > > > common/devices.c how it is initialized and used. > > > > Note thatt he "devices" are intialized pretty late in the boot > > sequence. Until then, all of the most of the important console > > messages have already beeen printed. > > >From the original post: "We're using some emulation box to develop our > SoC. Somehow the UART will the last component available for firmware > development." > > I don't think that is the situation that Shawn is describing. To me > it sounded like he is starting firmware development before all of the > functionality is delivered by the hardware engineers. I don't think You are right. Then Ladislav Michl suggested to use special console functions for output, which works, but misses most of the "interesting" startup messages which are printed long before the device funtions are installed. > that he is refering to initialization order. Shawn, could you please > clarify? Initialization order plays only a role here as a console device starts working too late. The native console port is the serial port. Best regards, Wolfgang Denk -- See us @ Embedded World, Nuremberg, Feb 22 - 24, Hall 10.0 Booth 310 Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de Cleverness and Style have no place in getting a project completed. -- Tom Christiansen