summaryrefslogtreecommitdiff
path: root/examples/standalone
diff options
context:
space:
mode:
authorManfred Schlaegl <manfred.schlaegl@ginzinger.com>2017-05-10 13:41:32 (GMT)
committerTom Rini <trini@konsulko.com>2017-06-12 12:36:18 (GMT)
commitcdde7de0364ffa505d631b342f1a2fa729e8e67d (patch)
tree9a2af676c1ce879fcee5c0078317222e182721b6 /examples/standalone
parent8cb3ce64f936f5dedbcfc1935c5caf31bb682474 (diff)
downloadu-boot-cdde7de0364ffa505d631b342f1a2fa729e8e67d.tar.xz
ARM: fixed relocation using proper alignment
Using u-boot-2017.05 on i.MX6UL we ran into following problem: Initially U-Boot could be started normally. If we added one random command in configuration, the newly generated image hung at startup (last output was DRAM: 256 MiB). We tracked this down to a data abort within relocation (relocated_code). relocated_code in arch/arm/lib/relocate.S copies 8 bytes per loop iteration until the source pointer is equal to __image_copy_end. In a good case __image_copy_end was aligned to 8 bytes, so the loop stopped as suggested, but in an errornous case __image_copy_end was not aligned to 8 bytes, so the loop ran out of bounds and caused a data abort exception. This patches solves the issue by aligning __image_copy_end to 8 byte using the linker script related to arm. I don't know if it's the correct way to solve this, so some review would be very appreciated.
Diffstat (limited to 'examples/standalone')
0 files changed, 0 insertions, 0 deletions