• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 1418 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:

Linux/PROCESSOR-SDK-AM335X: U-boot data abort

AM3352: U-Boot data abort

kashetty
Prodigy 160 points
Part Number: AM3352

Hi,

I am using U-Boot 2019.01 from ti-processor-sdk-linux-am335x-evm-06.00.00.07 on our custom board.

We are not using RTC. Hence I commented out all the RTC access related code from board.c file. I am getting following data abort error:

I am not using FDT booting. Anyway I have removed RTC node from am33xx.dtsi.

U-Boot SPL 2019.01-g8b90adfb16 (Mar 06 2020 - 14:13:42 +0530)
Trying to boot from MMC1


U-Boot 2019.01-g8b90adfb16 (Mar 06 2020 - 14:13:42 +0530)

CPU  : AM335X-GP rev 2.1
Model: TI AM335x EVM
DRAM:  1 GiB
NAND:  256 MiB
MMC:   OMAP SD/MMC: 0
Loading Environment from FAT... *** Warning - bad CRC, using default environment

<ethaddr> not set. Validating first E-fuse MAC
Returning from board_late_init *********
Net:   Returning from eth_post_probe() ****
eth0: ethernet@4a100000
Warning: usb_ether MAC addresses don't match:
Address in ROM is          de:ad:be:ef:00:01
Address in environment is  f4:84:4c:2f:a5:f8
Returning from eth_post_probe() ****
, eth1: usb_ether
data abort
pc : [<bff85134>]       lr : [<bff77753>]
reloc pc : [<8081c134>]       lr : [<8080e753>]
sp : bdf3a948  ip : bdf3a8a0     fp : 80800020
r10: 00000017  r9 : bdf48eb8     r8 : 81fffee0
r7 : bffcbd54  r6 : bffcbcbc     r5 : bffcbd58  r4 : 3f769000
r3 : 44e3e000  r2 : b0010000     r1 : bffcbd84  r0 : 00000000
Flags: nZcv  IRQs off  FIQs on  Mode SVC_32
Code: 44e3e000 83e70b13 95a4f1e0 4a064b05 (ba006e98)
Resetting CPU ...

resetting ...

I am able to boot successfully using U-Boot 2013 from ti sdk 7.0

What could be causing data abort error ?

Regards,

Pranay

  • 0
    TI__Guru 69602 points

    Hi Pranay,

    your crash dump contains r3 : 44e3e000 which is located in the RTC register range, so the crash may indeed have something to do with the RTC, meaning there could still be some stray access to the RTC register region.

    Did you make sure to have CONFIG_SPL_AM33XX_ENABLE_RTC32K_OSC turned off explicitly?

    Can you also please review this related thread and see if anything mentioned in there helps?
    https://e2e.ti.com/support/processors/f/791/t/679840

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 160 points

    Hi  Andreas,

    Thanks for the help. I have fixed the issue.

    I have disabled Enable support for checking boot count limit option in u-boot menuconfig.

    It can be found at Device Drivers --> Enable support for checking boot count limit

    This fixed my data abort issue and able to get the U-Boot prompt.

    Regards,

    Pranay