[Q] Mounting points on clockworkmod and a few other little questions - Android Q&A, Help & Troubleshooting

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

---

And the at last (i couldnt post everything together for some reason :S)
3 -
The main problem i have with all guides is
The two files you are interested in are recovery.fstab and kernel. The kernel in that directory is the stock one that was extracted from the boot.img that was provided earlier. For the most part, recovery.fstab will work on most devices that have mtd, emmc, or otherwise named partitions. But if not, recovery.fstab will need to be tweaked to support mounts and their mount points. For example, if your /sdcard mount is /dev/block/mmcblk1p1, you would need the following lines in your BoardConfig.mk
/sdcard vfat /dev/block/mmcblk1p1
Once the recovery.fstab has been properly setup, you can proceed to the next step.
Click to expand...
Click to collapse
how the hell im supossed to add the lines on the boardconfig.mk?, if i do it like this it fail
Code:
(...)
BOARD_FLASH_BLOCK_SIZE := 131072
TARGET_PREBUILT_KERNEL := device/unknown/m805_892x/kernel
BOARD_HAS_NO_SELECT_BUTTON := true
/sdcard vfat /dev/block/mmcblk0
i have been looking at boardconfig.mk others devices and the use something like this, which i tried and didnt work
Example:
Code:
BOARD_DATA_DEVICE := /dev/block/mmcblk0p5
BOARD_DATA_FILESYSTEM := auto
BOARD_SDCARD_DEVICE_PRIMARY := /dev/block/ndda1
BOARD_SDEXT_DEVICE := /dev/block/mmcblk0
How im supossed to make the mounting work? >< pls help me, explain this to my because i just dont get it at all sorry and thx
Here attached what i have already done, and what i used V