From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Gorsulowski Date: Thu, 23 Apr 2009 12:38:05 +0200 Subject: [U-Boot] Bug in new at91 clock framework? In-Reply-To: <20090422131402.GA29252@game.jcrosoft.org> References: <12391074912532-git-send-email-Daniel.Gorsulowski@esd.eu> <12391074972833-git-send-email-Daniel.Gorsulowski@esd.eu> <20090417060043.GN31923@game.jcrosoft.org> <49EEEE27.3040208@esd.eu> <20090422131402.GA29252@game.jcrosoft.org> Message-ID: <49F0450D.3080903@esd.eu> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Jean-Christophe PLAGNIOL-VILLARD schrieb: > On 12:15 Wed 22 Apr , Daniel Gorsulowski wrote: >> Hello Jean-Christophe, >> >> I'm not sure, but I think there is a bug in your new at91 clock framework. >> My board does only boot, if CONFIG_USB_ATMEL is defined. But the board does >> not have any usb-ports, so there is no need to define CONFIG_USB_ATMEL. >> The board is based on an Atmel AT91SAM9263 SoC. > I've seen in with the one on my clock branch > but if you use the one for the pull request normaly not > > I've test it on my 9263EK > > Best Regards, > J. > I'm working on git://git.denx.de/u-boot-at91.git branch clock I also have an AT91SAM9263-EK, but with a 16.0 MHz main oscillator. Everything is fine, as long as no changes were made. But if I undef CONFIG_USB_ATMEL and CONFIG_CMD_USB, the board does not boot. Only some cryptical characters appear after the "RomBOOT" term. It's the same behavior as on my own board. If i do the same on git://git.denx.de/u-boot.git branch master, everything works fine. (as well AT91SAM9263-EK as my board) Do you have any advice for debugging that problem? Best regards, Daniel Gorsulowski