• State TI Thinks Resolved
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 82 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AM6442: Flash emmc failed with dfu-util

Yiying Fu
Prodigy 20 points

Part Number: AM6442

Hello,

When attempting to program tiboot3.bin on our custom hardware using DFU, I'm seeing behavior that differs from the EVM.

Previously, on the EVM, after flashing tiboot3.bin to the bootloader area using dfu-util, running dfu-util -l would show entries naming with tispl.bin and u-boot.img. However, on the custom board, regardless of how many times I flash it, dfu-util -l continues to show only SocId and bootloader

The output remains unchanged, which makes it look as if the running of tiboot3.bin never completed successfully.

With DEBUG openend, from what I can see, DDR initialization appears to be completing successfully.

I've attached screenshots/logs for reference.serial-dfu.pngdfu-util-download.png Could you help me understand what might cause this behavior and whether there are any additional checks I should perform?

  • 0
    TI__Mastermind 23035 points

    Hi,

    Yiying Fu said:
    I've attached screenshots/logs for reference.

    Are these the entire boot logs? Can you share entire boot logs if not.

    tiboot3.bin failing usually indicates some issues with the DDR configuration, did you change the DDR configuration according to the part used on your custom board and rebuild these boot binaries? Please share your DDR part number as well as DDR configuraions.

    Best Regards,
    Meet.

  • 0 in reply to Meet Thakar
    Prodigy 20 points

    Yes. This is the entire boot log. Our custom board doesn't have a pre-installed image so this is the first step bringing up through DFU.

    I have modified the DDR configuration and I've checked the bring up tips here[FAQ] Board bring up tips for Sitara devices (AM64x, AM243x, AM62x, AM62L, AM62Ax, AM62D-Q1, AM62Px) - Processors forum - Processors - TI E2E support forums It says usually an incorrect DDR configuration will cause the log stop just behind SPL initial stack usage. Before I changed the parameters, it was indeed getting stuck at that point. Then I changed the parameters and now the last log message shows that it has successfully gone through run_usb_dnl_gadget(). Does this imply that DDR initialization has already completed successfully?

    Below is my DDR configuration(changing .dtsi to .log for upload). We are using a IS46LQ16512B device.k3-am64-ddr-config.log

  • 0 in reply to Meet Thakar
    Prodigy 20 points

    Hello Meet,

    Today I switched to a different board with the same hardware design and was able to boot into U-Boot using the exact same software version and flashing procedure. At this point, I suspect the issue may be related to hardware stability.

    We are checking with the hardware design. Thanks for your help and appreciate in advance if there are further suggestions in this direction.