UBIFS/NAND Partitioning - Android Q&A, Help & Troubleshooting

I have a device that uses UBIFS and I'm trying to increase the partition size of the /system disk as it doesn't have much space and only half of the NAND is partitioned. Unfortunately, it's not as simple as I thought as the entire nand chip doesn't populate in /dev as a single device.
Here's the boot log where MTD partitions are enumerated.
HTML:
[ 0.000000] Kernel command line: noinitrd rw console=ttyHSL0,115200,n8 androidboot.hardware=qcom ehci-hcd.park=3 msm_rtb.filter=0x37 lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78b1000 androidboot.serialno=796a00b0 androidboot.authorized_kernel=true androidboot.baseband=msm rootfstype=ubifs rootflags=bulk_read root=ubi0:rootfs ubi.mtd=13
Code:
[ 0.478465] sps: BAM device 0x07984000 is not registered yet.
[ 0.478706] sps:BAM 0x07984000 is registered.
[ 0.478723] msm_nand_bam_init: msm_nand_bam_init: BAM device registered: bam_handle 0xdde0c800
[ 0.478966] sps:BAM 0x07984000 (va:0xe0bc0000) enabled: ver:0x19, number of pipes:7
[ 0.481536] msm_nand_parse_smem_ptable: Parsing partition table info from SMEM
[ 0.481577] msm_nand_parse_smem_ptable: SMEM partition table found: ver: 4 len: 20
[ 0.481602] msm_nand_version_check: nand_major:1, nand_minor:5, qpic_major:1, qpic_minor:5
[ 0.481640] msm_nand_scan: NAND Id: 0x2690ac98 Buswidth: 8Bits Density: 512 MByte
[ 0.481649] msm_nand_scan: pagesize: 4096 Erasesize: 262144 oobsize: 256 (in Bytes)
[ 0.481656] msm_nand_scan: BCH ECC: 8 Bit
[ 0.481670] msm_nand_scan: CFG0: 0x290409c0, CFG1: 0x08045d5c
[ 0.481670] RAWCFG0: 0x2b8401c0, RAWCFG1: 0x0005055d
[ 0.481670] ECCBUFCFG: 0x00000203, ECCBCHCFG: 0x42040d10
[ 0.481670] RAWECCCFG: 0x42000d11, BAD BLOCK BYTE: 0x00000175
[ 0.481691] Creating 20 MTD partitions on "7980000.nand":
[ 0.481711] 0x000000000000-0x000000280000 : "sbl"
[ 0.482399] 0x000000280000-0x000000500000 : "mibib"
[ 0.482994] 0x000000500000-0x000001b80000 : "efs2"
[ 0.483584] 0x000001b80000-0x000001c80000 : "tz"
[ 0.484194] 0x000001c80000-0x000001d40000 : "rpm"
[ 0.484816] 0x000001d40000-0x000001e40000 : "aboot"
[ 0.485364] 0x000001e40000-0x000002880000 : "boot"
[ 0.485922] 0x000002880000-0x000002900000 : "scrub"
[ 0.486496] 0x000002900000-0x000006fc0000 : "modem"
[ 0.487080] 0x000006fc0000-0x000007140000 : "misc"
[ 0.487672] 0x000007140000-0x000007bc0000 : "recovery"
[ 0.488269] 0x000007bc0000-0x000007c80000 : "fota_none"
[ 0.488883] 0x000007c80000-0x000009340000 : "recoveryfs"
[ 0.489491] 0x000009340000-0x000011bc0000 : "system"
[ 0.490036] 0x000011bc0000-0x000012b40000 : "pad1"
[ 0.490729] 0x000012b40000-0x000013f80000 : "userrw"
[ 0.491301] 0x000013f80000-0x000017a40000 : "hdata"
[ 0.491890] 0x000017a40000-0x00001f000000 : "ntgfota"
[ 0.492500] 0x00001f000000-0x00001f8c0000 : "cust"
[ 0.493103] 0x00001f8c0000-0x000020000000 : "persist"
[ 0.493719] msm_nand_probe: NANDc phys addr 0x7980000, BAM phys addr 0x7984000, BAM IRQ 35
[ 0.493729] msm_nand_probe: Allocated DMA buffer at virt_addr 0xdf446000, phys_addr 0x9f446000
/dev
Code:
crw-rw---- 1 root root 90, 0 Jan 1 1970 mtd0
crw-rw---- 1 root root 90, 1 Jan 1 1970 mtd0ro
crw-rw---- 1 root root 90, 2 Jan 1 1970 mtd1
crw-rw---- 1 root root 90, 20 Jan 1 1970 mtd10
crw-rw---- 1 root root 90, 21 Jan 1 1970 mtd10ro
crw-rw---- 1 root root 90, 22 Jan 1 1970 mtd11
crw-rw---- 1 root root 90, 23 Jan 1 1970 mtd11ro
crw-rw---- 1 root root 90, 24 Jan 1 1970 mtd12
crw-rw---- 1 root root 90, 25 Jan 1 1970 mtd12ro
crw-rw---- 1 root root 90, 26 Jan 1 1970 mtd13
crw-rw---- 1 root root 90, 27 Jan 1 1970 mtd13ro
crw-rw---- 1 root root 90, 28 Jan 1 1970 mtd14
crw-rw---- 1 root root 90, 29 Jan 1 1970 mtd14ro
crw-rw---- 1 root root 90, 30 Jan 1 1970 mtd15
crw-rw---- 1 root root 90, 31 Jan 1 1970 mtd15ro
crw-rw---- 1 root root 90, 32 Jan 1 1970 mtd16
crw-rw---- 1 root root 90, 33 Jan 1 1970 mtd16ro
crw-rw---- 1 root root 90, 34 Jan 1 1970 mtd17
crw-rw---- 1 root root 90, 35 Jan 1 1970 mtd17ro
crw-rw---- 1 root root 90, 36 Jan 1 1970 mtd18
crw-rw---- 1 root root 90, 37 Jan 1 1970 mtd18ro
crw-rw---- 1 root root 90, 38 Jan 1 1970 mtd19
crw-rw---- 1 root root 90, 39 Jan 1 1970 mtd19ro
crw-rw---- 1 root root 90, 3 Jan 1 1970 mtd1ro
crw-rw---- 1 root root 90, 4 Jan 1 1970 mtd2
crw-rw---- 1 root root 90, 5 Jan 1 1970 mtd2ro
crw-rw---- 1 root root 90, 6 Jan 1 1970 mtd3
crw-rw---- 1 root root 90, 7 Jan 1 1970 mtd3ro
crw-rw---- 1 root root 90, 8 Jan 1 1970 mtd4
crw-rw---- 1 root root 90, 9 Jan 1 1970 mtd4ro
crw-rw---- 1 root root 90, 10 Jan 1 1970 mtd5
crw-rw---- 1 root root 90, 11 Jan 1 1970 mtd5ro
crw-rw---- 1 root root 90, 12 Jan 1 1970 mtd6
crw-rw---- 1 root root 90, 13 Jan 1 1970 mtd6ro
crw-rw---- 1 root root 90, 14 Jan 1 1970 mtd7
crw-rw---- 1 root root 90, 15 Jan 1 1970 mtd7ro
crw-rw---- 1 root root 90, 16 Jan 1 1970 mtd8
crw-rw---- 1 root root 90, 17 Jan 1 1970 mtd8ro
crw-rw---- 1 root root 90, 18 Jan 1 1970 mtd9
crw-rw---- 1 root root 90, 19 Jan 1 1970 mtd9ro
brw-rw---- 1 root root 31, 0 Jan 1 1970 mtdblock0
brw-rw---- 1 root root 31, 1 Jan 1 1970 mtdblock1
brw-rw---- 1 root root 31, 10 Jan 1 1970 mtdblock10
brw-rw---- 1 root root 31, 11 Jan 1 1970 mtdblock11
brw-rw---- 1 root root 31, 12 Jan 1 1970 mtdblock12
brw-rw---- 1 root root 31, 13 Jan 1 1970 mtdblock13
brw-rw---- 1 root root 31, 14 Jan 1 1970 mtdblock14
brw-rw---- 1 root root 31, 15 Jan 1 1970 mtdblock15
brw-rw---- 1 root root 31, 16 Jan 1 1970 mtdblock16
brw-rw---- 1 root root 31, 17 Jan 1 1970 mtdblock17
brw-rw---- 1 root root 31, 18 Jan 1 1970 mtdblock18
brw-rw---- 1 root root 31, 19 Jan 1 1970 mtdblock19
brw-rw---- 1 root root 31, 2 Jan 1 1970 mtdblock2
brw-rw---- 1 root root 31, 3 Jan 1 1970 mtdblock3
brw-rw---- 1 root root 31, 4 Jan 1 1970 mtdblock4
brw-rw---- 1 root root 31, 5 Jan 1 1970 mtdblock5
brw-rw---- 1 root root 31, 6 Jan 1 1970 mtdblock6
brw-rw---- 1 root root 31, 7 Jan 1 1970 mtdblock7
brw-rw---- 1 root root 31, 8 Jan 1 1970 mtdblock8
brw-rw---- 1 root root 31, 9 Jan 1 1970 mtdblock9
crw-rw---- 1 root root 10, 90 Jan 1 1970 ramdump_AR6320
crw-rw---- 1 root root 10, 89 Jan 1 1970 ramdump_AR6320_SD
crw-rw---- 1 root root 10, 85 Jan 1 1970 ramdump_modem
crw-rw---- 1 root root 10, 80 Jan 1 1970 ramdump_smem
cat /proc/mounts
Code:
rootfs / rootfs rw 0 0
ubi0:rootfs / ubifs rw,relatime,bulk_read,chk_data_crc 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,size=64k,mode=755 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620 0 0
tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
tmpfs /var/volatile tmpfs rw,relatime 0 0
tmpfs /media/ram tmpfs rw,relatime 0 0
ubi0:usrfs /data ubifs rw,relatime,bulk_read,chk_data_crc 0 0
/dev/ubi1_0 /firmware ubifs rw,relatime,bulk_read,chk_data_crc 0 0
ubi2:userrw /mnt/userrw ubifs rw,sync,relatime,bulk_read,chk_data_crc 0 0
ubi3:hdata /mnt/hdata ubifs ro,relatime,bulk_read,chk_data_crc 0 0
tmpfs /media/drives tmpfs ro,relatime,size=4k 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
var /var tmpfs rw,relatime 0 0
/dev/loop0 /mnt/hdata/licenses squashfs ro,relatime 0 0
I tried poking around /sys/devices/7980000.nand but I'm not as experienced with *NIX systems. I've also tried messing with QPST and similar tools but to no avail.

