Thanks- please keep the flashrom list included so everyone else can see your response as well. 
On Apr 12, 2013 1:42 AM, "Николай Николаев" <evrinoma@gmail.com> wrote:
>
> hi
>
> |Eon EN25S10:
> |+                .eraseblocks = { {32 * 1024, 4} },
> |+                .block_erase = spi_block_erase_d8,
> |The .block_erase appears to be wrong here- it should be spi_block_erase_52 according to the datasheet.
> |
> |Eon EN25S16:
> |+                .eraseblocks = { {32 * 1024, 64} },
> |+                .block_erase = spi_block_erase_52,
>
> |It appears both the .eraseblocks and the .block_erase are wrong:
> |.eraseblocks should be  { {64  * 1024, 32} } - there are 32 blocks of 64 KBytes, not 64 blocks of 32 KBytes.
> |.block_erase uses spi_block_erase_52 when it should use spi_block_erase_d8.
>
>
> you are right. this is my a typos. And i rechecked my patch with all chips parameters and found new some typos. I will rewrite a patch and resend him.
>
> |AMIC A25LQ016: I couldn't find a datasheet for this chip available- I've got a A25LQ032 datasheet, but not one for the A25LQ016. Could you point me to that
> |sheet, or provide me with a copy?
>
> Sorry this is my typos.
> Could you try to search again something like a A25LQ16
>  
> |Eon EN25S32:
> |+                .eraseblocks = { {32 * 1024, 128} },
> |+                .block_erase = spi_block_erase_52,
> |I don't see where you are getting that .eraseblocks from- I can't find it in the datasheet.
> |I also don't know where the .block_erase came from- there is no 0x52 opcode in the datasheet.
>
> http://www.transonics.com/images/file/pdf/eon/EN25S32.pdf
> please see page 1 and page 5 - memory organization 
> •Uniform Sector Architecture:
> -1024 sectors of 4-Kbyte
> -128 blocks of 32-Kbyte
> -64 blocks of 64-Kbyte
> -Any sector or block can be erased individually
>  
> please see page 12 - Table 4A. Instruction Set
> this is chip has a 0x52 opcode in the datasheet
>
> i think if the flashrom wiki page to give the link on chip documentation that It will be great decision to avoid problem with name chip and searching documentations.
>
> --
> With best regards Nikolay Nikolaev
> С Уважением Николаев Николай