Where do I get the flash chip to use with it?

The chip is an AMD Flash chip in DIP package. Part number is AM29f010-120PC. The parts have come in two waves from AMD over the last 6 or so years. the 2nd wave are 100% compatible, but they have a B in them. so, when you see part numbers like am29f010B-120PC, they will also work perfectly.

  • the 010 refers to the size. So, you can also use 29f020, or 29f040 if you find them.

  • the -120 refers to the speed. You can also use -90 or -70 if you find one. the 90 and 70 are *faster*, but the ez-kit software is configured to access the memory nice and slowly. This is a good thing, because it eliminates compatibility problems. And before anyone asks...NO! There is no need to make the kit access it any faster. perhaps for some specific applicatioins, it would get you the performance you need, but not for everyday saving and loading. if you do need that performance, tell me, and I'll help you config your ez-kit to run at the faster rates.

  • the PC refers to DIP package. do not get JC, EC, etc. Those are the wrong packages and won't physically fit into your ez-kit.

  • Finally, do not get st ee 29010- they are NOT compatiable, despite what they tell you.


    many of us ez-kit hackers are getting into using the AMD29F040-120PC. You can get these for about five dollars from Avnet . However, you have to buy them in lots of 11 at this time. People periodically get together on the mailing list and buy them. at the moment, I have a small stock and will share them for only $6 if anyone writes me e-mail.

  • You can also use the AMD 29f040 flash chip in your ez-kit. You will have to modify your board DIFFERENTLY from using the am29f010. hopefully, I'll get to post instructions here for doing that, but for now, it was briefly discussed on the list around october/november. the pinout is on page 5 of the spec below.

    1)connect wr/ from the 2181 to the eprom socket,

    2)put the jumper in place for 4 mbit operation as per the schematic in the white book, and

    3)connect all address lines. Click here for the am29f040B data sheet.

    that link may change but this one may still work: am29f040B

    It used to be you could get them from a few catalogs around, but now the only place I know to get them in single quantities is from a very friendly Australian named Laurie Biddulph. Email Laurie!! and he can sell you the proper Flash Chip for a modest fee.

    What to do with it

    Now that you've got your flash chip, go ahead and modify your kit to be able to use it.

    At one time Newark had them for $5.19 (Feb. 2000) Newark Part Number was 05F4802. They don't sell them anymore (fools).

    Also, they are not sold by Digi-Key anymore (fools).

    What's up with these sector sizes?

    The am29f040 and am29f010 are the same, but different :P Basically, the 040 has 512KB in 8 sectors of 64KB each. The 010 has 8 sectors of 16KB each. For the purposes of the DFS file system, it's setup as PROGRAM SLOTS. A program SLOT is 16KB. The program slot size matches the 010 sector size, so DFS is a no-brainer on the 010. You get 8 program slots, each equal in size to a sector.

    If you want to use an 040, though, you must think (sorry, heh ;P). In the 040, there are 32 PROGRAM SLOTS, but still only 8 SECTORS. Each 64KB sector holds 4 16KB programs. So, when you erase a sector, which is done automatically when you select "Program a .EXE file" in DFS, you erase 4 programs (!) This is especially hazardous when use an 040 and program something into slots 0-3. Why? Because erasing slot 0,1,2 or 3 will erase the whole sector, which means your boot sector (in program slot 0) gets wiped out, and you must reprogram it.

    How do you get around this?

    First of all, because the first sector in an 040 contains the necessary boot code, I wouldn't use program slots 1,2 and 3. Just go right to 4. That way, you can erase sector 1 (meaning slots 4,5,6 and 7) without screwing up your boot code. Get it? Now, the 2nd thing you should do is when you have a program in slot 4, and you don't want to erase it, you should NOT select "Program .EXE" from DFS, because it will erase the whole sector, including slot 4. Instead, do the 4-step process: 1) exe2dfs 2) dfs2s2 3) erase sector 4) program s2 file.

    What about using the interrupt button to auto-boot into program slot 1?

    Here's a tip: modify newmon to boot out of program slot 4, instead of program slot 1. That way, you can easily develop in slot 4, without ever messing up your boot sector. To do that, simply change the "ar=1" to "ar=4" and recompile, and re-burn.


    { coolness }

    ar = 1;

    dm(exec_start_addr) = ar;

    call run2;