bump

MR1100?

Related

[Q] does USB serial host exist?

I've been searching every where and not getting a good answer for this. Does the Gen8 USB host mode support USB serial tty ports? This thread:
http://forum.xda-developers.com/showthread.php?t=863853
seems to point at the possibility.
I understand that it would need to have a host side CDC driver and appropriate kernel support. Does anyone know how much of that, if any, exists in the stock Froyo install?
If it does not exist, what does it take? Is it reasonable to think about compiling a driver and modprobe'ing it in (assuming kernel support)? (I'm not afraid to try it, I wrote my first driver back in the days of punch cards, but.... I've only just installed the Android SDK and unboxed my Archos 70 four days ago -- I should be considered clueless but trainable. Links and other clues much appreciate.)
-dave
It works with usb-acm driver out of the box.
I have been trying to connect a FTDI Serial to USB converter on an A101.
The module is properly detected and shows up in dmesg and lsusb.
However, /dev/ttyUSBx is not assigned. I would have expected this address in linux, so maybe I has another name?
@Tizot: do you know more about this?
b.serengeti said:
I have been trying to connect a FTDI Serial to USB converter on an A101.
The module is properly detected and shows up in dmesg and lsusb.
However, /dev/ttyUSBx is not assigned. I would have expected this address in linux, so maybe I has another name?
@Tizot: do you know more about this?
Click to expand...
Click to collapse
Have you checked /dev/tty0 or /dev/tty1? I haven't done it in a while, but I'm pretty sure it was one of those.
This is my list of devices after I plug the converter:
Code:
# ls -l
total 0
crw------- 1 root root 189, 1 Jul 20 21:57 1-2
crw------- 1 root root 189, 129 Jul 20 22:04 2-1
crw-rw-rw- 1 root root 248, 0 Jul 20 21:57 DspBridge
crw-rw-rw- 1 root root 10, 233 Jul 20 21:57 accel_ctrl
crw-rw-r-- 1 storage 1001 10, 61 Jul 20 21:57 alarm
crw-rw-rw- 1 root root 10, 63 Jul 20 21:57 ashmem
crw-rw-rw- 1 root root 10, 59 Jul 20 21:57 binder
drwxr-xr-x 3 root root 760 Jul 20 21:57 block
crw------- 1 root root 5, 1 Jul 20 21:58 console
crw------- 1 root root 10, 55 Jul 20 21:57 cpu_dma_latency
drwxr-xr-x 4 storage 1000 0 Jul 20 21:57 cpuctl
crw------- 1 root root 10, 60 Jul 20 21:57 device-mapper
crwxrwxrwx 1 root root 10, 241 Jul 20 21:57 dmalloc
crwxr-xr-x 1 root root 230, 0 Jul 20 21:57 dsplink
drwxr-xr-x 4 root root 80 Jul 20 21:57 dvb
crw-rw-rw- 1 root root 29, 0 Jul 20 21:57 fb0
crw-rw-rw- 1 root root 1, 7 Jul 20 21:57 full
crw------- 1 root root 10, 229 Jul 20 21:57 fuse
drwxr-xr-x 2 root root 40 Jul 20 21:57 gadget
drwxr-xr-x 2 root root 60 Jul 20 21:57 graphics
crwxr-xr-x 1 root root 10, 239 Jul 20 21:57 hdmi
crw-rw-rw- 1 root root 247, 0 Jul 20 21:57 hdmitx
crw------- 1 root root 89, 1 Jul 20 21:57 i2c-1
crw------- 1 root root 89, 2 Jul 20 21:57 i2c-2
crw------- 1 root root 89, 3 Jul 20 21:57 i2c-3
drwxr-xr-x 2 root root 340 Jul 20 21:57 input
crw-r----- 1 root root 1, 2 Jul 20 21:57 kmem
crw------- 1 root root 1, 11 Jul 20 21:57 kmsg
drwxr-xr-x 2 root root 100 Jul 20 21:57 log
crw-r----- 1 root root 1, 1 Jul 20 21:57 mem
drwxr-xr-x 2 root root 40 Jul 20 21:57 mtp
crw------- 1 root root 10, 54 Jul 20 21:57 network_latency
crw------- 1 root root 10, 53 Jul 20 21:57 network_throughput
crw-rw-rw- 1 root root 1, 3 Jul 20 21:57 null
crw------- 1 root root 250, 0 Jul 20 21:57 omap-previewer
crw------- 1 root root 249, 0 Jul 20 21:57 omap-resizer
crw-rw-rw- 1 root root 30, 0 Jul 20 21:57 omaplfb
prw-rw-rw- 1 root root 0 Jul 20 21:57 pm_server_in
prw-rw-rw- 1 root root 0 Jul 20 21:57 pm_server_out
crw-rw---- 1 1001 1016 108, 0 Jul 20 21:57 ppp
crw-rw-rw- 1 root root 5, 2 Jul 20 22:28 ptmx
drwxr-xr-x 2 root root 0 Jan 1 1970 pts
crw-rw-rw- 1 root root 251, 0 Jul 20 21:57 pvrsrvkm
crw------- 1 root root 81, 3 Jul 20 21:57 radio0
crw-rw-rw- 1 root root 1, 8 Jul 20 21:57 random
crw------- 1 root root 254, 0 Jul 20 21:57 rtc0
brwxr-xr-x 1 root root 8, 0 Jul 20 21:57 sda
drwxrwxrwt 2 root root 60 Jul 20 21:57 shm
drwxr-xr-x 2 root root 280 Jul 20 21:57 snd
drwxrwxr-x 2 root 3004 200 Jul 20 21:57 socket
crw------- 1 root root 246, 0 Jul 20 21:57 tifm
crw-rw-rw- 1 root root 5, 0 Jul 20 21:57 tty
crw-rw---- 1 root 1000 4, 0 Jul 20 21:57 tty0
crw------- 1 root root 4, 1 Jul 20 21:57 tty1
crw------- 1 root root 4, 10 Jul 20 21:57 tty10
crw------- 1 root root 4, 11 Jul 20 21:57 tty11
crw------- 1 root root 4, 12 Jul 20 21:57 tty12
crw------- 1 root root 4, 13 Jul 20 21:57 tty13
crw------- 1 root root 4, 14 Jul 20 21:57 tty14
crw------- 1 root root 4, 15 Jul 20 21:57 tty15
crw------- 1 root root 4, 16 Jul 20 21:57 tty16
crw------- 1 root root 4, 17 Jul 20 21:57 tty17
crw------- 1 root root 4, 18 Jul 20 21:57 tty18
crw------- 1 root root 4, 19 Jul 20 21:57 tty19
crw------- 1 root root 4, 2 Jul 20 21:57 tty2
crw------- 1 root root 4, 20 Jul 20 21:57 tty20
crw------- 1 root root 4, 21 Jul 20 21:57 tty21
crw------- 1 root root 4, 22 Jul 20 21:57 tty22
crw------- 1 root root 4, 23 Jul 20 21:57 tty23
crw------- 1 root root 4, 24 Jul 20 21:57 tty24
crw------- 1 root root 4, 25 Jul 20 21:57 tty25
crw------- 1 root root 4, 26 Jul 20 21:57 tty26
crw------- 1 root root 4, 27 Jul 20 21:57 tty27
crw------- 1 root root 4, 28 Jul 20 21:57 tty28
crw------- 1 root root 4, 29 Jul 20 21:57 tty29
crw------- 1 root root 4, 3 Jul 20 21:57 tty3
crw------- 1 root root 4, 30 Jul 20 21:57 tty30
crw------- 1 root root 4, 31 Jul 20 21:57 tty31
crw------- 1 root root 4, 32 Jul 20 21:57 tty32
crw------- 1 root root 4, 33 Jul 20 21:57 tty33
crw------- 1 root root 4, 34 Jul 20 21:57 tty34
crw------- 1 root root 4, 35 Jul 20 21:57 tty35
crw------- 1 root root 4, 36 Jul 20 21:57 tty36
crw------- 1 root root 4, 37 Jul 20 21:57 tty37
crw------- 1 root root 4, 38 Jul 20 21:57 tty38
crw------- 1 root root 4, 39 Jul 20 21:57 tty39
crw------- 1 root root 4, 4 Jul 20 21:57 tty4
crw------- 1 root root 4, 40 Jul 20 21:57 tty40
crw------- 1 root root 4, 41 Jul 20 21:57 tty41
crw------- 1 root root 4, 42 Jul 20 21:57 tty42
crw------- 1 root root 4, 43 Jul 20 21:57 tty43
crw------- 1 root root 4, 44 Jul 20 21:57 tty44
crw------- 1 root root 4, 45 Jul 20 21:57 tty45
crw------- 1 root root 4, 46 Jul 20 21:57 tty46
crw------- 1 root root 4, 47 Jul 20 21:57 tty47
crw------- 1 root root 4, 48 Jul 20 21:57 tty48
crw------- 1 root root 4, 49 Jul 20 21:57 tty49
crw------- 1 root root 4, 5 Jul 20 21:57 tty5
crw------- 1 root root 4, 50 Jul 20 21:57 tty50
crw------- 1 root root 4, 51 Jul 20 21:57 tty51
crw------- 1 root root 4, 52 Jul 20 21:57 tty52
crw------- 1 root root 4, 53 Jul 20 21:57 tty53
crw------- 1 root root 4, 54 Jul 20 21:57 tty54
crw------- 1 root root 4, 55 Jul 20 21:57 tty55
crw------- 1 root root 4, 56 Jul 20 21:57 tty56
crw------- 1 root root 4, 57 Jul 20 21:57 tty57
crw------- 1 root root 4, 58 Jul 20 21:57 tty58
crw------- 1 root root 4, 59 Jul 20 21:57 tty59
crw------- 1 root root 4, 6 Jul 20 21:57 tty6
crw------- 1 root root 4, 60 Jul 20 21:57 tty60
crw------- 1 root root 4, 61 Jul 20 21:57 tty61
crw------- 1 root root 4, 62 Jul 20 21:57 tty62
crw------- 1 root root 4, 63 Jul 20 21:57 tty63
crw------- 1 root root 4, 7 Jul 20 21:57 tty7
crw------- 1 root root 4, 8 Jul 20 21:57 tty8
crw------- 1 root root 4, 9 Jul 20 21:57 tty9
crw-rw-rw- 1 1002 1002 4, 64 Jul 20 21:57 ttyS0
crw------- 1 root root 4, 65 Jul 20 21:57 ttyS1
crw-rw-rw- 1 root root 4, 66 Jul 20 21:57 ttyS2
crw-rw---- 1 root 1000 10, 62 Jul 20 21:57 twl4030-madc
crw-rw---- 1 storage 1002 10, 223 Jul 20 21:57 uinput
crw-rw-rw- 1 root root 1, 9 Jul 20 21:58 urandom
crw------- 1 root root 189, 0 Jul 20 21:57 usb1
crw------- 1 root root 189, 128 Jul 20 22:04 usb2
crw------- 1 root root 252, 1 Jul 20 21:57 usbdev1.1_ep00
crw------- 1 root root 252, 0 Jul 20 21:57 usbdev1.1_ep81
crw------- 1 root root 252, 6 Jul 20 21:57 usbdev1.2_ep00
crw------- 1 root root 252, 3 Jul 20 21:57 usbdev1.2_ep02
crw------- 1 root root 252, 5 Jul 20 21:57 usbdev1.2_ep04
crw------- 1 root root 252, 2 Jul 20 21:57 usbdev1.2_ep81
crw------- 1 root root 252, 4 Jul 20 21:57 usbdev1.2_ep83
crw------- 1 root root 252, 8 Jul 20 22:04 usbdev2.1_ep00
crw------- 1 root root 252, 7 Jul 20 22:04 usbdev2.1_ep81
crw------- 1 root root 252, 11 Jul 20 22:04 usbdev2.2_ep00
crw------- 1 root root 252, 10 Jul 20 22:04 usbdev2.2_ep02
crw------- 1 root root 252, 9 Jul 20 22:04 usbdev2.2_ep81
crw------- 1 root root 253, 0 Jul 20 21:57 usbmon0
crw------- 1 root root 253, 1 Jul 20 21:57 usbmon1
crw------- 1 root root 253, 2 Jul 20 22:04 usbmon2
crw------- 1 root root 7, 0 Jul 20 21:57 vcs
crw------- 1 root root 7, 128 Jul 20 21:57 vcsa
crwxrwxrwx 1 root root 81, 0 Jul 20 21:57 video0
crwxrwxrwx 1 root root 81, 1 Jul 20 21:57 video1
crwxrwxrwx 1 root root 81, 2 Jul 20 21:57 video2
crw------- 1 root root 10, 130 Jul 20 21:57 watchdog
crw-rw-rw- 1 root root 1, 5 Jul 20 21:57 zero
the new dev that appear are
2-1
usbdev2.2_*
Unfortunately, all of these have no access rights for non-root users.
Code:
# dmesg
.....
usb usb2: usb resume
hub 2-0:1.0: hub_resume
hub 2-0:1.0: port 1: status 0101 change 0001
hub 2-0:1.0: state 7 ports 1 chg 0002 evt 0000
hub 2-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
usb 2-1: new full speed USB device using musb_hdrc and address 2
usb 2-1: ep0 maxpacket = 8
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=0403, idProduct=6001
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: TTL232RG-VREG3V3
usb 2-1: Manufacturer: FTDI
usb 2-1: SerialNumber: FTSM9CPA
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: configuration #1 chosen from 1 choice
usb 2-1: adding 2-1:1.0 (config #1, interface 0)
usb 2-1:1.0: uevent
drivers/usb/core/inode.c: creating file '002'
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1 enable change, status 00000103
Code:
# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 227d:0a19
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
This means that the device is properly detected. However, I would expect an assignement to a port in dmesg.
This is what I get on my OpenSuse 11.3 PC:
Code:
[ 5092.095250] usb 1-4: reset high speed USB device using ehci_hcd and address 4
[ 6240.088138] usb 1-4: reset high speed USB device using ehci_hcd and address 4
[ 6360.089017] usb 1-4: reset high speed USB device using ehci_hcd and address 4
[ 7368.722185] usb 2-1.4: new full speed USB device using ehci_hcd and address 5
[ 7368.813944] usb 2-1.4: New USB device found, idVendor=0403, idProduct=6001
[ 7368.813947] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7368.813949] usb 2-1.4: Product: TTL232RG-VREG3V3
[ 7368.813951] usb 2-1.4: Manufacturer: FTDI
[ 7368.813953] usb 2-1.4: SerialNumber: FTSM9CPA
[ 7369.246761] usbcore: registered new interface driver usbserial
[ 7369.246794] USB Serial support registered for generic
[ 7369.247018] usbcore: registered new interface driver usbserial_generic
[ 7369.247020] usbserial: USB Serial Driver core
[ 7369.253357] USB Serial support registered for FTDI USB Serial Device
[ 7369.253457] ftdi_sio 2-1.4:1.0: FTDI USB Serial Device converter detected
[ 7369.253503] usb 2-1.4: Detected FT232RL
[ 7369.253505] usb 2-1.4: Number of endpoints 2
[ 7369.253846] usb 2-1.4: Endpoint 1 MaxPacketSize 64
[ 7369.253848] usb 2-1.4: Endpoint 2 MaxPacketSize 64
[ 7369.253849] usb 2-1.4: Setting MaxPacketSize 64
[ 7369.254055] usb 2-1.4: FTDI USB Serial Device converter now attached to ttyUSB0
[ 7369.254067] usbcore: registered new interface driver ftdi_sio
[ 7369.254069] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
I tried to cat /dev/tty0 or tty1, ttyS0, ttyS2, 2-1, but no success in obtaining any data.
Is there a way to check to which port the device is connected or to set a configuration file to determine a priori the port?
If you use the multiboot menu from bubu you can turn on serial debugging see here http://dev.openaos.org/wiki/SettingUpMultiRootGen8#Debugging
Maurice
Thx divx118.
But this is not what I am looking for. I am connecting a serial device to the Archos, not the Archos as serial device to the PC. I am trying to find the port for this device. The PC example I gave was for the serial device connected to the PC.
Of course, it is possible that there is a missing support somewhere for it, but I just can't find the issue.
b.serengeti said:
Thx divx118.
But this is not what I am looking for. I am connecting a serial device to the Archos, not the Archos as serial device to the PC. I am trying to find the port for this device. The PC example I gave was for the serial device connected to the PC.
Of course, it is possible that there is a missing support somewhere for it, but I just can't find the issue.
Click to expand...
Click to collapse
Oh sorry, I was too quick with my answer. You could try irc and ask your question there.
http://www.openaos.org/chat or #openpma on irc.freenode.net.
Maurice

