[flashrom] [PATCH] Dediprog SF100 support

[Carl-Daniel Hailfinger]

On 15.01.2010 17:08, Stefan Reinauer wrote:
> On 1/15/10 4:28 PM, Carl-Daniel Hailfinger wrote:
>   
>>> MacPro:flashrom stepan$ ./flashrom -p dediprog -V
>>> flashrom v0.9.1-r862
>>> Found USB device (0483:dada).
>>> Sending RDID
>>> Receiving response: 20 20 16 10 00 00 00 00 00 00 00 00 00 00 00 00
>>>     
>>>       
>> Which flash chip is this? The response suggests a ST M25P32 flash chip,
>> but the extra "10" at the end looks rather strange.
>>   
>>     
> It's a Numonyx M25P32 (until a couple of years ago parts of the company
> were known as SP)
>   

OK, thanks for confirming.


> Here I added this:
>   
>>>> buf[0xf]=0;
>>>> msg_pdbg("Found a Dediprog %s\n", buf);
>>>>     
>>>>       
>>>>         
>> That potentially truncates the string. I'll use strnlen/strncpy to write
>> the string to a separate buffer which is big enough.
>>   
>>     
> Yes, I just didn't want to fiddle with the buffer size and all dediprog
> devices I've seen have a space in the last character.
> Using a 0x11 bytes big buffer would be the correct approach.
>   

That's an option as well, right.


>>> Let me know if you need more information
>>>   
>>>     
>>>       
>> A log with SniffUsb 2.0.0006 from
>> http://www.pcausa.com/Utilities/UsbSnoop/ would be very appreciated.
>> I wrote a tool to decode the log generated with that SniffUsb version.
>> Feel free to point me to a private upload via IRC (the log may contain
>> programmer serial numbers).
>>
>>   
>>     
> Will produce these asap.
>   

Thanks.


>> It would be cool if you could use a small SPI chip (4 Mbit or so)
>> because the logs roughly have 4x-20x the size of the flash chip.
>>   
>>     
> That might be a problem, I think 32MBit are the only ones I have here at
> the moment.. :-}
> I'll have a look.
>   

OK, I can parse that stuff, it's just that the log may be rather large
(80-160 MByte).


>> Please do not use a SST chip (log would be at least 100x the size of the
>> flash chip). Pretty much all other vendors are OK.
>>   
>>     
> Why is that?
>   

SST doesn't support page write, so you get one USB transaction per
written byte. And one transaction takes ~1100 bytes (so yes, I was off
by an order of magnitude) in the log. I doubt you want to upload a log
with a size of 4 Gigabytes. Plus, my scripts will take a long time to
run on such a big log, and besides that the information gathered from a
SST log would be essentially zero because it has no long write
transactions (which is pretty much the only transaction type I don't
have in my log yet).

Regards,
Carl-Daniel

-- 
Developer quote of the year:
"We are juggling too many chainsaws and flaming arrows and tigers."