[#4533] write/erase flash cause watchdog not working
Submitted By: david wang
Open Date
2008-10-15 23:25:08 Close Date
2008-12-17 14:52:39
Priority:
Medium High Assignee:
Mike Frysinger
Status:
Closed Fixed In Release:
N/A
Found In Release:
2008R1.5-RC3 Release:
Category:
N/A Board:
N/A
Processor:
BF537 Silicon Revision:
0.2
Is this bug repeatable?:
Yes Resolution:
Rejected
Uboot version or rev.:
u-boot-1.1.6-2008R1.5 Toolchain version or rev.:
App binary format:
N/A
Summary: write/erase flash cause watchdog not working
Details:
If I add flash write operation into crash_test, the watchdog daemon can't reboot the system successfully after crash, and the board hang. By a jtag ice, I found it did assert a reset, but the u-boot not start. After one day's debugging, I thing I have found the problem making the board hang. I put a hardware breakpoint at 0x20000000 and another at 0x20000004. if every thing goes well, each breakpoint should be hit once when the system reboot , just like manual rest in u-boot. In my test, it can only reach the first breakpoint, not the next. I use x command to check the flash, it show me all of 0x00800080, that means the flash is not ready. But, I just find the problem, I don't know why the flash status is not ready, and how to fix it. Does anyone have any idea? Thanks
pls try my test program -- see attached file, in your stamp board to help me find out it's a hardware or software issue? Thanks a lot! The only thing you should change is the flash device. In my test , I use dev/mtd3. I have create 8 mtd device in my board.
I'm using my bf537 board which is very simular to STAMP board, with a intel 28f320c3t flash.
Follow-ups
--- Mike Frysinger 2008-12-17 14:52:38
not a bug in the watchdog/software. limitation in hardware.
Files
Changes
Commits
Dependencies
Duplicates
Associations
Tags
File Name File Type File Size Posted By
crash_test.c application/octet-stream 977 david wang