1. 21 Mar, 2014 4 commits
  2. 19 Feb, 2014 1 commit
  3. 07 Feb, 2014 1 commit
  4. 09 Jan, 2014 1 commit
  5. 31 Aug, 2013 1 commit
    • Marek Vasut's avatar
      ARM: mxs: tools: Add mkimage support for MXS bootstream · bce88370
      Marek Vasut authored
      Add mkimage support for generating and verifying MXS bootstream.
      The implementation here is mostly a glue code between MXSSB v0.4
      and mkimage, but the long-term goal is to rectify this and merge
      MXSSB with mkimage more tightly. Once this code is properly in
      U-Boot, MXSSB shall be deprecated in favor of mkimage-mxsimage
      Note that the mxsimage generator needs libcrypto from OpenSSL, I
      therefore enabled the libcrypto/libssl unconditionally.
      MXSSB: http://git.denx.de/?p=mxssb.git;a=summary
      The code is based on research presented at:
      http://www.rockbox.org/wiki/SbFileFormatSigned-off-by: default avatarMarek Vasut <marex@denx.de>
      Cc: Tom Rini <trini@ti.com>
      Cc: Fabio Estevam <fabio.estevam@freescale.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Otavio Salvador <otavio@ossystems.com.br>
  6. 24 Jul, 2013 1 commit
  7. 12 Jul, 2013 1 commit
    • Simon Glass's avatar
      bootm: Use selected configuration for ramdisk and fdt · f320a4d8
      Simon Glass authored
      If a specific configuraion is selected by the bootm command, e.g. with
      'bootm 84000000#recoveryconf' we must honour this for not just the kernel,
      but also the ramdisk and FDT.
      In the conversion to using a common fit_image_load() function for loading
      images from FITs (commits a51ec63b and 53f375fa) this feature was lost.
      Reinstate it by passing the selected configuration back from
      fit_image_load() to boot_get_kernel(), then use this configuration
      (which is stored in images->fit_uname_cfg) in both boot_get_ramdisk()
      and boot_get_fdt().
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
  8. 10 Jul, 2013 1 commit
  9. 28 Jun, 2013 1 commit
    • Simon Glass's avatar
      mkimage: Build signing only if board has CONFIG_FIT_SIGNATURE · 29ce737d
      Simon Glass authored
      At present mkimage is set up to always build with image signing support.
      This means that the SSL libraries (e.g. libssl-dev) are always required.
      Adjust things so that mkimage can be built with and without image signing,
      controlled by the presence of CONFIG_FIT_SIGNATURE in the board config file.
      If CONFIG_FIT_SIGNATURE is not enabled, then mkimage will report a warning
      that signing is not supported. If the option is enabled, but libraries are
      not available, then a build error similar to this will be shown:
      lib/rsa/rsa-sign.c:26:25: fatal error: openssl/rsa.h: No such file or directory
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
  10. 26 Jun, 2013 5 commits
    • Simon Glass's avatar
      image: Add support for signing of FIT configurations · 4d098529
      Simon Glass authored
      While signing images is useful, it does not provide complete protection
      against several types of attack. For example, it it possible to create a
      FIT with the same signed images, but with the configuration changed such
      that a different one is selected (mix and match attack). It is also possible
      to substitute a signed image from an older FIT version into a newer FIT
      (roll-back attack).
      Add support for signing of FIT configurations using the libfdt's region
      Please see doc/uImage.FIT/signature.txt for more information.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
    • Simon Glass's avatar
      image: Support signing of images · 56518e71
      Simon Glass authored
      Add support for signing images using a new signature node. The process
      is handled by fdt_add_verification_data() which now takes parameters to
      provide the keys and related information.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
    • Simon Glass's avatar
      image: Add signing infrastructure · 3e569a6b
      Simon Glass authored
      Add a structure to describe an algorithm which can sign and (later) verify
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
    • Simon Glass's avatar
      Add a 'fake' go command to the bootm command · d0ae31eb
      Simon Glass authored
      For tracing it is useful to run as much of U-Boot as possible so as to get
      a complete picture. Quite a bit of work happens in bootm, and we don't want
      to have to stop tracing before bootm starts.
      Add a way of doing a 'fake' boot of the OS - which does everything up to
      the point where U-Boot is about to jump to the OS image. This allows
      tracing to record right until the end.
      This requires arch support to work.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
    • Simon Glass's avatar
      Refactor the bootm command to reduce code duplication · 35fc84fa
      Simon Glass authored
      At present the bootm code is mostly duplicated for the plain 'bootm'
      command and its sub-command variant. This makes the code harder to
      maintain and means that changes must be made to several places.
      Introduce do_bootm_states() which performs selected portions of the bootm
      work, so that both plain 'bootm' and 'bootm <sub_command>' can use the
      same code.
      Additional duplication exists in bootz, so tidy that up as well. This
      is not intended to change behaviour, apart from minor fixes where the
      previously-duplicated code missed some chunks of code.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
  11. 04 Jun, 2013 4 commits
  12. 14 May, 2013 13 commits
  13. 27 Mar, 2013 1 commit
  14. 08 Feb, 2013 1 commit
  15. 05 Jan, 2013 1 commit
    • Fabio Estevam's avatar
      tools: imximage: Load a size that is multiple of 512 · 1411fb37
      Fabio Estevam authored
      In order to mx53 ROM to properly load the U-boot image, its header size should
      be multiple of 512 bytes.
      This issue was observed with gcc 4.6.2/4.7.3, which caused data aborts:
      U-Boot 2013.01-rc2-00172-gf8cfcf1b-dirty (Dec 26 2012 - 13:13:28)
      Board: MX53 LOCO
      I2C:   ready
      DRAM:  1 GiB
      MMC:   FSL_SDHC: 0, FSL_SDHC: 1
      In:    serial
      Out:   serial
      Err:   serial
      CPU:   Freescale i.MX53 family rev2.1 at 1000 MHz
      Reset cause: WDOG
      Net:   FEC
      Warning: FEC using MAC address from net device
      Hit any key to stop autoboot:  0
      data abort
          MAYBE you should read doc/README.arm-unaligned-accesses
      pc : [<aff72220>]          lr : [<aff721fc>]
      sp : af565e20  ip : af566918     fp : 00000000
      r10: 00000003  r9 : affabb5b     r8 : af565f58
      r7 : 00000000  r6 : 36747fff     r5 : af5668e8  r4 : 36747fff
      r3 : af5668ec  r2 : af5668eb     r1 : 00000000  r0 : af5668e8
      Flags: NzcV  IRQs off  FIQs off  Mode SVC_32
      Resetting CPU ...
      resetting ...
      ,and this patch fixes it.
      Also, even though the ROUND macro is already defined in common.h,
      the reason for redefining it in image.h is explained by Stefano Babic:
      "I will remark a previous comment - even if including common.h seems a
      good idea to avoid duplications, it makes tools like mkimage to depend
      on the selected board, because <board>_config must run. Even if this is
      not a problem for us u-boot developers, it becomes an issue when these
      tools are included in distros (like u-boot-tools in Ubuntu) and cannot
      be packaged."
      Signed-off-by: default avatarTroy Kisky <troy.kisky@boundarydevices.com>
      Signed-off-by: default avatarFabio Estevam <fabio.estevam@freescale.com>
  16. 13 Dec, 2012 1 commit
  17. 13 Nov, 2012 1 commit
    • Gabe Black's avatar
      fdt: Add option to default to most compatible conf in a fit image · d95f6ec7
      Gabe Black authored
      When booting a fit image with multiple configurations, the user either has to
      specify which configuration to use explicitly, or there has to be a default
      defined which is chosen automatically. This change adds an option to change
      that behavior so that a configuration can be selected explicitly, or the
      configuration which has the device tree that claims to be compatible with the
      earliest item in U-Boot's device tree.
      In other words, if U-Boot claimed to be compatible with A, B, and then C, and
      the configurations claimed to be compatible with A, D and B, D and D, E, the
      first configuration, A, D, would be chosen. Both the first and second
      configurations match, but the first one matches a more specific entry in
      U-Boot's device tree. The order in the kernel's device tree is ignored.
      Signed-off-by: default avatarGabe Black <gabeblack@google.com>
      Commit-Ready: Gabe Black <gabeblack@chromium.org>
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
  18. 04 Nov, 2012 1 commit
    • Kim Phillips's avatar
      include/image.h: sparse fixes · 2f220500
      Kim Phillips authored
      include/image.h:378:1: warning: cast to restricted __be32
      include/image.h:381:1: warning: cast to restricted __be32
      include/image.h:382:1: warning: cast to restricted __be32
      include/image.h:383:1: warning: cast to restricted __be32
      fix by annotating image header integers big endian.
      Signed-off-by: default avatarKim Phillips <kim.phillips@freescale.com>