Need help?

Hallo all, I need help! Anyone want to send me log after adb shell command
Code:
ls /dev/oncrpc
Thanks!
Code:
crw-rw---- 1 0 1000 253, 0 Jun 8 12:19 00000000:0
crw-rw---- 1 0 1000 253, 9 Jun 8 12:19 30000000:e9fb8210
crw-rw---- 1 0 1000 253, 8 Jun 8 12:19 30000002:00020002
crw-rw---- 1 0 1000 253, 4 Jun 8 12:19 30000003:f94d6efb
crw-rw---- 1 0 1000 253, 25 Jun 8 12:19 3000000a:00010001
crw-rw---- 1 0 1000 253, 23 Jun 8 12:19 3000000e:00020001
crw-rw---- 1 0 1000 253, 19 Jun 8 12:19 30000012:00010001
crw-rw---- 1 0 1000 253, 18 Jun 8 12:19 30000013:00020002
crw-rw---- 1 0 1000 253, 17 Jun 8 12:19 30000014:00020001
crw-rw---- 1 0 1000 253, 15 Jun 8 12:19 30000016:d6bb93e6
crw-rw---- 1 0 1000 253, 14 Jun 8 12:19 30000019:821a1945
crw-rw---- 1 0 1000 253, 13 Jun 8 12:19 3000001b:90258183
crw-rw---- 1 0 1000 253, 10 Jun 8 12:19 3000001d:ba845703
crw-rw---- 1 0 1000 253, 12 Jun 8 12:19 3000003c:aa5a11fe
crw-rw---- 1 0 1000 253, 24 Jun 8 12:19 30000048:00010004
crw-rw---- 1 0 1000 253, 11 Jun 8 12:19 3000005b:a60286b0
crw-rw---- 1 0 1000 253, 7 Jun 8 12:19 3000005f:00010001
crw-rw---- 1 0 1000 253, 5 Jun 8 12:19 30000060:00010002
crw-rw---- 1 0 1000 253, 2 Jun 8 12:19 30000061:00010001
crw-rw---- 1 0 1000 253, 26 Jun 8 12:19 30000066:00010001
crw-rw---- 1 0 1000 253, 22 Jun 8 12:19 3000006b:00010001
crw-rw---- 1 0 1000 253, 1 Jun 8 12:19 30000081:00010002
crw-rw---- 1 0 1000 253, 21 Jun 8 12:19 3000008c:00020002
crw-rw---- 1 0 1000 253, 16 Jun 8 12:19 30000091:00010001
crw-rw---- 1 0 1000 253, 20 Jun 8 12:19 3000fe00:a82d4624
crw-rw---- 1 0 1000 253, 6 Jun 8 12:19 30100001:00000000
crw-rw---- 1 0 1000 253, 3 Jun 8 12:19 30100002:00000000
unlocking
Hi munjeni, can you unlock my htc Desire c, it is a seconde device i have to unlock
Code:
00000000:0
30000000:e9fb8210
30000002:00020002
30000003:f94d6efb
3000000a:00010001
3000000e:00020001
30000012:00010001
30000013:00020002
30000014:00020001
30000016:d6bb93e6
30000019:821a1945
3000001b:90258183
3000001d:ba845703
3000003c:aa5a11fe
30000048:00010004
3000005b:a60286b0
3000005f:00010001
30000060:00010002
30000061:00010001
30000066:00010001
3000006b:00010001
30000081:00010002
3000008c:00020002
30000091:00010001
3000fe00:a82d4624
30100001:00000000
30100002:00000000

