• Visit https://www.embeddedcomputers.net/ for Hardware; Software and all other things related to FlashcatUSB

Support NAND Micron MT29F4G08ABAEA ??

arrobazo

Member
Hello, it will be possible to add support for MT29F4G08ABAEA due to connecting it to Xport or Mach1 detects it as "Micron_MT29F4G08ABAHC"

thanks
 

Attachments

  • micron.jpg
    micron.jpg
    145.7 KB · Views: 47
  • mach1.png
    mach1.png
    443.3 KB · Views: 49
any solution? Your family of xport and mach1 programmers is not able to make a successful backup MT29F4G08ABAEA, these are badly done, I have tried many times and it should be noted that this process is quite long due to the low programming speed! ... the only way to have a successful dump is with another RT809H programmer and even if you use that same backup to write with mach1 or xport it is not successful.

Will they give support?
 
Can the staff actually look into this? I'm avoiding using my Mach 1 with this IC
 
well the requirement is not taken into account and in my case it was modem´s (sbg8300 and others) that could triple the cost of a Mach1.
I leave here a few tests where the bad thing that the entire Fcusb family read this type of memory Micron

video1

backup test read and written with rt809h is functional, the screenshot belongs to the emmc reading of the Phison controller shows the patitions

 
Last edited:
video 2

Proof that the backup made correctly with rt809h was written completely wrong with only 50.4% of matches, when connecting the nand to emmc the Phison controller does not recognize partitions if not a raw with the density of the nand

 
protocol setting nand




I can not upload everything in the same answer but I hope that a solution can be given, hopefully I am the error because I can not have satisfactory readings and writes about this type of Nand, it is not nice to have a backup badly done in case of ruining in My case is a much more expensive modem cable than your programmer, sorry, I am calling on another programmer but it is the only way to show them
 
Enclosed is updated EXE with change to NAND definition.

Mode -> Protocol Settings:
NAND tab -> Bad block manager: DISABLED
NAND tab -> Main/space area layout: combined
Mode -> Verify Programming (UNCHECK).

Then write the entire, and it should work.
 

Attachments

  • FlashcatUSB.rar
    589.3 KB · Views: 13
Enclosed is updated EXE with change to NAND definition.

Mode -> Protocol Settings:
NAND tab -> Bad block manager: DISABLED
NAND tab -> Main/space area layout: combined
Mode -> Verify Programming (UNCHECK).

Then write the entire, and it should work.

Now write well. Thank you!

I saw some differences compared to before, with twice the speed to compare of (~1 mb/s) and wrote much faster, the 512mb took 12min compared to before it took almost 35 mi to write ... I hope that soon the clock improves to write faster in mach1, other programmers of equal cost take almost 2min to write that 512mb density ...
Thanks again :) :) :)

PS Does this update work for xport?

Captura de pantalla (251).pngCaptura de pantalla (252).pngCaptura de pantalla (253).png
 
Last edited:
Now write well. Thank you!

I saw some differences compared to before, with twice the speed to compare of (~1 mb/s) and wrote much faster, the 512mb took 12min compared to before it took almost 35 mi to write ... I hope that soon the clock improves to write faster in mach1, other programmers of equal cost take almost 2min to write that 512mb density ...
Thanks again :) :) :)

PS Does this update work for xport?

View attachment 1338View attachment 1339View attachment 1340


I wrote again and seeing the seconds that appear in the log of the console does not correspond, the writing speed is maintained, it is delayed, I withdraw what was said ... but the problem was solved, also probe in xport 2.0 and wrote it perfect
 
XPORT should not be used for NAND devices greater than 4Gbit.

I am continually updating and developing MACH1. There will be many firmware/software updates in the future to improve performance.
 
Back
Top