Guys,The normal story here. I have a M001 which has been bricked during a firmware upgrade process.I've connected up the console port to find out that it's dead as a door nail. Some people here have found that w-load is present, but U-Boot is missing (corrupt). In my case, w-load doesn't appear to be there either. I've had a cro on the console TXD pin (and RXD), and it doesn't appear to do anything, suggesting its not a baud rate problem, or one with my hardware (using a FT232R FTDI cable).From looking at some console logs posted, and the M001 boards, it appears there is two FLASH memory parts. There is a cFeon F40-100GCP SPI Serial Flash on the CPU Daughtercard (SO8) and a TSSOP parallel flash on the back of the main motherboard.It would also appear the WM8505 is bootstrapped to boot from the SPI serial flash after looking at console logs and the MTD partitions. There appears to be no MTD partition for w-load on the SAMSUNG_K9XXG08UXM parallel flash, only the SPI Flash.I've desoldered the SPI serial flash from the CPU DaughterCard. It has markings "cFeonF40-100GCP" and would appear to be a 4 Mbit Serial Flash from EON (EN25F40-100GCP, 100MHz, 8 pin 150mil SOP, Commercial Temp, Lead Free) part.I've been unable to talk to it properly. It is not responding correctly when I issue the Read Identification command, in fact it responds with 0x00 for all commands. I was hoping on reading the contents to get an understanding on where the firmware upgrade failed.I've got a replacement ATMEL 4 Mbit SPI Flash part (which works) and I now want to program w-load and u-boot onto it, and solder it back onto the CPU daughtercard and see what happens.However my problem is the partitioning. I believe its a 4 Mbit part (524,288 bytes) but the MTD table for the SPI Flash reports 16Mbytes :Creating 6 MTD partitions on "mtdsf device": (16,777,216 bytes)0x000000000000-0x000000d00000 : "filesystem-SF" (13,631,488 bytes)0x000000d00000-0x000000f80000 : "kernel-SF" (2,621,440 bytes)0x000000f80000-0x000000fd0000 : "u-boot-SF" (327,680 bytes)0x000000fd0000-0x000000fe0000 : "u-boot env. cfg. 1-SF" (65,636 bytes)0x000000fe0000-0x000000ff0000 : "u-boot env. cfg. 2-SF" (65,536 bytes)0x000000ff0000-0x000001000000 : "w-load-SF" (65,536 bytes)Is it possible to dump the raw contents of the serial flash if so, can someone provide it as a bin file?Otherwise, does anyone know how the serial flash is formatted? At what offset is w-load?