missing boot partition on xperia

Hello
I want to install new kernel image, but there is no boot partition, trying "ls" command gives this output:
~ # ls
acct init.goldfish.rc sd-ext
cache init.rc sdcard
config mnt sys
d modules system
data pre_hw_config.sh tmp
default.prop proc ueventd.delta.rc
dev recovery.fstab ueventd.goldfish.rc
etc res ueventd.rc
init root vendor
init.delta.rc sbin
~ # ls -l
drwxr-xr-x 3 root root 0 Feb 28 15:56 acct
drwxrwx--x 1 system cache 2048 Aug 31 16:12 cache
dr-x------ 2 root root 0 Feb 28 15:56 config
lrwxrwxrwx 1 root root 17 Feb 28 15:56 d -> /sys/kernel/debug
drwxrwx--x 1 system system 2048 Aug 31 16:12 data
-rw-r--r-- 1 root root 118 Jul 1 2012 default.prop
drwxr-xr-x 14 root root 3340 Feb 28 15:57 dev
lrwxrwxrwx 1 root root 11 Feb 28 15:56 etc -> /system/etc
-rwxr-xr-x 1 root root 98576 Aug 22 2012 init
-rwxr-xr-x 1 root root 5802 Jul 1 2012 init.delta.rc
-rwxr-xr-x 1 root root 1677 Jul 1 2012 init.goldfish.rc
-rwxr-xr-x 1 root root 15559 Aug 22 2012 init.rc
drwxrwxr-x 6 root system 0 Feb 28 15:56 mnt
drwxr-xr-x 2 root root 0 Feb 25 2012 modules
-rwxr-xr-x 1 root root 1406 Jul 1 2012 pre_hw_config.sh
dr-xr-xr-x 138 root root 0 Jan 1 1970 proc
-rwxr-xr-x 1 root root 243 Jul 1 2012 recovery.fstab
drwxr-xr-x 3 root root 0 Feb 28 15:57 res
drwx------ 2 root root 0 Aug 22 2012 root
drwxr-xr-x 2 root root 0 Jul 1 2012 sbin
drwxrwx--x 2 system system 0 Feb 28 15:56 sd-ext
lrwxrwxrwx 1 root root 11 Feb 28 15:56 sdcard -> /mnt/sdcard
drwxr-xr-x 12 root root 0 Jan 1 1970 sys
drwxr-xr-x 1 root root 2048 Feb 22 12:24 system
drwxr-xr-x 2 root root 0 Feb 28 15:57 tmp
-rw-r--r-- 1 root root 744 Jul 1 2012 ueventd.delta.rc
-rw-r--r-- 1 root root 0 Jul 1 2012 ueventd.goldfish.rc
-rw-r--r-- 1 root root 4225 Jul 1 2012 ueventd.rc
lrwxrwxrwx 1 root root 14 Feb 28 15:56 vendor -> /system/vendor
what should I do? its xperia x8, doesnt support fastboot

