Do any current branches currently build / boot for pandaboard

Showing 21-88 of 88 messages
Do any current branches currently build / boot for pandaboard Weston Weems 10/10/12 7:52 AM
Do any branches or head currently build and boot with appropriate graphics drivers?

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)

Weston
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.

JBQ
> --
> 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
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en



--
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
warning.
Re: [android-building] Do any current branches currently build / boot for pandaboard Weston Weems 10/10/12 9:41 AM
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 omap-android-panda-3.0?

Weston
Re: [android-building] Do any current branches currently build / boot for pandaboard Weston Weems 10/10/12 9:47 AM
Actually nevermind, I see the changes in device/ti/panda repo


On Wednesday, October 10, 2012 9:32:41 AM UTC-7, Jean-Baptiste Queru wrote:
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
4a094a55476cad51c85928e7c5766d71944e87ea

JBQ
Re: [android-building] Do any current branches currently build / boot for pandaboard Adrien Grassein 10/11/12 12:16 AM
Hi,

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? 

Thanks,
Adrien

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).

JBQ
Re: [android-building] Do any current branches currently build / boot for pandaboard Adrien Grassein 10/11/12 6:24 AM
Do you have a Pandaboard or a Pandaboard ES (OMAP 4430 or OMAP 4460)?

2012/10/11 Jean-Baptiste Queru <j...@android.com>

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.

JBQ

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?

Thanks,
Adrien

2012/10/11 Jean-Baptiste Queru <j...@android.com>

Re: [android-building] Do any current branches currently build / boot for pandaboard G. Blake Meike 10/11/12 9:27 AM
Apropos: I have an ES.  Is there any plan to support it, ever?  No biggie, just curious.

thanks
  Blake Meike
Re: [android-building] Do any current branches currently build / boot for pandaboard Dan Murphy 10/17/12 7:10 AM
I have booted the lastest master on a Panda ES.

It is running right now.

Dan
Re: [android-building] Do any current branches currently build / boot for pandaboard Weston Weems 10/18/12 8:13 AM
Any problems with it just general use? I've got a slightly older version of jb running on mine and there were a decent number of bugs in dalvik alloc stuff, and DisplayListRenderer, which I've fixed in my local build... but would much rather be being able to just sync latest stuff and go from there.

Weston
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 :(


Thanks,
Adrien

2012/10/17 Dan Murphy <murp...@gmail.com>

Re: [android-building] Do any current branches currently build / boot for pandaboard Brad Arnold 10/18/12 9:14 PM
I'm also unable to get it running on my Panada ES (rev B1).

I'm on master. I did a "repo sync" just tonight, so I've got to be up to date, but it won't boot.

Why would it work for some of us, but not others?

Thanks,

Brad
Re: [android-building] Do any current branches currently build / boot for pandaboard Weston Weems 10/19/12 8:31 AM
I'm also still not seeing a functional booted panda....
I've made sure the gfx binaries are in sync... but still getting tons of

[  198.991485] init: untracked pid 4525 exited
[  202.165466] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4807, drivers/gpu/pvr/bridged_pvr_bridge.c]
[  202.198089] init: untracked pid 4782 exited

and manually pvrsrvctl --start --no-module doesnt seem to do anything either
Re: [android-building] Do any current branches currently build / boot for pandaboard Brad Arnold 10/19/12 10:26 AM
I'm not even that far. Mine won't boot at all.

