I am trying to bring up panda-board omap4430 with Android jellybean pre-built binaries, which I have downloaded from linaro.org (http://releases.linaro.org/12.12/android/panda/).
I am creating two partitions on SD card into file systems.
First is bootable FAT32 containing boot.tar.bz2 and u-boot.img and other ext3 partition is having userdata.tar.bz2 and system.tar.bz2.
After putting my SD card in panda board & connecting it through minicom on my Ubuntu pc, I am not able to see even a single charecter of untaring or something or any logs.
Am I missing something.
I have done Ubuntu porting on Beagle board earlier successfully.
you are flashing it first time on panda board then it has some other method, as they have given like below process
format sd card
copy MLO and u-boot.bin in fat 32 partitions
then follow the given process on OMAPpedia release nots.
Related
After an attempt to install Lineageos+Magisk on a Xiaomi Mi A1, ended in a boot loop,
I installed stock from tissot_images_V10.0.9.0.PDHMIXM_20190514.0000.00_9.0_3ded3e7b82.tgz with containing flash_all.sh which applies fastboot. I got a working starting point with a tidy a/b partitioning.
I flashed Lineage, addonsu and stock camera with a temporary (unflashed) TWRP
Everything works well but there is too little storage, Lineage displays a size of 32GB instead of 64GB
df tells me: /dev/block/mmcblk0p49 19092180 15660496 3431684 83% /data
but blockdev --getsize64 /dev/block/mmcblk0p49 reports 55087439360 (bytes)
I mounted the userdata.img from the stock firmware mentioned above on my Linux PC and df showed me
/dev/loop1 19092180 118172 18762328 1% /mnt/...
This seems to be the source of the problem, isn't it?
(How) can I resize the partition / file system (preferably) without loosing data)?
I found a solution for my problem.
TWRP has added resize2fs to its features:
https://www.theandroidsoul.com/twrp-2-8-7-0-introduces-resize2fs-feature-to-fix-incorrect-storage-space-available-on-a-device/
So I started TWRP
sudo fastboot boot twrp-3.3.0-1-tissot.img
In TWRP I launched command line and with a single command
resize2fs /dev/block/mmcblk0p49 <newsize>
the problem was solved. I did not extend to the full size of the partition but left some MBs (at the end) because I seem to remember having read that this space is necessary for meta data when encrypting the device.
I want to boot android pre-built bbbandroid.img.xz from internal mmc its always fail to boot whereas same procedure for SD Card it boot successfully.
To flash this image into internal mmc, I boot from SD Card and find internal memory at /dev/mmcblk1. Following command I used to flash image
sudo xz -cd bbbandroid.img.xz > /dev/mmcblk1
It shows partitions correctly. But always on console only slowly CCCCC printing and stopped.
Same procedure I am following to flash image into SD Card using UBuntu host machine and sd card reader and use similar command from ubuntu host machine
sudo xz -cd bbbandroid.img.xz > /dev/sdc
For Sd card, everything ok and booting successfully
I compared partitions of SD Card and internal mmc looks exactly same.
What might be problem any have idea?
We have an development board that has been run Yocto system. and we want it to run android system, we already has compiled android image with Yocto kernel that has android's some patch.
We don't know how to flash the android image (such as system.img boot.img and recovery.img and so on) to the development board because of the Yocto system partition different with android system.
we can use fastboot tool to flash Yocto system to EVB.and we want to know:
How to partition eMMC that we can use fastboot tool to flash android system. Do we need to modify Little Kernel code ? and how to modify it in Yocto system.
How to we boot the android system up?
It would be appreciated if you offer any useful information.
Thanks
How to partition eMMC that we can use fastboot tool to flash android system.
You'll need a tool that can partition the eMMC. Considering you are using yocto your best bet is gptfdisk package. gptfdisk recipe is at path poky/meta/recipes-devtools/fdisk/gptfdisk_1.0.0.bb. gptfdisk provides following text-mode partitioning tools
gdisk,
cgdisk,
sgdisk,
fixparts
You can use one of these tools to recreate the partitions in the partition table.
and how to modify it in Yocto system.
Do IMAGE_INSTALL_append = " gptfdisk " in conf file to make the tools of this package part of your image.
How to we boot the android system up?
You'll need 3 partitions
system.img - goes in partition named system
boot.img - goes in system named boot
and recovery.img - goes in system named recovery
Each tool has a man page on Linux. You can read the manuals using man sgdisk, man gdisk, man cgdisk and man fixparts. Some example usages of sgdisk
sgdisk -p </dev/sda> - To print all partitions on the disk
sgdisk --delete=partnum </dev/sda> - Delete a partition. This action deletes the entry from the partition table
There is a lot of way to partition the eMMC, it depends on your system: via USB, sdcard, nfs, uboot...
I think you can have a look at the meta-variscite, especially in the scripts folder. They have flash scripts for Yocto poky images, and android image (on the same boards). They flash from the SDcard to the eMMC.
I ported these scripts for a use with uboot: I run the command ums mmc 0 to start mass storage mode via USB OTG, and on my PC I run an install script which use dd for erasing partitions, fdisk for creating partitions, mkfs to format my device connected by USB.
You can also use mmc part in uboot, but I never tested this option.
Recently I ported marshmallow on my board. I was exploring USB functions and found an issue:
If I'm using a non-partitioned USB disk with NTFS file system, it's unable to detect it and display a notification as "Corrupted USB disk".
So I tried with other scenarios like, NTFS with partitioned USB disk, FAT32 on non-partitioned USB disk and all these are working fine.
Then I tried to mount it manually from adb shell:
# mount -t ntfs /dev/sda /mnt/usbdisk
and it's working fine.
But I'm still not able to find why it's not able to auto mount it when I've NTFS on non-partitioned USB disk.
Till now what all I came across is, my usb disk should be detected as DISK when non-partitioned but in case of NTFS file system it's taking it as PART i.e. partitioned disk and getting stuck somewhere.
Any suggestion or leads will be great help.
Thanks in Advance.
Please make few things....
U said ported to my board.
Talking about Android marshmallow or any other android ....
It is upon ur phone os to support NTFS file system.
Generally in stock Android there is no NTFS file system support.
Although it also depends upon brand , that they are providing NTFS file system support in their is or not.
Generally custom os ROM for ur phone may help.
I rooted android galaxy nexus. I don't see any video devices under dev folder checked through adb shell.
I am trying to use External USB camera http://brain.cc.kogakuin.ac.jp/research/usb-e.html.
Modified Kernel settings and build custom zImage , After unpacking boot.img and replacing zImage then repacked to new-boot.img. I flashed with new boot.img. Once i run sample camera app from above mentioned url cannot see any video frames. I think it could because there is no video device under /dev normally device should have /dev/video0,1 so on.
Any body can help or show some direction ?