| Author |
 Topic  |
|
|
rvanzo
Italy
3 Posts |
 Posted - 06/28/2008 : 14:52:51
|
Simple question from a noob.
Can I program an AMIC A290021T using True USB Programmer? I did not found it in Compatible device list  .
I found there is a work-around for "dual power" version programmer, but it consists in pretending the device is an SST device (one device for clear and another device for read/write!) and those are not present in my GQ-3x rev 1.0 programmer "device compatibility list" too  !
Then I tried adding the device in device.txt but I'm stucked with device id....being not an expert...
Can you help me
Thanks.
Update:
Worked on it for a bit more...
Using AMIC datasheet i saw that Manifacturere ID for amic is 37h, and device id is 8C0Dh  .
Now I understand also that what really matters for inserting a new device in the list is the existence of a device CLASS using same programming algorithm. Perhaps generic 29F002 or 29F002NT will do, but there is no way to know this because "classes" are yet not documented (i think).
So perhaps adding
Name="A290021T",ID="8C0D",Class="29F002",Category="Flash",MFG="AMIC",
Package="DIP32",VCC="5v";
Will do it....BUT..
Using this settings and getting ID gives strange results: Manifacturere ID is 370C (concatenation of Manifacturer ID and Device's id top byte). It seems software gets Manifacturer's right value (the first byte) but maps on wrong byte position of JEDEC tables-> so Manifacturer is mapped wrongly on Zarlink (formerly Plessey).
Device ID comes out wrong too, because second (bottom) byte of device id is lost. Something really strange is happening, something like a single byte wrong offset both for Manifacturer (shoud it be 0037h?) and Device ID determination. So I feel it is a bit risky to try to program the device with my "supposed" parameters... I'll wait for advice from someone more expert on the subject than me.
PS: I tried 2.07 an 2.08beta software.
PS2: I probably found the device class for using the work-around: SST29EE010 for clearing (or W29EE010?) and class 29F002 or 29F002NT (don't know)for programming, but i'm not sure this works on true usb programmer: using both class for reading turns out "FF data" and wrong Manifacturer ID. |
Edited by - rvanzo on 06/29/2008 04:37:57
|
|
| Reply #1
ZLM
2945 Posts |
Posted - 06/29/2008 : 10:18:07
|
The device string should be:
Name="A290021T",ID="378C",Class="29F002",Category="Flash",MFG="AMIC",Package="DIP32",VCC="5V";
You should be able to get correct ID. Otherwise check your chip if well contacted with ZIF socket.
If not working, try:
Name="A290021T",ID="378C",Class="29F002",Category="Flash",MFG="AMIC",Package="DIP32",VCC="5V",RVPP="5V";
|
 |
|
| Reply #2
rvanzo
Italy
3 Posts |
Posted - 06/29/2008 : 17:17:47
|
Thanks for your perfect and quick answer ZLM.
In the meantime I discovered that datasheet of AMD AM29f002N is totally identical to datasheet of MIC A290021T (the only differerence is that AMIC did non complete some of the tests), so i tried configuring AM29F002NT/NBT (ignoring device id warnings)and everything went ok both with clearing and programming.
Seing your answer I'm very pleased because your solution, practically, is identical to what I did: class in this case is what really matters. Default VCC seems ok also, without specifing it.
Only one observation: for what I understand, using ID="378C" is an hack for ignoring bad ID reading/mapping (probably a sw problem). Am I right?
Thankyou.
It'a really a plasure to know the support on this product is so strong and made by competent and friendly people!
|
Edited by - rvanzo on 06/29/2008 17:19:12 |
|
|
| Reply #3
ZLM
2945 Posts |
Posted - 07/01/2008 : 14:28:21
|
The ID="378C" is not the hack. It is the real device ID of the chip. See datasheet page 11(Table 5).
The 37 is manufacturer ID.
There are two device IDs for this type of device: "8C" for A290021T and "0D" for A290021B.
So, basically you can add both chips into he device list:
Name="A290021T",ID="378C",Class="29F002",Category="Flash",MFG="AMIC";
Name="A290021B",ID="370D",Class="29F002",Category="Flash",MFG="AMIC";
|
|
|
| Reply #4
rvanzo
Italy
3 Posts |
Posted - 07/02/2008 : 13:52:08
|
I see.
I thought B and T were Top And Bottom Byte of the device ID (being this a 2-byte data) and did not know that the first byte was by design the Manifacturer id.
Did not know of the existence of a A290021B version of the device also.
Thankyou very much for the puntualization.
|
|
|
| |
Topic |
|
|
|
AMIC A290021T-70
