Android Tablets Forum banner
1 - 10 of 10 Posts

·
Registered
Joined
·
18 Posts
Discussion Starter · #1 ·
Hi all. This seems like the right place to post this. I am trying to understand the update.sh script in hopes of customizing it. One thing I am interested in is using the same installer mechanism to install Debian, rather than Abrasive's Debian installer, which just doesn't work for me anyway. Does anyone know of the partition scheme in the onboard flash ROM?There are partitions for uboot, wload, kernel, and boot image, but they aren't specified in the scriptcmd file, only addresses.In the update.sh script, there are references to:/dev/mtd7/dev/mtdblock7/dev/mtd8/dev/mtdblock8/dev/mtd9/dev/mtdblock9/dev/mtd11/dev/mtdblock11mtdX and mtdblockX seem to be referring to the same partition, just in different contexts.mtd7 looks like the root filesystem.There's a data partition on mtd8 and a cache partition on mtd9. mtd11 is User Space? Can someone explain that? Is this Android-specific?Are these partitions fixed in stone? Do I ignore the ones not relevant to Debian? Can I use them for data storage?If I wanted to modify this script to install a Debian rootfs, I would copy it to mtd7? Would I use the same format (yaffs2) as Android?Thanks for your help!
 

·
Registered
Joined
·
446 Posts
mtd11 is the 2gb of storage on the device, apps need to be modified to access it. All the stock peacock apps can, but anything else cant, once we have source we could probly turn that into a partition for swap/a2sd (would recommend to use it for swap)
 

·
Registered
Joined
·
18 Posts
Discussion Starter · #3 ·
[quote name='ECOTOX;7511]mtd11 is the 2gb of storage on the device' date=' apps need to be modified to access it. All the stock peacock apps can, but anything else cant, once we have source we could probly turn that into a partition for swap/a2sd (would recommend to use it for swap)[/QUOTE'] What about mtd0-mtd6, mtd10, and the others?It seems that Android uses a small partition for root, and then sets up other partitions as mounts off of the root dir.So if mtd11 is the big partition, I could just put the Debian rootfs there and set that in the U-Boot bootargs env var?By the way, welcome back! And thanks for the help.
 

·
Registered
Joined
·
446 Posts
[quote name='scooter66;7516]What about mtd0-mtd6' date=' mtd10, and the others?It seems that Android uses a small partition for root, and then sets up other partitions as mounts off of the root dir.So if mtd11 is the big partition, I could just put the Debian rootfs there and set that in the U-Boot bootargs env var?By the way, welcome back! And thanks for the help.[/QUOTE'] Dont take my word completely though, thats what I am assuming since it would make the most sense to put the data partition last. Also, just so you know, make sure to do your homework on the eken uboot, its not a exactly the same as normal uboot =)
 

·
Registered
Joined
·
18 Posts
Discussion Starter · #5 ·
[quote name='ECOTOX;7534]Dont take my word completely though' date=' thats what I am assuming since it would make the most sense to put the data partition last. Also, just so you know, make sure to do your homework on the eken uboot, its not a exactly the same as normal uboot =)[/QUOTE'] I can't really find decent docs on the normal uboot, let alone this one. But this raises another question, I've been trying to modify the scriptcmd file without much success. I know about mkimage, and I can make a bootable script, but the script simply doesn't work as it should. Eg, I modified f00kie's scriptcmd with different setenv commands, but it never works! It's very frustrating! Any suggestions?
 

·
Registered
Joined
·
18 Posts
Discussion Starter · #6 ·
[quote name='ECOTOX;7511]mtd11 is the 2gb of storage on the device' date=' apps need to be modified to access it. All the stock peacock apps can, but anything else cant, once we have source we could probly turn that into a partition for swap/a2sd (would recommend to use it for swap)[/QUOTE'] Okay, I give up. What's a "peacock app?"
 

·
Registered
Joined
·
446 Posts
peacock app...they are the ones that have privaledges to access the 2gb storage.....looking into them more though =)
 