My output is (sorry for the long body, for some reason google groups won't take this as an attachment):

                                             
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

In:    serial
Out:   serial
Err:   serial

efi partition table:
     256     128K xloader
     512     256K bootloader
    2048       8M recovery
   18432       8M boot
   34816     512M system
 1083392     256M cache
 1607680   14510M userdata
Net:   KS8851SNL
Hit any key to stop autoboot:  0
kernel   @ 80008000 (3691628)
ramdisk  @ 81000000 (222400)
I2C read: I/O error

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.0.31-g4a094a5 (jbq[at]jqueru.mtv.corp.google.com) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Tue Aug 7 10:35:16 PDT 2012
[    0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[    0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: OMAP4 Panda board
[    0.000000] Truncating RAM at 80000000-bfffffff to -afffffff (vmalloc region overlap).
[    0.000000] Reserving 16777216 bytes SDRAM for VRAM
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] OMAP4460 ES1.1
[    0.000000] SRAM: Mapped pa 0x40300000 to va 0xfe400000 size: 0xd000
[    0.000000] On node 0 totalpages: 190208
[    0.000000] free_area_init_node: node 0, pgdat c075f5e0, node_mem_map c08df000
[    0.000000]   Normal zone: 1536 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 188672 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 7 pages/cpu @c0ee9000 s6944 r8192 d13536 u32768
[    0.000000] pcpu-alloc: s6944 r8192 d13536 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 188672
[    0.000000] Kernel command line: console=ttyO2,115200n8 mem=1G androidboot.console=ttyO2 androidboot.serialno=6D86000200000001 androidboot.bootloader=U-Boot_1.1.4-gedeced79
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 512MB 231MB = 743MB total
[    0.000000] Memory: 744496k/744496k available, 41936k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
[    0.000000]     vmalloc : 0xf0800000 - 0xf8000000   ( 120 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .init : 0xc0008000 - 0xc0046000   ( 248 kB)
[    0.000000]       .text : 0xc0046000 - 0xc06ff000   (6884 kB)
[    0.000000]       .data : 0xc0700000 - 0xc075fdc0   ( 384 kB)
[    0.000000]        .bss : 0xc075fde4 - 0xc08deb30   (1532 kB)
[    0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:410
[    0.000000] omap_hwmod: dpll_mpu_m2_ck: missing clockdomain for dpll_mpu_m2_ck.
[    0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
[    0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
[    0.000061] Calibrating delay loop... 1194.24 BogoMIPS (lpj=4665344)
[    0.070404] pid_max: default: 32768 minimum: 301
[    0.070404] Mount-cache hash table entries: 512
[    0.070404] Initializing cgroup subsys debug
[    0.070404] Initializing cgroup subsys cpuacct
[    0.070404] Initializing cgroup subsys freezer
[    0.071868] CPU: Testing write buffer coherency: ok
[    0.072113] L310 cache controller enabled
[    0.072235] l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x5e470000, Cache size: 1048576 B
[    0.150756] CPU1: Booted secondary processor
[    0.181640] Brought up 2 CPUs
[    0.181640] SMP: Total of 2 processors activated (2388.48 BogoMIPS).
[    0.185485] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for emif_fw
[    0.185485] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l3_instr
[    0.185516] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l3_main_1
[    0.185516] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l3_main_2
[    0.185546] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_abe
[    0.185577] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_cfg
[    0.185577] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_per
[    0.185607] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_wkup
[    0.185607] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for mpu_private
[    0.185607] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for sl2if
[    0.185729] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for thermal_sensor
[    0.185760] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for usbhs_ohci
[    0.185760] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for usbhs_ehci
[    0.186035] omap_hwmod: l3_div_ck: missing clockdomain for l3_div_ck.
[    0.186035] omap_hwmod: l4_div_ck: missing clockdomain for l4_div_ck.
[    0.194488] omap_hwmod: mcpdm: cannot be enabled (3)
[    0.197235] print_constraints: dummy:
[    0.197235] NET: Registered protocol family 16
[    0.197235] GPMC revision 6.0
[    0.199279] EMIF0 is enabled with IRQ142
[    0.199279] EMIF1 is enabled with IRQ143
[    0.199432] Last reset was cold reset (PRM_RSTST=0x1)
[    0.199432]
[    0.199615] HSI: device registered as omap_hwmod: hsi
[    0.200134] OMAP GPIO hardware version 0.1
[    0.201843] omap_mux_init: Add partition: #1: core, flags: 2
[    0.203613] omap_mux_init: Add partition: #2: wkup, flags: 2
[    0.203613] ram_console: got buffer at a0000000, size 200000
[    0.203613] ram_console: uncorrectable error in header
[    0.204101] ram_console: no valid data in buffer (sig = 0xaaaa2aa0)
[    0.214294] console [ram-1] enabled
[    0.214355] omap_mux_get_by_name: Could not find signal uart1_cts.uart1_cts
[    0.215789] omap_hwmod_mux_init: Could not allocate device mux entry
[    0.228118] OMAP DMA hardware revision 0.0
[    0.237457] bio: create slab <bio-0> at 0
[    0.237823] print_constraints: vwl1271: 1800 mV
[    0.238342] SCSI subsystem initialized
[    0.238342] usbcore: registered new interface driver usbfs
[    0.238342] usbcore: registered new interface driver hub
[    0.240020] usbcore: registered new device driver usb
[    0.251922] omap_i2c omap_i2c.1: bus 1 rev4.0 at 400 kHz
[    0.252929] Skipping twl internal clock init and using bootloader value (unknown osc rate)
[    0.253692] twl6030: PIH (irq 39) chaining IRQs 368..387
[    0.255432] print_constraints: VUSB: 3300 mV normal standby
[    0.458160] twl6030_usb twl6030_usb: Initialized TWL6030 USB module
[    0.459045] print_constraints: VMMC: 1200 <--> 3000 mV at 3000 mV normal standby
[    0.459808] print_constraints: VPP: 1800 <--> 2500 mV at 1900 mV normal standby
[    0.459808] print_constraints: VCXIO: 1800 mV normal standby
[    0.459808] print_constraints: VDAC: 1800 mV normal standby
[    0.461456] print_constraints: VAUX2_6030: 1200 <--> 2800 mV at 1800 mV normal standby
[    0.462280] print_constraints: VAUX3_6030: 1000 <--> 3000 mV at 1200 mV normal standby
[    0.463378] print_constraints: CLK32KG:
[    0.463378] print_constraints: VANA: 2100 mV normal standby
[    0.478485] omap_i2c omap_i2c.2: bus 2 rev4.0 at 400 kHz
[    0.494110] omap_i2c omap_i2c.3: bus 3 rev4.0 at 100 kHz
[    0.509735] omap_i2c omap_i2c.4: bus 4 rev4.0 at 400 kHz
[    0.509735] omap-rproc omap-rproc.0: dsp is available
[    0.510742] omap-rproc omap-rproc.1: ipu is available
[    0.510742] Advanced Linux Sound Architecture Driver Version 1.0.24.
[    0.510742] Bluetooth: Core ver 2.16
[    0.512145] NET: Registered protocol family 31
[    0.512145] Bluetooth: HCI device and connection manager initialized
[    0.512145] Bluetooth: HCI socket layer initialized
[    0.512542] Bluetooth: L2CAP socket layer initialized
[    0.512542] Bluetooth: SCO socket layer initialized
[    0.513366] cfg80211: Calling CRDA to update world regulatory domain
[    0.513702] Switching to clocksource 32k_counter
[    0.516937] musb-hdrc: version 6.0, musb-dma, peripheral
[    0.517395] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    0.517578] Switched to NOHz mode on CPU #1
[    0.517852] Switched to NOHz mode on CPU #0
[    0.517852] musb-hdrc: MHDRC RTL version 2.0
[    0.517974] musb-hdrc: setup fifo_mode 4
[    0.517974] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    0.517974] musb-hdrc musb-hdrc: USB Peripheral mode controller at fc0ab000 using DMA, IRQ 124
[    0.518981] NET: Registered protocol family 2
[    0.519226] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.519226] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.519226] TCP bind hash table entries: 65536 (order: 8, 1572864 bytes)
[    0.526214] TCP: Hash tables configured (established 131072 bind 65536)
[    0.526763] TCP reno registered
[    0.526763] UDP hash table entries: 512 (order: 3, 32768 bytes)
[    0.527343] UDP-Lite hash table entries: 512 (order: 3, 32768 bytes)
[    0.527343] NET: Registered protocol family 1
[    0.527343] Trying to unpack rootfs image as initramfs...
[    0.550872] Freeing initrd memory: 216K
[    1.719482] omap-iommu omap-iommu.0: ducati registered
[    1.719482] omap-iommu omap-iommu.1: tesla registered
[    1.728424] ashmem: initialized
[    1.735290] fuse init (API version 7.16)
[    1.738464] msgmni has been set to 1454
[    1.740509] io scheduler noop registered
[    1.740753] io scheduler deadline registered
[    1.740753] io scheduler cfq registered (default)
[    1.741149] start plist test
[    1.746856] end plist test
[    1.750915] OMAP DSS rev 4.0
[    1.759735] dsscomp: initializing.
[    1.759735] misc dsscomp: display0=generic_dpi_panel
[    1.759735] misc dsscomp: display1=hdmi_panel
[    1.760162] misc dsscomp: found 2 displays and 4 overlays
[    1.760620] could not allocate slot
[    1.761047] omap-rproc omap-rproc.1: powering up ipu
[    1.761657] virtio_rpmsg_bus virtio0: rpmsg backend virtproc probed successfully
[    1.761657] virtio_rpmsg_bus virtio1: rpmsg backend virtproc probed successfully
[    1.763031] rpmsg_virtio TX: 28 00 00 00 64 00 00 00 35 00 00 00 00 00 00 00  (...d...5.......
[    1.763244] rpmsg_virtio TX: 72 70 6d 73 67 2d 72 65 73 6d 67 72 00 00 00 00  rpmsg-resmgr....
[    1.763244] rpmsg_virtio TX: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[    1.763244] rpmsg_virtio TX: 64 00 00 00 00 00 00 00                          d.......
[    1.763854] rpmsg_virtio TX: 28 00 00 00 64 00 00 00 35 00 00 00 00 00 00 00  (...d...5.......
[    1.764068] rpmsg_virtio TX: 72 70 6d 73 67 2d 72 65 73 6d 67 72 00 00 00 00  rpmsg-resmgr....
[    1.764068] rpmsg_virtio TX: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[    1.764068] rpmsg_virtio TX: 64 00 00 00 00 00 00 00                          d.......
[    1.764984] omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 104) is a OMAP U
...
Re: [android-building] Do any current branches currently build / boot for pandaboard Weston Weems 10/19/12 11:03 AM
rebuilding everything after making clean gets me android boot logo, but never gets beyond that... lots of untracked pid exited errors


Weston
Re: [android-building] Do any current branches currently build / boot for pandaboard Alex 10/19/12 12:36 PM
I think you need to flash the cache partition.

Am Freitag, 19. Oktober 2012 19:26:03 UTC+2 schrieb Brad Arnold:
I'm not even that far. Mine won't boot at all.

My output is (sorry for the long body, for some reason google groups won't take this as an attachment):

     ...
[    5.051513] EXT4-fs (mmcblk0p6): VFS: Can't find ext4 filesystem
...
[    5.108612] fs_mgr: Cannot mount filesystem on /dev/block/platform/omap/omap_hsmmc.0/by-name/cache at /cache
[    5.119842] init: fs_mgr_mount_all returned an error 
...
[    5.397674] Kernel panic - not syncing: Attempted to kill init!
Re: [android-building] Do any current branches currently build / boot for pandaboard Brad Arnold 10/19/12 1:28 PM
Thanks for the reply, Alex. I noticed that output and I kind of figured that's where the problem was, but I don't know why this would be the case as I followed the README exactly:

...
fastboot erase cache
fastboot flash userdata
fastboot flashall
...

Of course, I don't see any step that flashes the cache partition. I just assumed this was perhaps done in the "flashall" step or that an "erased" cache was an okay starting point (so long as it was "erased" and not just garbage).

Clearly I'm new to building Android (this is to be my starting point). Is there a step (or steps) missing from the devices/ti/panda/README that I am assumed to just know?

Thanks,

Brad
Re: [android-building] Do any current branches currently build / boot for pandaboard Brad Arnold 10/19/12 5:58 PM
I had that (untracked pid...android splash...nothing more). So I did a fresh "repo sync". then from the root of the repo I did a slightly modified version of what the readme says:

source build/envsetup.sh
lunch full_panda-userdebug
make fastboot

# Initial setup, part 2:
# With no SD card inserted, plug USB first, then the power cord,
#   and load fastboot over USB:
device/ti/panda/usbboot device/ti/panda/bootloader.bin

# Initial setup, part 3:
# Once in fastboot, insert and initialize an SD card (4GB or greater):
fastboot oem format
fastboot flash xloader device/ti/panda/xloader.bin
fastboot flash bootloader device/ti/panda/bootloader.bin

# Build and flash, part 1: Do a build
source build/envsetup.sh
lunch full_panda-userdebug
make

# Build and flash, part 2: Flash
# Reboot into the SD card's fastboot (hold GPIO_121 and press PWRON_RESET)
#   and flash the system:
cd out/target/product/panda
fastboot erase cache
fastboot flash cache
fastboot flash userdata
fastboot flashall

My changes are bolded and in red. I'm not sure what images it's using when you run fastboot from the root of the repo, but it worked when I changed directory before running fastboot. (or maybe the repo sync of today's code fixed it?). It was one of those things that did it for me. Also, for the record, I did exactly the commands listed above (I even rebuilt fastboot, even though I already had a binary). I'm not saying all of it is necessary, but one of those things fixed it for me.

Now Android fully boots. However the display blinks and I get a bunch of:

[  337.227355] omapdss DISPC error: VID2_FIFO_UNDERFLOW, disabling VID2
[  337.994750] omapdss DISPC error: VID3_FIFO_UNDERFLOW, disabling VID3
[  338.578674] omapdss DISPC error: VID3_FIFO_UNDERFLOW, disabling VID3
[  338.762176] omapdss DISPC error: VID2_FIFO_UNDERFLOW, disabling VID2
[  341.548278] omapdss DISPC error: VID3_FIFO_UNDERFLOW, disabling VID3
[  341.798522] omapdss DISPC error: VID2_FIFO_UNDERFLOW, disabling VID2

But oh well. Progress is progress. :)

Brad
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 :

device/ti/panda/usbboot device/ti/panda/bootloader.bin

./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


Thanks,
Adrien


2012/10/19 Alex <ame...@online.de>
--
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
android-buildi...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

Re: [android-building] Do any current branches currently build / boot for pandaboard Weston Weems 10/22/12 9:40 AM
You know... I found for whatever reason timezone info database was infact NOT populated... so I had to find a zoneinfo.dat, zoneinfo.idx, zoneinfo.version to toss in /usr/share/zoneinfo, and now the pid exited stuff is not an issue. Its booting just fine.

I'll report back on the stability of this build (seeing as the last few syncs seemed to have a decent number of bugs in libdvm, and libhwui.

Weston
Re: [android-building] Do any current branches currently build / boot for pandaboard Brad Arnold 10/22/12 9:51 AM
Yes!

The machine I had the success on suffered a disk failure. Now I've gone though the exact same motions as before on two different machines and I'm back to the "init: untracked pid xxx exited" and stuck at the bootsplash. 

I compared the two working directories after a "make clean" (on the machine where the build worked, and one one where it didn't), and I also noticed this was a difference between the two. Despite having done a "repo sync" on both.

What gives?

Brad
Re: [android-building] Do any current branches currently build / boot for pandaboard Brad Arnold 10/22/12 10:16 AM
Oh, I see there was a commit in bionic by Elliott Hughes last week updating the zoneinfo.* file generation code. I think there is a bug here.

On fresh working directories, the zoneinfo files never get generated. I suspect that's the source of all my problems.

Thoughts?

Brad

On Monday, October 22, 2012 10:40:29 AM UTC-6, Weston Weems wrote:
Re: [android-building] Do any current branches currently build / boot for pandaboard Weston Weems 10/23/12 10:29 AM
Got checkin hash? I'd be willing to look into it.

Weston

On Monday, October 22, 2012 10:16:14 AM UTC-7, Brad Arnold wrote:
Oh, I see there was a commit in bionic by Elliott Hughes last week updating the zoneinfo.* file generation code. I think there is a bug here.

On fresh working directories, the zoneinfo files never get generated. I suspect that's the source of all my problems.

Thoughts?

Brad

On Monday, October 22, 2012 10:40:29 AM UTC-6, Weston Weems wrote:
You know... I found for whatever reason timezone info database was infact NOT populated... so I had to find a zoneinfo.dat, zoneinfo.idx, zoneinfo.version to toss in /usr/share/zoneinfo, and now the pid exited stuff is not an issue. Its booting just fine.

I'll report back on the stability of this build (seeing as the last few syncs seemed to have a decent number of bugs in libdvm, and libhwui.

Weston

On Monday, October 22, 2012 1:11:59 AM UTC-7, Adrien Grassein wrote:
My pandaboard boots now (with graphics). This is my flashing script :

device/ti/panda/usbboot device/ti/panda/bootloader.bin

./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


Thanks,
Adrien


2012/10/19 Alex <ame...@online.de>
I think you need to flash the cache partition.

Am Freitag, 19. Oktober 2012 19:26:03 UTC+2 schrieb Brad Arnold:
I'm not even that far. Mine won't boot at all.

My output is (sorry for the long body, for some reason google groups won't take this as an attachment):

     ...
[    5.051513] EXT4-fs (mmcblk0p6): VFS: Can't find ext4 filesystem
...
[    5.108612] fs_mgr: Cannot mount filesystem on /dev/block/platform/omap/omap_hsmmc.0/by-name/cache at /cache
[    5.119842] init: fs_mgr_mount_all returned an error 
...
[    5.397674] Kernel panic - not syncing: Attempted to kill init!

--
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
android-buildi...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

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:

commit 551ca77e35098272abfe9484457827c661d23ef0
Merge: 2266e49 328a484
Author: Elliott Hughes <e...@google.com>
Date:   Fri Oct 19 13:37:24 2012 -0700

    Merge "Do all the zoneinfo.* file generation in Java."

commit 328a48458880ed12f2e7d1632b98c5df8d211be7
Author: Elliott Hughes <e...@google.com>
Date:   Fri Oct 19 13:03:52 2012 -0700

    Do all the zoneinfo.* file generation in Java.
    
    Bug: 7012465
    Change-Id: Ia5d5ad75db94d680a6b34ccc26eb68d5bd2bfc29

commit 2266e4956f4b245903acd66f0cc32ec5caf5abae
Merge: 1022507 eb06129
Author: Elliott Hughes <e...@google.com>
Date:   Fri Oct 19 13:01:04 2012 -0700

    Merge "Switch bionic over to using libcore's copy of libcore.util.ZoneInfo."

commit eb06129c5c569897a897f9ec9ee300560ec3b436
Author: Elliott Hughes <e...@google.com>
Date:   Fri Oct 19 12:05:24 2012 -0700

    Switch bionic over to using libcore's copy of libcore.util.ZoneInfo.
    
    Bug: 7012465
    Change-Id: I1225494c5d77a20fd48be1e904d8695ef95860e3


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.

Brad
Re: [android-building] Do any current branches currently build / boot for pandaboard Weston Weems 10/24/12 8:56 AM
Yep looks like the functionality is half there... it definitely doesnt create zoneinfo stuff, and tz initialization stuff on the java side expects them to be there. I guess this is the danger in dealing with the head. I'm gonna just grab 4.1.2_r1 and make it work for panda...

Weston
Re: [android-building] Do any current branches currently build / boot for pandaboard michael 10/25/12 4:13 AM
Hi Weston,
Does branch 4.1.2_r1 work on pandaboard for you?
Now im building 4.1.2_r1, i hope that can boot up successfully on pandaboard.

在 2012年10月24日星期三UTC+8下午11时56分00秒,Weston Weems写道:
Re: [android-building] Do any current branches currently build / boot for pandaboard Weston Weems 10/26/12 9:12 AM
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.

Things are a LOT more stable than the head branch. finally! =)

Weston
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.

Brad
Re: [android-building] Do any current branches currently build / boot for pandaboard Weston Weems 10/29/12 9:24 AM
Head is basically a dev branch... as its been explained to me.

I've had LOADS of issues of just staying running consistently... without crashes in bionic. I would say your assumption is 100% correct. A good deal of the time it wouldn't pass cts tests.

Weston
Re: Do any current branches currently build / boot for pandaboard John 10/30/12 6:21 AM
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 Alexander Meinke 10/30/12 12:21 PM
Heyde,

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>:
Re: [android-building] Do any current branches currently build / boot for pandaboard AndroidNewb 11/3/12 5:37 AM

Dan, Can you give me the link to the right graphics binaries you have used?
Thanks
On Wednesday, October 17, 2012 10:10:31 AM UTC-4, Dan Murphy wrote:
I have booted the lastest master on a Panda ES.

It is running right now.

Dan

On Thursday, October 11, 2012 11:27:46 AM UTC-5, G. Blake Meike wrote:
Apropos: I have an ES.  Is there any plan to support it, ever?  No biggie, just curious.

thanks
  Blake Meike

On Thursday, October 11, 2012 6:24:09 AM UTC-7, Adrien Grassein wrote:
Do you have a Pandaboard or a Pandaboard ES (OMAP 4430 or OMAP 4460)?

2012/10/11 Jean-Baptiste Queru <j...@android.com>
I have evidence that the latest kernel boots on my boards, but I'm
hitting other issues (no display, no adb).

JBQ

On Thu, Oct 11, 2012 at 12:16 AM, Adrien Grassein
<adrien....@gmail.com> wrote:
> Hi,
>
> 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?
>
> Thanks,
> Adrien
>
>
> 2012/10/10 Weston Weems <wwe...@gmail.com>
>>
>> Definitely fixed the graphics driver problem... I'm slapping together my
>> changes in the kernel now...
>>
>>
>> On Wednesday, October 10, 2012 9:52:10 AM UTC-7, Jean-Baptiste Queru
>> wrote:
>>>
>>> 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
>>> 4a094a55476cad51c85928e7c5766d71944e87ea
>>>
>>> JBQ
>>>
>>> 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
>>> > omap-android-panda-3.0?
>>> >
>>> > Weston
>>> >
>>> >
>>> > On Wednesday, October 10, 2012 9:32:41 AM UTC-7, Jean-Baptiste Queru
>>> > wrote:
>>> >>
>>> >> 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.
>>> >>
>>> >> JBQ
>>> >>
>>> >> 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
>>> >> > drivers?
>>> >> >
>>> >> > 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)
>>> >> >
>>> >> > Weston

>>> >> >
>>> >> > --
>>> >> > 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
>>> >> > android-buildi...@googlegroups.com
>>> >> > For more options, visit this group at
>>> >> > http://groups.google.com/group/android-building?hl=en
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> 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
>>> >> warning.

>>> >
>>> > --
>>> > 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
>>> > android-buildi...@googlegroups.com
>>> > For more options, visit this group at
>>> > http://groups.google.com/group/android-building?hl=en
>>>
>>>
>>>
>>> --
>>> 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
>>> warning.

>>
>> --
>> 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
>> android-buildi...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-building?hl=en
>
>
> --
> 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
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en



--
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
warning.


--
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
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

Re: [android-building] Do any current branches currently build / boot for pandaboard Brad Arnold 11/5/12 7:32 AM
There's nothing wrong with these ones: https://developers.google.com/android/nexus/drivers#panda

(I've also run master using these)
Re: [android-building] Do any current branches currently build / boot for pandaboard Duncan Cunningham 11/5/12 2:48 PM
I haven't had any luck getting my pandaboard to boot master.

If I use a build from master, when booting up it will just hang on Uncompressing Linux... done, booting the kernel.  No other output is display over serial.  I found some posts claiming that if you hit enter a bunch of times, the kernel will boot.  This doesn't do anything for me.  Then found some other posts claiming I need to use a version of the kernel that uses 1.8@785978 of the SGX driver.  So I built the kernel from this commit: 52f476403350050beb0dff135a55c06c9e7a82a9 and got the 1.8@785978 SGX binaries.  Now when it boots, I just get the below error repeated infinitely.  I've double checked and there isn't a SGX version mismatches.  The pandaboard doesn't display anything on screen.

[ 2895.670898] init: untracked pid 9335 exited
[ 2900.918670] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4836, drivers/gpu/pvr/bridged_pvr_bridge.c]
[ 2900.966613] init: untracked pid 9350 exited
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/ ?
Re: [android-building] Do any current branches currently build / boot for pandaboard Duncan Cunningham 11/6/12 11:51 AM
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 12:35 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.
Re: [android-building] Do any current branches currently build / boot for pandaboard Duncan Cunningham 11/6/12 1:40 PM
Looks like zygote is the untracked pid exiting.
Re: [android-building] Do any current branches currently build / boot for pandaboard Brad Arnold 11/6/12 1:50 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.
Re: [android-building] Do any current branches currently build / boot for pandaboard Duncan Cunningham 11/6/12 2:12 PM
If I do a checkout of master, and use the latest version of the SGX binaries, the kernel hangs at Uncompressing Linux... done, booting the kernel.  This is why I downgraded the kernel, and I got older versions of the SGX binaries.  Both the kernel and SGX binaries are 1.8@785978.  I know there is some problem with the downgraded kernel and the binaries, but I don't know what it is, since the versions match.
Re: [android-building] Do any current branches currently build / boot for pandaboard Jay Yang 11/7/12 7:17 PM
Hi Arnold,
How do you make it ? Could you describe it in detail? I use the latest system and kernel on rev ES,it still has some problems:
1、If I don't hit Enter key,the system will suspend in the process of boot up,and show "Uncompressing Linux... done, booting the kernel. "
2、If I hit Enter key continuously during the system boot up,the system will dead and the screen will block at Android starting-up frame,finally.

Thanks

Jay Yang

在 2012年11月7日星期三UTC+8上午5时50分59秒,Brad Arnold写道:
Re: [android-building] Do any current branches currently build / boot for pandaboard hagenp 11/8/12 12:54 AM
On Tuesday, 6 November 2012 23:12:55 UTC+1, Duncan Cunningham wrote:
If I do a checkout of master, and use the latest version of the SGX binaries, the kernel hangs at Uncompressing Linux... done, booting the kernel.  This is why I downgraded the kernel, and I got older versions of the SGX binaries.  Both the kernel and SGX binaries are 1.8@785978.  I know there is some problem with the downgraded kernel and the binaries, but I don't know what it is, since the versions match.

Please check the kernel command line that is set in the boot loader (U-Boot),
and the kernel command line flags (should be similar to "append command line options to builtin").

If the kernel matches your hardware (in older Linux kernels for ARM, R2 contains a Hardware ID - if this is not found the Kernel stays in an endless loop), there are still a number of reasons why you can "hang".
E.g., one is the console tty needs to be set to the correct devce (otherwise you deonÄt get any output).
Then for some Panda configurations you need to have a "memory hole".
Next pitfall is that newer Linux kernels (e.g. 3.2.x) require a "flattened device tree", which needs to be referenced via the U-Boot boot command (after the rootfs image) to be passed on properly to the kernel.

Once the kernel boots, with PandaBoard ES2.1 and Linux 3.0.8+ I discovered an instabiity when using fewer than four partitions (with MBR as well as with GPT) that prevented booting into the GUI.

Good Luck!
Re: [android-building] Do any current branches currently build / boot for pandaboard Gabriel Beddingfield 11/8/12 4:06 AM


On Nov 5, 2012 4:49 PM, "Duncan Cunningham" <dunc...@gmail.com> wrote:
>
> I haven't had any luck getting my pandaboard to boot master.
>
> If I use a build from master, when booting up it will just hang on Uncompressing Linux... done, booting the kernel.  No other output is display over serial.  I found some posts

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.

-gabriel

Re: [android-building] Do any current branches currently build / boot for pandaboard Brad Arnold 11/8/12 8:06 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
$ tar xzvf imgtec-panda-20120807-c4e99e89.tgz
$ chmod +x extract-imgtec-panda.sh
$ ./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
$ make

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. 

Cheers,

Brad
Re: [android-building] Do any current branches currently build / boot for pandaboard Ilya Tikhonovsky 11/8/12 11:48 PM
Hi Brad,

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

In:    serial
Out:   serial
Err:   serial

efi partition table:
     256     128K xloader
     512     256K bootloader
    2048       8M recovery
   18432       8M boot
   34816     512M system
 1083392     256M cache
 1607680   14598M userdata
Net:   KS8851SNL
Hit any key to stop autoboot:  0 
kernel   @ 80008000 (3691628)
ramdisk  @ 81000000 (167091)
I2C read: I/O error

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
------------------------------------------------------------------------------

Regards,
Tim.
Re: [android-building] Do any current branches currently build / boot for pandaboard Brad Arnold 11/9/12 8:19 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"). 

Brad
Re: [android-building] Do any current branches currently build / boot for pandaboard Ilya Tikhonovsky 11/9/12 12:12 PM
Brad,

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 1:08 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 Weston Weems 11/12/12 9:21 AM
Make sure you have all the kernel debugging flipped on and EARLYPRINTK and the like.. .as they may give you a clue to the issue.
Re: [android-building] Do any current branches currently build / boot for pandaboard Don Han 11/13/12 1:21 AM
Brad

this worked for me, thanks.
but i don't know how to get hw video acceleration working.
i added ducati decoder to /etc/media_codecs.xml, and copied ducati-m3.bin to /system/vendor/firmware.
it is supposed that /dev/rpmsg-omx1 be created during kernel startup. but it's not there.

any sugestions from you?

Don
Re: [android-building] Do any current branches currently build / boot for pandaboard Brad Arnold 11/13/12 7:48 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).

Brad
Re: [android-building] Do any current branches currently build / boot for pandaboard Don Han 11/13/12 8:31 AM
Brad

i found that the ducati-m3.bin i used is a little old (version 1), and i replaced it with version 2.1 extracted from linaro 12.10.
now the /dev/rpmsg-omx1 shows up, but there're still errors:

D/DOMX    (  667): ERROR: Can't open misc driver device 0xd
D/DOMX    (  667): 
D/DOMX    (  667): ERROR: Can't read from the misc driver
D/DOMX    (  667): ERROR: Can't close the misc driver
I/dalvikvm(  268): Jit: resizing JitTable from 4096 to 8192
I/wpa_supplicant(  330): wpa_driver_nl80211_driver_cmd: Unsupported command SETSUSPENDMODE 0
E/ion     (  667): open /dev/ion failed!
D/DOMX    (  667): ERROR: failed check:(eError == OMX_ErrorNone) || (eError == OMX_ErrorNoMore) - returning error: 0x8000101a - Error returned from OMX API in ducati
D/DOMX    (  667): ERROR: failed check:eError == OMX_ErrorNone - returning error: 0x8000101a -  Error in Proxy SetParameter for Enhanced port reconfig usage

any clue about this?
Re: Do any current branches currently build / boot for pandaboard Andrey Vostrikov 11/16/12 12:24 PM
Looks like most of the problems are because of changes in HW composer API, surface flinger and SGX drivers.
This is procedure to bring up Android 4.2 on pandaboard ES rev B1.

repo sync to master branch (tested on 15-Nov-2012)

install pandaboard powervr binaries for master branch

cd hardware/ti/omap4xxx

# roll-back some of the latest changes that break pandaboard
git checkout b82d9c17662dce095133ffcd492fd0c967823408
# use HWC with API version compatible with android 4.2
cp hardware/ti/omap4-aah/hwc/hwc.c hardware/ti/omap4xxx/hwc/hwc.c
cd -
cd device/ti/panda
# roll-back panda device folder as well
git checkout 5f567f13b76dc6b2e1bfe3d279fbac0427704a09
# fix Audio HAL, storage configuration for multi-user feature, pvrsrvctl executable attribute
patch -p1 < dirty_bringup.patch
cd -

build and update device according to device/ti/panda/README with substitution of
fastboot erase cache => fastboot flash cache

UI is not very responsive, looks like vsync issues in surface flinger and most likely it is needed to cherry-pick one of rolled-back patches. And I hope there would be normal fixes on master branch soon.

adb behaves in a strange way after boot. If adb devices list is empty, try restart adbd:
device# stop adbd
device# start adbd

Re: Do any current branches currently build / boot for pandaboard Keith Deacon 11/20/12 10:08 PM

Yes - the UI is not responsive due to a vsync issue.  Looked at fixing it in the HWC, but it could cause issues with other omap4 devices so Dan patched the kernel instead - probably best there anyhow.  You can pull a new pre-built kernel here: https://android-review.googlesource.com/#/c/46477/.  Works on my ES rev B3 (i.e. 4460 based board).  It was not stable on any of the 4430 boards I have - thus the Nak.  Most everyone is out for thanksgiving break - so, hopefully we will have an update early next week.

...Kd
Re: Do any current branches currently build / boot for pandaboard Andrey Vostrikov 11/21/12 11:31 AM
Hi, I've already set software vsync flag in framework EventThread.
frameworks/native/services/surfaceflinger/EventThread.cpp
It also helps.

As for adb issue - it looks like that condition inside driver/usb/gadget/android.c::
adb_ready_callback() lacks negation. It causes extra call to android_enable (as enable flag already set in enable_store()) and messes dev->disable_depth counter.

-        if (data->enabled)
-                android_enable(dev);
+        if (!data->enabled)
+               android_enable(dev);

Looks this was improperly fixed by counterbalancing in the other adb functions:

adb_android_function_enable()
-        /* Disable the gadget until adbd is ready */
-        if (!data->opened)
-                android_disable(dev);

adb_android_function_disable()
-        /* Balance the disable that was called in closed_callback */
-        if (!data->opened)
-                android_enable(dev);

I have not found on source.android.com procedure how to submit patches for AOSP kernel.
If somebody knows, I could prepare patch.

Also, other kernels trees could have same issue.

Best regards,
Andrey.
Re: [android-building] Do any current branches currently build / boot for pandaboard Ahmed Abdelfattah 11/25/12 7:46 AM
I confirm this is working for rev B1 .
Re: Do any current branches currently build / boot for pandaboard Janosch Maier 11/26/12 7:56 AM
I am building for the panda board from the main repo. The kernel is android-omap-panda-3.0.

After flashing the panda board the kernel hungs. The last message I get on the serial console is ‘Booting kernel..’.
Re: Do any current branches currently build / boot for pandaboard Andrey Vostrikov 11/26/12 10:51 AM
Usually it indicates mismatch between bootloader and kernel.
Try first prebuilt images from top of master branch.
Re: Do any current branches currently build / boot for pandaboard Alex 11/26/12 11:34 AM
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:
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.

JBQ
Re: Do any current branches currently build / boot for pandaboard Yuriy Privezentsev 12/4/12 1:50 PM
Hi Andrey,

I am trying to follow your instructions but I am getting message that there is no such revision on the tree. What could went wrong?
Re: [android-building] Re: Do any current branches currently build / boot for pandaboard Alex 12/5/12 10:46 AM
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 boot.

Pandaboard Rev A2 / OMAP4430 ES2.1 

Am Dienstag, 4. Dezember 2012 04:20:13 UTC+1 schrieb Jean-Baptiste Queru:
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).

JBQ
Re: Do any current branches currently build / boot for pandaboard Andrey Vostrikov 12/6/12 3:55 AM
I am sorry for that. Missing hash is for cherry-picked commit in my git.

correct hash for omap4xxx was:
git checkout 7e093dba39ffb912fea76826a96d82bf91008f66

and this cherry-pick on top:
git cherry-pick c5d2fc3ce62f91306fe342d3aa2bfe37f6b51ef6

But you'd better try current master branch. It works on Pandaboard ES.

Set one of the live wallpaper (any but Magic Smoke) to eliminate flicker of SystemUI and show up navigation bar.
adb connection is not working right after boot, need to disable and enable again USB debugging or "stop adbd && start adbd" in device console or use my patch.
Also I attached manifest with revisions taken today from master branch that boots on Pandaboard ES.
Re: [android-building] Re: Do any current branches currently build / boot for pandaboard ramesh polasa 1/23/13 7:31 AM

ERROR while building 4AJ.2.1 on Pandaboard OMAP 4430


i'm getting following error while building AFS of 4AJ.2.1(omappedia.org/wiki/4AJ.2.1_OMAP4_Panda_ES) for 

pandaboard OMAP 4430 (R4AJ.2.ev EA2)can any one guide me in solving this problem?

user@user:/opt/android/4AJ.2.1/mydroid# make -j4 2>&1 |tee $MYDROID/logs/android_make.out
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2
TARGET_PRODUCT=full_panda
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.2.0-29-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=JOP40C
OUT_DIR=out
============================================
device/ti/proprietary-open/Android.mk:257: warning: overriding commands for target `out/target/product/panda/fake_packages/ti-wpan-fw'
build/core/base_rules.mk:502: warning: ignoring old commands for target `out/target/product/panda/fake_packages/ti-wpan-fw'
find: `src': No such file or directory
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/Effect_Tick.ogg:system/media/audio/ui/Effect_Tick.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressStandard.ogg:system/media/audio/ui/KeypressStandard.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressSpacebar.ogg:system/media/audio/ui/KeypressSpacebar.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressDelete.ogg:system/media/audio/ui/KeypressDelete.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressReturn.ogg:system/media/audio/ui/KeypressReturn.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/VideoRecord.ogg:system/media/audio/ui/VideoRecord.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/camera_click.ogg:system/media/audio/ui/camera_click.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/LowBattery.ogg:system/media/audio/ui/LowBattery.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/Dock.ogg:system/media/audio/ui/Dock.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/Undock.ogg:system/media/audio/ui/Undock.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/Lock.ogg:system/media/audio/ui/Lock.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/Unlock.ogg:system/media/audio/ui/Unlock.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Sceptrum.ogg:system/media/audio/ringtones/Sceptrum.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressStandard_120.ogg:system/media/audio/ui/KeypressStandard.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressSpacebar_120.ogg:system/media/audio/ui/KeypressSpacebar.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressDelete_120.ogg:system/media/audio/ui/KeypressDelete.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/KeypressReturn_120.ogg:system/media/audio/ui/KeypressReturn.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/notifications/ogg/Capella.ogg:system/media/audio/notifications/Capella.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/notifications/ogg/CetiAlpha.ogg:system/media/audio/notifications/CetiAlpha.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/notifications/ogg/Polaris.ogg:system/media/audio/notifications/Polaris.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/notifications/ogg/Pollux.ogg:system/media/audio/notifications/Pollux.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/notifications/ogg/Procyon.ogg:system/media/audio/notifications/Procyon.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Aquila.ogg:system/media/audio/ringtones/Aquila.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/ArgoNavis.ogg:system/media/audio/ringtones/ArgoNavis.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Carina.ogg:system/media/audio/ringtones/Carina.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Centaurus.ogg:system/media/audio/ringtones/Centaurus.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Cygnus.ogg:system/media/audio/ringtones/Cygnus.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Draco.ogg:system/media/audio/ringtones/Draco.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Machina.ogg:system/media/audio/ringtones/Machina.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Orion.ogg:system/media/audio/ringtones/Orion.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Pegasus.ogg:system/media/audio/ringtones/Pegasus.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Pyxis.ogg:system/media/audio/ringtones/Pyxis.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Rigel.ogg:system/media/audio/ringtones/Rigel.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Scarabaeus.ogg:system/media/audio/ringtones/Scarabaeus.ogg ignored.
PRODUCT_COPY_FILES frameworks/base/data/sounds/ringtones/ogg/Solarium.ogg:system/media/audio/ringtones/Solarium.ogg ignored.
No private recovery resources for TARGET_DEVICE panda
Copying: out/target/common/obj/JAVA_LIBRARIES/bouncycastle_intermediates/classes.jar
Copying: out/target/common/obj/JAVA_LIBRARIES/ext_intermediates/classes.jar
Copying: out/target/common/obj/JAVA_LIBRARIES/core-junit_intermediates/classes.jar
target Symbolic: libdl (out/target/product/panda/symbols/system/lib/libdl.so)
host Java: MonkeyRunnerTest (out/host/common/obj/JAVA_LIBRARIES/MonkeyRunnerTest_intermediates/classes)
Copying: out/host/common/obj/JAVA_LIBRARIES/apache-harmony-tests-hostdex_intermediates/classes-jarjar.jar
Copying: out/host/common/obj/JAVA_LIBRARIES/core-tests-hostdex_intermediates/classes-jarjar.jar
Install: out/host/linux-x86/framework/lint.jar
Install: out/host/linux-x86/framework/sdkmanager-tests.jar
target Static Jar: guava (out/target/common/obj/JAVA_LIBRARIES/guava_intermediates/javalib.jar)
target thumb C++: libstagefright <= frameworks/av/media/libstagefright/ACodec.cpp
target thumb C++: libstagefright <= frameworks/av/media/libstagefright/AwesomePlayer.cpp
target thumb C++: libstagefright <= frameworks/av/media/libstagefright/CameraSource.cpp
frameworks/av/media/libstagefright/ACodec.cpp: In member function 'android::status_t android::ACodec::setupFlacCodec(bool, int32_t, int32_t, int32_t)':
frameworks/av/media/libstagefright/ACodec.cpp:1321:9: error: 'OMX_AUDIO_PARAM_FLACTYPE' was not declared in this scope
frameworks/av/media/libstagefright/ACodec.cpp:1321:34: error: expected ';' before 'def'
frameworks/av/media/libstagefright/ACodec.cpp:1322:24: error: 'def' was not declared in this scope
frameworks/av/media/libstagefright/ACodec.cpp:1326:50: error: 'OMX_IndexParamAudioFlac' was not declared in this scope
frameworks/av/media/libstagefright/ACodec.cpp: In member function 'android::status_t android::ACodec::setSupportedOutputFormat()':
frameworks/av/media/libstagefright/ACodec.cpp:1464:5: error: 'OMX_TI_COLOR_FormatYUV420PackedSemiPlanar' was not declared in this scope
frameworks/av/media/libstagefright/ACodec.cpp:1464:5: error: 'OMX_QCOM_COLOR_FormatYVU420SemiPlanar' was not declared in this scope
frameworks/av/media/libstagefright/ACodec.cpp:1464:5: error: 'OMX_QCOM_COLOR_FormatYUV420PackedSemiPlanar64x32Tile2m8ka' was not declared in this scope
frameworks/av/media/libstagefright/ACodec.cpp: In function 'android::status_t android::GetVideoCodingTypeFromMime(char const*, OMX_VIDEO_CODINGTYPE*)':
frameworks/av/media/libstagefright/ACodec.cpp:1487:23: error: 'OMX_VIDEO_CodingVPX' was not declared in this scope
frameworks/av/media/libstagefright/CameraSource.cpp: In function 'int32_t android::getColorFormat(char const*)':
frameworks/av/media/libstagefright/CameraSource.cpp:119:15: error: 'OMX_TI_COLOR_FormatYUV420PackedSemiPlanar' was not declared in this scope
frameworks/av/media/libstagefright/CameraSource.cpp:123:16: error: 'OMX_COLOR_FormatAndroidOpaque' was not declared in this scope
frameworks/av/media/libstagefright/AwesomePlayer.cpp: In member function 'void android::AwesomePlayer::onVideoEvent()':
frameworks/av/media/libstagefright/AwesomePlayer.cpp:1898:51: error: 'kKeyVideoFPS' was not declared in this scope
make: *** [out/target/product/panda/obj/SHARED_LIBRARIES/libstagefright_intermediates/CameraSource.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** [out/target/product/panda/obj/SHARED_LIBRARIES/libstagefright_intermediates/ACodec.o] Error 1
make: *** [out/target/product/panda/obj/SHARED_LIBRARIES/libstagefright_intermediates/AwesomePlayer.o] Error 1
Note: sdk/monkeyrunner/test/com/android/monkeyrunner/AllTests.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

of is there any way to avoid or leave ACodec and camera modules because i didnt needed them in my project

More topics »