From mboxrd@z Thu Jan  1 00:00:00 1970
From: Reinhard Meyer <u-boot@emk-elektronik.de>
Date: Mon, 11 Apr 2011 12:11:58 +0200
Subject: [U-Boot] U-Boot support for board(s) meesc, otc570
In-Reply-To: <4D3D64E4.3060401@esd.eu>
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>
	<4D394DDD.5020304@esd.eu> <4D3D64E4.3060401@esd.eu>
Message-ID: <4DA2D3EE.80001@emk-elektronik.de>
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

Dear Daniel Gorsulowski,

>>> 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.
>>
> 
> I have to correct myself.
> My board_init() and checkboard() fanctions are executed. But the board
> crashes, before misc_init_r() functions executes.
> (I guess, it crashes somwhere in board_init_f())
> I'll try to find out more infos. But without an appropriate opportunity
> to debug, it will be verry difficult.

Any updates on this patch yet?

Best Regards,

Reinhard