1. 20 Aug, 2010 2 commits
  2. 19 Aug, 2010 5 commits
  3. 18 Aug, 2010 6 commits
    • Wolfgang Denk's avatar
    • Sandeep Paulraj's avatar
      ARM: Update ARM mach-types · 9ce2c4b7
      Sandeep Paulraj authored
      This patch updates the mach-types.h based on the latest linux kernel
      Signed-off-by: default avatarSandeep Paulraj <s-paulraj@ti.com>
      9ce2c4b7
    • Philippe De Muyter's avatar
      Work around bug in Numonyx P33/P30 256-Mbit 65nm flash chips. · 54652991
      Philippe De Muyter authored
      I have "ported" U-boot to a in house made board with Numonyx Axcell P33/P30
      256-Mbit 65nm flash chips.
      
      After some time :( searching for bugs in our board or soft, we have
      discovered that those chips have a small but annoying bug, documented in
      "Numonyx Axcell P33/P30 256-Mbit Specification Update"
      
      It states :
      When customer uses [...] block unlock, the block lock status might be
      altered inadvertently. Lock status might be set to either 01h or 03h
      unexpectedly (00h as expected data), which leads to program/erase failure
      on certain blocks.
      
      A working workaround is given, which I have applied and tested with success :
      
      Workaround:  If the interval between 60h and its subsequent command
      	     can be guaranteed within 20us, Option I is recommended,
      	     otherwise Option II (involves hardware) should be selected.
      Option I: The table below lists the detail command sequences:
      Command
      	      Data bus           Address bus       Remarks
      Sequence
        1              90h            Block Address
      						   Read Lock Status
        2             Read         Block Address + 02h
       (2)(3)                                      (1)
      3                60h           Block Address
       (2)(3)                                      (1)   Lock/Unlock/RCR Configuration
      4           D0h/01h/03h        Block Address
      Notes:
      (1) Block Address refers to RCR configuration data only when the 60h
          command sequence is used to set RCR register combined with 03h
          subsequent command.
      (2) For the third and fourth command sequences, the Block Address must
          be the same.
      (3) The interval between 60h command and its subsequent D0h/01h/2Fh/03h
          commands should be less than 20us.
      
      And here is a log comparison of a simple (destructive) flash test without
      and with the workaround.
      
       diff without-numonyx-workaround.log with-numonyx-workaround.log
       -U-Boot 2010.06-00696-g22b002c-dirty (Aug 16 2010 - 15:07:47)
       +U-Boot 2010.06-00696-g22b002c-dirty (Aug 16 2010 - 15:25:19)
      
        CPU:   Freescale MCF5484
               CPU CLK 200 MHz BUS CLK 100 MHz
        Board: Macq Electronique ME2060
        I2C:   ready
        DRAM:  64 MiB
        FLASH: 32 MiB
        In:    serial
        Out:   serial
        Err:   serial
        Net:   FEC0, FEC1
        -> flinfo
      
        Bank # 1: CFI conformant FLASH (16 x 16)  Size: 32 MB in 259 Sectors
          Intel Extended command set, Manufacturer ID: 0x89, Device ID: 0x8922
          Erase timeout: 4096 ms, write timeout: 1 ms
          Buffer write timeout: 5 ms, buffer size: 1024 bytes
      
          Sector Start Addresses:
          FE000000 RO   FE008000 RO   FE010000 RO   FE018000 RO   FE020000 RO
          FE040000 RO   FE060000 RO   FE080000 RO   FE0A0000 RO   FE0C0000 RO
          ...
          FFF80000 RO   FFFA0000 RO   FFFC0000 RO   FFFE0000 RO
        -> protect off all
        Un-Protect Flash Bank # 1
        ................... done
        -> erase all
        Erase Flash Bank # 1
        ................... done
        -> cp.b 1000000 fe000000 2000000
       -Copy to Flash... Flash not Erased
       +Copy to Flash... done
        ->
      Signed-off-by: default avatarPhilippe De Muyter <phdm@macqel.be>
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      54652991
    • Stefan Roese's avatar
      cfi_flash: Cleanup flash_print_info() · 70084df7
      Stefan Roese authored
      This patch does the following:
      
      - Extract code to detect if sector is erased into function
        sector_erased().
      - Because of this, we don't have variable declarations inside the
        sector loop in flash_print_info()
      - Change "return" to "break" in the "if (ctrlc()) statement:
        This fixes a problem with the resulting output. Before this
        patch the output was:
      
        Sector Start Addresses:
        FC000000        FC020000        FC040000   =>
      
        With this patch it is now:
      
        Sector Start Addresses:
        FC000000        FC020000        FC040000
        =>
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Cc: Kim Phillips <kim.phillips@freescale.com>
      Cc: Wolfgang Denk <wd@denx.de>
      70084df7
    • Philippe De Muyter's avatar
      Fix printing & reading of 16-bit CFI device identifiers · d77c7ac4
      Philippe De Muyter authored
      Fix reading and printing of CFI flashes 16-bit devices identifiers
      
      Nowadays CFI flashes have a 16-bit device identifier.  U-boot still
      print them and read them as if they were only 8-bit wide.  Fix that.
      Before:
        Intel Extended command set, Manufacturer ID: 0x89, Device ID: 0x1B
      After:
        Intel Extended command set, Manufacturer ID: 0x89, Device ID: 0x881B
      Signed-off-by: default avatarPhilippe De Muyter <phdm@macqel.be>
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      d77c7ac4
    • Kim Phillips's avatar
      cfi_flash: flinfo: allow user interrupt in flash print info fn · 2e97394a
      Kim Phillips authored
      flashes getting larger, users more impatient.
      Signed-off-by: default avatarKim Phillips <kim.phillips@freescale.com>
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      2e97394a
  4. 13 Aug, 2010 1 commit
  5. 12 Aug, 2010 6 commits
  6. 11 Aug, 2010 3 commits
  7. 10 Aug, 2010 10 commits
  8. 09 Aug, 2010 7 commits