fail to flash Android 4.2 image to Pandaboard ES-REV-B3

Hi Andy,

By : "We used to use Pandaboard ES-REV-B3, but recently we got Pandboard ES-REV-B3" You mean that you have one b3 board with working android and the new one isn't?

What android version are you working with?

Regards,

Boyko

Hi Boyko,

Sorry for my typo. It should be "We used to use Pandaboard ES-REV-B2, but recently we got Pandboard ES-REV-B3" instead.

Thanks & Best Regards

Andy

And the Android version is 4.2 Jellybean.

Hi Andy,

Please follow the guide below and see if you achieve any results.

http://www.svtronics.com/support/pandaboard-es-b3-developers-guide/

Regards,

Boyko

Hi Boyko,

This is a really good document. I'll try and post my feedback here later. Thanks a lot.

Best Regards

Andy

Hi Boyko,

I had downlaoded pre-built binary format of boot loader for Android per the instruction of the above link. And I had replaced the /device/ti/panda/bootloader.bin in my software branch with the u-boot.bin that I just downloaded. Then I tried flash bootloader.bin again with same steps as before:

----------------------------------------------------------------------------------------------------------------------------------------------------------

1. remove sdcard, usb cable, power cable

2. put in usb cable

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

----------------------------------------------------------------------------------------------------------------------------------------------------------

I still failed to flash bootloader.bin and the phenomenon was similar as before.

Thank & Best Regards

Andy

Hi Boyko,

Below is my complete script for flashing the board.

----------------------------------------------------------------------------------------------------------------------------------------------------------

##Run usbboot to set pandaboard runing in boot mode
sudo ./device/ti/panda/usbboot ./device/ti/panda/bootloader.bin

##Start flash
sudo ./out/host/linux-x86/bin/fastboot oem format
sudo ./out/host/linux-x86/bin/fastboot flash xloader ./device/ti/panda/xloader.bin
sudo ./out/host/linux-x86/bin/fastboot flash bootloader ./device/ti/panda/bootloader.bin
sudo ./out/host/linux-x86/bin/fastboot erase cache
sudo ./out/host/linux-x86/bin/fastboot flash boot ./out/target/product/panda/boot.img
sudo ./out/host/linux-x86/bin/fastboot flash userdata ./out/target/product/panda/userdata.img
sudo ./out/host/linux-x86/bin/fastboot flash system ./out/target/product/panda/system.img

----------------------------------------------------------------------------------------------------------------------------------------------------------

If I would like to create the xloader.bin and the bootloader.bin for the B3 board, is it possible? And is there a

guide if it is possible? Thanks ahead.

Thanks & Best Regards

Andy

You could use the fastboot.sh script provided with the official Android releases from TI.

What operating system are you trying to run on this board?.

Most of the Android releases use a really simple boot-loaders.

Regards,

Boyko

Hi Boyko,

The operating system I'm trying to run on this board is AOSP Android 4.2.

Because it has been running well on B2 board, but fails on B3 board at flashing bootloader.bin, is it likely that B3 board requires different bootloader.bin and xloader.bin from B2 board's?  As I know from the link below, B2 board uses Micron 8Gb memory, but B3 board uses Elpida 2x4Gb memory. 

http://omappedia.org/wiki/PandaBoard_Revisions

Thanks & Best Regards

Andy

Hello,

Did this ever get resolved? I have been attempting a similar effort to get Android on the Rev B3 board. Once u-boot is patched the kernel loads but I get nothing to the HDMI port. I get a bunch of messages on the console that say:

[ 6627.242156] request_suspend_state: wakeup (0->0) at 6627251068557 (2000-01-01 01:50:22.422058546 UTC)
[ 6627.267822] init: untracked pid XXXX exited

When I switch the video cable to the DVI port I see:

ANDROID_ (underscore flashing)

I've tried the prebuilts on the SVT site and also built Linaro for PandaBoard from scratch and neither work. I've even tried build the omap AOSP kernel from google source using the .config from linaro.

I'm about ready to give up on this effort and go to a BeagleBoard.

Any ideas?

Thanks

Dave

