SESION 3
---------
we are in a sesion 3 now, we already understand basic things about eMMC and eMCP, i will make another threads that will discuss about spesific RAM in the eMCP and all of symptomp that would be show up because RAM problem.
now we will going back to the topics, yea it was "eMMC things"
all of thoose eMMC and eMCP have a eMMC blocks anyway
inside eMMC there is controller and NAND, trough this controller whole of NAND can be accessed by the HOST.
in the phone PCB our PHONE PROCESSOR are the HOST, all of processor have a right to access the eMMC trough controller.
huh, what do you mean about all of processor ?
there are application processor part, there are baseband processor part
it was not new things.. if you remember some of NOKIA BB5 PHONES, have a RAP3G ( works as baseband processor / CMT / modem ) and OMAP ( works as application processor or APE part ) the same things is still happen now, some processor chip build BASEBAND PROCESSOR and APE PROCESSOR in a single chip, many of MEDIATEK PROCESSOR have structure like this.
MT65xx : APP processor + BASEBAND processor that supported 2G and 3G
MT67xx : APP processor + BASEBAND processor that supported 2G, 3G and 4G
so many MTK processor it was build in APP and BB processor, you will not found two processor chip inside Phone PCB.
the samething will found in QUALCOMM based phones, if that phone use QUALCOMM processor "MSM" products ( Mobile station modem ) processor, this kind of CHIP have APP processor and BB processor inside of it.
if we found some phone use Exynoz processor or intel atom processor, they doesnt have BASEBAND inside that processor chip, so... manufacture need to put another processor as BB processor... so... shanon, infineon or qualcomm "MDM" processor ussualy choosen to works as BASEBAND procsessor.
i would love to start sesion about thoose processor things for sure, maybe i need to create another threads for it, now we need to go back to our primary discussion : "all of processor on our phone can access to the NAND trough the controller" yes, as the host, processor can send command, and read, erase, or write to NAND area trough eMMC controller.
eMMC controler is easy to communicate, only need two supplies of VCC and VCCQ, VSS ( GND ), and CLK, CMD, the HOST can access NAND use 8 bit data ways ( dat0 - dat7 )
the HOST need to have NAND access to RUN the mobile phones hardware, to run basaeband / modem part and app part, all of operating system that store inside the NAND
for example :
bootloader
sbl
mbr / gpt
recovery
boot image
nv
modem
splash screen
system
cache
user data
all oF NAND inside the eMMC, have a 4 basic partition :
BOOT1 PARTITION
BOOT2 PARTITION
RPMB PARTITION
USER AREA PARTITION
manufacture have a right to put their bootloader to any of partition, actually the manufacture will follow the typical of based processor / platform, for example if it use MTK processor, so manufacture need to know that MTK processor wil works when bootloader is in BOOT1 PARTITON, so the preloader file that operated as BOOTLOADER in MTK PHONE need to be write on BOOT 1 PARTITION as well, and write another to USER AREA partition.
"each platform have their own methode, you need to know little bit of it, some of it similiar, some of it have a special need, its ok no need to worry, all of your box for emmc programing will help you to prepare emmc for each target phone platform, specially if you have ext_csd for that phones ( this is why we need works togather to make some huge database of dump + ext_CSD collection of phone you might be found for repair )
WHy we need to have ANY OF EMMC BOX TOOLS ? ------------------------------------------------
all of thats box will act just like our phone processor as HOST, will become external HOST, inside syscobox have a ARM processor, and from thats IO, we build communcation to the eMMC CMD, DATA0 - DATA7, CLK.
inside of it need to have LDO, and will supply VCC and VCCQ for our target eMMC.
any of emmc box tool will access eMMC just like your phone processor access it. the good things is we can deploy any command we are need, our programmer use speccial command to the eMMC controler to acces registry on eMMC controler, this is why any emmc box.. not only can READ, WRITE, or ERASE to our NAND... your emmc box tool need to totally identify, can accessing OCR, CID, CSD, EXT_CSD, can ask smart report, etc.. from eMMC that connected to our emmc box tool
make sure your emmc box tool can do modification on CID for change PNM ( productname ) MID, MDT, etc... also can do eMMC controller flash programming, that known as FFU.. it will make our target eMMC back to the default state, just like new eMMC.
we can do this operation use any emmc box as external host, this kind of operation procedure its called eMMC direct programming.
WHEN WE NEED TO DO THIS ?
------------------------------
when your phone NAND can not be programmed ( partial / full ) use any software that use USB connection.
normal phone can be programmed use USB methode, use many software, some of them can be programmed under FASTBOOT methode, some of them can be programmed under SOC methode.... yes it was correct procedure... and if your phone have no problem with their eMMC, you will found everthings works fine.... but, iam not talking about phone that still can be programmed use USB, iam not talking about phone that still have full normal eMMC inside of it... iam talking about phone that might be have a problem with their emmc, iam talking about phone that cant be done use regular USB software.
in this condition you always still have option to do direct eMMC programming, for repairing the old eMMC purpose or for prepare the replacement eMMC for that phone.
so you need to have some products to do this direct eMMC programming methode, isnt ? the most importand things for me is many people know about emmc and emmc direct programming methode.
Thankyou
br,
Yongky felaz