Flash NAND Lite Memory Programmer! TSOP48

Shipping to every country around the world: 21 PLN

Thank you Funai. works fine can you do english?

I can only do, I am sick now. I need to gain strength and I will make language versions with charts Maybe it will be possible at the end of the week.

If I had an "exe" file, I could translate it into English.

Relax ... there will be language files in XML so you can translate freely.

Thank you, good luck.

Added after 13 [hours] 53 [minutes]:

Not working with 29F8G08ABABA Can you add?

Added after 25 [minutes]:

I found, sorry, my nand is guilty.

Hello everyone, I have a question whether the programmer will handle such a nand 256W3A2BN6E system. Please answer

Yes, this memory is even on the list of supported chipsets, so you don't need to do anything else.

Thank you for your response. Where can you buy your programmer?

For me, directly via PW or simply on Allegro.
I issue an invoice for the product.

Hello,
After connecting bga to spider (it is possible)
the programmer will handle Toshiba THGBMDG5D1LBAIL?
Datasheet for ease of use in the attachment

Hello

Unfortunately, this memory cannot be handled at this time.
I mean, theoretically, it could be done, but there is no programming support on my part yet.

Support will come with version v2.0 which I estimate in about 2-3 months. I need to prepare a test environment for myself.
I have 4GB memory in stock, but I still have to buy a BGA adapter and connect it somehow to the programmer and make the software.

Thanks. I'm waiting for info in this thread. I will be watching

Is it true that there is a patent for four-wire eMMC memory access?
I see on YouTube that Indians connect the DO, CLK, CMD and GND wires to the eMMC and make a jumper on the main Prock quartz. This way they choose eMMC in SPI mode.

Can it somehow be embraced by your programmer or some other? I am skipping the RT809H which is just a bit expensive for me.

Added after 20 [minutes]:

I guess I found they use a regular SD reader + 3.3v to 1.8v level converter.
Description in the attachment. Only unfortunately it looks like most SD readers do not have access to the boot partitions I care about. Nevertheless, in the SPI mode, Indians use the RT809H programmer to select the boot partition

funak - Fyuzy how to program?

pawol wrote:

Is it true that there is a patent for four-wire eMMC memory access?
I see on YouTube that Indians connect the DO, CLK, CMD and GND wires to the eMMC and make a jumper on the main Prock quartz. This way they choose eMMC in SPI mode.

Of course it's true.

Quote:

Nevertheless, in the SPI mode, Indians use the RT809H programmer to select the boot partition

Take it easy, so do Poles ;-)

You have read about the super positives, now read about the negatives, because, for example, many colleagues from across the eastern border skip such operations and, however, take out the layout because the data does not always match, and then an avalanche of problems ... there are also advantages in favor of "time" , and the cons that speak "against", that is, you think it's okay and in fact your dump is a dump and that the ripped batch once worked is a fluke Of course, such a problem does not occur often, but it does happen.

I don't know. I need a total of ubooty and how it works, the rest will be overwritten from scratch

EXab wrote:

funak - Fyuzy how to program?

BOOTRST - BOOTLOADER
TOSCSEL - PINS
BODPD - CONTINOUS
BODACT - CONTINUOS

Funak Can you send me the language files in XML? I'll do the translation myself. And more. I did everything as instructed on page 2. I didn't save my native software. Do I have to save native software?

Hello, when will the new software version be released and will the TC58DVM92A5TA10 chip be added to the list of supported devices?

The new version will be in mid-April.

However, this chip: TC58DVM92A5TA00 should be detected.
If not, please select this layout manually from the layout list.

In the database, I suspect that the user gave me incorrect data and it concerns the system with the designation A3.

Hello, after inserting the TC58DVM92A5TA10 chip into the programmer, it does not detect it, but when I manually select the TC58DVM92A5TA00 chip, it is OK and the question here is that the systems differ in the final 10 and 00, does it have any effect on the reading and correct writing?

