• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 335 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

AM3359: Could not able to compile u-boot images.

u-boot is getting failed with data abort

Rakshith kumar I M
Prodigy 40 points
Other Parts Discussed in Thread: AM3359

Hii Ti Support Team,

I am using AM3359 Based processor and i have generated  u-boot-spl.bin  and u-boot.img from u-boot SDK but When I loaded both images I got data abort error as shown below:

CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
U-Boot SPL 2019.01-g1ebdbc7-dirty (Jan 24 2023 - 13:33:31)
Load U-Boot image...
CxyzModem - CRC mode, 3(SOH)/371(STX)/0(CAN) packets, 4 retries
Loaded 379352 bytes


U-Boot SPL 2019.01-g1ebdbc7-dirty(Jan 24 2023 - 13:33:31)

I2C: ready
DRAM: 256 MiB
NAND: 256 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

data abort

MAYBE you should read doc/README.arm-unaligned-accesses

pc : [<8f761270>] lr : [<8f760d9c>]
sp : 8f32fe58 ip : 00000062 fp : 8f334be8
r10: 8f3327c8 r9 : 8f32ff38 r8 : 8f3327d0
r7 : 8f32fed4 r6 : 000000d6 r5 : 8f334bec r4 : 8f330008
r3 : 00000000 r2 : 00000001 r1 : 00000001 r0 : 00000000
Flags: NzCv IRQs off FIQs on Mode SVC_32
Resetting CPU ...

resetting ...

Pleaser Help us on this 

Thanks and Regards

Rakshith

  • 0
    TI__Guru 68670 points

    Hello,
    Do we have additional data points?
    - Full boot log?
    - Linux SDK version?
    - HW board under testing?
    Best,
    -Hong

  • 0 in reply to Hong Guan64
    Prodigy 40 points

    Hi Hong,

    Thank you for your quick response.

    We are using Linux SDK version :06.01 (ti-processor-sdk-linux-am335x-evm-06.01.00.08-Linux-x86-Install.bin file for Linux SDK) and Linux version 4.19.59-g5f8c1c6121.

    We are using AM3359 processor based custom board.

    please find the below complete U-Boot log print:

    CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
    U-Boot SPL 2019.01-g1ebdbc7-dirty(Jan 24 2023 - 13:33:31)
    Load U-Boot image...
    CxyzModem - CRC mode, 3(SOH)/371(STX)/0(CAN) packets, 4 retries
    Loaded 379352 bytes

    U-Boot 2019.01-g1ebdbc7-dirty(Jan 24 2023 - 13:33:31)

    I2C: ready
    DRAM: 256 MiB
    NAND: 256 MiB
    MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
    Using default environment

    data abort

    MAYBE you should read doc/README.arm-unaligned-accesses

    pc : [<8f761270>] lr : [<8f760d9c>]
    sp : 8f32fe58 ip : 00000062 fp : 8f334be8
    r10: 8f3327c8 r9 : 8f32ff38 r8 : 8f3327d0
    r7 : 8f32fed4 r6 : 000000d6 r5 : 8f334bec r4 : 8f330008
    r3 : 00000000 r2 : 00000001 r1 : 00000001 r0 : 00000000
    Flags: NzCv IRQs off FIQs on Mode SVC_32
    Resetting CPU ...

    resetting ...
    CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
    U-Boot SPL 2019.01-g1ebdbc7-dirty(Jan 24 2023 - 13:33:31)
    Load U-Boot image...
    CxyzModem - CRC mode, 3(SOH)/371(STX)/0(CAN) packets, 4 retries
    Loaded 379352 bytes

    U-Boot 2019.01-g1ebdbc7-dirty(Jan 24 2023 - 13:33:31)

    I2C: ready
    DRAM: 256 MiB
    NAND: 256 MiB
    MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
    Using default environment

    data abort

    MAYBE you should read doc/README.arm-unaligned-accesses

    pc : [<8f761270>] lr : [<8f760d9c>]
    sp : 8f32fe58 ip : 00000062 fp : 8f334be8
    r10: 8f3327c8 r9 : 8f32ff38 r8 : 8f3327d0
    r7 : 8f32fed4 r6 : 000000d6 r5 : 8f334bec r4 : 8f330008
    r3 : 00000000 r2 : 00000001 r1 : 00000001 r0 : 00000000
    Flags: NzCv IRQs off FIQs on Mode SVC_32
    Resetting CPU ...

    resetting ...
    CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
    U-Boot SPL 2019.01-g1ebdbc7-dirty(Jan 24 2023 - 13:33:31)
    Load U-Boot image...
    CxyzModem - CRC mode, 3(SOH)/371(STX)/0(CAN) packets, 4 retries
    Loaded 379352 bytes

    U-Boot 2019.01-g1ebdbc7-dirty(Jan 24 2023 - 13:33:31)

    I2C: ready
    DRAM: 256 MiB
    NAND: 256 MiB
    MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
    Using default environment

    data abort

    MAYBE you should read doc/README.arm-unaligned-accesses

    pc : [<8f761270>] lr : [<8f760d9c>]
    sp : 8f32fe58 ip : 00000062 fp : 8f334be8
    r10: 8f3327c8 r9 : 8f32ff38 r8 : 8f3327d0
    r7 : 8f32fed4 r6 : 000000d6 r5 : 8f334bec r4 : 8f330008
    r3 : 00000000 r2 : 00000001 r1 : 00000001 r0 : 00000000
    Flags: NzCv IRQs off FIQs on Mode SVC_32
    Resetting CPU ...

    resetting ...

    Regards,

    Rakshith