On Tuesday, April 29, 2003, at 07:42 AM, ron minnich wrote:
Do you have a plain old flash part you can put in there? SST 28SF040 is ideal.
So I ordered the flash parts that were already in the machine when I bought it, the chances of another type of flash working is slim to none right? Were I to purchase the one above, how would I know if it would work?
On Tue, 29 Apr 2003, Nathanael Noblet wrote:
So I ordered the flash parts that were already in the machine when I bought it, the chances of another type of flash working is slim to none right? Were I to purchase the one above, how would I know if it would work?
better yet, let's just try to fix flash_rom so it works for you.
Tell me the flash part # again.
ron
On Tuesday, April 29, 2003, at 10:07 AM, ron minnich wrote:
On Tue, 29 Apr 2003, Nathanael Noblet wrote:
So I ordered the flash parts that were already in the machine when I bought it, the chances of another type of flash working is slim to none right? Were I to purchase the one above, how would I know if it would work?
better yet, let's just try to fix flash_rom so it works for you.
Tell me the flash part # again.
w29c020c (p90b)
spec sheet I just found is available at http://www.winbond.com/e-winbondhtm/partner/b_2_h_1_1.htm the p90b is for plcc 90ns and b I can't remember...
Tell me the flash part # again.
w29c020c (p90b)
It is already supported.
-Andrew
On Tue, 2003-04-29 at 11:10, Andrew Ip wrote:
Tell me the flash part # again.
w29c020c (p90b)
It is already supported.
-Andrew
ok so it may be supported but I get nothing when I run ./flash_rom with no arguments. So if it is supported and I'm not even to the point of trying to write to the flash. How come it is not detected? What can I start doing to fix it? Where do I look, what do I look at? etc... Here's the output of ./flash_rom
Try 2097152 timeusec is 44995 Try 20971520 timeusec is 449132 Try 209715200 timeusec is 4491720 one us is 466 count Trying Am29F040B, 512 KB probe_29f040bid1 37, id2 241 Trying At29C040A, 512 KB probe_jedecid1 37, id2 241 Trying Mx29f002, 256 KB probe_29f002id1 37, id2 241 Trying SST29EE020A, 256 KB probe_jedecid1 37, id2 241 Trying SST28SF040A, 512 KB probe_28sf040id1 37, id2 241 Trying SST39SF020A, 256 KB probe_39sf020id1 37, id2 241 Trying SST39VF020, 256 KB probe_39sf020id1 37, id2 241 Trying W29C020C, 256 KB probe_jedecid1 37, id2 241 Trying W49F002U, 256 KB probe_49f002id1 37, id2 241 Trying M29F400BT, 512 KB probe_m29f400bt id1 25, id2 2d Trying 82802ab, 512 KB probe_82802abid1 37, id2 241 EEPROM not found
On 29 Apr 2003, Nathanael D. Noblet wrote:
look in flash.h. id1 is the vendor, and i2 is the part. 37 is 25 hex, which is an unknown vendor to me.
I think we may still be at 'no write enable to flash :-('
ron
On Tue, 2003-04-29 at 13:36, ron minnich wrote:
On 29 Apr 2003, Nathanael D. Noblet wrote:
look in flash.h. id1 is the vendor, and i2 is the part. 37 is 25 hex, which is an unknown vendor to me.
I removed the current flash chip that was in there and replaced it with one of the ones I bought. Ran ./flash_rom again and got... Try 2097152 timeusec is 44994 Try 20971520 timeusec is 449133 Try 209715200 timeusec is 4491595 one us is 466 count Trying Am29F040B, 512 KB probe_29f040bid1 255, id2 255 Trying At29C040A, 512 KB probe_jedecid1 255, id2 255 Trying Mx29f002, 256 KB probe_29f002id1 255, id2 255 Trying SST29EE020A, 256 KB probe_jedecid1 255, id2 255 Trying SST28SF040A, 512 KB probe_28sf040id1 255, id2 255 Trying SST39SF020A, 256 KB probe_39sf020id1 255, id2 255 Trying SST39VF020, 256 KB probe_39sf020id1 255, id2 255 Trying W29C020C, 256 KB probe_jedecid1 255, id2 255 Trying W49F002U, 256 KB probe_49f002id1 255, id2 255 Trying M29F400BT, 512 KB probe_m29f400bt id1 ff, id2 ff Trying 82802ab, 512 KB probe_82802abid1 255, id2 255 EEPROM not found
I think we may still be at 'no write enable to flash :-('
so to be able to detect the flash part I need to enable flash write? I have the data sheet and found the sequence of commands to enable flash write to it. but that still doesn't explain the wrong return for the id1 & id2...
I'll look into it a little more. I think with the bit of reading I've found in the flash parts spec sheets I may be able to make a little more sense of the code found in flash_and_burn... hopefully ;)
On 29 Apr 2003, Nathanael D. Noblet wrote:
so to be able to detect the flash part I need to enable flash write? I have the data sheet and found the sequence of commands to enable flash write to it. but that still doesn't explain the wrong return for the id1 & id2...
flash write is not enabled, most likely. Do you have a scope handy?
ron
-
Andrew Ip -
Nathanael D. Noblet -
Nathanael Noblet
-
ron minnich