From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Babic Date: Fri, 14 Nov 2014 14:24:52 +0100 Subject: [U-Boot] [PATCH v3 2/2] imx: fix exception vectors relocation in imx27 In-Reply-To: <20141114131033.4c68d987@lilith> References: <1415897955-9676-1-git-send-email-albert.u.boot@aribaud.net> <1415897955-9676-3-git-send-email-albert.u.boot@aribaud.net> <5465C7B2.4010009@denx.de> <20141114124927.1bc01488@lilith> <20141114131033.4c68d987@lilith> Message-ID: <546602A4.1030404@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 Hi Albert, On 14/11/2014 13:10, Albert ARIBAUD wrote: >> I'll have a look at the i.MX25, i.MX31 and i.MX35 reference manuals, >> but at most that will only tell me if they have the same problem as >> i.MX27 has about ROM/RAM and low/high vectors; it probably won't tell >> me how their ROM code handles exceptions. > > According to the i.MX25, i.MX31 and i.MX35 RM, all three SoCs have ROM > at address 0x00000000 and no RAM at address 0xffff0000, so they most > certainly have the same kind of issue as i.MX27, but there is no > indication that the indirect vectors table is always the same, and it > is quite probable that it is located at a different place for each SoC. > > So in order to solve the issue, we would need a dump (or better yet a > disassembly) of ROM addresses 0x00000000 to 0x0000001F for each of the > three SoCs. > ok - I have a MX35 based board, and I can do some tests, maybe in the week-end. Best regards, Stefano -- ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================