• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 99 subscribers
  • Views 228 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.

AM625: Flash an application Error

yu chai
Prodigy 220 points
Part Number: AM625
Other Parts Discussed in Thread: UNIFLASH

1 I am testing the flash an example application function, and the reference tutorial is linked as follows:

2 When I perform the step of running the flashed application, m4f and r5f cores start normally, while A cores cannot complete uboot normally. The specific error is as follows:

3 I m using ti e1 development board without any changes to the hardware and software.
4 If set to sd card start, the uboot and the kernel can start normally 
5 The process of generating linux.appimage is generated by copying bl31.bin,bl32.bin and u-boot-spl.bin-am62xx-evm from the virtual machine ubuntu to under win10.

 

6 My hsmappimage is also generated under win10, so it's not here, right? 

7 So what caused spl to load uboot error? 

  • +1
    TI__Guru 69291 points

    Hi,

    The boot logs suggest that the A53 SPL is failing to read A53 U-Boot Proper (u-boot.img) & so the boot fails. One of the reason A53 SPL fails to read `u-boot.img` is if the `u-boot.img` image is not flashed at all or flashed at the wrong offset in the eMMC or OSPI.

    Please note the `u-boot.img` image is not part of Linux Appimage & must be flashed separately at the correct offset. The default raw offset of `u-boot.img` unless changed is 0x280000. Now, we can flash this image with the UART Uniflash tool in MCU+ SDK itself. Please choose one of the following lines according to the media & add to the configuration file (*.cfg) you are using

    # For OSPI
--file={UBOOT_IMG_PATH} --operation=flash --flash-offset=0x280000

# For eMMC
--file={UBOOT_IMG_PATH} --operation=flash-emmc --flash-offset=0x280000

    Once the flashing of `u-boot.img` is successful, the boot error should not come anymore.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Prodigy 220 points

    1 I burned uboot.img to spi and the problem was solved. Thank you so much 。

    2 The official instruction manual does not mention this step. Convenient, you can update the guidance document 

  • 0 in reply to yu chai
    TI__Guru 69291 points

    Hi,

    Thank you for your feedback. I will create a ticket internally to have these instructions included in the Linux Appimage Generator section in the documentation.

    Thanks!

  • 0 in reply to Prashant Shivhare
    Prodigy 220 points

    1 I tried to change boot from ospi to emmc in loading driver times wrong see log for details.

    2 As if the emmc address conflicts. The boot-associated appimage occupies the first 64m.

    3 Can you help me see the reason for the error in the startup log? How do I solve it. emmc start error .log

  • 0 in reply to yu chai
    TI__Guru 69291 points

    Hi,

    Please create a new thread for the new issue so that it can be assigned to the right expert.

    Thanks!