Not yet resolved. And it looks like you already go farther than me, as you have got kernel loaded while I am still struggling with flashing the bootloader.bin.

Did you also have the similar problem in flashing the bootloader.bin before you patched the u-boot? Which Android did you patch the u-boot on, AOSP 4.2 or some other versions?

Thanks & Best Regards

Andy

Hi Guys,

so you both followed the SVtronics guide step by step and still no output to the HDMI nor is the console responcive?

What is the console change you get when you press the wakeup button?

Also what version of the cross compiler did you use?

Regards,

Boyko

Andy,

Yes I saw the same problem with the bootloader that you had. I patched the Linaro Android on one of the panda builds at:

https://android-build.linaro.org/builds/~linaro-android-member-ti/panda-linaro/

However, you can simply use the instruntions to build u-boot form source in the SVT pandaboard-es-b3-developers-guide. I did that and it got me past the bootloader problem. If you have further issues, let me know and I can try to recreate what I did to get it working.

--dave

Hi Boyko,

I tried following the SVT guide and yes I get no HDMI output, but the console log shows this when I hot plug the hdmi (I don't know what the wakeup button - assume you mean display?):

------------------------------------------------------

[ 35.077301] in hpd work 0, state=0
[ 35.125427] hpd 1
[ 35.175201] in hpd work 1, state=0
[ 35.180236] hdmi_set_timings: hdmi.mode=1
[ 35.280364] omapdss DISPC error: timeout waiting for EVSYNC
[ 35.343139] in hpd work 2, state=1
[ 35.835571] request_suspend_state: wakeup (0->0) at 35844207767 (2000-01-01 00:00:30.962738039 UTC)
[ 35.847564] init: untracked pid 1792 exited
[ 35.992828] edid[000] = 00 ff ff ff ff ff ff 00 10 ac 53 a0 55 46 30 31
[ 35.999816] edid[010] = 03 14 01 03 80 30 1b 78 ee ee 95 a3 54 4c 99 26
[ 36.006805] edid[020] = 0f 50 54 a5 4b 00 71 4f 81 80 d1 c0 01 01 01 01
[ 36.013793] edid[030] = 01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c
[ 36.013793] edid[040] = 45 00 dd 0c 11 00 00 1e 00 00 00 ff 00 4b 37 32
[ 36.027740] edid[050] = 36 50 30 31 45 31 30 46 55 0a 00 00 00 fc 00 44
[ 36.034729] edid[060] = 45 4c 4c 20 53 58 32 32 31 30 54 0a 00 00 00 fd
[ 36.041717] edid[070] = 00 38 4c 1e 53 11 00 0a 20 20 20 20 20 20 01 02
[ 36.041717] edid[080] = 02 03 1f f1 4c 90 05 04 03 02 07 16 01 14 1f 12
[ 36.055694] edid[090] = 13 23 09 07 07 65 03 0c 00 10 00 83 01 00 00 02
[ 36.062683] edid[0a0] = 3a 80 18 71 38 2d 40 58 2c 45 00 dd 0c 11 00 00
[ 36.069519] edid[0b0] = 1e 01 1d 80 18 71 1c 16 20 58 2c 25 00 dd 0c 11
[ 36.076660] edid[0c0] = 00 00 9e 01 1d 00 72 51 d0 1e 20 6e 28 55 00 dd
[ 36.076660] edid[0d0] = 0c 11 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96
[ 36.090606] edid[0e0] = 00 dd 0c 11 00 00 18 00 00 00 00 00 00 00 00 00
[ 36.097595] edid[0f0] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 af
[ 36.104583] edid[100] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.104583] edid[110] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.118530] edid[120] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.125518] edid[130] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.125518] edid[140] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.139465] edid[150] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.146453] edid[160] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.153442] edid[170] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.160430] edid[180] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.167419] edid[190] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.174407] edid[1a0] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.181396] edid[1b0] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.181396] edid[1c0] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.195343] edid[1d0] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.202331] edid[1e0] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.209320] edid[1f0] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 36.209320] panel size 48 by 27

--------------------------------------------------

Perhaps I have some kind of display issue?

The cross compiler version with the Linaro build is:

