• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 98 subscribers
  • Views 1241 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Android Gingerbread on Beagleboard-XM -

PRAJITH WARRIER80347
Intellectual 310 points

Hi

 

I am trying to port Android Gingerbread on Beagleboard-XM.

I have downloaded the Android source code from

"http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/TI_Android_GingerBread_2_3_4_DevKit_2_1/index_FDS.html"

Host System is : Ubuntu 11.04

Issue: 

I. I copied the uimage ,u-boot.bin,MLO,boot.scr given on the TI site  to Sandisk 4GB SD card and tried to start the board . The output  was a red screen with android logo .

  I kept the board ON for 15-20 minutes still there was no change in the display(HDMI). 

II. I tried to recompile the kernel to generate a new uImage using following:

 

$ make ARCH=arm CROSS_COMPILE=arm-none-eabi-  distclean
  $ make ARCH=arm CROSS_COMPILE=arm-none-eabi- omap3_beagle_android_defconfig
  $ make ARCH=arm CROSS_COMPILE=arm-none-eabi-  uImage

the u-boot ,MLO and boot.scr file was the same. 
  
 when i tried to boot android with this new uImage,the display did not show anything.



 need  help  to resolve the above issue.

Regards
Prajith

 

 

  • 0
    TI__Expert 5400 points

    Hi Prajith,

    Did you thry with our pre-built image?

    Please provide kernel boot lags and output of logcat command so that we can debug this  issue.

     

    Thanks and Regards,

    Pankaj Bharadiya

  • 0 in reply to Pankaj Bharadiya
    Intellectual 310 points

    Hi pankaj

     

    Texas Instruments X-Loader 1.51 (Apr 21 2011 - 15:20:42)

    Unsupported Chip!

    Beagle unknown 0x02

    Starting X-loader on MMC

    Reading boot sector

     

    213412 Bytes Read from MMC

    Starting OS Bootloader from MMC...

    Starting OS Bootloader...

     

     

    U-Boot 2010.06 (Apr 21 2011 - 15:12:08)

     

    OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz

    OMAP3 Beagle board + LPDDR/NAND

    I2C: ready

    DRAM: 256 MiB

    NAND: HW ECC [Kernel/FS layout] selected

    0 MiB

    *** Warning - bad CRC or NAND, using default environment

     

    In: serial

    Out: serial

    Err: serial

    Beagle unknown 0x02

    Die ID #0f4000029ff80000015f26ad0f017027

    Hit any key to stop autoboot: 10 \0x08\0x08\0x08 9 \0x08\0x08\0x08 8 \0x08\0x08\0x08 7 \0x08\0x08\0x08 6 \0x08\0x08\0x08 5 \0x08\0x08\0x08 4 \0x08\0x08\0x08 3 \0x08\0x08\0x08 2 \0x08\0x08\0x08 1 \0x08\0x08\0x08 0

    mmc1 is available

    reading boot.scr

     

    415 bytes read

    Running bootscript from mmc ...

    ## Executing script at 82000000

    reading uImage

     

    2663420 bytes read

    ***** Kernel: /dev/mmcblk0p1/uImage *****

    ***** RootFS: /dev/mmcblk0p2 *****

    ## Booting kernel from Legacy Image at 80200000 ...

    Image Name: Linux-2.6.37-gd85ca21-dirty

    Image Type: ARM Linux Kernel Image (uncompressed)

    Data Size: 2663356 Bytes = 2.5 MiB

    Load Address: 80008000

    Entry Point: 80008000

    Verifying Checksum ... OK

    Loading Kernel Image ... OK

    OK

     

    Starting kernel ...

     

    Uncompressing Linux... done, booting the kernel.

     

     

    //boot arguments

    OMAP3 beagleboard.org # printenv

     

    bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else if run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run nandboot; fi

    bootdelay=10

    baudrate=115200

    loadaddr=0x82000000

    usbtty=cdc_acm

    console=ttyO2,115200n8

    mpurate=500

    vram=12M

    dvimode=1024x768MR-16@60

    defaultdisplay=dvi

    mmcroot=/dev/mmcblk0p2 rw

    mmcrootfstype=ext3 rootwait

    nandroot=/dev/mtdblock4 rw

    nandrootfstype=jffs2

    mmcargs=setenv bootargs console=${console} mpurate=${mpurate} vram=${vram} omapfb.mode=dvi:${dvimode} omapdss.def_disp=${defaultdisplay} root=${mmcroot} rootfstype=${mmcrootfstype}

    nandargs=setenv bootargs console=${console} mpurate=${mpurate} vram=${vram} omapfb.mode=dvi:${dvimode} omapdss.def_disp=${defaultdisplay} root=${nandroot} rootfstype=${nandrootfstype}

    loadbootscript=fatload mmc 0 ${loadaddr} boot.scr

    bootscript=echo Running bootscript from mmc ...; source ${loadaddr}

    loaduimage=fatload mmc 0 ${loadaddr} uImage

    mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}

    nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 280000 400000; bootm ${loadaddr}

    stdin=serial

    stdout=serial

    stderr=serial

    dieid#=0f4000029ff80000015f26ad0f017027

     

    Environment size: 1195/131068 bytes

     

     

    Regards

    Prajith

     

     

  • 0 in reply to Vishveshwar Bhat
    TI__Expert 5400 points

    Hi Prajith,

     

    Texas Instruments X-Loader 1.51 (Apr 21 2011 - 15:20:42)

    Unsupported Chip!

    Beagle unknown 0x02

    Starting X-loader on MMC

    Reading boot sector

     

    As you are getting Unspported Chip! in boot log, please make sure that you have following patches  on you x-loader, u-boot and kernel sources.

     

    xloader patch:

    https://gitorious.org/rowboat/x-loader/commit/2ea24cb536bdccd53e302610cda3f93c548b9270

     

    u-boot patch:

    https://gitorious.org/rowboat/u-boot/commit/24febf528e9e357f07a5221690e594af3921db53

     

    kernel patch:

    https://gitorious.org/rowboat/kernel/commit/1f91dcf4e93dba6755120b3666fb621c5788d91e

     

     

    Thanks and Regards,

    Pankaj Bharadiya

     

  • 0 in reply to Pankaj Bharadiya
    Intellectual 310 points

    Hi Pankaj

     

    I checked the x-loader, u- boot and kernel files.These patches are already present in the respective files.

     

     

    A. The error log - for the image files downloaded from the TI site.

         Texas Instruments X-Loader 1.51 (Jul 11 2011 - 21:11:32)
    Unsupported Chip!
    Beagle xM Rev C
    Starting X-loader on MMC 
    Reading boot sector
     
    213256 Bytes Read from MMC 
    Starting OS Bootloader from MMC...
    Starting OS Bootloader...
     
     
    U-Boot 2010.06 (Jul 08 2011 - 04:37:45)
     
    OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz
    OMAP3 Beagle board + LPDDR/NAND
    I2C:   ready
    DRAM:  384 MiB
    NAND:  HW ECC [Kernel/FS layout] selected
    0 MiB
    *** Warning - bad CRC or NAND, using default environment
     
    In:    serial
    Out:   serial
    Err:   serial
    Beagle xM Rev A/C
    Die ID #0f4000029ff80000015f26ad0f017027
    Hit any key to stop autoboot: 10  9  8  7  6  5  4  3  2  1  0 
    mmc1 is available
    reading boot.scr
     
    460 bytes read
    Running bootscript from mmc ...
    ## Executing script at 82000000
    reading uImage
     
    2745172 bytes read
    ***** Kernel: /dev/mmcblk0p1/uImage *****
    ***** RootFS: /dev/mmcblk0p2 *****
    ## Booting kernel from Legacy Image at 82000000 ...
       Image Name:   Linux-2.6.37-g06ebbba
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    2745108 Bytes = 2.6 MiB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
       Loading Kernel Image ... OK
    OK
     
    Starting kernel ...
     
    Uncompressing Linux... done, booting the kernel.
    Linux version 2.6.37-g06ebbba (a0131746@swubn01) (gcc version 4.4.3 (GCC) ) #1 Fri Jul 8 04:28:11 IST 2011
    CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    Machine: OMAP3 Beagle Board
    Reserving 8388608 bytes SDRAM for VRAM
    Memory policy: ECC disabled, Data cache writeback
    OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk )
    SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x10000
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 62976
    Kernel command line: console=ttyO2,115200n8 androidboot.console=ttyO2 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off omap_vout.vid1_static_vrfb_alloc=y vram=8M omapfb.vram=0:8M
    PID hash table entries: 1024 (order: 0, 4096 bytes)
    Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
    Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
    Memory: 248MB = 248MB total
    Memory: 245300k/245300k available, 16844k reserved, 0K highmem
    Virtual kernel memory layout:
        vector  : 0xffff0000 - 0xffff1000   (   4 kB)
        fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
        DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
        vmalloc : 0xd0800000 - 0xf8000000   ( 632 MB)
        lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
        modules : 0xbf000000 - 0xc0000000   (  16 MB)
          .init : 0xc0008000 - 0xc003b000   ( 204 kB)
          .text : 0xc003b000 - 0xc052f000   (5072 kB)
          .data : 0xc0530000 - 0xc0574940   ( 275 kB)
    NR_IRQS:409
    Clocking rate (Crystal/Core/MPU): 26.0/400/600 MHz
    Reprogramming SDRC clock to 400000000 Hz
    dpll3_m2_clk rate change failed: -22
    IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
    Total of 96 interrupts on 1 active controller
    GPMC revision 5.0
    Trying to install interrupt handler for IRQ402
    Trying to install interrupt handler for IRQ403
    Trying to install interrupt handler for IRQ404
    Trying to install interrupt handler for IRQ405
    Trying to install interrupt handler for IRQ406
    Trying to install interrupt handler for IRQ407
    Trying to install interrupt handler for IRQ408
    Trying to install type control for IRQ409
    Trying to set irq flags for IRQ409
    OMAP clockevent source: GPTIMER1 at 32768 Hz
    Console: colour dummy device 80x30
    Calibrating delay loop... 597.64 BogoMIPS (lpj=2334720)
    pid_max: default: 32768 minimum: 301
    Security Framework initialized
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    regulator: core version 0.5
    regulator: dummy: 
    NET: Registered protocol family 16
    OMAP GPIO hardware version 2.5
    OMAP GPIO hardware version 2.5
    OMAP GPIO hardware version 2.5
    OMAP GPIO hardware version 2.5
    OMAP GPIO hardware version 2.5
    OMAP GPIO hardware version 2.5
    omap_mux_init: Add partition: #1: core, flags: 0
    OMAP3 Beagle Rev: xM C
    Found NAND on CS0
    Registering NAND on CS0
    Unable to get DVI reset GPIO
    hw-breakpoint: debug architecture 0x4 unsupported.
    OMAP DMA hardware revision 5.0
    bio: create slab <bio-0> at 0
    SCSI subsystem initialized
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    omap_device: omap_i2c.1: new worst case activate latency 0: 30517
    omap_i2c omap_i2c.1: bus 1 rev4.0 at 2600 kHz
    twl4030: PIH (irq 7) chaining IRQs 368..375
    twl4030: power (irq 373) chaining IRQs 376..383
    twl4030: gpio (irq 368) chaining IRQs 384..401
    regulator: VUSB1V5: 1500 mV normal standby
    regulator: VUSB1V8: 1800 mV normal standby
    regulator: VUSB3V1: 3100 mV normal standby
    twl4030_usb twl4030_usb: Initialized TWL4030 USB module
    regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal standby
    regulator: VDAC: 1800 mV normal standby
    regulator: VDVI: 1800 mV normal standby
    regulator: VSIM: 1800 <--> 3000 mV at 1800 mV normal standby
    regulator: VAUX3: 1800 mV normal standby
    regulator: VAUX4: 1800 mV normal standby
    omap_device: omap_i2c.1: new worst case deactivate latency 0: 30517
    omap_i2c omap_i2c.2: bus 2 rev4.0 at 400 kHz
    omap_i2c omap_i2c.3: bus 3 rev4.0 at 100 kHz
    Advanced Linux Sound Architecture Driver Version 1.0.23.
    Switching to clocksource 32k_counter
    musb-hdrc: version 6.0, otg (peripheral+host), debug=0
    musb-hdrc musb-hdrc.0: dma type: dma-inventra
    musb-hdrc musb-hdrc.0: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
    NET: Registered protocol family 2
    IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
    TCP established hash table entries: 8192 (order: 4, 65536 bytes)
    TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
    TCP: Hash tables configured (established 8192 bind 8192)
    TCP reno registered
    UDP hash table entries: 256 (order: 0, 4096 bytes)
    UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
    NET: Registered protocol family 1
    NetWinder Floating Point Emulator V0.97 (double precision)
    omap-iommu omap-iommu.0: isp registered
    AM37x/DM37x  Linux PSP version 04.02.00.07 (OMAP3BEAGLE)
    ashmem: initialized
    VFS: Disk quotas dquot_6.5.2
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
    msgmni has been set to 479
    io scheduler noop registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    OMAP DSS rev 2.0
    OMAP DISPC rev 3.0
    OMAP VENC rev 2
    OMAP DSI rev 1.0
    Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
    omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 72) is a OMAP UART0
    omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 73) is a OMAP UART1
    omap_uart.2: ttyO2 at MMIO 0x49020000 (irq = 74) is a OMAP UART2
    console [ttyO2] enabled
    omap_uart.3: ttyO3 at MMIO 0x49042000 (irq = 80) is a OMAP UART3
    brd: module loaded
    loop: module loaded
    mtdoops: mtd device (mtddev=name/number) must be supplied
    omap2-nand driver initializing
    No NAND device found.
    No NAND device found.
    OneNAND driver initializing
    usbcore: registered new interface driver asix
    usbcore: registered new interface driver cdc_ether
    usbcore: registered new interface driver smsc95xx
    usbcore: registered new interface driver net1080
    usbcore: registered new interface driver cdc_subset
    usbcore: registered new interface driver zaurus
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ehci-omap.0 supply hsusb0 not found, using dummy regulator
    ehci-omap.0 supply hsusb1 not found, using dummy regulator
    ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
    ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
    ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
    ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
    usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    usb usb1: Product: OMAP-EHCI Host Controller
    usb usb1: Manufacturer: Linux 2.6.37-g06ebbba ehci_hcd
    usb usb1: SerialNumber: ehci-omap.0
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 3 ports detected
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    android init
    android_probe pdata: c053ff2c
    android_bind
    android_usb gadget: android_usb ready
    musb-hdrc musb-hdrc.0: MUSB HDRC host driver
    musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 2
    usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
    usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    usb usb2: Product: MUSB HDRC host driver
    usb usb2: Manufacturer: Linux 2.6.37-g06ebbba musb-hcd
    usb usb2: SerialNumber: musb-hdrc.0
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 1 port detected
    f_adb init
    android_register_function adb
    adb_bind_config
    f_mass_storage init
    android_register_function usb_mass_storage
    mice: PS/2 mouse device common for all mice
    input: gpio-keys as /devices/platform/gpio-keys/input/input0
    input: twl4030_pwrbutton as /devices/platform/omap/omap_i2c.1/i2c-1/1-0049/twl4030_pwrbutton/input/input1
    using rtc device, twl_rtc, for alarms
    twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
    twl_rtc twl_rtc: Power up reset detected.
    twl_rtc twl_rtc: Enabling TWL-RTC.
    i2c /dev entries driver
    Linux media interface: v0.10
    Linux video capture interface: v2.00
    omap3isp supply VDD_CSIPHY1 not found, using dummy regulator
    omap3isp supply VDD_CSIPHY2 not found, using dummy regulator
    omap3isp omap3isp: Revision 15.0 found
    omap-iommu omap-iommu.0: isp: version 1.1
    mt9v113 2-003c: chip id mismatch read 0x0, expecting 0x2280
    isp_register_subdev_group: Unable to register subdev mt9v113
    omap_device: omap_wdt.-1: new worst case activate latency 0: 30517
    OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
    twl4030_wdt twl4030_wdt: Failed to register misc device
    twl4030_wdt: probe of twl4030_wdt failed with error -16
    device-mapper: uevent: version 1.0.3
    device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    logger: created 64K log 'log_main'
    logger: created 256K log 'log_events'
    logger: created 64K log 'log_radio'
    logger: created 64K log 'log_system'
    usbcore: registered new interface driver snd-usb-audio
    OMAP3 Beagle/Devkit8000 SoC init
    usb 1-2: new high speed USB device using ehci-omap and address 2
    asoc: twl4030-hifi <-> omap-mcbsp-dai.1 mapping ok
    ALSA device list:
      #0: omap3beagle
    oprofile: hardware counters not available
    oprofile: using timer interrupt.
    TCP cubic registered
    Initializing XFRM netlink socket
    NET: Registered protocol family 17
    NET: Registered protocol family 15
    Registering the dns_resolver key type
    VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
    ThumbEE CPU extension supported.
    Power Management for TI OMAP3.
    smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
    smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
    SmartReflex Class3 initialized
    clock: disabling unused clocks to save power
    platform mpu.0: omap_voltage_scale: Already at the requestedrate 600000000
    usb 1-2: New USB device found, idVendor=0424, idProduct=9514
    usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    hub 1-2:1.0: USB hub found
    hub 1-2:1.0: 5 ports detected
    regulator_init_complete: incomplete constraints, leaving VDAC on
    twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
    omap_vout omap_vout: Buffer Size = 3686400
    omap_vout omap_vout: : registered and initialized video device 15
    omap_vout omap_vout: Buffer Size = 3686400
    omap_vout omap_vout: : registered and initialized video device 16
    Waiting 1sec before mounting root device...
    mmc0: host does not support reading read-only switch. assuming write-enable.
    mmc0: new SDHC card at address e624
    mmcblk0: mmc0:e624 SU04G 3.69 GiB 
     mmcblk0: p1 p2 p3
    usb 1-2.1: new high speed USB device using ehci-omap and address 3
    usb 1-2.1: New USB device found, idVendor=0424, idProduct=ec00
    usb 1-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    smsc95xx v1.0.4
    smsc95xx 1-2.1:1.0: usb0: register 'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet, c6:05:24:1d:1e:a1
    EXT3-fs: barriers not enabled
    kjournald starting.  Commit interval 5 seconds
    EXT3-fs (mmcblk0p2): using internal journal
    EXT3-fs (mmcblk0p2): 1 truncate cleaned up
    EXT3-fs (mmcblk0p2): recovery complete
    EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
    VFS: Mounted root (ext3 filesystem) on device 179:2.
    Freeing init memory: 204K
    init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
    init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
    enabling adb
    adb_open
    # pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    warning: `zygote' uses 32-bit capabilities (legacy support in use)
    request_suspend_state: wakeup (3->0) at 16000793460 (2000-01-01 00:00:12.407012940 UTC)
    init: untracked pid 969 exited
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    request_suspend_state: wakeup (0->0) at 21239898684 (2000-01-01 00:00:17.646148682 UTC)
    init: untracked pid 1042 exited
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    request_suspend_state: wakeup (0->0) at 26492584231 (2000-01-01 00:00:22.898834229 UTC)
    init: untracked pid 1067 exited
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    request_suspend_state: wakeup (0->0) at 31761444094 (2000-01-01 00:00:28.167694092 UTC)
    init: untracked pid 1092 exited
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    request_suspend_state: wakeup (0->0) at 37013885500 (2000-01-01 00:00:33.420135498 UTC)
    init: untracked pid 1117 exited
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    request_suspend_state: wakeup (0->0) at 42321044924 (2000-01-01 00:00:38.727294922 UTC)
    init: untracked pid 1144 exited
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    request_suspend_state: wakeup (0->0) at 47579589846 (2000-01-01 00:00:43.985809327 UTC)
    init: untracked pid 1174 exited
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    request_suspend_state: wakeup (0->0) at 52835388186 (2000-01-01 00:00:49.241638184 UTC)
    init: untracked pid 1199 exited
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    request_suspend_state: wakeup (0->0) at 58098114017 (2000-01-01 00:00:54.504364015 UTC)
    init: untracked pid 1224 exited
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    request_suspend_state: wakeup (0->0) at 63317871096 (2000-01-01 00:00:59.724121094 UTC)
    init: untracked pid 1249 exited
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    request_suspend_state: wakeup (0->0) at 68573242191 (2000-01-01 00:01:04.979492189 UTC)
    init: untracked pid 1274 exited
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb: disagrees about version of symbol module_layout
    request_suspend_state: wakeup (0->0) at 73833374026 (2000-01-01 00:01:10.239624024 UTC)
    init: untracked pid 1299 exited
    pvrsrvkm: disagrees about version of symbol module_layout
    omaplfb:

     

     

    B. error log - x-loader,MLO and image files compiled by me

    Texas Instruments X-Loader 1.51 (Jul 11 2011 - 21:11:32)
    Unsupported Chip!
    Beagle xM Rev C
    Starting X-loader on MMC 
    Reading boot sector
     
    213256 Bytes Read from MMC 
    Starting OS Bootloader from MMC...
    Starting OS Bootloader...
     
     
    U-Boot 2010.06 (Jul 08 2011 - 04:37:45)
     
    OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz
    OMAP3 Beagle board + LPDDR/NAND
    I2C:   ready
    DRAM:  384 MiB
    NAND:  HW ECC [Kernel/FS layout] selected
    0 MiB
    *** Warning - bad CRC or NAND, using default environment
     
    In:    serial
    Out:   serial
    Err:   serial
    Beagle xM Rev A/C
    Die ID #0f4000029ff80000015f26ad0f017027
    Hit any key to stop autoboot: 10  9  8  7  6  5  4  3  2  1  0 
    mmc1 is available
    reading boot.scr
     
    460 bytes read
    Running bootscript from mmc ...
    ## Executing script at 82000000
    reading uImage
     
    2663472 bytes read
    ***** Kernel: /dev/mmcblk0p1/uImage *****
    ***** RootFS: /dev/mmcblk0p2 *****
    ## Booting kernel from Legacy Image at 82000000 ...
       Image Name:   Linux-2.6.37-gd85ca21-dirty
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    2663408 Bytes = 2.5 MiB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
       Loading Kernel Image ... OK
    OK
     
    Starting kernel ...
     
    Uncompressing Linux... done, booting the kernel.

     

     

  • 0 in reply to PRAJITH WARRIER80347
    TI__Expert 5400 points

    Hi Ranjith,

    A.

    I think your SD card is not populated properly with pre-built images.

    Please refer to procedure mentioned in below user guide for creating a bootable SD card.

    http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_UserGuide#Out_of_the_Box_Demo

     

    B.

    Which boot arguments are your using?

    Please refer to bootargs metioned in below link and try.

    http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_UserGuide#Boot_arguments

     

    Thanks and Regards,

    Pankaj Bharadiya

     

  • 0 in reply to PRAJITH WARRIER80347
    TI__Genius 10210 points

    Make sure that you are building the kernel uImage using the correct defconfig and the sources are cleaned before building.

    $ cd rowboat/kernel
    $ make ARCH=arm distclean
    $ make ARCH=arm omap3_beagle_android_defconfig
    $ make ARCH=arm CROSS_COMPILE=arm-eabi- uImage

  • 0 in reply to Vishveshwar Bhat
    Intellectual 310 points

     

     

     

     

    Hi

     

    now the board is working with the pre-built images given by TI. After mounting the RootFs again properly,it worked.

     

    But problem B still remains i.e the uImage generated by me is not working.

     

    i used the following bootargs given in TI wiki link

    setenv bootargs 'console=ttyO2,115200n8 androidboot.console=ttyO2 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off omap_vout.vid1_static_vrfb_alloc=y vram=8M omapfb.vram=0:8M'

     

     

    Also i am building the kernel uImage using following

     

    $ make ARCH=arm CROSS_COMPILE=arm-none-eabi     distclean
    $ make ARCH=arm     CROSS_COMPILE=arm-none-eabi     omap3_beagle_android_defconfig
    $ make ARCH=arm     CROSS_COMPILE=arm-none-eabi     uImage

     

    Regards

    Prajith


  • 0 in reply to PRAJITH WARRIER80347
    TI__Genius 10210 points

    Not sure why the sources compiled by you appears to not boot, unlike the prebuilt one. Ensure that you have the correct sources.

    Could you give the full logs when executing the following commands:

    $ cd rowboat/kernel
    $ git status
    $ git log --oneline -10
    $ make ARCH=arm distclean
    $ make ARCH=arm omap3_beagle_android_defconfig
    $ make CROSS_COMPILE=arm-eabi- uImage

     

    Also, any specific reason you are using a different toolchain than the one recommended in TI Android DevKit?

  • 0 in reply to PRAJITH WARRIER80347
    TI__Expert 5400 points

    Hi Prajith,

    I think you are using wrong compiler (arm-none-eabi) in make command.

    $ make ARCH=arm CROSS_COMPILE=arm-none-eabi  distclean
    $ make ARCH=arm     CROSS_COMPILE=arm-none-eabi  omap3_beagle_android_defconfig
    $ make ARCH=arm     CROSS_COMPILE=arm-none-eabi  uImage

    Please follow steps mentioned in Developer guide and compile source with CROSS_COMPILE=arm-eabi- .

    http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_DeveloperGuide#Tool_chain_setup

    Thanks and Regards,

    Pankaj Bharadiya

  • 0 in reply to Pankaj Bharadiya
    Intellectual 310 points

    Hi Pankaj,

    thanks.

    I used arm-eabi-  compiler and it worked.

     

    I have a doubt?

    Is it that arm-none-eabi does not support BeagleBoard. actually i had downloaded codesourcery tools "arm-2011.03-42-arm-none-eabi.bin"  for the build environment of the kernel.

    I will be very thankful if u can tell me the diff  between 'arm-none-eabi' and 'arm-eabi-' compiler.

     

    Thanks and Regards

    Prajith Warrier

     

  • 0 in reply to PRAJITH WARRIER80347
    TI__Genius 10210 points

    PRAJITH WARRIER80347 said:

    I will be very thankful if u can tell me the diff  between 'arm-none-eabi' and 'arm-eabi-' compiler.

    'arm-eabi-' compiler is built and supplied by Google for Android development. It is supplied with the Android sources. The equivalent toolchain from codesourcery for kernel compilation is 'arm-none-linux-gnueabi-'.

    As per my knowledge, 'arm-none-eabi-' is meant for 'bare' ARM compilation (Non-linux system - e.g running C code directly on ARM)