View Single Post
Old 04-02-2020, 19:05   #4 (permalink)
micro_media
Crazy Poster
 
Join Date: Jun 2006
Location: indonesia
Posts: 50
Member: 300199
Status: Offline
Thanks Meter: 261
hello friends,
after you read my thread about # eMMC Basic Knowledge # i believe all of us understand that flash memory ic on major android mobile phones use eMMC and eMCP right now.

we already discuss about all packages of eMMC and eMCP that oftenly used by the mobile phone manufacturer, and i hope we understand the difference between eMMC and eMCP is a the exixtence of RAM hardware inside of it... whatever the difference of all those package, they have an equality anyway..yes, all of it must have a eMMC inside

in the # eMMC Basic Knowledge # thread we also discuss about what condition that makes us need to do eMMC direct programming, i dont wanna repeat what i wrote on previous thread, you can read it there my friends, now i will continue the discussion about eMMC direct programming procedure, what we exactly need to do

Direct EMMC is a procedure of communication with the eMMC
directly. Execution with this procedure is the most complete and
most thorough, compared with the activity execution using
USB or JTAG procedure, because it can execute all the parts of the
eMMC, either filling every partition in the NAND/storage as well
as part controller, such as, accessing the register even the firmware
of the eMMC itself.

The standart procedure of direct eMMC method :
---------------------------------------------------
1. Identification to analyze the feasibility of the eMMC
2. Do read ( backup ) the partial / whole partition, if necessary
3. Do a emmc repair step if found any discrepancy on it
4. Do the appropriate configuration for the target device
5. Do write correct dump file for the target device
6. Do a final check to make sure the eMMC is ready to reused

The above procedure does not need to be done sort appropriate
numbering, the most important is the need to know the function
of each procedure, so as to understand when is the right time to
do and how to do such a procedure using any of emmc tools

1. Identification the eMMC

This process is the first step in any execution eMMC, which in this
step will be invalidated, the status and condition of the eMMC is
being executed, and it helps to take a step for proper execution
that required in that eMMC repairing / preparation

When you take off old eMMC ic from your phone, and you wanna try to identify it, you will find the possibility of that eMMC fail identified by syscobox, it is possible.. referring to the eMMC conditions may vary, when eMMC cant boot properly, it can be in weak condition or needs special behavior and so forth ( do not forget it was from broken mobile phone that cant be solved by regular usb methode flashing procedure, isnt ? )

syscobox provides the option to set the interfacing condition in Manual ( auto is default ) includes, the setting of :

1. Voltage of VCC and VCCQ that you wanna supply to eMMC
2. Communication speed (clock) to the each bus
3. Bus width that is used to communicate (1 bit/4 bit/8 bit)
  Reply With Quote
The Following 3 Users Say Thank You to micro_media For This Useful Post:
Show/Hide list of the thanked
 
Page generated in 0.07353 seconds with 7 queries