Quantcast
Channel: xda-developers - Android Q&A, Help & Troubleshooting
Viewing all articles
Browse latest Browse all 18891

[Q] Mounting points on clockworkmod and a few other little questions

$
0
0
So the past few days i have been working on porting clockworkmod to my tablet Vexia Navlet 2 White (cpu telechip tcc892x, board m805_892x_evm), i have setup a build environment and managed to make a bootable CWM but have reached a bit of a wall, my recovery dont mount anything ><

And so i have a few doubts:


1 -

In boardconfig.mk

i have these lines

Code:

BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00a00000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00a00000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x19000000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x39800000
BOARD_FLASH_BLOCK_SIZE := 131072

the size must be set based on the cat /proc/mtd result (or so it says on the different guides i found)

Code:

dev:    size        erasesize  name
mtd0: 00a00000 00200000 "boot"
mtd1: 00600000 00200000 "kpanic"
mtd2: 19000000 00200000 "system"
mtd3: 00400000 00200000 "splash"
mtd4: 09600000 00200000 "cache"
mtd5: 39800000 00200000 "userdata"
mtd6: 00a00000 00200000 "recovery"
mtd7: 00200000 00200000 "misc"
mtd8: 00200000 00200000 "tcc"

after searching on the forums and googling i saw that some people use the hexadecimal value of the column size but other people convert it to decimal, what is the right way? are both okay? is the code from my boardconfig.mk up there ok?


2 -

Code:

BOARD_FLASH_BLOCK_SIZE := 131072
This value, after researching it seems that this must be the decimal converted value of the erase column

Code:

mtd8: 00200000 00200000 "tcc"
in this case 00200000 (hex) -> 2097152 (dec), but if i set this value i get and boot.img too big error, i dont know if this is the reason of the mounting not working, but leaving the default value i can make it and the recovery boot

Viewing all articles
Browse latest Browse all 18891

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>