> Well I bricked a $15k board today :) > > The Flash on this ARM926EJ-S core board is 2 512Mbit NOR Spansion > S29GL512N-11F chips arranged 32M x 32bit.
If you paid $15K for an ARM926EJ-S board, it sounds like you got screwed -- but because I now feel bad for you, I'm totally willing to sell you another for half price :) > I was reading & writing to a blank sector just to test out my configs and > I noticed that when I did any fill command (b,h,w) to flash, when I read > back I didn't get the same results. > > Here is what a flash fillb 0x20000000 0xaa 128 looks like: > 0x20030000: ffffaaaa ffffaaaa ffffaaaa ffffaaaa ffffaaaa ffffaaaa ffffaaa ffffaaaa > 0x20030020: ffffaaaa ffffaaaa ffffaaaa ffffaaaa ffffaaaa ffffaaaa ffffaaaa > ffffaaaa > 0x20030040: ffffaaaa ffffaaaa ffffaaaa ffffaaaa ffffaaaa ffffaaaa ffffaaaa > ffffaaaa > 0x20030060: ffffaaaa ffffaaaa ffffaaaa ffffaaaa ffffaaaa ffffaaaa ffffaaaa > ffffaaaa Looks like you have the chip select configured wrong. Without knowing anything else about your processor, it seems as though the access width is configured incorrectly based on what you show here. > But that wasn't the bad news ... when I rebooted ... no u-boot. > Displaying memory where uboot "was" showed that half the words of the > address where it lived were filled with 0xffff so something went crazy and > hosed my flash in areas I wasn't even messing with. That could also be explained by having a bad config for your peripheral bus. --Chris _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