export TARGET_TOOLS_PREFIX=prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8-linaro/bin/arm-linux-androideabi-

Thanks

--dave

Just to be sure I went back and tried the SVT pandaboard ES android pre-builts again.

https://www.dropbox.com/sh/nehzvckcbkdhui6/n3G5wbi-47

I verified 2 things:

1) The boot problem does not occur. (weird since I thought it did before with this load)

2) The kernel loads but I get no HDMI display out.

Once the Kernel was running, I went to the console and got a command line. I ran logcat to see what was going on and noticed something that may be related :

<snippet from logcat>----------------------------------------------

I/ServiceManager( 2026): Waiting for service SurfaceFlinger...
I/ServiceManager( 2026): Waiting for service SurfaceFlinger...
I/SurfaceFlinger( 2045): SurfaceFlinger is starting
I/SurfaceFlinger( 2045): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/libEGL ( 2045): eglGetDisplay:123 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 2045): eglInitialize:139 error 3008 (EGL_BAD_DISPLAY)
I/gralloc ( 2045): using (fd=12)
I/gralloc ( 2045): id = omapfb
I/gralloc ( 2045): xres = 1280 px
I/gralloc ( 2045): yres = 720 px
I/gralloc ( 2045): xres_virtual = 1280 px
I/gralloc ( 2045): yres_virtual = 1440 px
I/gralloc ( 2045): bpp = 32
I/gralloc ( 2045): r = 16:8
I/gralloc ( 2045): g = 8:8
I/gralloc ( 2045): b = 0:8
I/gralloc ( 2045): width = 203 mm (160.157639 dpi)
I/gralloc ( 2045): height = 114 mm (160.421051 dpi)
I/gralloc ( 2045): refresh rate = 73.12 Hz
E/ti_hwc ( 2045): Composer HAL failed to load compatible Graphics HAL
E/SurfaceFlinger( 2045): composer device failed to initialize (Invalid argument)
W/SurfaceFlinger( 2045): getting VSYNC period from fb HAL: 13676897
E/libEGL ( 2045): validate_display:251 error 3008 (EGL_BAD_DISPLAY)
F/libc ( 2045): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 2046 (SurfaceFlinger)
I/DEBUG ( 1344): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1344): Build fingerprint: 'pandaboard/pandaboard/pandaboard:4.2.2/JDQ39/2:tests/test-keys'
I/DEBUG ( 1344): Revision: '0'
I/DEBUG ( 1344): pid: 2045, tid: 2046, name: SurfaceFlinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 1344): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
I/DEBUG ( 1344): r0 00000000 r1 00000027 r2 a0000000 r3 00000000
I/DEBUG ( 1344): r4 00000000 r5 4061ad6c r6 401d7ff8 r7 41b399b0
I/DEBUG ( 1344): r8 4061adb0 r9 00000005 sl 0000003e fp bec8bb58
I/DEBUG ( 1344): ip 40239278 sp 4061ad68 lr deadbaad pc 401f8ad0 cpsr 60010130

......

<end snippet>----------------------------------------------------------------------

I wonder if the monitor I am using is causing a problem. It is a Dell SX2210T touch screen. This fault occurs continuously and I have a feeling that it aslo results in the "init: untracked pid xxxx exited" messages.

I'm going to try another monitor and see if that helps.

Hello,

I think I face the same issue.

I have the solution to update xloader to support rev B3, I written it here:

http://e2e.ti.com/support/omap/f/849/t/328364.aspx

But now I think we also need to update the kernel, but I do not (yet) know how.

Jean-Marc

I finally got Android to work on my ES-RevB3. Both SVT prebuilts and Linaro built from source.

The problem was the third party imagtec runtime libs. I noticed that logcat reported that it could not find the proper libEGL implementation. I found out how at:

http://www.omappedia.com/wiki/Android_Panda_Build_Source

....

# Get graphics binaries
$ wget http://people.linaro.org/~vishalbhoj/install-binaries-4.0.4.sh
$ chmod a+x install-binaries-4.0.4.sh
$ ./install-binaries-4.0.4.sh /dev/sdX2 "device node of system partition"

I haven't gotten and AOSP build to work yet though.

Hope this helps.