|Re: [android-building] Do any current branches currently build / boot for pandaboard||Jean-Baptiste Queru||10/10/12 9:32 AM|
Only the master branch. There's been an issue with graphics since the
most recent drop of the kernel/libraries, and I've just merged a
change that should fix that (literally minutes ago). I haven't had
time to try it but there's a reasonable chance that it'll work.
On Wed, Oct 10, 2012 at 7:52 AM, Weston Weems <wwe...@gmail.com> wrote:
> Do any branches or head currently build and boot with appropriate graphics
> It looks like the the nature of how the sgx driver was loaded may have
> changed, and in the several ics/jb builds I've attempted in the past couple
> days resulted in lots of different problems. (kernel modules not loading,
> pvrinit vs pvrsrvctl etc)
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> For more options, visit this group at
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Jean-Baptiste Queru||10/10/12 9:52 AM|
Definitely stick with master. PandaBoard doesn't work with any other branches.
On the kernel front, omap-android-panda-3.0, which should be commit
On Wed, Oct 10, 2012 at 9:41 AM, Weston Weems <wwe...@gmail.com> wrote:
> Just to clarify (so I can test)
> I just need to make sure to repo sync master, and then make sure the kernels
> I am building are master from kernel/omap? or should I still be grabbing
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Adrien Grassein||10/11/12 12:16 AM|
The pandaboard still not boot with master of device/ti/panda (kernel problem on I2c commit 6c8e76e158a9bc849ec946ab030595e06ad89210).
After revert this commit, there is a kernel panic.
Is the kernel booting on your board or not?
2012/10/10 Weston Weems <wwe...@gmail.com>
Definitely fixed the graphics driver problem... I'm slapping together my changes in the kernel now...
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Jean-Baptiste Queru||10/11/12 5:50 AM|
I have evidence that the latest kernel boots on my boards, but I'm
hitting other issues (no display, no adb).
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Adrien Grassein||10/11/12 6:04 AM|
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Jean-Baptiste Queru||10/11/12 6:25 AM|
One of each. I'm seeing the same result on both.
On Thu, Oct 11, 2012 at 6:04 AM, Adrien Grassein
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Adrien Grassein||10/11/12 6:32 AM|
So it's very strange.
I checkouted the latest Android version (branch master on .repo/manifest commit f46b8df32efc4979bdca52bf52e83fd816819f60)
On device/ti/panda I am on 5f567f13b76dc6b2e1bfe3d279fbac0427704a09.
It's allright or not?
2012/10/11 Jean-Baptiste Queru <j...@android.com>
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Adrien Grassein||10/18/12 12:16 AM|
Could you copy/paste your manifest please. I'am on the top of Android master and my pandaboard still not boot :(
2012/10/17 Dan Murphy <murp...@gmail.com>
I have booted the lastest master on a Panda ES.
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Adrien Grassein||10/22/12 1:11 AM|
My pandaboard boots now (with graphics). This is my flashing script :
./out/host/linux-x86/bin/fastboot oem format
./out/host/linux-x86/bin/fastboot flash xloader device/ti/panda/xloader.bin
./out/host/linux-x86/bin/fastboot flash bootloader device/ti/panda/bootloader.bin
./out/host/linux-x86/bin/fastboot erase cache
./out/host/linux-x86/bin/fastboot -p panda flash userdata
./out/host/linux-x86/bin/fastboot -p panda flash cache
./out/host/linux-x86/bin/fastboot -p panda flashall
2012/10/19 Alex <ame...@online.de>
I think you need to flash the cache partition.
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Brad Arnold||10/23/12 4:24 PM|
I don't know the specific commit that would have broke it, but these caught my eye:
Merge: 2266e49 328a484
Date: Fri Oct 19 13:37:24 2012 -0700
Merge "Do all the zoneinfo.* file generation in Java."
Date: Fri Oct 19 13:03:52 2012 -0700
Do all the zoneinfo.* file generation in Java.
Merge: 1022507 eb06129
Date: Fri Oct 19 13:01:04 2012 -0700
Merge "Switch bionic over to using libcore's copy of libcore.util.ZoneInfo."
Date: Fri Oct 19 12:05:24 2012 -0700
Switch bionic over to using libcore's copy of libcore.util.ZoneInfo.
But that might not be exactly it. There's also an entry in the git log about "Pull bionic's time zone data from the new single 'tzdata' file." It sounds like those zoneinfo.* files are depreciated for some uses?
What I do know is that earlier last week the code would build and make working img files. But now if you do a completely fresh repo init and sync, then make, you'll not end up with any "bionic/libc/zoneinfo/zoneinfo.*" files or "out/target/product/panda/system/usr/share/zoneinfo/zoneinfo.*" files. These zoneinfo.* files missing from the system.img prevents android from booting past the splash-screen. (and logcat on the device shows complaints relating to zoneinfo).
If I place zoneinfo.* files (from an old build) in "out/target/product/panda/system/usr/share/zoneinfo/zoneinfo.*" and re-run make to re-generate the .img files, I end up with a build that will boot.
On Tue, Oct 23, 2012 at 11:29 AM, Weston Weems <wwe...@gmail.com> wrote:
Got checkin hash? I'd be willing to look into it.
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Brad Arnold||10/26/12 10:37 AM|
I've noticed that with master on the panda lots of apps that are not included with AOSP don't run at all. I've assumed that this may be due to an API which isn't exactly consistent with the last released version. I suspect master wouldn't pass the CTS (with any target device). Have you tried running other apps on the build you created? Is it better?
I was actually going to try this myself too, but it takes me so long to build on my home machine.
On Fri, Oct 26, 2012 at 10:12 AM, Weston Weems <wwe...@gmail.com> wrote:
Not out of the box, but it was rather easy to get it going... I just made sure hardware/ti/panda was current from head, kernel was at android-omap-panda-3.0, and that the sgx binaries matched. Everything else was simple sync from 4.1.2_r1.
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Alexander Meinke||10/30/12 12:21 PM|
it is quite interesting to see, that the i2c problem mentioned by @p fu is not specific to omap4430. I managed to boot my Panda by changing the SYSC register offset in drivers/i2c/busses/i2c-omap.c of the linux kernel from 0x10 to 0x20.
I think the problem lies in the code using/surrounding SYSC register (i2c subsys/drvier), because newer linux kernels (I tested version 3.6) have the register offset 0x10 and boot well on the same board!
Pandaboard Rev A2 / OMAP4430 ES2.1
Am 30.10.2012 um 14:21 schrieb p fu <fupin...@gmail.com>:
I can not boot my pandaboard ES(4460), with newest aosp code, and after add debug in kernel i found some thing wrong with i2c, who can give me some help?
<6>omap_i2c omap_i2c.1: bus 1 rev4.0 at 400 kHz
<4>Skipping twl internal clock init and using bootloader value (unknown osc rate)
<3>omap_i2c omap_i2c.1: controller timed out
<3>twl: i2c_write failed to transfer all messages (addr 0x0049, reg 3, len 4)
<3>omap_i2c omap_i2c.1: controller timed out
<3>twl: i2c_write failed to transfer all messages (addr 0x0049, reg 6, len 4)
<3>omap_i2c omap_i2c.1: controller timed out
<3>twl: i2c_write failed to transfer all messages (addr 0x0049, reg 0, len 4)
<6>twl6030: PIH (irq 39) chaining IRQs 368..387
<3>omap_i2c omap_i2c.1: controller timed out
<3>twl: i2c_read failed to transfer all messages (addr 0x0048, reg 29, len 1)
<3>twl6030: I2C err reading REG_VBATMIN_HI_CFG_STATE: -110
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Brad Arnold||11/5/12 7:29 AM|
There's nothing wrong with these ones: https://developers.google.com/android/nexus/drivers#panda
(I've also run master using these)
On Sat, Nov 3, 2012 at 6:37 AM, AndroidNewb <neelima.h...@gmail.com> wrote:
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Brad Arnold||11/5/12 3:50 PM|
Do you have three files in: out/target/product/panda/system/usr/share/zoneinfo/ ?
On Mon, Nov 5, 2012 at 4:48 PM, Duncan Cunningham <dunc...@gmail.com> wrote:
I haven't had any luck getting my pandaboard to boot master.
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Brad Arnold||11/6/12 12:22 PM|
Not sure about the panda version and kernel stuff then.
But it does sound (at least to me) that you're missing some zoneinfo files. Can you run ps aux or top or something to figure out what task your PID actually correlates to? (run ps aux, wait for next untracked PID printout, reference back to ps ax output). This should at least point you in the right direction.
On Tue, Nov 6, 2012 at 1:51 PM, Duncan Cunningham <dunc...@gmail.com> wrote:
The only file I have in that directory is tzdata. I'm not for sure if the problem I am running in to is related to the zoneinfo files being removed. If I use the master version of the kernel, the kernel won't boot at all. Also I am using the regular Pandaboard, not the ES.
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Brad Arnold||11/6/12 1:43 PM|
I've seen that before when I forgot to extract the graphics binaries.
Are you certain the the latest kernel + latest binaries don't work on the rev A? Because they work great for me on rev B / ES.
On Tue, Nov 6, 2012 at 3:40 PM, Duncan Cunningham <dunc...@gmail.com> wrote:
Looks like zygote is the untracked pid exiting.
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Gabriel Beddingfield||11/8/12 4:06 AM|
This is a known issue and seems to be related to I2S init. Seems to affect "older" boards (don't know if that means a specific rav). I know that Dan is working on a solution.
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Brad Arnold||11/8/12 7:59 AM|
I was able to make master work (as of about a week ago) as long as I inserted the three zoneinfo files (this is on rev B1). However, I decided I didn't want to run master, I wanted to run 4.1 (which I find to be more stable). So here's my process start to finish:
$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.2_r1
$ repo sync
download latest driver from: http://code.google.com/android/nexus/drivers.html#panda
$ tar xzvf imgtec-panda-20120807-c4e99e89.tgz
$ chmod +x extract-imgtec-panda.sh
$ cd device/ti/panda/
$ git checkout aosp/master
$ cd ../../../hardware/ti/omap4xxx/
$ git checkout aosp/master
$ source build/envsetup.sh
$ lunch full_panda-userdebug
and then when it's all done:
$ device/ti/panda/usbboot device/ti/panda/bootloader.bin
power up board with no sd card, let it boot from usb, then insert SD card
$ fastboot oem format
$ fastboot flash xloader device/ti/panda/xloader.bin
$ fastboot flash bootloader device/ti/panda/bootloader.bin
reboot into fastboot by holding the GPIO button
$ fastboot flash cache
$ fastboot flash userdata
$ fastboot flashall
I've bolded the parts that are different from the typical documentation that is floating around. (including device/ti/panda/README)
No promises that this works with any revision other than B1. But I would assume it works with B2 as well, because I believe the only difference is the DDR manufacturer.
On Wed, Nov 7, 2012 at 9:17 PM, Jay Yang <zwy...@marvell.com> wrote:
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Ilya Tikhonovsky||11/8/12 11:48 PM|
I also have the same problem with booting pandaboard es Rev. B
I repeated all the steps you mentioned and got the same result.
The boot process hangs at the same stage - blank screen with no other log records.
Also I see i2c error in the log.
Could you please suggest me how can I troubleshoot the boot process or solve this problem.
Texas Instruments X-Loader 1.41 (Oct 21 2011 - 09:28:33)
OMAP4460: 1.2 GHz capable SOM
Starting OS Bootloader from MMC/SD1 ...
U-Boot 1.1.4-gedeced79 (Feb 6 2012 - 09:27:11)
Load address: 0x80e80000
DRAM: 1024 MB
Flash: 0 kB
Using default environment
efi partition table:
256 128K xloader
512 256K bootloader
2048 8M recovery
18432 8M boot
34816 512M system
1083392 256M cache
1607680 14598M userdata
Hit any key to stop autoboot: 0
kernel @ 80008000 (3691628)
ramdisk @ 81000000 (167091)
I2C read: I/O error
Starting kernel ...
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Brad Arnold||11/9/12 8:03 AM|
Where did you see that output? The RS232 port?
That I2C error doesn't seem to matter, I get the exact same output as you from u-boot (including the I2C error), but the kernel boots fine. That message is a red herring.
It seems like the kernel doesn't properly have stdout set up. But that's odd if you're using the kernel from master and the same hardware rev as me. I would expect you'd see some output from the kernel.
Here's a thought: what program are you using to view the serial output? Maybe the kernel is set up to use flow control, but your serial terminal isn't supporting it? I'm using screen (ie: "sudo screen /dev/ttyUSB0 115200").
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Ilya Tikhonovsky||11/9/12 12:12 PM|
I'm using minicom. I set it up as described in this article http://omappedia.org/wiki/PandaBoard_Ubuntu_Minicom
and I had no problem with the terminal and linaro android image. Also the device works fine with ubuntu.
I'd say that the kernel hangs because the activity leds don't blink and no signal on hdmi and dvi ports.
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Brad Arnold||11/9/12 12:52 PM|
I'm out of ideas. The latest kernel works fine for me. :/
|Re: [android-building] Do any current branches currently build / boot for pandaboard||Brad Arnold||11/13/12 7:37 AM|
I've not tried to get video acceleration working yet (though it's on my to-do list). If you have any luck, please post back :) .
I have had it working on other branches, but I don't remember which. It may have been 4.1.1, or it may have been master (a few weeks ago).
On Tue, Nov 13, 2012 at 3:21 AM, Don Han <ples...@gmail.com> wrote:
|Re: [android-building] Re: Do any current branches currently build / boot for pandaboard||Jean-Baptiste Queru||12/3/12 7:20 PM|
I've merged in a bunch of changes, both in user-space and in the
kernel, and in my latest tests the master branch boots (but hangs) on
PandaBoard, and seems fine on PandaBoard ES.
On Mon, Nov 26, 2012 at 11:34 AM, Alex <ame...@online.de> wrote:
> Mismatch between bootloader and kernel is only one of three causes mentioned
> at Common Problems Booting Linux.
> Am Montag, 26. November 2012 19:51:40 UTC+1 schrieb Andrey Vostrikov:
>> Usually it indicates mismatch between bootloader and kernel.
>> Try first prebuilt images from top of master branch.
>> On Monday, November 26, 2012 7:56:51 PM UTC+4, Janosch Maier wrote:
>>> I am building for the panda board from the main repo. The kernel is
>>> After flashing the panda board the kernel hungs. The last message I get
>>> on the serial console is ‘Booting kernel..’.
|Re: [android-building] Re: Do any current branches currently build / boot for pandaboard||Jean-Baptiste Queru||12/5/12 6:01 PM|
Unfortunately, 4430 is likely to remain somewhat tricky. The
PandaBoard kernel is based on the one that is used in the Galaxy
Nexus, which uses a 4460, and it's very possible that there are other
changes lurking in there that make 4430 unhappy (we found one, but we
have to assume there are more).
On Wed, Dec 5, 2012 at 10:46 AM, Alex <ame...@online.de> wrote:
> Thank you for the bunch of changes JBQ. At least the prebuilt kernel now
> boots without the need to build the kernel from source with different SYSC
> offset that marked kernel dirty.
> Sadly the system hang most of the time after the line "acc_release". If
> Dexopt is done which include rebooting three to five times, the last line is
> "eth0: no IPv6 routers present". Sometimes it really come up to the lock
> screen and further (see attached screencap0). The system seem stable until
> class_start main in init.rc. In my opinion, mediaserver make the system
> hang, but needs more investigation.
> I further need to change init.rc to start console as root, because I need to
> restart adbd. My newest bootlog (attached) indicate a problem with
> persistent, writeable memory (storage). That means, if I flash userdata and
> cache and got to the settings app changing time or language it will
> definitely hang on next reboot. Flashing partitions again make the system