• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 97 subscribers
  • Views 404 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.

AM62A7: AM62A LP u-boot ethaddr value is different from the value written on the EVK circuit board.

song minho
Prodigy 20 points
Part Number: AM62A7

Hello, I am developing an AM62A SKEVM board.

I found something strange while working on it.

The MAC address written on the Ethernet connector and the ethaddr address shown in the U-BOOT are different.

Please help me.

  • 0
    TI__Mastermind 40080 points

    Hi,

    Could you please share the two MAC addresses that you see? I don't have a board handy at the moment to reproduce the problem you see. Why I am asking is I am curious if both addresses were purchased by TI or if one is a random number.

    Other than the two addresses not matching what is the concern that you have? 

    Which TI SDK are you using and are you using the pre-built images from that SDK.

    Best Regards,

    Schuyler

  • 0 in reply to Schuyler Patton
    Prodigy 20 points

    Hi,

    The MAC address attached to the LAN connector on the motherboard is 70 FF 761F 1E 0C.

    However, the MAC address displayed through the U-BOOT is 1c:63:49:17:20:08.

    The firmware image is the prebuild image contained in the SDK.

    I read eeprom with the i2c command, but the MAC address was only 70 FF 761F 1E 0C written on the board.

    Thank you for your interest.

  • +1 in reply to song minho
    TI__Mastermind 40080 points

    Hi,

    Thank you for posting the different MAC addresses.

    Both MAC addresses were purchased by TI. As you have noticed the EEPROM MAC address matches the label on the board. u-boot is using is the internal one that is programmed as the device is tested. 

    You can verify the 1c:63:49:17:20:08 MAC address is internal to the device by using the devmem2 command:

    devmem2 0x43000200 --- this is the least significant 4 bytes of the MAC address

    devmem2 0x43000204 --- this is the most significant 2 bytes of the MAC address

    The reason for the two addresses is that U-Boot as it boots reads the EEPROM MAC address it is passed to the kernel as a boot parameter. This serves as an example on how to read in a MAC addresses so when you design your board you do not have to use the MAC address in the device but rather one your company may purchase.

    Best Regards,

    Schuyler

  • 0 in reply to Schuyler Patton
    Prodigy 20 points

    Thank you. Thanks to you, my curiosity has been solved.

    An error occurs when trying to read the corresponding area with the "md" command of the U-BOOT, is it blocked by the security function?

    If it's a security function, is it ATF?

  • +1 in reply to song minho
    TI__Mastermind 40080 points

    Hi, 

    Could you please post the console log showing this issue?

    Best Regards,

    Schuyler

  • 0 in reply to Schuyler Patton
    Prodigy 20 points

    I'm sorry.
    I think there was a mistake the other day.
    It works well now.
    Thank you.

    U-Boot SPL 2023.04-dirty (Dec 11 2023 - 08:55:53 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.5--v09.01.05 (Kool Koala)')
    am62a_init: board_init_f done
    SPL initial stack usage: 17032 bytes
    am62a_init: spl_boot_device: devstat = 0x24b bootmedia = 0x9 bootindex = 0
    Trying to boot from MMC1
    am62a_init: spl_boot_device: devstat = 0x24b bootmedia = 0x9 bootindex = 0
    Authentication passed
    am62a_init: spl_boot_device: devstat = 0x24b bootmedia = 0x9 bootindex = 0
    Authentication passed
    am62a_init: spl_boot_device: devstat = 0x24b bootmedia = 0x9 bootindex = 0
    Authentication passed
    am62a_init: spl_boot_device: devstat = 0x24b bootmedia = 0x9 bootindex = 0
    Authentication passed
    am62a_init: spl_boot_device: devstat = 0x24b bootmedia = 0x9 bootindex = 0
    Authentication passed
    Starting ATF on ARM64 core...

    NOTICE: BL31: v2.9.0 (release):v2.10-rc0-4-g5e52433dd
    NOTICE: BL31: Built : 09:10:56, Nov 14 2023
    ERROR: Failed to get response (-19)
    ERROR: Transfer send failed (-19)
    ERROR: Unable to query firmware capabilities (-19)
    I/TC:
    I/TC: OP-TEE version: 4.0.0-54-gb501c0084 (gcc version 11.3.1 20220712 (Arm GNU Toolchain 11.3.Rel1)) #1 Tue Nov 14 05:02:26 UTC 2023 aarch64
    I/TC: WARNING: This OP-TEE configuration might be insecure!
    I/TC: WARNING: Please check optee.readthedocs.io/.../porting_guidelines.html
    I/TC: Primary CPU initializing
    I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.5--v09.01.05 (Kool Koala)')
    I/TC: HUK Initialized
    I/TC: Activated SA2UL device
    I/TC: Enabled firewalls for SA2UL TRNG device
    I/TC: SA2UL TRNG initialized
    I/TC: SA2UL Drivers initialized
    I/TC: Primary CPU switching to normal world boot

    U-Boot SPL 2023.04-dirty (Dec 11 2023 - 08:56:02 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.5--v09.01.05 (Kool Koala)')
    am62a_init: board_init_f done
    am62a_init: spl_boot_device: devstat = 0x24b bootmedia = 0x9 bootindex = 0
    Trying to boot from MMC1
    am62a_init: spl_boot_device: devstat = 0x24b bootmedia = 0x9 bootindex = 0
    Authentication passed
    am62a_init: spl_boot_device: devstat = 0x24b bootmedia = 0x9 bootindex = 0
    Authentication passed


    U-Boot 2023.04-dirty (Dec 11 2023 - 08:56:02 +0000)

    SoC: AM62AX SR1.0 HS-FS
    Model: Texas Instruments AM62A7 SK
    DRAM: 2 GiB (effective 4 GiB)
    Core: 58 devices, 28 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
    =>
    =>
    =>
    => md 0x43000200 1
    43000200: 49172008 . .I
    => md 0x43000204 1
    43000204: 00001c63 c...
    =>