1. 29 May, 2010 1 commit
  2. 26 May, 2010 5 commits
  3. 24 May, 2010 5 commits
  4. 21 May, 2010 4 commits
  5. 20 May, 2010 1 commit
    • gcembed's avatar
      nand : Add Freescale iMX27 nand flash controller support · f40faeb3
      gcembed authored
      This patch add support of iMX27 nand flash controller. This is based on
      driver for imx31 nand flash controller.
      OOB functionality is not fully working. As in mx31 controller, mx2 NFC
      has a bug that swap two bytes between SPARE and MAIN buffer.
      I used this driver for several months and no problems appear.
      f40faeb3
  6. 19 May, 2010 2 commits
    • Gary Carlson's avatar
      reset: fix reset halt bug · 8465e994
      Gary Carlson authored
      
      
      I was finally able to figure out the cause of this problem.  There are two
      parts to the patch.  The first patch modifies the configuration file I
      originally generated for the Atmel AT91SAM9G20 board and achieves the
      following:
      
      +++ Splits the reset-init handler into a reset-start handler for some of the
      initial configuration activities and keeps the remainder in the reset-init
      handler as was the case before.  This was the real issue that was causing
      the timing problems I identified before.  This solution was confirmed with
      an o-scope on actual target hardware.
      
      +++ Adds a new instruction in the reset-start handler to disable fast memory
      accesses in the reset-start handler.  When the target jtag clock is started
      out at 2 kHz during system clock initialization, memory writes (i.e.
      register write to enable external reset pin -- basically to RSTC_MR) are
      naturally slow and cause GDB keep-alive issues (refer to PATCH 2/2 for
      additional fixes).
      
      +++ Modifies the configuration file to use srst_only reset action. The
      reset-start/reset-init handler split also now allows the correct behavior to
      be used in the configuration file (previously had to use both SRST and TRST
      even though only SRST is actually used and connected on the evaluation
      board).
      
      +++ Adds external NandFlash configuration support to take advantage of flash
      driver added earlier.  Doesn't fix any bugs but adds functionality that was
      marked as TBD before and thrown in when I did other work on the
      configuration file.
      
      Signed-off-by: default avatarØyvind Harboe <oyvind.harboe@zylin.com>
      8465e994
    • Gary Carlson's avatar
      target: slow targets could cause GDB to time out · b80d0501
      Gary Carlson authored
      This second half of the patch is proposed to clean up some GDB keep alive
      issues on arm7_9 targets that start up with very slow clocks.  If an attempt
      is made to write to key registers on the processor with a slow jtag speed,
      GDB timeout warnings appear on the console (at least mine) when "reset halt"
      or "reset init" commands are issued from the gdb client:
      
      *** BEFORE PATCH ***
      
      (gdb) monitor reset init
      fast memory access is disabled
      2 kHz
      keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not
      sent! (1026). Workaround: increase "set remotetimeout" in GDB
      JTAG tap: at91sam9g20.cpu tap/device found: 0x0792603f (mfg: 0x01f, part:
      0x7926, ver: 0x0)
      target state: halted
      target halted in ARM state due to breakpoint, current mode: Supervisor
      cpsr: 0x000000d3 pc: 0x00000000
      MMU: disabled, D-Cache: disabled, I-Cache: disabled
      keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not
      sent! (1027). Workaround: increase "set remotetimeout" in GDB
      keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not
      sent! (1006). Workaround: increase "set remotetimeout" in GDB
      keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not
      sent! (1006). Workaround: increase "set remotetimeout" in GDB
      keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not
      sent! (1006). Workaround: increase "set remotetimeout" in GDB
      keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not
      sent! (1004). Workaround: increase "set remotetimeout" in GDB
      RCLK - adaptive
      dcc downloads are enabled
      fast memory access is enabled
      NAND flash device 'NAND 256MiB 3,3V 8-bit' found
      (gdb)
      
      I added additional keep alive steps in areas that troubleshooting revealed
      were causing problems.  I only did this however for non-fast write memory
      accesses.  I don't think most people would be using fast memory accesses to
      write to memory when the jtag and system clocks are slow anyway.
      
      If you disagree with my feeling, think there is a more elegant way to handle
      the problem, or think the patch will cause other unforeseen problems with
      other targets, let me know.  As you can see below, the patch does eliminate
      the problem on my development station and I suspect that it will benefit
      others.
      
      *** AFTER PATCH ***
      
      (gdb) monitor reset init
      fast memory access is disabled
      2 kHz
      JTAG tap: at91sam9g20.cpu tap/device found: 0x0792603f (mfg: 0x01f, part:
      0x7926, ver: 0x0)
      target state: halted
      target halted in ARM state due to breakpoint, current mode: Supervisor
      cpsr: 0x000000d3 pc: 0x00000000
      MMU: disabled, D-Cache: disabled, I-Cache: disabled
      RCLK - adaptive
      dcc downloads are enabled
      fast memory access is enabled
      NAND flash device 'NAND 256MiB 3,3V 8-bit' found
      (gdb)
      
      Gary Carlson
      
      Gary Carlson, MSEE
      Principal Engineer
      Carlson-Minot Inc.
      b80d0501
  7. 18 May, 2010 5 commits
  8. 17 May, 2010 1 commit
  9. 16 May, 2010 12 commits
  10. 15 May, 2010 1 commit
  11. 14 May, 2010 3 commits