From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Gorsulowski Date: Fri, 21 Jan 2011 10:11:57 +0100 Subject: [U-Boot] U-Boot support for board(s) meesc, otc570 In-Reply-To: <4D392AFC.6080200@emk-elektronik.de> References: <20101127215828.7CD40220233A@lilith> <4D072AED.6080703@esd.eu> <4D355CFC.5050806@esd.eu> <4D356200.5000801@aribaud.net> <4D3577A9.8050505@esd.eu> <4D3586D7.7040009@emk-elektronik.de> <4D37E8CE.5010404@esd.eu> <4D392AFC.6080200@emk-elektronik.de> Message-ID: <4D394DDD.5020304@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 Dear Reinhard, Reinhard Meyer wrote: > Dear Daniel Gorsulowski, >> Hello Reinhard, >> >> Reinhard Meyer wrote: >>> Dear Daniel Gorsulowski, > > ... > >>> The at91sam9260(9xe)ek board builds fine and works. >> >> I can confirm that. >> >>> Use that as a template or reference what to do. >>> You should *only* need to adapt board/*/files and your configs/.h >>> files. And of course updated entries in boards.cfg. >> >> Not quiet. I had to fix arch/arm/cpu/arm926ejs/at91/at91sam9263_devices.c >> additionally. > Yes, of course... I had only "reworked" the 9260 variant yet. You should > need > to change it similarly to at91sam9260_devices.c... >> >> With my adoptions, my boards builds fine. But they do not boot. >> Can you really confirm that the at91sam9260ek board boots? I have no >> chance to debug my problems, so I have no idea, why my boards does not >> boot. > Yes it does. > > What exactly does "does not boot" mean? No message at all? Yes, sorry for indefinite description... There is no message at all, except for bootrom 'RomBOOT' promt. > > Check that your AT91Bootstrap loads u-boot to a sane address not at the > very end > of DRAM, and that CONFIG_SYS_TEXT_BASE is exactly the address where > AT91Bootstrap > loads u-boot. (I changed AT91Bootstrap to load u-boot to the very begin > of DRAM > for our boards.) > I neither change the AT91Bootstrap nor the CONFIG_SYS_TEXT_BASE address, so the problem must be located elsewhere. Today I found out by GPIO debugging, that U-Boot seems to boot but prints its startup messages to wrong USART with proper baudrate. I'll try to find out, why there is no output on DBGU. >> >> Nevertheless, should I send my patches for reviewing? >> > > Of course. We might see something that helps you. Ok, I'll do so. > > Best Regards, > Reinhard > > > Best regards, Daniel Gorsulowski