u-boot-2013-10-release/

Beginning today, we’ll start shipping boards with a new release of U-Boot, aligned with the 2013.10 release from main-line.

A binary package is available here:

If you extract the content to an SD card, you can upgrade on our standard 1GiB versions of Nitrogen6X or BD-SL-i.MX6 boards like so:
U-Boot > bootfile=u-boot.nitrogen6q ; run upgradeu
Refer to this post for more detail and this post for the list of available machine configurations.

There aren’t too many new features in this release, and no critical bug fixes for most users, so don’t feel pressured to upgrade immediately.

There are a couple of notable bug fixes though:
  • This patch to the clock startup fixed an issue for QNX users. Without it, the GPU would fail to start in around 1 of 10 boot cycles. We also noticed that it cured an occasional hang initializing the SD card and/or SATA under U-Boot, and
  • This patch from Fabio fixed the artifacts on HDMI on Dual-Lite and Solo boards.
We also added support for device-tree in the boot scripts for SABRE Lite and Nitrogen6x and added support for a couple of new 1280×800 displays with the Focaltech FT5X06 touch controller.

Finally, we removed the U-Boot (Linux penguin) logo from the splash screen. As much as we love Tux, it didn’t make a lot of sense when booting QNX or Windows CE (err. Embedded 7). Splash screen support is still present, so you can put him back.

The source code is in the normal place (“production” branch on GitHub). We’ve kept the older release in branch production-before-20131107.

In case there’s a regression, binaries of the older 2013.07 release are available here: As always, please let us know how this upgrade goes for you, and reach out if you have any trouble.

Tags:

9 Responses to “u-boot-2013-10-release/”

  1. Daniel November 18, 2013 3:32 am #

    Hey,
    I just made a dumb mistake, I accidentally forgot the last 0 in the sf write command and just executed ‘U-Boot > sf write 10000000 c200 ${filesize}’. So, if I got this right I have overwritten my u-boot. I now already have loaded the last u-boot image over your imx_usb_loader tool and then used ‘bootfile=u-boot.nitrogen6q;run upgradeu’, This worked pretty fine, but I still get a black Screen after a reset.
    PS.: After executing the ‘upgradeu’ command again I get a message that u-boot versions match, so no update is performed. How can I get u-boot loading again?

    • Daniel November 18, 2013 3:44 am #

      Hey guys, its me again… I simply forgot to set the DIP switches Back to normal position. Mondays…
      But the Boo Flow section in this Article helped me alot: http://boundarydevices.com/u-boot-on-i-mx6/

      • ericn November 18, 2013 7:31 am #

        Glad to hear it.

  2. embedsri December 4, 2013 2:32 am #

    Hi Eric,
    I’m assuming BoundaryDevices used Freescale DDR Stress test tool as referenced here: https://community.freescale.com/docs/DOC-96412

    for i.MX6-BD.SL board and updated the DDR3 related parameter into the dcd table of u-boot.

    Can you share the script you used for this purpose? Its contents should have looked a lot like this:

    //=============================================================================
    // DDR Controller Registers
    //=============================================================================
    // Manufacturer: Micron
    // Device Part Number: MT41K128M16JT-125:K
    // Clock Freq.: 528MHz
    // Density per CS in Gb: 8
    // Chip Selects used: 1
    // Number of Banks: 8
    // Row address: 14
    // Column address: 10
    // Data bus width 64
    //=============================================================================

    //=============================================================================
    // Calibration setup.
    //=============================================================================
    setmem /32 0x021b0800 = 0xA1390003 // DDR_PHY_P0_MPZQHWCTRL, enable both one-time & periodic HW ZQ calibration.

    // For target board, may need to run write leveling calibration to fine tune these settings.
    setmem /32 0x021b080c = 0×00000000
    setmem /32 0x021b0810 = 0×00000000
    setmem /32 0x021b480c = 0×00000000
    setmem /32 0x021b4810 = 0×00000000

    ////Read DQS Gating calibration
    setmem /32 0x021b083c = 0×00000000 // MPDGCTRL0 PHY0
    setmem /32 0x021b0840 = 0×00000000 // MPDGCTRL1 PHY0
    setmem /32 0x021b483c = 0×00000000 // MPDGCTRL0 PHY1
    setmem /32 0x021b4840 = 0×00000000 // MPDGCTRL1 PHY1

    • tsheffield June 10, 2014 3:46 pm #

      I’m also wondering if anyone has gotten the Freescale DDR stress test running – I’m trying on a Nitrogen 6x Solo. Tried to load the .bin with usb loader, but I just get the ‘unknown load address’ error. I’ve seen this created before by a problem with stuff being removed by setting a garbage collection flag –gc-sections for the linker.

      • tsheffield June 10, 2014 3:53 pm #

        Ah, I see I grabbed the wrong .bin. Does anybody have a version of this that uses UART 2? I guess the original uses 1. Might have to go bug the Freescale FAE.

        • ericn June 11, 2014 7:16 am #

          All of our binaries use UART2 (/dev/ttymxc1 under Linux).

  3. Wilson January 15, 2014 2:20 am #

    Hi,

    Got errors when upgrading the u-boot
    =============================
    MX6Q SABRELITE U-Boot > run upgradeu
    Card did not respond to voltage select!
    mmc0(part 0) is current device
    MMC: block number 0×1 exceeds max(0×0)
    ** Can’t read from device 0 **

    ** Unable to use mmc 0:1 for fatload **
    ** Bad partition 1 **
    mmc1 is current device
    reading /6q_upgrade

    ** Unable to read “/6q_upgrade” from mmc 1:1 **
    Loading file “/6q_upgrade” from mmc device 1:1 (xxb1)
    1465 bytes read
    ## Executing script at 10008000
    ERROR: There is a global environment variable with the same name.
    check U-Boot
    ** Block device 1:1 301989888 not supported
    ** Block device 1:1 301989888 not supported
    No U-Boot image found on SD card

    I just copy 6q_upgrade and u-boot.imx to the SD card and then run upgardeu.
    I tried different cards already. Any clues?

    P.S. I am able to boot this u-boot.imx through USB OTG port.

    • ericn January 15, 2014 7:25 am #

      Hi Wilson,

      The source of the issue you’re seeing is the really old version you’re running. we switched from using 6q_upgrade to 6x_upgrade when we switched to main-line U-Boot because there are command-line incompatibilities. See this thread for details, but the short answer is that you’ll need the 6q_upgrade script from this post.

Leave a Reply