Author |
Topic |
|
iceman78
13 Posts |
Posted - 04/30/2019 : 09:24:04
|
I'm trying to program ic in the object but id gives me error and reads a 256k file. if instead I select W25Q64B it gives me ID Hex C22012 and type MX25L2005MC. If I read it this way I get a file of 8MB (correct size). but I can't understand if he reads it correctly. what should i do? |
|
Reply #1
anniel
2572 Posts |
Posted - 05/02/2019 : 08:09:41
|
quote: Originally posted by iceman78
I'm trying to program ic in the object but id gives me error and reads a 256k file. if instead I select W25Q64B it gives me ID Hex C22012 and type MX25L2005MC. If I read it this way I get a file of 8MB (correct size). but I can't understand if he reads it correctly. what should i do?
It seems both have the same ID. |
|
|
Reply #2
iceman78
13 Posts |
Posted - 05/02/2019 : 10:41:33
|
quote: it seems both have the same ID.
so what should i set to read it correctly? it is a bios of a computer and should be 8mb |
|
|
Reply #3
anniel
2572 Posts |
Posted - 05/02/2019 : 17:42:53
|
quote: Originally posted by iceman78
quote: it seems both have the same ID.
so what should i set to read it correctly? it is a bios of a computer and should be 8mb
If you use MX25L2005MC does it read? |
|
|
Reply #4
iceman78
13 Posts |
Posted - 05/02/2019 : 21:46:06
|
quote: If you use MX25L2005MC does it read?
reads a 250kb file. should read 8mb. and if I press the id button it tells me that it does not recognize the chip |
Edited by - iceman78 on 05/03/2019 00:15:10 |
|
|
Reply #5
laptech
United Kingdom
58 Posts |
Posted - 05/03/2019 : 06:10:10
|
It appears the chip you want to program mx25l2006e is not supported in the older GQ-4X machine. The max software version for the old machine is 6.38 but if you look on the sites supported devices list, it shows the chip is supported BUT under the latest software 7.23 which is for the newer machine, the GQ-4X V4.
What machine do you have, the GQ-4X or the GQ-4X V4 ?
Also, the supported device list shows that ADP-004 is required. Do you have this adapter? |
Laptronics UK LTd. Specialist motherboard repair. |
Edited by - laptech on 05/03/2019 06:13:23 |
|
|
Reply #6
anniel
2572 Posts |
Posted - 05/03/2019 : 07:39:57
|
quote: Originally posted by iceman78
quote: If you use MX25L2005MC does it read?
reads a 250kb file. should read 8mb. and if I press the id button it tells me that it does not recognize the chip
8 M-bits or 8 M-bytes? |
|
|
Reply #7
anniel
2572 Posts |
Posted - 05/03/2019 : 07:40:32
|
quote: Originally posted by laptech
It appears the chip you want to program mx25l2006e is not supported in the older GQ-4X machine. The max software version for the old machine is 6.38 but if you look on the sites supported devices list, it shows the chip is supported BUT under the latest software 7.23 which is for the newer machine, the GQ-4X V4.
What machine do you have, the GQ-4X or the GQ-4X V4 ?
Also, the supported device list shows that ADP-004 is required. Do you have this adapter?
Good questions. |
|
|
Reply #8
iceman78
13 Posts |
Posted - 05/03/2019 : 10:24:54
|
quote: Originally posted by laptech
It appears the chip you want to program mx25l2006e is not supported in the older GQ-4X machine. The max software version for the old machine is 6.38 but if you look on the sites supported devices list, it shows the chip is supported BUT under the latest software 7.23 which is for the newer machine, the GQ-4X V4.
What machine do you have, the GQ-4X or the GQ-4X V4 ?
Also, the supported device list shows that ADP-004 is required. Do you have this adapter?
I have GQ-4X4 1.0. Software version is 7.23. I have ADP-004. if I select the exact chip on the software with id read gives me all FFFFF (and I can read a few kbytes), instead if instead I select W25Q64B it gives me hexadecimal ID C22012 and chip MX25L2005MC. If I read it this way I get a file of 8 mega bytes (correct size). but I can't understand if he reads it correctly. what should I do? |
|
|
Reply #9
anniel
2572 Posts |
Posted - 05/03/2019 : 17:16:27
|
quote: Originally posted by iceman78
quote: Originally posted by laptech
It appears the chip you want to program mx25l2006e is not supported in the older GQ-4X machine. The max software version for the old machine is 6.38 but if you look on the sites supported devices list, it shows the chip is supported BUT under the latest software 7.23 which is for the newer machine, the GQ-4X V4.
What machine do you have, the GQ-4X or the GQ-4X V4 ?
Also, the supported device list shows that ADP-004 is required. Do you have this adapter?
I have GQ-4X4 1.0. Software version is 7.23. I have ADP-004. if I select the exact chip on the software with id read gives me all FFFFF (and I can read a few kbytes), instead if instead I select W25Q64B it gives me hexadecimal ID C22012 and chip MX25L2005MC. If I read it this way I get a file of 8 mega bytes (correct size). but I can't understand if he reads it correctly. what should I do?
That IS strange!?! If you can ID that way read should be correct more so if it is the right size. What happens if you try to write? |
|
|
Reply #10
iceman78
13 Posts |
Posted - 05/04/2019 : 01:42:14
|
quote:
If you can ID that way read should be correct more so if it is the right size. What happens if you try to write?
he writes but if I re-read the chip is empty |
Edited by - iceman78 on 05/04/2019 02:11:20 |
|
|
Reply #11
anniel
2572 Posts |
Posted - 05/04/2019 : 08:09:39
|
quote: Originally posted by iceman78
quote:
If you can ID that way read should be correct more so if it is the right size. What happens if you try to write?
he writes but if I re-read the chip is empty
Does it verify ok when written? |
|
|
Reply #12
laptech
United Kingdom
58 Posts |
Posted - 05/15/2019 : 00:42:51
|
I looked in the devices.txt file for software version 7.23 and what your saying in my opinion is impossible, unless you have corrupt files.
In the devices.txt file, this is the line that shows up for W25Q64B Name="W25Q64BVFIG*SOIC16 ",ID="EF4017",Class="W25X10",Category="SERIAL_EPROM",MFG="Winbond",Vcc="3.6V",CodeSize="8388608",Adapter="ADP-098 adapter";
Now when i search for the chip you are trying to use, mx25l2006e, this line shows up: Name="MX25L2006E",ID="C22012",Class="AT25FS010",Category="SERIAL_EPROM",MFG="Macronix",Vcc="3.6V",CodeSize="262144",Adapter="ADP-004";
Unless some corruption of the software files has occurred, it be impossible for the programmer to get the two chips confused with one another
|
Laptronics UK LTd. Specialist motherboard repair. |
|
|
Reply #13
anniel
2572 Posts |
Posted - 05/15/2019 : 02:42:58
|
quote: Originally posted by laptech
I looked in the devices.txt file for software version 7.23 and what your saying in my opinion is impossible, unless you have corrupt files.
In the devices.txt file, this is the line that shows up for W25Q64B Name="W25Q64BVFIG*SOIC16 ",ID="EF4017",Class="W25X10",Category="SERIAL_EPROM",MFG="Winbond",Vcc="3.6V",CodeSize="8388608",Adapter="ADP-098 adapter";
Now when i search for the chip you are trying to use, mx25l2006e, this line shows up: Name="MX25L2006E",ID="C22012",Class="AT25FS010",Category="SERIAL_EPROM",MFG="Macronix",Vcc="3.6V",CodeSize="262144",Adapter="ADP-004";
Unless some corruption of the software files has occurred, it be impossible for the programmer to get the two chips confused with one another
laptech, ID C22012 does appear for both MX25L2005MC and MX25L2006E in the devices.txt file. |
|
|
Reply #14
laptech
United Kingdom
58 Posts |
Posted - 05/15/2019 : 03:18:19
|
quote: Originally posted by anniel
quote: Originally posted by laptech
I looked in the devices.txt file for software version 7.23 and what your saying in my opinion is impossible, unless you have corrupt files.
In the devices.txt file, this is the line that shows up for W25Q64B Name="W25Q64BVFIG*SOIC16 ",ID="EF4017",Class="W25X10",Category="SERIAL_EPROM",MFG="Winbond",Vcc="3.6V",CodeSize="8388608",Adapter="ADP-098 adapter";
Now when i search for the chip you are trying to use, mx25l2006e, this line shows up: Name="MX25L2006E",ID="C22012",Class="AT25FS010",Category="SERIAL_EPROM",MFG="Macronix",Vcc="3.6V",CodeSize="262144",Adapter="ADP-004";
Unless some corruption of the software files has occurred, it be impossible for the programmer to get the two chips confused with one another
laptech, ID C22012 does appear for both MX25L2005MC and MX25L2006E in the devices.txt file.
That is correct because they are very similar chips BUT if you look at the OP's original post and the issue in question, he is saying that MX25L2006E is not being detected and thus when he selects W25Q64B, he says the programmer ID's the chip as MX25L2005MC with hex ID of C22012.
It is impossible for that to happen unless file corruption has occurred. |
Laptronics UK LTd. Specialist motherboard repair. |
|
|
Reply #15
anniel
2572 Posts |
Posted - 05/15/2019 : 04:03:41
|
quote: Originally posted by laptech
quote: Originally posted by anniel
quote: Originally posted by laptech
I looked in the devices.txt file for software version 7.23 and what your saying in my opinion is impossible, unless you have corrupt files.
In the devices.txt file, this is the line that shows up for W25Q64B Name="W25Q64BVFIG*SOIC16 ",ID="EF4017",Class="W25X10",Category="SERIAL_EPROM",MFG="Winbond",Vcc="3.6V",CodeSize="8388608",Adapter="ADP-098 adapter";
Now when i search for the chip you are trying to use, mx25l2006e, this line shows up: Name="MX25L2006E",ID="C22012",Class="AT25FS010",Category="SERIAL_EPROM",MFG="Macronix",Vcc="3.6V",CodeSize="262144",Adapter="ADP-004";
Unless some corruption of the software files has occurred, it be impossible for the programmer to get the two chips confused with one another
laptech, ID C22012 does appear for both MX25L2005MC and MX25L2006E in the devices.txt file.
That is correct because they are very similar chips BUT if you look at the OP's original post and the issue in question, he is saying that MX25L2006E is not being detected and thus when he selects W25Q64B, he says the programmer ID's the chip as MX25L2005MC with hex ID of C22012.
It is impossible for that to happen unless file corruption has occurred.
That points to a wrong MX25L2006E definition, corrupt AT25FS010 class or fake chip. |
|
|
|
Topic |
|
|
|