8G eMMC for AOSP5.0 cannot be started. aosp5.0emmc

8G eMMC for AOSP5.0 cannot be started. aosp5.0emmc

On the AOSP5.0 MT6572 platform, you can use H9TP32A4GDBCPR_KGM, a 4G eMMC. However, the 8G H9TP65A8JDACPR_KGM cannot be used to start the machine and restart the system. You can use the serial port to capture logs to find:

[2.028532] <1>. (0) [6: kworker/u4: 0] total reserve: l_otp_reserve = 0x0 blocks, l_mtk_reserve = 0xa800 blocks, l_offset = 0x7fd000 blocks

[2.028538] <1>. (0) [6: kworker/u4: 0] maid = 0x807800

[2.030884] <1>. (0) [6: kworker/u4: 0] [mmc_blk_probe]: mmcblk0 by manufacturer settings, quirks = 0x10000000

[2.032043] <1>. (0) [65: mmcqd/0] msdc0-> Address offset in user region (Capacity 7456 MB) is 0xffffd000 <-msdc_cal_offset (): L <2574> PID <mmcqd/0> <0x41>

[2.032057] <1>. (0) [65: mmcqd/0] msdc0-> XXX Address offset error (-12288), please check MBR start address !! <-Msdc_cal_offset (): L <2576> PID <mmcqd/0> <0x41>

[2.032075] <1>-(0) [65: mmcqd/0] [KERN Warning] ERROR/WARN forces debug_lock off!

[2.032079] <1>-(0) [65: mmcqd/0] [KERN Warning] check backtrace:

According to the error message "Address offset error" above, locate the code to the file:... h10 \ kernel-3.10 \ drivers \ misc \ mediatek \ mmc-host \ mt6572 \ sd. c.

The serial port log of 4G eMMC is as follows:

[2.016319] <0>. (1) [58: kworker/u4: 1] [mmc_blk_probe]: mmcblk0 by manufacturer settings, quirks = 0x10000000

[2.017554] <0>. (1) [65: mmcqd/0] msdc0-> Address offset in user region (Capacity 3696 MB) is 0x0 <-msdc_cal_offset (): L <2574> PID <mmcqd/0> <0x41>

[2.020739] <0>. (0) [1: swapper/0] warning init time too long!

[2.021471] <0>. (0) [1: swapper/0] [pdev] mtk-msdc

It seems that something is wrong. Combined with code analysis, the macro definition of MBR_START_ADDRESS_BYTE should be problematic. This macro is ...... the value of Boot1 (KB) + Boot2 (KB) + RPMB (KB) in the emmc_region table in the h10 \ bootable \ bootloader \ preloader \ tools \ emigen \ MT6572 \ MemoryDeviceList_MT6572.xls file. Someone said it was ...... change MBR_Start_Address_KB in h10 \ device \ mediatek \ build \ tools \ ptgen \ MT6572 \ mbr_addr.pl, but I cannot try it. I don't know why.

Several articles are found during Problem Solving for your reference and will be reserved for future study:

1. About the problem that mt6572 cannot be started-Tracy Mcgrady's column-blog channel-CSDN. NET

When I first came into contact with the mtk platform, I encountered a problem. After the new Code was configured with flash, I burned it to the Board. The system could not start normally. When I configured the serial port to 115200, I could only get the following information:

[DL] 00001388 00000015 010301F0: 1028 0000F3: 0000 0000V0: 0000 0000 [0001]00: 1027 000201: 0000 0000BP: 0000 0051G0: 0090 0003T0: 0000 1499EC: 0000 0080 [0000]Jump to BL

This section of information is printed cyclically without much information output. No, I didn't even access preloader, because I have read a little bit of preloader code and there are at least a few print functions. Is there a problem with flash configuration or ddr configuration? I searched for the code, I didn't see where to configure the ddr (I later learned that the ddr and nand flash are a module ). Later, I found the same problem on the Internet when I was about to give up. Modify the mediatek/custom/projec_dir/preloader/inc/cust_bldr.h file. The modification is as follows:

-#define CFG_UART_LOG                (UART2)+#define CFG_UART_LOG                (UART1)

That is, the log information is changed to output from UART1 with a baud rate of 921600. After re-Compiling and writing preloader, The preloader information is obtained, and the output information is finally found to be faulty. The problem is as follows:

[EMI] no flash ID match, no DRAM info match ! mt_emi.c:line 1048 0PL fatal error...PL delay for Long Press Rebootpl pmic powerkey Release[PLFM] emergency download mode(timeout: 5s).mtk_arch_reset at pre-loader!

Oh, preloader is in. That is to say, it is not in the mtk rom as we previously imagined, or jumped to the preloader, But flash does not match correctly. As a result, preloader is continuously restarted, after the flash is reconfigured, the system starts up.
If flash is not correctly configured, writing or burning should fail. Is it true that the flash ID is not detected when preloader executes the download mode?

2. [FAQ08871] cannot be started after the new (eMCP) emmc is changed

[DESCRIPTION]
After a new emmc is changed, especially when the capacity of the new emmc is large, such as 16 GB, the system will find that the emmc cannot be started on.
The following error message is displayed when you view the kernel log:
[MSDC] msdc0-> Address offset in user region (Capacity 15032 MB) is 0xffffd000 <-msdc_cal_offset br style = 'font-size: 14px; font-style: normal; font-weight: normal; font-family: Tahoma; color: rgb (51, 51, 51); '/> L <2937> PID <0x40>
[MSDC] msdc0-> XXX Address offset error (-12288), please check MBR start address !! <-Msdc_cal_offset br style = 'font-size: 14px; font-style: normal; font-weight: normal; font-family: Tahoma; color: rgb (51, 51, 51); '/> L <2939> PID <0x40>
[SOLUTION]
For example, a problem occurs after H9TP17ABLDMCNR_KGM_MMD2 is replaced.
1. Go to the emmc_region page in alps/mediatek/build/tools/emigen/MT65XX/MemoryDeviceList_MT65XX.xls to find
The total size of BOOT1 + BOOT2 + RPMB corresponding to H9TP17ABLDMCNR_KGM_MMD2 (for example, 4096 + 4096 + 4096 = 12288 ).
2. If H9TP17ABLDMCNR_KGM_MMD2 cannot be found in emmc_region, but H9TP17ABLDMCNR_KGM can be found, you need
H9TP17ABLDMCNR_KGM this row is copied to the new row, and the first column name of the new row is changed to H9TP17ABLDMCNR_KGM_MMD2.
3. Open alps/mediatek/config/project_name/mbr_addr.pl and check the value of $ MBR_Start_Address_KB (such as 6144). If
$ MBR_Start_Address_KB <BOOT1 BOOTRPMBsize MBR_Start_Address_KB ="
Total size of BOOT1 + BOOT2 + RPMB ($ MBR_Start_Address_KB = 12288)
4. After modification, re-build new

Copyright Disclaimer: This article is an original article by the blogger and cannot be reproduced without the permission of the blogger.