[Q] Create a edify_defs file

I tried to create my own edify_defs file to cook my own roms, but every time I try to flash the zip it fails because of that file it's not well. I don't know how to adapt it for my device. I tried to follow the template and other tutorials but it fails too.
Can anyone help me to create this file?
I attach some info:
recovery.fstab
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/bootimg /bootimg emmc defaults defaults
/dev/recovery /recovery emmc defaults defaults
/dev/uboot /uboot emmc defaults defaults
/[email protected] /system ext4 ro,noatime wait
/[email protected] /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/[email protected] /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto vfat defaults voldmanaged=sdcard1:auto
Code:
~ # ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 Oct 19 01:35 boot
drwxr-xr-x 2 root root 0 Oct 19 01:35 cache
drwxrwx--x 26 system system 4096 Oct 19 01:14 data
drwxr-xr-x 2 root root 0 Oct 19 01:35 datadata
-rwx------ 1 400 401 1618 Sep 24 20:19 default.prop
drwxr-xr-x 10 root root 3120 Oct 19 01:36 dev
drwxr-xr-x 2 root root 0 Oct 19 01:35 emmc
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected] -> /dev/block/mmcblk0p7
drwx------ 2 400 401 0 Oct 19 01:44 etc
drwxr-xr-x 2 root root 0 Oct 19 01:35 external_sd
-rwx------ 1 400 401 27410 Sep 24 20:19 file_contexts
-rwx------ 1 400 401 975 Sep 24 20:19 fstab.mt8127
-rwx------ 1 400 401 187840 Sep 24 20:19 init
-rwx------ 1 400 401 3151 Sep 24 20:19 init.rc
drwxr-xr-x 2 root root 0 Oct 19 01:35 internal_sd
drwxrwxr-x 5 root system 0 Oct 19 01:35 mnt
dr-xr-xr-x 108 root root 0 Jan 1 1970 proc
-rwx------ 1 400 401 2201 Sep 24 20:19 property_contexts
drwxr-xr-x 2 root root 0 Oct 19 01:35 recovery
drwx------ 3 400 401 0 Sep 24 20:19 res
drwx------ 2 root root 0 Aug 13 16:33 root
drwx------ 3 400 401 0 Sep 24 20:19 sbin
drwxr-xr-x 2 root root 0 Oct 19 01:35 sd-ext
lrwxrwxrwx 1 root root 13 Oct 19 01:35 sdcard -> /data/media/0
-rwx------ 1 400 401 663 Sep 24 20:19 seapp_contexts
-rwx------ 1 400 401 75012 Sep 24 20:19 sepolicy
d---r-x--- 3 root sdcard_r 60 Oct 19 01:35 storage
dr-xr-xr-x 17 root root 0 Oct 19 01:35 sys
drwxr-xr-x 3 400 401 0 Sep 24 20:19 system
drwxrwxr-x 2 root shell 140 Oct 19 01:38 tmp
-rwx------ 1 400 401 7275 Sep 24 20:19 ueventd.rc
Code:
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1017272 160 1017112 0% /dev
tmpfs 1017272 276 1016996 0% /tmp
tmpfs 1017272 0 1017272 0% /storage
tmpfs 1017272 0 1017272 0% /mnt/secure
tmpfs 1017272 0 1017272 0% /mnt/fuse
/[email protected] 28194832 7112272 21082560 25% /data
/dev/block/vold/179:97
1927480 679284 1248196 35% /storage/sdcard1
/[email protected] 1032088 662876 369212 64% /system
/[email protected] 705512 12632 692880 2% /cache
Thanks.

