Post #875876

hai to all hardware hackers/u-boot knowers !!! (boosts appreciated) a firmware update killed my embedded device (powerpc 40x) and now it wont boot, but i managed to get to a uboot (v1.0.0) console over serial and discovered that the memory-mapped area of flash where the linux ramdisk image is supposed to be is just FULL of FFs. i know the flash isnt totally cooked because i was able to run saveenv and it does persist , but is it possible that only SOME of the sectors could be broken somehow? none of the memory write commands change anything , its just a ton of FFs in that part of flash when i run md. i know everything else works because if i "tethered boot" it by using tftpboot to save the ramdisk to an area of RAM via a network and then change the offset to point to it, it boots fine. but obviously i want it to work without having to do that. i dont know how any of this works really, this is my first time in a uboot console :o