Home Forum Getting Started U-Boot build instruction do not lead to usable image

Tagged: 

This topic contains 2 replies, has 3 voices, and was last updated by  cpwrunner 2 months, 1 week ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #495

    xypron
    Participant

    When I build U-Boot according to http://wiki.macchiatobin.net/tiki-index.php?page=Build+from+source+-+Bootloader and write it to SD and reboot I always only get

    BootROM - 2.03
    Starting CP-0 IOROM 1.07
    Booting from SD 0 (0x29)
    Found valid image at boot postion 0x002
    lNOTICE:  Starting binary extension
    NOTICE:  Gathering DRAM information
    mv_ddr: mv_ddr-armada-17.06.1-g47f4c8b-dirty (Oct 15 2017 - 01:08:50)
    mv_ddr: completed successfully

    U-Boot never appears.

    There are some github repositories that have scripts based on the same directions (e.g. https://github.com/hkominos/ENEA_PicoCluster) but they lead to the same result.

    The only working image I found was at https://wiki.solid-run.com/lib/exe/fetch.php?media=products:a8040:software:os:flash-image.bin.gz.

    Please, add the missing in information to the build instructions to get a working U-Boot image.

    Best regards

    Heinrich

    #502

    nanasi
    Participant

    You might want to change
    – atf build option LOG_LEVEL=20 to LOG_LEVEL=50.
    – atf build option DEBUG=0 to DEBUG=1.
    – boot device to eMMC.
    – boot device to SPI-nor.

    #6828

    cpwrunner
    Participant

    I had the same problem and the solution for me was to recompile my x86_64 version of gcc and disable the pie flag. Someone else on the internet deserves credit for this, but I lost the link.

    Good luck

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Technical specification tables can not be displayed on mobile. Please view on desktop