• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 100 subscribers
  • Views 632 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM6548: OSPI Boot issue

Artem Boyarchuk
Intellectual 370 points
Part Number: AM6548

Hello,

We are developing a custom device based on the AM6548 SR2.0 processor with OSPI flash MX66UM1G45G that connected as OSPI flash in dev board.

For development, we use the Linux SDK for AM65x 07_00_01

We have checked the flash in u-boot and linux, it works. We have flashed images (tiboot3.bin, tispl.bin, u-boot.img, sysfw.itb).

But when we try to boot from OSPI the board doesn't load. We set right boot configuration according to documentation. 

Could you tell us what might be causing this problem?

Does OSPI BOOT for AM6548 SR2.0 work right?

Best regards,

Artem

  • 0
    TI__Guru**** 155270 points

    Hi Artem,

    I will try this on SR2.0 board and get back to you in couple of days.

    Best Regards,
    Keerthy

  • 0 in reply to Keerthy J
    TI__Guru**** 155270 points

    Hi Artem,

    This seems like an issue on SR 2.0. I do not see any prints from u-boot/SPL when i try to boot from OSPI. The same is working
    very well on SR 1.0. I have reached out to internal teams on this. I will provide feedback as soon as i hear back from them.

    Best Regards,
    Keerthy

  • 0 in reply to Keerthy J
    TI__Guru**** 155270 points

    Hi Artem,

    I have intimated the internal teams regarding this issue. This will be fixed most likely
    in the next release. I believe you do not see any traces on UART when you boot from OSPI.

    Let me know if you have different observations.

    Best Regards,
    Keerthy

  • 0 in reply to Keerthy J
    TI__Guru**** 155270 points

    Hi Artem,

    Any updates?

    Best Regards,
    Keerthy

  • 0 in reply to Keerthy J
    Intellectual 370 points

    No, We are seeing driving chip select pin, clock and data, but system is not loaded and we see nothing in console

    Best Regards,
    Artem

  • 0 in reply to Artem Boyarchuk
    TI__Guru**** 155270 points

    Hi Artem,

    Can you try the binaries in the attached zip file?

    Best Regards,
    Keerthy

    pg2.0.zip

  • 0 in reply to Keerthy J
    Intellectual 370 points

    Hi Keerthy,

    Sorry for the delay. We have checked the binaries that you sent and the binaries didn't solve the problem, I see nothing in debug console.

    Best Regards,
    Artem

  • 0 in reply to Artem Boyarchuk
    TI__Guru**** 155270 points

    Artem,

    With the attached binaries i was able to boot to u-boot prompt. Can you please share the commands
    that you used to flash to OSPI and the outputs as well?

    Are you using fatload mmc or tftp?

    Best Regards,
    Keerthy

  • 0 in reply to Keerthy J
    Intellectual 370 points

    Keerthy,

    Thank you for reply

    => setenv ipaddr 192.168.0.110
    => setenv serverip 192.168.0.103
    => setenv gatewayip 192.168.0.1
    => setenv netmask 255.255.255.0
    => sf probe
    SF: Detected mx66um1g45g with page size 256 Bytes, erase size 4 KiB, total 128 MiB
    => tftp ${loadaddr} tiboot3.bin
    link up on port 1, speed 100, full duplex
    Using cpsw_nuss@046000000 device
    TFTP from server 192.168.0.103; our IP address is 192.168.0.110
    Filename 'tiboot3.bin'.
    Load address: 0x80080000
    Loading: #############################
    1.7 MiB/s
    done
    Bytes transferred = 147568 (24070 hex)
    => sf update $loadaddr 0x0 $filesize
    device 0 offset 0x0, size 0x24070
    147568 bytes written, 0 bytes skipped in 1.103s, speed 136627 B/s
    => tftp ${loadaddr} tispl.bin
    link up on port 1, speed 100, full duplex
    Using cpsw_nuss@046000000 device
    TFTP from server 192.168.0.103; our IP address is 192.168.0.110
    Filename 'tispl.bin'.
    Load address: 0x80080000
    Loading: #################################################################
    #################################################################
    ##############
    2.6 MiB/s
    done
    Bytes transferred = 734080 (b3380 hex)
    => sf update $loadaddr 0x80000 $filesize
    device 0 offset 0x80000, size 0xb3380
    734080 bytes written, 0 bytes skipped in 5.548s, speed 135416 B/s
    => tftp ${loadaddr} u-boot.img
    link up on port 1, speed 100, full duplex
    Using cpsw_nuss@046000000 device
    TFTP from server 192.168.0.103; our IP address is 192.168.0.110
    Filename 'u-boot.img'.
    Load address: 0x80080000
    Loading: #################################################################
    #################################################################
    #################################################################
    #
    3.3 MiB/s
    done
    Bytes transferred = 1000016 (f4250 hex)
    => sf update $loadaddr 0x280000 $filesize
    device 0 offset 0x280000, size 0xf4250
    1000016 bytes written, 0 bytes skipped in 7.608s, speed 134544 B/s
    => tftp ${loadaddr} sysfw.itb
    link up on port 1, speed 100, full duplex
    Using cpsw_nuss@046000000 device
    TFTP from server 192.168.0.103; our IP address is 192.168.0.110
    Filename 'sysfw.itb'.
    Load address: 0x80080000
    Loading: ####################################################
    2.7 MiB/s
    done
    Bytes transferred = 266094 (40f6e hex)
    => sf update $loadaddr 0x6C0000 $filesize
    device 0 offset 0x6c0000, size 0x40f6e
    266094 bytes written, 0 bytes skipped in 2.7s, speed 135562 B/s
    =>

    Could you send Boot Mode Pins configuration that you used ?

    Best Regards,
    Artem

  • 0 in reply to Artem Boyarchuk
    TI__Guru**** 155270 points

    Artem,

    I again tried the attached pg2.0.zip in earlier reply from me: https://e2e.ti.com/support/processors/f/791/p/941230/3497369#3497369

    Here are the commands i used:

    sf probe
    sf erase 0x0 0x1000000

    fatload mmc 1 ${loadaddr} tiboot3.bin; sf update $loadaddr 0x0 $filesize; fatload mmc 1 ${loadaddr} tispl.bin; sf update $loadaddr 0x80000 $filesize; fatload mmc 1 ${loadaddr} u-boot.img; sf update $loadaddr 0x280000 $filesize; fatload mmc 1 ${loadaddr} sysfw.itb; sf update $loadaddr 0x6C0000 $filesize

    DIP SWITCHES:


    |--------------------------|
    |1 0 0 0 0 0 0 1 0 0  |
    |--------------------------|
     1 2 3 4 5 6 7 8 9 10
             SW3

    |---------------------------|
    |  0 0 1 0 0 0 0 0 0 0  |
    |----------------------------|
     1 2 3 4 5 6 7 8 9 10
             SW3


    With that i am able to boot from OSPI. Logs here:

    U-Boot SPL 2020.01-geea7380073 (Oct 06 2020 - 04:47:33 +0000
                                                                SYSFW ABI: 3.1 (firmware rev 0x0014 '20.7.1-v2020.07-RC3 (Terfic L')
    Trying to boot from SPI
    WARN: PHY calibration failed: -2
    Starting ATF on ARM64 core...

    NOTICE:  BL31: v2.3():07.01.0002-dirty
    NOTICE:  BL31: Built : 02:26:59, Oct  4 2020

    U-Boot SPL 2020.01-geea7380073 (Oct 06 2020 - 04:47:43 +0000
                                                                SYSFW ABI: 3.1 (firmware rev 0x0014 '20.7.1-v2020.07-RC3 (Terrific L')
    Detected: AM6-IDKAPPEVM rev A
    Detected: SER-PCIE2LEVM rev A
    Trying to boot from SPI
    WARN: PHY calibration failed: -2


    U-Boot 2020.01-geea7380073 (Oct 06 2020 - 04:47:43 +0000)

    SoC:   AM65X SR2.0
    oard: AM6-COMPROCEVM rev AM654 Base Board
    DRAM:  4 GiB
    MMC:   sdhci@4f80000: 0, sdhci@4fa0000: 1
    Loading Environment from M... OK
    In:    serial
    Out:   serial
    Err:   serial
    Detected: AM6-IDKAPPEVM rev A
    Detected: SER-PCIE2LEVM rev A
    Net:   
    Warning: ethernet@46000000 using MAC address from ROM
    eth0: ethernet@46000000
    Hit any key to stop aoboot:  0

    Hope you can resolve the issue.

    Best Regards,
    Keerthy

  • 0 in reply to Keerthy J
    Intellectual 370 points

    Keerthy,

    Thank you for reply

    We have resolved the issue and now U-boot can be loaded from OSPI Flash.

    To do this, we have set special Boot Mode Pins configuration for our OPSI Flash and added supporting our SPI Flash driver into SPL

    Best Regards,
    Artem