Please let me know what does not detect?
That is, it gives the identifier 00 00 00 00, is the ID like 98 76 ....?

If he gives all zeros, there is no need to dwell on memory, there is no contact with it.

OK, let me say that the system is detectable as TC58DVM92A5TAJ0 ID 98 76 A5 C0 29 04 00 00 after clicking on this layout icon and going to the transfer tab, I can't do anything, read, delete or save. I will manually select the chip from the table TC58DVM92A5TA00 without function (detect chip) is OK. And now the question is whether the TC58DVM92A5TA10 chip is the same as the TC58DVM92A5TA00, I will add that the difference is in the final number. I mainly mean whether I will have the correct memory.

Ok, so it looks like there is no layout signature added to the layout database.

fachura wrote:

And now the question is whether the TC58DVM92A5TA10 chip is the same as the TC58DVM92A5TA00, I will add that the difference is in the final number. I mainly mean whether I will have the correct memory.

The tip has little effect on the basic functions of memory.

For example, if you compare TC58DVM92A5TA00 vs TC58DVM92A3TA00:

This version of A5 is characterized by lower power consumption and higher speed, so it can be concluded that A5 simply means memory generation.

According to the manufacturer, the ID is 98 76 = 2 bytes. Thus, it can be concluded that each TC58DVM92 memory will be supported equally.

Added after 2 [minutes]:

Writing to memory will be correct. The more that it is an SLC type memory. I recommend that you verify the record, if there are NO errors then you can conclude that the record is correct.

For this memory, the number of possible error bits is 1. This means that if two errors (Error Count bit> 1) occur during verification - the memory is to be thrown away.

Buddy, does memory verification on this software always take ages?
Recently I have used this option and after an hour or so the progress bar neither shuddered some kind of massacre.

Theoretically, it should take about 2-3 minutes for this memory.

Added after 1 [minutes]:

If the progress bar hasn't flickered, the memory is not responding.

It is customary to conclude that if nothing happens in 10 seconds, further waiting will not help.
Then only remove the programmer from the USB and insert it again.

Exactly, and this is not the case, I did it with three computers on different memory bones and without changes. Tell me what's the problem?

I mean it happens, it scans block by block but a lot slowiiiiiiiiiii .

When it comes to erasing and saving it takes no time, I'm happy with it.

For example, I can give a memory taken from an SSD with the designation TT58G2ZASA.




I only know that the memory comes from a 128GB SSD for mSATA.
There were 4 chips on the disk, so it can be concluded that this memory has a capacity of 32GB or 256Gbit.

So I enter large values from my hand
Target: 1
LUN: 1
LUNSize: 32768
BlockSize: 256
PageSize: 32768 + 8192

The program calculated a memory capacity of 274GB, but we are going on.


We go to the Content tab and try to read any page.
We move the indicators and what do we see?


And we see that:
- The memory is empty because they are all FFs
- memory changes its content around 0x4500, which is 17 664.
And here we can see what the page size is. Basically MainPage is a power of two, so the page size is: 16384 + 1280.

I assume that the block size is 256, so we change it to get the 32GB:


Now the memory should be erased, so let's go:


Memory erased and here's a surprise:


From block 4212, there are only errors, so the number of blocks in this memory is 4212.


So we correct:
LUNSize: 4212
And the program counts that 17.6GB of memory capacity, so where is the rest?
It looks like there are two structures in this physical memory that are switched by separate CE inputs.

Thus, target: 2

To sum up:


And so it was easy to communicate with my unknown memory.
The example may not be universal and there are many possibilities, but it shows how universal the programmer is, where you can experiment yourself

OK, I understand the new memory chip erasing and here we can see it.

and the verification of the same memory goes like this

The memory verification screen shot was taken 45 minutes after it started working and the progress bar will not budge. What is it - let me add that memory is new and so is the case with each of them.