MCUmall EPROM BIOS Chip Burner Forum
MCUmall EPROM BIOS Chip Burner Forum
Home | Profile | Register | Active Topics | Members | Search | FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 MCUmall Forums
 GQ-5X
 GQ-5X nand support list

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Screensize:
UserName:
Password:
Format Mode:
Format: BoldItalicizedUnderlineStrikethrough Align LeftCenteredAlign Right Horizontal Rule Insert HyperlinkInsert EmailInsert Image Insert CodeInsert QuoteInsert List Spell Checker
   
Message:

* HTML is OFF
* Forum Code is ON
Smilies
Smile [:)] Big Smile [:D] Cool [8D] Blush [:I]
Tongue [:P] Evil [):] Wink [;)] Clown [:o)]
Black Eye [B)] Eight Ball [8] Frown [:(] Shy [8)]
Shocked [:0] Angry [:(!] Dead [xx(] Sleepy [|)]
Kisses [:X] Approve [^] Disapprove [V] Question [?]

   Insert an Image File
Check here to include your profile signature.
    

T O P I C    R E V I E W
drqmka Posted - 02/09/2017 : 07:00:54
In the configuration file GQ-5X NAND Flash does not describe whether a memory is a x8 or x16 bus. Does this mean that the programer does not support 16 bit organization? If not why not? And if it works, how do I add a chip with 16 bit data? Thanks!
13   L A T E S T    R E P L I E S    (Newest First)
eduardo48 Posted - 05/23/2018 : 05:09:16
Hi,, I recommend you to create your own definitions with the datasheet, one letter can change parameters of the memory
skdaddy69 Posted - 05/22/2018 : 17:29:43
quote:
Originally posted by skdaddy69

[quote]Originally posted by drqmka

So if I understand correctly logic to add new drives in the configuration file. I propose to your attention one elaborated by me, NAND.txt file.

https://drive.google.com/file/d/0BxAYOQA9KpN_ZWYtaDNGbWpmUE0/view?usp=sharing

Without having claims that there are no errors! On the contrary I would be grateful if you find any, let me show them. Also will not be angry if someone has something, let's complete the list. I think it will be beneficial to all. Thanks!




Hi,
I'm working with H27UAG8T2MTR and used your NAND_TXT_FILE.

Name="H27UAG8T2M",MFG="Hynix",ID1="adh",ID2="D5h",ID3="14h",ID4="B6h",ID5="44h",size="84000000h",PageSize="1080h",BlockSize="80h"

I checked datasheet and your values are good for MTR.

For ATR and BTR in my original file I had:

Name="H27UAG8T2ATR",MFG="Hynix",ID1="adh",ID2="d5h",ID3="94h",ID4="25h",ID5="44h",ID6="41h",size="84000000h",PageSize="1080h",BlockSize="80h"
Name="H27UAG8T2BTR",MFG="Hynix",ID1="adh",ID2="d5h",ID3="94h",ID4="9ah",ID5="74h",ID6="42h",size="87000000h",PageSize="21c0h",BlockSize="100h"
Are they right? By checking with datasheet, they are NOT correct.


P.S. Thank you for your time and effort to create and post your list!

anniel Posted - 02/25/2018 : 05:29:09
quote:
Originally posted by elbronco

Thanks, it was very useful.




Feedback is always good.
elbronco Posted - 02/24/2018 : 14:03:15
Thanks, it was very useful.
supervizeur Posted - 07/09/2017 : 09:03:09
quote:
Originally posted by anniel

quote:
Originally posted by supervizeur

quote:
Originally posted by drqmka

So if I understand correctly logic to add new drives in the configuration file. I propose to your attention one elaborated by me, NAND.txt file.

https://drive.google.com/file/d/0BxAYOQA9KpN_ZWYtaDNGbWpmUE0/view?usp=sharing

Without having claims that there are no errors! On the contrary I would be grateful if you find any, let me show them. Also will not be angry if someone has something, let's complete the list. I think it will be beneficial to all. Thanks!



Thank you drqmka for the time you take populating the list.



+1 Useful work for the community.



Yes.
anniel Posted - 06/15/2017 : 16:30:29
quote:
Originally posted by supervizeur

quote:
Originally posted by drqmka

So if I understand correctly logic to add new drives in the configuration file. I propose to your attention one elaborated by me, NAND.txt file.

https://drive.google.com/file/d/0BxAYOQA9KpN_ZWYtaDNGbWpmUE0/view?usp=sharing

Without having claims that there are no errors! On the contrary I would be grateful if you find any, let me show them. Also will not be angry if someone has something, let's complete the list. I think it will be beneficial to all. Thanks!



Thank you drqmka for the time you take populating the list.



+1 Useful work for the community.
supervizeur Posted - 06/12/2017 : 09:00:25
quote:
Originally posted by drqmka

So if I understand correctly logic to add new drives in the configuration file. I propose to your attention one elaborated by me, NAND.txt file.

https://drive.google.com/file/d/0BxAYOQA9KpN_ZWYtaDNGbWpmUE0/view?usp=sharing

Without having claims that there are no errors! On the contrary I would be grateful if you find any, let me show them. Also will not be angry if someone has something, let's complete the list. I think it will be beneficial to all. Thanks!



Thank you drqmka for the time you take populating the list.
drqmka Posted - 02/13/2017 : 01:14:09
So if I understand correctly logic to add new drives in the configuration file. I propose to your attention one elaborated by me, NAND.txt file.

https://drive.google.com/file/d/0BxAYOQA9KpN_ZWYtaDNGbWpmUE0/view?usp=sharing

Without having claims that there are no errors! On the contrary I would be grateful if you find any, let me show them. Also will not be angry if someone has something, let's complete the list. I think it will be beneficial to all. Thanks!
drqmka Posted - 02/11/2017 : 01:22:00
Another thing that me bother. These are memory with the same ID:
Name = "K9GAG08B0D", MFG = "Samsung", ID1 = "ech", ID2 = "D5h", ID3 = "94h", ID4 = "29h", ID5 = "34h", ID6 = "41h", size = "86D00000h", PageSize = "10DAh", BlockSize = "80h", CE = "1"

Name = "K9GAG08U0D", MFG = "Samsung", ID1 = "ech", ID2 = "D5h", ID3 = "94h", ID4 = "29h", ID5 = "34h", ID6 = "41h", size = "86D00000h", PageSize = "10DAh", BlockSize = "80h", CE = "1"
Is this a problem for the programmer?
drqmka Posted - 02/10/2017 : 23:48:55

If I have understood correctly every x16 bit memory can be addressed that x8 bit. So every word is read byte by byte and is actually irrelevant for copying after crawling the entire address space of memory.
ie in the configuration file, we work only with x8 bit organization. So the memory that have x16 bit bus will assume that is with twice as large address space when working with bytes, they are twice smaller than words. So this should affect on the organization of the page:(1K + 32 spare) Words = (2K +64 spare) bytes, but not on the size in bits
The size and number on blocks, therefore the size on the memory, in bits should not be changed
HY27UF162G2B - x16: (1K + 32) words x 64 pages x 2048 blocks
for NAND.txt file will assume that is x8 = (2K + 64) bytes x 64 pages x 2048 blocks
GQ5XSupport Posted - 02/09/2017 : 18:54:48
Only 8 bit is supported. But as for chip backup/copying it does not really matters.
drqmka Posted - 02/09/2017 : 14:25:09
I am confused. I think we need some way to tell the programer that has to work accordingly with byte or word because it is a different number of pins the outlet:
  - IO0-IO7 (x8)
  - IO0-IO15 (x16 Only)
and changing the organization of memory:
PAGE SIZE
- (2K + 64 spare) Bytes
- (1K + 32 spare) Words
Unfortunately, in the previous example I did not see anything like that. Can someone please tell me if something is wrong. Thanks!
drqmka Posted - 02/09/2017 : 12:24:27
This is from NAND.txt. Is this true?
Name="HY27UF082G2B",MFG="Hynix",ID1="adh",ID2="DAh",ID3="10h",ID4="95h",ID5="44h",size="10800000h",PageSize="840h",BlockSize="40h"
Name="HY27UF162G2B",MFG="Hynix",ID1="adh",ID2="CAh",ID3="10h",ID4="D5h",ID5="44h",size="10800000h",PageSize="840h",BlockSize="40h"
How the programer works in HY27UF082G2B with byte and in the HY27UF162G2B with words?

MCUmall EPROM BIOS Chip Burner Forum © Copyright 2003 - 2009 Mcumall Electronics Inc. Go To Top Of Page
Generated in 0.06 sec. Snitz Forums 2000