Hi,
I am having a few problems with getting android up and running on my pandaboard ES
After getting the final message -
Done creating Linaro Android image on /dev/sdb
I remove the SD card and place it in my pandaboard but all I get is a blank screen.
I also seem to be having some issues with minicom working at this point.
I get the message - minicom: cannot open /dev/ttyUSB0: No such file or directory
As android in flashed to my SD card this is what it says.
I see...
Device Mount point Size
/dev/sda none 305245MB
/dev/sda1 none 10000MB
/dev/sda2 none 247569MB
/dev/sda3 none 47674MB
/dev/sda5 / 43837MB
/dev/sda6 none 3836MB
/dev/sdb none 7580MB
/dev/sdb1 /media/boot 131MB
/dev/sdb2 /media/system 512MB
/dev/sdb3 /media/cache 256MB
/dev/sdb4 none 6680MB
/dev/sdb5 /media/userdata 511MB
/dev/sdb6 /media/sdcard 6167MB
/dev/sr0 none 0MB
Are you 100% sure, on selecting [/dev/sdb] (y/n)? y
Checking that no-one is using this disk right now ...
OK
Warning: bad partition start (earliest 1843201)
partition ends on cylinder 1023, beyond the end of the disk
partition ends on cylinder 1023, beyond the end of the disk
Warning: partition 1 does not end at a cylinder boundary
end of partition 4 has impossible value for cylinders: 1023 (should be in 0-1020)
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
Formating boot partition
mkfs.vfat 3.0.12 (29 Oct 2011)
mke2fs 1.42 (29-Nov-2011)
Filesystem label=userdata
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
131072 inodes, 524272 blocks
26213 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
64 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
mke2fs 1.42 (29-Nov-2011)
Filesystem label=cache
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
65536 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67371008
32 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
mke2fs 1.42 (29-Nov-2011)
Filesystem label=system
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
32768 inodes, 131072 blocks
6553 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=134217728
4 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
mkfs.vfat 3.0.12 (29 Oct 2011)
Image Name: boot script
Created: Fri Jul 6 19:31:57 2012
Image Type: ARM Linux Script (uncompressed)
Data Size: 385 Bytes = 0.38 kB = 0.00 MB
Load Address: 00000000
Entry Point: 00000000
Contents:
Image 0: 377 Bytes = 0.37 kB = 0.00 MB
Done creating Linaro Android image on /dev/sdb
Is there any problems you can see there?
Thanks
Dale
Hey everyone!
I need some advice on the following topic:
Discuss how representative 'panda-ics-tracking' is vs other builds
This is related to this blueprint:
https://blueprints.launchpad.net/linaro-android/+spec/build-tests
I did all my analysis of tests present in AOSP on the panda tree (both
source an binary). I assume that's pretty representative and I don't
need to repeat the work for snowball/vexpress/etc but I'd like your
opinion on this topic.
Thanks
ZK
--
Zygmunt Krynicki
Linaro Validation Team
s/Validation/Android/
Hi, all
I met a problem that the omapzoom and aosp build of panda can't be booted
up in lava.
here is the bug link:
https://bugs.launchpad.net/lava-dispatcher/+bug/1012546
When we passed the bootcmd and bootargs via u-boot, and run boot to boot
the images deployed on partition3,
the u-boot load kernel image and initrd file successfully, and displayed
the line:
"Uncompressing Linux... done, booting the kernel."
but after this line, it seems that the board rebooted and boot the master
image as default again, not boot up the android image.
I guess it has relation with uboot in master image because I have tried to
use the MLO and u-boot.bin and u-boot.img in omapzoom build
to replace the files on boot partition of master image, then I can boot
the omapzoom and aosp build successfully.
(also can boot the tracking build)
What I did was as following:
1. deploy omapzoom build to sdcard with linaro-android-media-create command
2. copy the MLO and u-boot.bin and u-boot.img 3 file from sdcard to
someplace in local
3. use "./lava-create-master -r 2G panda" to create the sdcard used for
master image
we can get the lava-create-master script from
lp:lava-master-image-scripts
4. plug in the sdcard and boot the board
5. wait the board to complete the partition job.
after this, the uImage and uInitrd file in boot partition has been
change,
and then the master image can be booted with the uboot files from
omapzoom build
but I don't know why and what change has been done.
6. copy the MLO and u-boot.bin and u-boot.img 3 file to the boot partition
of sdcard
7. plug the sdcard to the board and boot it, then it can be use to boot the
tracking/omapzoom/aosp 3 builds of panda.
The version original u-boot for master image is: U-Boot 2011.12 (Feb 16
2012 - 21:46:14)
The u-boot version of omapzoom build is: U-Boot 2011.06 (Aug 20 2011 -
18:00:16).
The u-boot version of tracking build is : U-Boot SPL 2012.04.01 (Jun 14
2012 - 08:05:54)
The tracking build works fine with the original uboot of master image.
So I guess there are some differences between the original uboot for master
image and the uboot build in omapzoom build.
Anyone know the details why it can not boot the omapzoom and aosp build on
the 3rd partition,
and if I can boot the omapzoom and aosp build of panda with the
original u-boot of master image?
Thanks,
Yongqin Liu
Hey everyone.
It seems that monkey trips over new test apks that have been added as a
side effect of building TARGET_BUILD_VARIANT=tests images.
For example, see: https://pastebin.linaro.org/636/
We may need to blacklist some (all?) of them initially to get meanigful
results.
Best regards
ZK
--
Zygmunt Krynicki
Linaro Validation Team
s/Validation/Android/
Dear Sir/Madam,
I am trying to download the Linaro builded staging-panda-11.11-release code.
While the "repo sync" process failed when I was fetching the project "people/andygreen/repo-branch-archive.git /" from Remote "http://git.linaro.org/git".
Then, I tried the manual download the project by "git clone" command with http, git and ssh link available for that branch but also failed.
Is that because of the repository configuration error?
Would you please help me to figure it out?
Thank you,
David Qian | Senior Engineer, Office of the CTO | RSA, The Security Division of EMC | Shanghai +86 021 60951100 - 3284 |
www.rsa.com<http://www.rsa.com>
Hey.
I'm seeing a lot of messages like those on my panda:
[ 172.220275] emif emif.2: SDRAM temperature change, new level MR4=5
[ 172.559173] emif emif.2: temperature alert before registers are
calculated, not de-rating timings
Is that something to worry about?
NOTE: the unit does run hot (far too hot to touch comfortably).
Thanks
ZK
--
Zygmunt Krynicki
Linaro Validation Team
s/Validation/Android/
