How to debug u-boot data abort

[qianfan]

在 2022/3/23 15:51, Abder 写道:
> Le mer. 23 mars 2022 à 03:28, qianfan <qianfanguijin at 163.com> a écrit :
>> Hi:
>>
>> I had a custom AM335X board connected my computer by usbnet. It always report
>> data abort when 'dhcp':
>>
>> Next it the log:
>>
>> U-Boot 2022.01-rc1-00183-gfa5b4e2d19-dirty (Feb 25 2022 - 15:45:02 +0800)
>>
>> CPU  : AM335X-GP rev 2.1
>> Model: WISDOM AM335X CCT
>> DRAM:  512 MiB
>> NAND:  256 MiB
>> MMC:   OMAP SD/MMC: 0
>> Loading Environment from NAND... *** Warning - bad CRC, using default environment
>>
>> Net:   Could not get PHY for ethernet at 4a100000: addr 0
>> eth2: ethernet at 4a100000, eth3: usb_ether
>> Hit any key to stop autoboot:  0
>> => setenv autoload no
>> => dhcp
>> using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
>> MAC de:ad:be:ef:00:01
>> HOST MAC de:ad:be:ef:00:00
>> RNDIS ready
>> musb-hdrc: peripheral reset irq lost!
>> high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
>> USB RNDIS network up!
>> BOOTP broadcast 1
>> BOOTP broadcast 2
>> BOOTP broadcast 3
>> DHCP client bound to address 192.168.200.4 (757 ms)
>> data abort
>> pc : [<9fe9b0a2>]          lr : [<9febbc3f>]
>> reloc pc : [<808130a2>]    lr : [<80833c3f>]
>> sp : 9de53410  ip : 9de53578     fp : 00000001
>> r10: 9de5345c  r9 : 9de67e80     r8 : 9febbae5
>> r7 : 9de72c30  r6 : 9feec710     r5 : 0000000d  r4 : 00000018
>> r3 : 3fdd8e04  r2 : 00000002     r1 : 9feec728  r0 : 9feec700
>> Flags: Nzcv  IRQs off  FIQs on  Mode SVC_32 (T)
>> Code: f023 0303 60ca 4403 (6091) 685a
>> Resetting CPU ...
>>
> Don't have any idea on what is causing the crash,  but to answer your
> question about debugging data abort :
> from the reg dump, you can look at the PC and LR registers to see the
> function that caused the crash (in PC) and its caller (in LR) by using
> the .map file (generated after compilation).
> use the values of pc and lr ante relocation (the 2nd ligne in the dump
> above: reloc pc ...)

Hi:

Thanks for your's guide. I had this data abort message:

data abort
pc : [<9ff8196c>]          lr : [<9ffa1cd7>]
reloc pc : [<8081496c>]    lr : [<80834cd7>]

and found the pc and lc address in u-boot.map:

  .text.env_attr_walk
                 0x0000000080834c54       0xb4 env/built-in.o
                 0x0000000080834c54                env_attr_walk
  .text.malloc   0x0000000080814900      0x420 common/built-in.o
                 0x0000000080814900                malloc

Is means that data abort when 'malloc' called from env_attr_walk? It's there has 
a better way that can dump stack?

>
> Regards
> --
> Abder
>
>> resetting ...
>>
>>
>> It's there has any doc about how to debug data abort? Or is the bug is already
>> fixed?
>>
>> Thanks