summaryrefslogtreecommitdiffstats
path: root/board/bf527-ezkit
diff options
context:
space:
mode:
authorJohn Schmoller <jschmoller@xes-inc.com>2010-10-22 00:20:25 -0500
committerKumar Gala <galak@kernel.crashing.org>2010-10-22 02:17:19 -0500
commit72fb68d53cfbe505319cbb4aa92a1fe7ecf3d4fb (patch)
tree560c19ad46b92223c88e5f67173b6bfed7b23788 /board/bf527-ezkit
parent92af6549b8c52e9c973e4e197aa4d1edf4df5803 (diff)
downloadu-boot-72fb68d53cfbe505319cbb4aa92a1fe7ecf3d4fb.tar.gz
u-boot-72fb68d53cfbe505319cbb4aa92a1fe7ecf3d4fb.tar.xz
u-boot-72fb68d53cfbe505319cbb4aa92a1fe7ecf3d4fb.zip
xes: Add board_flash_wp_on()
Add board_flash_wp_on() to check a pca9557 gpio pin to see if non-volatile memory write protection is enabled. Previously, write protected NOR flashes would fail initialization which resulted in a bootup error such as: ... DTT: 53 C local / 64 C remote (adt7461@4c) DTT: 54 C local (ds1621@48) FLASH: Executed from FLASH1 POST memory PASSED FLASH: ## Unknown FLASH on Bank 1 - Size = 0x00000000 = 0 MB ## Unknown FLASH on Bank 2 - Size = 0x00000000 = 0 MB *** failed *** ### ERROR ### Please RESET the board ### With this patch, NOR flash initialization is skipped: ... DTT: 53 C local / 64 C remote (adt7461@4c) DTT: 54 C local (ds1621@48) FLASH: Executed from FLASH1 POST memory PASSED FLASH: Uninitialized - Write Protect On L2: 1024 KB enabled NAND: 1024 MiB ... Note that flash related commands such as flinfo and saveenv will error out when flash write protection is enabled. Signed-off-by: John Schmoller <jschmoller@xes-inc.com> Signed-off-by: Peter Tyser <ptyser@xes-inc.com> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Diffstat (limited to 'board/bf527-ezkit')
0 files changed, 0 insertions, 0 deletions