03 Jan, 2014

2 commits

  • Single-source clocking is new feature introduced in T1040.
    In this mode, a single differential clock is supplied to the
    DIFF_SYSCLK_P/N inputs to the processor, which in turn is
    used to supply clocks to the sysclock, ddrclock and usbclock.

    So, both ddrclock and syclock are driven by same differential
    sysclock in single-source clocking mode whereas in normal clocking
    mode, generally separate DDRCLK and SYSCLK pins provides
    reference clock for sysclock and ddrclock

    DDR_REFCLK_SEL rcw bit is used to determine DDR clock source
    -If DDR_REFCLK_SEL rcw bit is 0, then DDR PLLs are driven in
    normal clocking mode by DDR_Reference clock

    -If DDR_REFCLK_SEL rcw bit is 1, then DDR PLLs are driven in
    single source clocking mode by DIFF_SYSCLK

    Add code to determine ddrclock based on DDR_REFCLK_SEL rcw bit.

    Signed-off-by: Poonam Aggrwal
    Signed-off-by: Priyanka Jain

    Priyanka Jain
     
  • CONFIG_SPL_NAND_MINIMAL should not be used as it was defined for temporary
    review purpose.

    So, use CONFIG_SPL_NAND_BOOT config.

    Signed-off-by: Prabhakar Kushwaha

    Prabhakar Kushwaha
     

13 Dec, 2013

1 commit

  • Given a multi-file image created through the mkimage's -d option:

    $ mkimage -A x86 -O linux -T multi -n x86 -d vmlinuz:initrd.img:System.map \
    multi.img

    Image Name: x86
    Created: Thu Jul 25 10:29:13 2013
    Image Type: Intel x86 Linux Multi-File Image (gzip compressed)
    Data Size: 13722956 Bytes = 13401.32 kB = 13.09 MB
    Load Address: 00000000
    Entry Point: 00000000
    Contents:
    Image 0: 4040128 Bytes = 3945.44 kB = 3.85 MB
    Image 1: 7991719 Bytes = 7804.41 kB = 7.62 MB
    Image 2: 1691092 Bytes = 1651.46 kB = 1.61 MB

    It is possible to perform the innverse operation -- extracting any file from
    the image -- by using the dumpimage's -i option:

    $ dumpimage -i multi.img -p 2 System.map

    Although it's feasible to retrieve "data files" from image through scripting,
    the requirement to embed tools such 'dd', 'awk' and 'sed' for this sole purpose
    is cumbersome and unreliable -- once you must keep track of file sizes inside
    the image. Furthermore, extracting data files using "dumpimage" tool is faster
    than through scripting.

    Signed-off-by: Guilherme Maciel Ferreira
    Signed-off-by: Simon Glass

    Guilherme Maciel Ferreira
     

11 Dec, 2013

2 commits


06 Dec, 2013

1 commit


02 Dec, 2013

1 commit


26 Nov, 2013

2 commits


25 Nov, 2013

2 commits


13 Nov, 2013

3 commits


12 Nov, 2013

2 commits

  • As
    http://www.denx.de/wiki/view/U-Boot/DesignPrinciples#2_Keep_it_Fast
    states:
    "Initialize devices only when they are needed within U-Boot"

    enable the RTC32K OSC only, if CONFIG_SPL_AM33XX_ENABLE_RTC32K_OSC is
    enabled. Enable this in ti_am335x_common.h, so all boards in mainline
    should work as before.

    Signed-off-by: Heiko Schocher
    Cc: Tom Rini

    Heiko Schocher
     
  • If no softreset save registers are found on the hardware
    "bootcount" is stored in the environment. To prevent a
    saveenv on all reboots, the environment variable
    "upgrade_available" is introduced. If "upgrade_available" is
    0, "bootcount" is always 0 therefore no need to save the
    environment on u-boot boot, if "upgrade_available" is 1 "bootcount"
    is incremented in the environment and environment gets written
    on u-boot start.
    So the Userspace Applikation must set the "upgrade_available"
    and "bootcount" variable to 0 (for example with fw_setenv),
    if a boot was successfully.

    Signed-off-by: Heiko Schocher

    Heiko Schocher
     

09 Nov, 2013

2 commits


08 Nov, 2013

2 commits

  • There is no CONFIG_PCA953X_INFO symbol.
    U-Boot uses CONFIG_CMD_PCA953X_INFO instead, which is described in
    "Monitor Functions" section and thus no need to be repeated in the
    "GPIO Support" section.
    Remove the whole line.

    Signed-off-by: Igor Grinberg

    Igor Grinberg
     
  • env exists is a way to test (in hush) if an environment variable
    exists. A workaround existed using printenv but this new command
    doesn't require all the stdout/stderr redirection to prevent
    printing information to the screen.

    Example:
    $ set testexists 1
    $ env exists testexists && echo "yes"
    yes
    $ env exists testexists || echo "no"
    $ set testexists
    $ env exists testexists && echo "yes"
    $ env exists testexists || echo "no"
    no
    $

    Signed-off-by: Andrew Ruder

    Andrew Ruder
     

