AM625: sdk 10: u-boot: mii dump synchronous abort

Joshua Bourgeot

Part Number: AM625
Other Parts Discussed in Thread: AM62A7

Tool/software:

Hello,

We are trying to interface with the Ethernet registers in u-boot on the am62x and am62a starter kits. Attempting to access the registers while no ethernet cable is connected leads to a "Synchronous Abort" error which causes the som to reset. This is seen on booth the 62x and the 62a.

62x:

U-Boot SPL 2023.04-ti-g836606420854 (May 09 2024 - 05:42:45 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.8--v09.02.08 (Kool Koala)')
SPL initial stack usage: 13408 bytes
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE:  BL31: Built : 16:09:05, Feb  9 2024

U-Boot SPL 2023.04-ti-g836606420854 (May 09 2024 - 05:42:45 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.8--v09.02.08 (Kool Koala)')
SPL initial stack usage: 1856 bytes
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted


U-Boot 2023.04-ti-g836606420854 (May 09 2024 - 05:42:45 +0000)

SoC:   AM62X SR1.0 GP
Model: Texas Instruments AM625 SK
EEPROM not available at 80, trying to read at 81
Board: AM62-SKEVM rev E2
DRAM:  2 GiB
Core:  72 devices, 32 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0 
=> dhcp 
ethernet@8000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
=> mii dump 3 1 
"Synchronous Abort" handler, esr 0x02000000
elr: 0000000002ef9458 lr : 00000000808259ac (reloc)
elr: 0000000081d0f458 lr : 00000000ff63b9ac
x0 : 00000000fd5fa550 x1 : 0000000000000003
x2 : 00000000ffffffff x3 : 0000000000000001
x4 : 0000000081d0f458 x5 : 00000000fd6015e0
x6 : 0000000000000075 x7 : 0000000000000044
x8 : 0000000000000010 x9 : 0000000000000008
x10: 0000000000000001 x11: 0000000000000000
x12: 00000000ffffffff x13: 0000000000000000
x14: 00000000fd5e7820 x15: 0000000000000002
x16: 0000000081d0f458 x17: 0000000081d0cf98
x18: 00000000fd5f6d80 x19: 00000000fd5e6d68
x20: 0000000000000003 x21: 0000000000000001
x22: 0000000000000003 x23: 00000000fd5e6d68
x24: 0000000000000003 x25: 0000000000000000
x26: 0000000000000001 x27: 00000000ff6f4000
x28: 00000000fd615cd0 x29: 00000000fd5e6c70

Code: 00000000 00000000 81d0f288 00000000 (80c801d8) 
Resetting CPU ...

resetting ...

62a:

U-Boot SPL 2024.04-00052-gd8cef0b37a8-dirty (Oct 23 2024 - 08:44:53 -0400)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
SPL initial stack usage: 13568 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE:  BL31: Built : 16:09:05, Feb  9 2024

U-Boot SPL 2024.04-00052-gd8cef0b37a8-dirty (Oct 23 2024 - 08:45:05 -0400)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
Trying to boot from MMC2
Authentication passed
Authentication passed


U-Boot 2024.04-00052-gd8cef0b37a8-dirty (Oct 23 2024 - 08:45:05 -0400)

SoC:   AM62AX SR1.0 HS-FS
Model: Texas Instruments AM62A7 SK
DRAM:  2 GiB (effective 4 GiB)
Core:  87 devices, 30 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0 
=> dhcp
ethernet@8000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
=> mii dump 3 1
"Synchronous Abort" handler, esr 0x96000010, far 0x8000f80
elr: 000000008086237c lr : 0000000080862378 (reloc)
elr: 00000000fff3f37c lr : 00000000fff3f378
x0 : 0000000000085e2c x1 : 00000000000003e8
x2 : 00000000ffffffff x3 : 0000000000000001
x4 : 00000000fff3f4e8 x5 : 00000000fdea81e0
x6 : 0000000000000075 x7 : 0000000000000044
x8 : 0000000000000010 x9 : 0000000000000001
x10: 00000000fdebed38 x11: 00000000ffffffff
x12: 0000000000000000 x13: 00000000fde890e0
x14: 00000000ffffffff x15: 00000000fdec0f61
x16: 00000000fff3f4e8 x17: 0000000000000000
x18: 00000000fde9cda0 x19: 0000000000085e2c
x20: 0000000008000f00 x21: 0000000000000003
x22: 00000000fdea7f30 x23: 00000000fde88df8
x24: 0000000000000003 x25: 0000000000000000
x26: 0000000000000001 x27: 00000000fffe8000
x28: 00000000fdea8ef0 x29: 00000000fde88cb0

Code: aa0003f4 d2800000 940154c5 aa0003f3 (b9408280) 
Resetting CPU ...

resetting ...

Is this a known issue, or a configuration problem? How would we go about addressing this issue?

Thank you,

Joshua Bourgeot

10 months ago

0 Schuyler Patton 10 months ago

TI__Mastermind 40080 points

Hi,

I am away from my board at the moment, I will try to reproduce what your are experiencing on probably the AM62a board. I wanted to confirm you mean SOC instead of SOM and the boards you are working with are TI EVMs?

I am asking these questions since you are using PHY address 3, the only PHY configured I believe is PHY 0 on the TI EVM.

Best Regards,

Schuyler

0 Joshua Bourgeot 10 months ago in reply to Schuyler Patton

Prodigy 240 points

Hello Schuyler,

Yes, my apologies, we are doing this testing on the TI EVM, however we see the same issue on our custom SOM.

Thank you,

Joshua Bourgeot

0 Schuyler Patton 10 months ago in reply to Joshua Bourgeot

TI__Mastermind 40080 points

Hi Joshua,

Could you please try the following to see if you still experience the data abort? This example shows selecting the mii interface first prior to mii calls.

Best Regards,

Schuyler

0 Joshua Bourgeot 10 months ago in reply to Schuyler Patton

Prodigy 240 points

Hello Schuyler,

There does not appear to be an ethernet device. I'm not accustomed to seeing a "ethernet" device in this context either.

U-Boot 2024.04-ti-g818c76aed67f (Aug 01 2024 - 19:19:47 +0000)

SoC:   AM62AX SR1.0 HS-FS
Model: Texas Instruments AM62A7 SK
DRAM:  2 GiB (effective 4 GiB)
Core:  87 devices, 30 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0
=> mii device
MII devices: 'mdio@f00'
Current device: 'mdio@f00'
=> mii device ethernet@8000000port@1
No such device: ethernet@8000000port@1

Thank you,

Joshua Bourgeot

0 Schuyler Patton 10 months ago in reply to Joshua Bourgeot

TI__Mastermind 40080 points

Hi Joshua,

Is the above console log from a TI EVM? If so, which TI board? And TI SDK 10?

Best Regards,

Schuyler

0 Joshua Bourgeot 10 months ago in reply to Schuyler Patton

Prodigy 240 points

Hello Schuyler,

This log is from a TI EVM, specifically the AM62A7 Starter Kit. We are running the provided image for the TI SDK 10: https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-D37Ls3JjkT/10.00.00.08/tisdk-edgeai-image-am62a-evm.wic.xz

Thank you,

Joshua Bourgeot

0 Schuyler Patton 10 months ago in reply to Joshua Bourgeot

TI__Mastermind 40080 points

Hi Joshua,

OK, I was using the same board, but it an earlier SDK. I will try the later SDK. The fact you are not seeing an ethernet port on the TI EVM is odd. Is the TI EVM functioning as expected network wise when booted into Linux?

Best Regards,

Schuyler

0 Joshua Bourgeot 10 months ago in reply to Schuyler Patton

Prodigy 240 points

Hello Schuyler,

Yes, the network appears to be completely functional when booted into Linux, although I have not done extensive testing.

Thank you,

Joshua Bourgeot

0 Schuyler Patton 9 months ago in reply to Joshua Bourgeot

TI__Mastermind 40080 points

Hi Joshua,

I apologize for the delay. This issue you are seeing was reported over a year ago and an internal ticket was filed. Currently the ticket was not been resolved. This issue also is not limited to TI devices. This appears to be a common recovery method in u-boot for when the abort handler of u-boot is triggered. The handler will automatically reset the part so there is a recovery method from the error encountered. For example if I use do a md.l command of a bad address the abort handler resets the device.

Is there an issue for your application with the u-boot abort handler triggering a reset of the device?

Best Regards,

Schuyler

0 Joshua Bourgeot 9 months ago in reply to Schuyler Patton

Prodigy 240 points

Hello Schuyler,

Thank you for this information. I'm a little confused. Is the internal ticket just about the abort handler, or does it also include the mii dump failure? We are less concerned about the abort handler and more so what is causing it.

Thank you,

Joshua Bourgeot

0 Schuyler Patton 9 months ago in reply to Joshua Bourgeot

TI__Mastermind 40080 points

Hi Joshua,

The internal ticket was file to report the issue and put it in the queue for review.

The abort handler is the recovery mechanism that u-boot uses so from one perspective since u-boot is recovering this issue is not considered critical at the moment by the dev team.

Can you describe if this issue is impacting your product development? I reviewed the thread and this issue only happens when the cable is not plugged in?

Best Regards,

Schuyler

0 Joshua Bourgeot 9 months ago in reply to Schuyler Patton

Prodigy 240 points

Hello Schuyler,

Thank you for the clarification. This issue does not directly impact our product development yet, so as long as the issue is in queue, it is not a pressing concern.

Thank you,

Joshua Bourgeot

Processors

Processors forum

AM625: sdk 10: u-boot: mii dump synchronous abort