<br><br><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>The SST25VF040B was added before the new naming scheme was implemented. We did not want to break any existing software which depends on certain strings.</div>
</div></div></div></blockquote><div>Ok i support your fears. it is old chip and has a small capacity.š</div><div>š { <br>
.vendor = "SST", <br>
.name = "SST25VF032B", <br>
.bustype = BUS_SPI, <br>
.manufacture_id = SST_ID, <br>
.model_id = SST_SST25VF032B, <br>
.total_size = 4096, <br>
.page_size = 256, <br>
.feature_bits = FEATURE_WRSR_EWSR, <br>
.tested = TEST_OK_PREW, š<br>
.probe = probe_spi_rdid, <br>
.probe_timing = TIMING_ZERO, <br>
.block_erasers = <br>
{ <br>
{ <br>
.eraseblocks = { {4 * 1024, 1024} }, <br>
.block_erase = spi_block_erase_20, <br>
}, { <br>
.eraseblocks = { {32 * 1024, 128} }, <br>
.block_erase = spi_block_erase_52, <br>
}, { <br>
.eraseblocks = { {64 * 1024, 64} }, <br>
.block_erase = spi_block_erase_d8, <br>
}, {<br> .eraseblocks = { {4 * 1024 * 1024, 1} },<br> .block_erase = spi_block_erase_60,<br> }, {<br> .eraseblocks = { {4 * 1024 * 1024, 1} },<br>
.block_erase = spi_block_erase_c7,<br> },<br> },<br> .printlock = spi_prettyprint_status_register_sst25, /* TODO: check */<br> .unlock = spi_disable_blockprotect,<br>
.write = spi_aai_write, š š š š š š š š š š š š š š š š š š š š š š š š/* what do i see? - this is a fetch š*/<br> .read = spi_chip_read,<br> .voltage = {2700, 3600},<br>
},</div><div><br></div><div>for example:</div><div>if i used chip MX25L3205 and i want to change it on SST25VF032B, that i can't reprogram chip because this chip didn't have a AAI OPcodes 0xAD (i can't change opcodes in SPI controller). But i knowšmy controller has a standard codes for reading and page programming.š<br>
<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Voltage can be important for external programmer usage. It's not much effort to add it, anyway.<br>
</div></div></div></div></blockquote><div>š</div><div>How will you choosešvoltage for external program if you want to program MX25L6439E and MX25U6435F? What value we will write to field voltage?</div><div>š</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="im">Some SST25VF040B chips identify using the REMS opcode, others use RDID. Complain to the manufacturer :-)</div></div></div></div></blockquote>
<div>Sorry but i can't found REMS code in documentation on this chip. Mayby you give me link on pdf and išwill be study on my free time. 8)</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Support for this chip came before the new naming scheme. In the future, part names like this will be written as "EN25Q80...P" where the dot '.' is a wildcard for each letter which does not affect programming capabilities.</div>
</div></div></div></blockquote><div><br></div><div>Ok how will you mark next chips MX25L6439E and MX25U6435F? That chips has a identical chip ID = 0x2537. if if will be MX25.64...(F) that i think it's don't readable.</div>
<div><br clear="all"></div></div><br>-- <br><div>With best regards Nikolay Nikolaev</div><div>ó õ×ÁÖÅÎÉÅÍ îÉËÏÌÁÅ× îÉËÏÌÁÊ</div>