30 Oct, 2013

1 commit


17 Oct, 2013

3 commits


15 Oct, 2013

1 commit


08 Oct, 2013

2 commits


02 Oct, 2013

1 commit


24 Sep, 2013

2 commits

  • DFU spec mentions it as a method to upgrade firmware (software stored
    in writable non-volatile memory). It also says other potential uses of
    DFU is beyond scope of the spec.

    Here such a beyond the scope use is being attempted - directly pumping
    binary images from host via USB to RAM. This facility is a developer
    centric one in that it gives advantage over upgrading non-volatile
    memory for testing new images every time during development and/or
    testing.

    Directly putting image onto RAM would speed up upgrade process. This and
    convenience was the initial thoughts that led to doing this, speed
    improvement over MMC was only 1 second though - 6 sec on RAM as opposed
    to 7 sec on MMC in beagle bone, perhaps enabling cache and/or optimizing
    DFU framework to avoid multiple copy for ram (if worth) may help, and
    on other platforms and other boot media like NAND maybe improvement
    would be higher.

    And for a platform that doesn't yet have proper DFU suppport for
    non-volatile media's, DFU to RAM can be used.

    Another minor advantage would be to increase life of mmc/nand as it
    would be less used during development/testing.

    usage: ram
    eg. kernel ram 0x81000000 0x1000000

    Downloading images to RAM using DFU is not something new, this is
    acheived in openmoko also.

    DFU on RAM can be used for extracting RAM contents to host using dfu
    upload. Perhaps this can be extended to io for squeezing out register
    dump through usb, if it is worth.

    Signed-off-by: Afzal Mohammed
    Cc: Heiko Schocher
    Cc: Marek Vasut
    Cc: Lukasz Majewski
    Cc: Pantelis Antoniou
    Cc: Gerhard Sittig
    Acked-by: Marek Vasut
    Acked-by: Lukasz Majewski
    Acked-by: Heiko Schocher

    Afzal Mohammed
     
  • Besides the change of this patchset it also updates the
    README to reflect that GOT-generated relocations are no
    longer supported on ARM.

    cc: Albert ARIBAUD
    Signed-off-by: Jeroen Hofstee

    Jeroen Hofstee
     

20 Sep, 2013

2 commits


19 Sep, 2013

1 commit


12 Sep, 2013

1 commit


04 Sep, 2013

1 commit


21 Aug, 2013

3 commits

  • Due to the nand SPL on some board(e.g. P1022DS)has a size limit, it can
    not be more than 4K. So, the SPL cannot initialize the DDR with the SPD
    code. This patch introduces TPL to enable a loader stub that is loaded
    by the code from the SPL. It initializes the DDR with the SPD or other
    operations.

    The TPL's size is sizeable, the maximum size is decided by the memory's
    size that TPL runs. It initializes the DDR through SPD code, and copys
    final uboot image to DDR. So there are three stage uboot images:
    * spl_boot, * tpl_boot, * final uboot image

    Signed-off-by: Ying Zhang
    Acked-by: York Sun

    Ying Zhang
     
  • Enable p1022ds to start from eSDHC with SPL.

    Signed-off-by: Ying Zhang
    Acked-by: York Sun

    Ying Zhang
     
  • The code from the internal on-chip ROM. It loads the final uboot image
    into DDR, then jump to it to begin execution.

    The SPL's size is sizeable, the maximum size must not exceed the size of L2
    SRAM. It initializes the DDR through SPD code, and copys final uboot image
    to DDR. So there are two stage uboot images:
    * spl_boot, 96KB size. The env variables are copied to L2 SRAM, so that
    ddr spd code can get the interleaving mode setting in env. It loads
    final uboot image from offset 96KB.
    * final uboot image, size is variable depends on the functions enabled.

    Signed-off-by: Ying Zhang
    Acked-by: York Sun

    Ying Zhang
     

19 Aug, 2013

1 commit


17 Aug, 2013

1 commit

  • At present the console for linux is silent if the U-Boot console is silent,
    unless CONFIG_SILENT_U_BOOT_ONLY is set. I wonder if a better way would be
    to have an environment variable to control this? Then we can control the
    verbosity from scripts, and set the variable to 'no' for those boards that
    want Linux to boot with console output.

    Signed-off-by: Simon Glass

    Simon Glass