·
Registered
Joined
·
25 Posts
scooter66;7505]Does anyone know of the partition scheme in the onboard flash ROM?There are partitions for uboot said:
There are two different flash chips -- a 512KB SPI ("serial") flash and a 2GB NAND flash chip. The partitions you mentioned are in the SPI flash and accessed through the low-numbered mtd device nodes:
Code:
VT8500 SPI Flash Driver, (c) 2007 VIA Electronics ltd.Find SPI Flash, ID = 0x001C3113Find SPI Flash, ID = 0x00000000un-know id = 0x0vt8500 sf controller initial okcmdlinepart partition parsing not availableCreating 6 MTD partitions on "mtdsf device":0x000000000000-0x000000d00000 : "filesystem-SF"0x000000d00000-0x000000f80000 : "kernel-SF"0x000000f80000-0x000000fd0000 : "u-boot-SF"0x000000fd0000-0x000000fe0000 : "u-boot env. cfg. 1-SF"0x000000fe0000-0x000000ff0000 : "u-boot env. cfg. 2-SF"0x000000ff0000-0x000001000000 : "w-load-SF"
I don't think that the first two are actually used -- trying to examine /dev/mtd/mtd0ro shows it as being all FF, and trying to access mtd1ro causes a kernel panic (!). w-load and u-boot come from the SPI flash; u-boot reads environment variables from the 2 "env" partitions that tell it where to find the kernel.
In the update.sh script, there are references to:/dev/mtd7/dev/mtdblock7/dev/mtd8/dev/mtdblock8/dev/mtd9/dev/mtdblock9/dev/mtd11/dev/mtdblock11mtdX and mtdblockX seem to be referring to the same partition, just in different contexts.mtd7 looks like the root filesystem.
Yes, these are on the NAND flash:
Code:
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd514b6 (Samsung SAMSUNG_K9XXG08UXM)Bad block table found at page 524160, version 0x01Bad block table found at page 524032, version 0x01Creating 6 MTD partitions on "SAMSUNG_K9XXG08UXM":0x000000000000-0x000000300000 : "kernel-NAND"0x000000300000-0x000009900000 : "filesystem-NAND"0x000009900000-0x000012f00000 : "filesystem-data"0x000012f00000-0x000019300000 : "filesystem-cache"0x000019300000-0x000019900000 : "logo-NAND"0x000019900000-0x000080000000 : "user-data-NAND"nand initialised ok
Here's how things look when the system is running:
Code:
/ # mountrootfs on / type rootfs (rw)/dev/root on / type yaffs2 (rw)tmpfs on /dev type tmpfs (rw,mode=755)devpts on /dev/pts type devpts (rw,mode=600)proc on /proc type proc (rw)sysfs on /sys type sysfs (rw)tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)/dev/block/mtdblock8 on /data type yaffs2 (rw)/dev/block/mtdblock9 on /cache type yaffs2 (rw)/dev/block/mtdblock11 on /UserSpace type yaffs2 (rw)/dev/block/loop0 on /LocalDisk type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)/ # df -hFilesystem                Size      Used Available Use% Mounted on/dev/root               150.0M     73.5M     76.5M  49% //dev/block/mtdblock8    150.0M     42.4M    107.6M  28% /data/dev/block/mtdblock9    100.0M      4.5M     95.5M   5% /cache/dev/block/mtdblock11       1.6G      9.4M      1.6G   1% /UserSpace/dev/block/loop0          1.4G     16.0K      1.4G   0% /LocalDisk/ # getenv bootcmdnand read 0 0 300000;bootm 0/ # getenv bootargsmem=109M noinitrd root=/dev/mtdblock7 rootfstype=yaffs2 rw console=ttyS0,115200n8 init=/init lcdid=1
The bootcmd (stored in the SPI flash, in the u-boot environment) point to a kernel stored in NAND at offset 0 (which happens to be mtd0). The bootargs specify the root partition as mtd7, and I'm not entirely sure how the other partitions get mounted by Android -- but in any case, the bulk of the NAND flash gets mounted as /UserSpace. You could mount mtdblock11 whereever using /etc/fstab on a normal (Debian) system.
 

·
Registered
Joined
·
27 Posts
[quote name='bushing;8623]... and I'm not entirely sure how the other partitions get mounted by Android -- but in any case' date=' the bulk of the NAND flash gets mounted as /UserSpace. You could mount mtdblock11 whereever using /etc/fstab on a normal (Debian) system.[/QUOTE'] Isn't that done by init.rc? I read some mount, mkdir, chown, and chmod there ...
 

·
Registered
Joined
·
384 Posts
[quote name='rizapn;9129]Isn't that done by init.rc? I read some mount' date=' mkdir, chown, and chmod there ...[/QUOTE'] init.rc (very different language than debian one, this is android parsed ;) ) can create and mount paths..
 
1 - 10 of 10 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top