Building AOSP and Kernel from manufacturer - how to generate boot.img?

I have been able to successfully build AOSP for Android 8.1 (I want to say `lunch aosp_arm64`), and I also got the source for the kernel from the manufacturer which successfully builds. The problem is when I try to flash it onto the device with `fastboot flashall`. There is no boot.img file anywhere. I guess I'm kind of confused on where to put the kernel build output and how to generate a valid boot.img.
Here's what files are output from the kernel build:
HTML:
Image .Image.cmd Image.gz .Image.gz.cmd Image.gz-dtb .Image.gz-dtb.cmd
Here's what is in the AOSP directory out/target/product/generic:
HTML:
-rwxrwx--- 1 root vboxsf 85 Dec 31 16:21 advancedFeatures.ini
-rwxrwx--- 1 root vboxsf 7 Dec 31 16:15 android-info.txt
-rwxrwx--- 1 root vboxsf 61 Jan 2 16:00 build_fingerprint.txt
drwxrwx--- 1 root vboxsf 68 Jan 1 04:23 cache
-rwxrwx--- 1 root vboxsf 69206016 Jan 1 04:23 cache.img
-rwxrwx--- 1 root vboxsf 91766 Dec 31 15:23 clean_steps.mk
-rwxrwx--- 1 root vboxsf 380 Dec 31 16:21 config.ini
drwxrwx--- 1 root vboxsf 136 Jan 1 13:49 data
drwxrwx--- 1 root vboxsf 102 Jan 1 02:15 dex_bootjars
drwxrwx--- 1 root vboxsf 204 Jan 1 14:21 fake_packages
drwxrwx--- 1 root vboxsf 204 Dec 31 18:03 gen
-rwxrwx--- 1 root vboxsf 304809 Jan 1 14:25 installed-files.json
-rwxrwx--- 1 root vboxsf 96906 Jan 1 14:25 installed-files.txt
-rwxrwx--- 1 root vboxsf 42220 Jan 1 14:24 installed-files-vendor.json
-rwxrwx--- 1 root vboxsf 12044 Jan 1 14:24 installed-files-vendor.txt
-rwxrwx--- 1 root vboxsf 4088328 Dec 31 16:21 kernel-ranchu
-rwxrwx--- 1 root vboxsf 2248129 Dec 31 16:15 module-info.json
drwxrwx--- 1 root vboxsf 782 Jan 1 14:24 obj
-rwxrwx--- 1 root vboxsf 38 Dec 31 15:10 previous_build_config.mk
-rwxrwx--- 1 root vboxsf 1025236 Jan 1 14:21 ramdisk.img
drwxrwx--- 1 root vboxsf 102 Dec 31 16:09 recovery
drwxrwx--- 1 root vboxsf 1122 Jan 1 14:21 root
drwxrwx--- 1 root vboxsf 306 Jan 1 13:48 symbols
drwxrwx--- 1 root vboxsf 612 Jan 1 14:25 system
-rwxrwx--- 1 root vboxsf 2147483648 Jan 1 14:30 system.img
-rwxrwx--- 1 root vboxsf 2149580800 Jan 1 14:33 system-qemu.img
-rwxrwx--- 1 root vboxsf 576716800 Jan 1 14:12 userdata.img
drwxrwx--- 1 root vboxsf 340 Jan 1 13:49 vendor
-rwxrwx--- 1 root vboxsf 99999744 Jan 1 14:25 vendor.img
-rwxrwx--- 1 root vboxsf 102760448 Jan 1 14:33 vendor-qemu.img
I feel like there's just one step I'm missing/not understanding somewhere.
It ended up being that Image.gz-dtb was the kernel image and Image.gz was the ramdisk image, so I was able to use those with abootimg to create a boot.img file

Categories

Resources