From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Babic Date: Thu, 08 Jul 2010 11:54:04 +0200 Subject: [U-Boot] davinci: lowlevel_init for davinci boards In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D9F0B6A87@dlee01.ent.ti.com> References: <4C34A48E.8030000@denx.de> <0554BEF07D437848AF01B9C9B5F0BC5D9F0B6A87@dlee01.ent.ti.com> Message-ID: <4C35A03C.6050409@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 Paulraj, Sandeep wrote: >> Hi, >> Hi, > > Yes the lowlevel_init.S is meant only for DM6446. > > Later TI decided to do all the low level init in the UBL for both > NAND and NOR boot modes. Thus the lowlevel_init.S actually became > redundant w.r.t to our most recent releases, but for legacy reasons > it continues to be present in U-Boot. Ok, I see, thanks. I have at the moment no other solution as to port the initialization of the processor (PLL,DDR2, etc.) into a specialized lowlevel_init.S for the DM365. I am quite unsure about the role of the RBL, too. I have assumed that the setup to access the AEMIF interface is provided only by setting the AECFG pins and the role of RBL is to copy the UBL into IRAM and start it. However, the RBL could initialize the processor in some way I do not know before loading the UBL and then I could get further problems due to a missing or wrong initialization that I have not seen in UBL. Do you know if the RBL is responsible to some further initialization before loading the UBL ? Best regards, Stefano Babic -- ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de =====================================================================