Skip to content
Snippets Groups Projects
  1. Jul 07, 2009
    • Scott Wood's avatar
      nand_spl: Fix cmd_ctrl usage in nand_boot.c. · 1dac3a51
      Scott Wood authored
      
      When adding large page NAND support to this file, I had a misunderstanding
      about the exact semantics of NAND_CTRL_CHANGE (which isn't documented
      anywhere I can find) -- it is apparently just a hint to drivers,
      which aren't required to preserve the old value for subsequent
      non-"change" invocations.
      
      This change makes nand_boot.c no longer assume this.  Note that this
      happened to work by chance with some NAND drivers, which don't preserve
      the value, but treat 0 equivalently to NAND_CTRL_ALE.
      
      I don't have hardware to test this, so any testing is appreciated.
      
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
      1dac3a51
    • Guennadi Liakhovetski's avatar
      nand_spl: read environment early, when booting from NAND using nand_spl · b74ab737
      Guennadi Liakhovetski authored
      
      Currently, when booting from NAND using nand_spl, in the beginning the default
      environment is used until later in boot process the dynamic environment is read
      out. This way environment variables that must be interpreted early, like the
      baudrate or "silent", cannot be modified dynamically and remain at their
      default values. Fix this problem by reading out main and redundand (if used)
      copies of the environment in the nand_spl code.
      
      Signed-off-by: default avatarGuennadi Liakhovetski <lg@denx.de>
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
      b74ab737
  2. Jul 06, 2009
  3. Jun 21, 2009
    • Magnus Lilja's avatar
      MX31: Add NAND SPL for i.MX31. · 40c642bc
      Magnus Lilja authored
      
      This patch adds the NAND SPL framework needed to boot i.MX31 boards
      from NAND.
      
      It has been tested on a i.MX31 PDK board with large page NAND. Small
      page NANDs should work as well, but this has not been tested.
      
      Note: The i.MX31 NFC uses a non-standard layout for large page NANDs,
      whether this is compatible with a particular setup depends on how
      the NAND device is programmed by the flash programmer (e.g. JTAG
      debugger).
      
      The patch is based on the work by Maxim Artamonov.
      
      Signed-off-by: default avatarMaxim Artamonov <scn1874@yandex.ru>
      Signed-off-by: default avatarMagnus Lilja <lilja.magnus@gmail.com>
      40c642bc
  4. May 15, 2009
  5. Mar 20, 2009
    • Trent Piepho's avatar
      Fix all linker script to handle all rodata sections · f62fb999
      Trent Piepho authored
      
      A recent gcc added a new unaligned rodata section called '.rodata.str1.1',
      which needs to be added the the linker script.  Instead of just adding this
      one section, we use a wildcard ".rodata*" to get all rodata linker section
      gcc has now and might add in the future.
      
      However, '*(.rodata*)' by itself will result in sub-optimal section
      ordering.  The sections will be sorted by object file, which causes extra
      padding between the unaligned rodata.str.1.1 of one object file and the
      aligned rodata of the next object file.  This is easy to fix by using the
      SORT_BY_ALIGNMENT command.
      
      This patch has not be tested one most of the boards modified.  Some boards
      have a linker script that looks something like this:
      
      *(.text)
      . = ALIGN(16);
      *(.rodata)
      *(.rodata.str1.4)
      *(.eh_frame)
      
      I change this to:
      
      *(.text)
      . = ALIGN(16);
      *(.eh_frame)
      *(SORT_BY_ALIGNMENT(SORT_BY_NAME(.rodata*)))
      
      This means the start of rodata will no longer be 16 bytes aligned.
      However, the boundary between text and rodata/eh_frame is still aligned to
      16 bytes, which is what I think the real purpose of the ALIGN call is.
      
      Signed-off-by: default avatarTrent Piepho <xyzzy@speakeasy.org>
      f62fb999
  6. Mar 09, 2009
  7. Jan 28, 2009
  8. Jan 26, 2009
  9. Jan 23, 2009
    • Ron Madrid's avatar
      mpc83xx: New board support for SIMPC8313 · 5bb907a4
      Ron Madrid authored
      
      This patch will create a new board, SIMPC8313, from Sheldon Instruments.  This
      board boots from NAND devices and is configureable for either large or small
      page devices.  The board supports non-soldered DDR2, one ethernet port, a
      Marvell 88E1118 PHY, and PCI host support.  The board also has a FPGA connected
      to the eLBC providing glue logic to a TMS320C67xx DSP.
      
      Signed-off-by: default avatarRon Madrid <ron_madrid@sbcglobal.net>
      Signed-off-by: default avatarKim Phillips <kim.phillips@freescale.com>
      5bb907a4
    • Dave Liu's avatar
      NAND: Fix cache and memory inconsistency issue · c70564e6
      Dave Liu authored
      
      We load the secondary stage u-boot image from NAND to
      system memory by nand_load, but we did not flush d-cache
      to memory, nor invalidate i-cache before we jump to RAM.
      When the system has cache enabled and the TLB/page attribute
      of system memory is cacheable, it will cause issues.
      
      - 83xx family is using the d-cache lock, so all of d-cache
        access is cache-inhibited. so you can't see the issue.
      - 85xx family is using d-cache, i-cache enable, partial
        cache lock. you will see the issue.
      
      This patch fixes the cache issue.
      
      Signed-off-by: default avatarDave Liu <daveliu@freescale.com>
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
      c70564e6
  10. Nov 18, 2008
  11. Oct 29, 2008
  12. Oct 18, 2008
  13. Aug 30, 2008
  14. Aug 21, 2008
  15. Aug 14, 2008
  16. Aug 12, 2008
  17. Aug 06, 2008
  18. Jul 29, 2008
  19. Jun 12, 2008
    • Becky Bruce's avatar
      Change initdram() return type to phys_size_t · 9973e3c6
      Becky Bruce authored
      
      This patch changes the return type of initdram() from long int to phys_size_t.
      This is required for a couple of reasons: long int limits the amount of dram
      to 2GB, and u-boot in general is moving over to phys_size_t to represent the
      size of physical memory.  phys_size_t is defined as an unsigned long on almost
      all current platforms.
      
      This patch *only* changes the return type of the initdram function (in
      include/common.h, as well as in each board's implementation of initdram).  It
      does not actually modify the code inside the function on any of the platforms;
      platforms which wish to support more than 2GB of DRAM will need to modify
      their initdram() function code.
      
      Build tested with MAKEALL for ppc, arm, mips, mips-el. Booted on powerpc
      MPC8641HPCN.
      
      Signed-off-by: default avatarBecky Bruce <becky.bruce@freescale.com>
      9973e3c6
  20. Jun 04, 2008
  21. Jun 03, 2008
    • Kenneth Johansson's avatar
      Remove shell variable UNDEF_SYM. · 2918eb9d
      Kenneth Johansson authored
      
      UNDEF_SYM is a shell variable in the main Makefile used to force the
      linker to add all u-boot commands to the final image. It has no use here.
      
      Signed-off-by: default avatarKenneth Johansson <kenneth@southpole.se>
      2918eb9d
    • Stefan Roese's avatar
      ppc4xx: Change Kilauea to use the common DDR2 init function · ec724f88
      Stefan Roese authored
      
      This patch changes the kilauea and kilauea_nand (for NAND booting)
      board port to not use a board specific DDR2 init routine anymore. Now
      the common code from cpu/ppc4xx is used.
      
      Thanks to Grant Erickson for all his basic work on this 405EX early
      bootup.
      
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      ec724f88
    • Stefan Roese's avatar
      ppc4xx/NAND_SPL: Consolidate 405 and 440 NAND booting code in start.S · 64852d09
      Stefan Roese authored
      
      This patch consolidates the 405 and 440 parts of the NAND booting code
      selected via CONFIG_NAND_SPL. Now common code is used to initialize the
      SDRAM by calling initdram() and to "copy/relocate" to SDRAM/OCM/etc.
      Only *after* running from this location, nand_boot() is called.
      
      Please note that the initsdram() call is now moved from nand_boot.c
      to start.S. I experienced problems with some boards like Kilauea
      (405EX), which don't have internal SRAM (OCM) and relocation needs to
      be done to SDRAM before the NAND controller can get accessed. When
      initdram() is called later on in nand_boot(), this can lead to problems
      with variables in the bss sections like nand_ecc_pos[].
      
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Acked-by: default avatarScott Wood <scottwood@freescale.com>
      64852d09
  22. May 14, 2008
  23. Apr 30, 2008
  24. Apr 18, 2008
  25. Mar 15, 2008
    • Stefan Roese's avatar
      ppc4xx: Add Canyonlands NAND booting support · 71665ebf
      Stefan Roese authored
      
      460EX doesn't support a fixed bootstrap option to boot from 512 byte page
      NAND devices. The only bootstrap option for NAND booting is option F for
      2k page devices. So to boot from a 512 bype page device, the I2C bootstrap
      EEPROM needs to be programmed accordingly.
      
      This patch adds basic NAND booting support for the AMCC Canyonlands aval
      board and also adds support to the "bootstrap" command, to enable NAND
      booting I2C setting.
      
      Tested with 512 byte page NAND device (32MByte) on Canyonlands.
      
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      71665ebf
  26. Jan 12, 2008
    • Wolfgang Denk's avatar
      Fix linker scripts: add NOLOAD atribute to .bss/.sbss sections · 64134f01
      Wolfgang Denk authored
      
      With recent toolchain versions, some boards would not build because
      or errors like this one (here for ocotea board when building with
      ELDK 4.2 beta):
      ppc_4xx-ld: section .bootpg [fffff000 -> fffff23b] overlaps section .bss [fffee900 -> fffff8ab]
      
      For many boards, the .bss section is big enough that it wraps around
      at the end of the address space (0xFFFFFFFF), so the problem will not
      be visible unless you use a 64 bit tool chain for development. On
      some boards however, changes to the code size (due to different
      optimizations) we bail out with section overlaps like above.
      
      The fix is to add the NOLOAD attribute to the .bss and .sbss
      sections, telling the linker that .bss does not consume any space in
      the image.
      
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      64134f01
  27. Jan 09, 2008
  28. Jan 04, 2008
Loading