From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Thu, 20 Nov 2014 13:08:47 +0100 Subject: [U-Boot] [PATCH v3 2/2] imx: fix exception vectors relocation in imx27 In-Reply-To: <546602A4.1030404@denx.de> 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> <546602A4.1030404@denx.de> Message-ID: <20141120130847.6bdcd7d2@lilith> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello Stefano, On Fri, 14 Nov 2014 14:24:52 +0100, Stefano Babic wrote: > 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. (thanks for applying my patch) Did you do the tests on i.MX35? Should there be a followup patch to fix i.MX35 as i.MX27 i now fixed? > Best regards, > Stefano Amicalement, -- Albert.