Beagleboard-xM rev. C Android pre-built image from TI Froyo 2.2 devkit does not work

Hi Jiming,

First I would recommend to test with DVI screen.

We will get back with test result on 720p.

Note : We have not tested prebuilt images with Beagleboard-XM rev C. It have been tested with rev A1/A2.

BR,

satish

Hi Satish,

I am currently using a ASUS LED monitor with DVI/PC/HDMI inputs and it should sync with both VGA and 720HD modes. Like I said before, I did see a Android desktop eventually but it was just not the way I saw on one of rev. B board and both mouse and keyboard are not functional. Please let me know after we verify the prebuilt image with rev. C. BTW, the sd card that comes with my xM rev. C is a Angstrom image (I believe) and it is working fine with everything. Any idea where I can find the source code of that image and work on it before Android issues are fixed ? Thanks in advance for your help and information.

Thanks,

Jiming

Hi Jiming,

You can find froyo 2.2. source code at:

http://code.google.com/p/rowboat/wiki/Source

Use Manifest : TI-Android-FroYo-DevKit-V2.2.0.0.xml

http://processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide

Also, to get gingerbread source follow link at

http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3-DevKit-1.0_UserGuide

I hope this will help you out.

BR,

satish

Hi Satish,

I am actually using Froyo 2.2 you listed above and went through the whole process in user guide to build an UImage for beagleboard xM but the result is same as the one I described in my first post. Any idea when TI will support xM rev. C HW in their 2.2 Froyou Devkit ?

Thanks,

Jiming

Hi Jiming,

1. You need to build roofs - File system also and give a try.

2. Also you can try with prebuilt images available at below link. I should work.

Froyo prebuilt images:

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_02_00/index_FDS.html

Images  : http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_02_00/exports/beagleboard-xm.tar.gz

Gingerbread prebuilt images:

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

(http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/TI_Android_GingerBread_2_3_DevKit_1_0/exports/beagleboard-xm.tar.gz)

3. Currently we do not have h/w mentioned by you. However we are open to test the same if it is available to us.

Kindly revert back if you still face problem.

xM revC is not supported in rowboat yet.

http://code.google.com/p/rowboat/issues/detail?id=100 - this is a patch to kernel to support the USB on revC. I did not try it though.

HI Satish,

It's probably easier to show you what happened after I use the pre-built image from Froyo and Gingerbread devkit.

First image below is the starting screen snapshot when I used both Froyo and Gingerbread pre-built image from TI. The second image is what I got after I waited a long time.

Thanks,

Jiming

Hi Jiming,

I think we would need log details to analyze the issue further.

Could you enable log level to 8 in init.rc ? Also send us logcat output while booting..

It will help to dig further

BR,

satish

Jiming Wang said:

Hi,

 

I just received Beagleboard-xM rev. C from digi-key a couple of weeks ago and after following the user guide to prepare an Android image on my Sony MicroSD card, I noticed the first screen is already wrong with RED background and out of sync robot images, and then the second screen and font size of "ANDROID" is wrong (too big) and background is RED again which is wrong (should be black). After more than or around ten minutes the android is up but it looks like 640x480 and out-of-sync too. On top of that, both mouse and keyboard are not functional neither. I have friend who is using xM rev B. and we found out the RED background does not appear on rev. B but the first screen still have out-of-sync robots. I used to be a graphic driver developer and my feeling of the screen is the image thats comes with TI devkit is not for HD (1280x720) and for some reason it is using a lower resolution on HDMI output. I am new to Linux/Android world, so any help and comment is appreciated.

 

Thanks,

Jiming

Everything that Jiming tells is also happened to me (xM version C). I'm currently looking for solutions at least to fix usb problem.  

Booting logs is here http://paste.pocoo.org/show/401496/,

I'm currently trying this solution right now: http://code.google.com/p/rowboat/issues/detail?id=100

Thx,

Alper

Hi Alper,

I actually worked with Robert (from Digikey Tech. support) to try the patch he created but the result is the same. I already sent a log file to Robert per his request.

Thanks,

Jiming

jiming,

Robert share me working image which fixes usb and screen problem. But that image also has problem it is extreamly slow. He is now working with new kernel for gingerbread.

Hi,

Because the new board  version is not recongized correctly, so the pad mux configuration is not done correctly.

What you need to do to fix it is patch the u-boot source code to make correct pad mux configuration, I have tried to do that and make board works well.

Good Luck.

Hi David,

I'm also facing the same problem with Mouse and Keyboard detection on Beagleboard xM -C board with Ginger bread image. Can you please let me know what are the changes you made it to work.

I'm trying with prebuild image from TI.

BR,

Sreedhar.

Hi, Sreedhar

The usb bus power is inverted so the old detection won't work.

You need to modify the kernel source board-omap3beagle.c to make the usb bus power correct. Of coure you should follow what I saied in my last post before modify the kernel source code.


BR,

David

Hi David,

Any chance you can attach the change you have done in your next reply

Thanks,

Jiming

Also recommend to post the patches/code to the rowboat project forum at http://groups.google.com/group/rowboat

Once the code is accepted into rowboat, it will be available in future TI Android DevKit releases

Hi, All

Recently, I am a little busy, so miss posts here.

As people here need it, I will post the files and modifications here.

Well, the following is the files modified to support BB-xM Rev C.

1. X-loader

Check REVISION_XMC used in the following file.

7345.omap3beagle.c.txt

2. u-boot

1. beagle.h

/* BeagleBoard revisions */
#define REVISION_AXBX    0x7
#define REVISION_CX        0x6
#define REVISION_C4        0x5
#define REVISION_XM        0x0
#define REVISION_XMC    0x02

Add the REVISION_XMC definition

2.  beagle.c

      modify in the misc_init_r function,  add case REVISION_XMC below REVISION_XM to configuration correct pinmux registers.

    case REVISION_XM:
    case REVISION_XMC:
        printf("Beagle xM Rev A/C\n");
        MUX_BEAGLE_XM();
        /* Set VAUX2 to 1.8V for EHCI PHY */
        twl4030_pmrecv_vsel_cfg(TWL4030_PM_RECEIVER_VAUX2_DEDICATED,
                    TWL4030_PM_RECEIVER_VAUX2_VSEL_18,
                    TWL4030_PM_RECEIVER_VAUX2_DEV_GRP,
                    TWL4030_PM_RECEIVER_DEV_GRP_P1);
        setenv("mpurate", "1000");

       break;

3. Kernel

board-omap3beagle.c

in function static int beagle_twl_gpio_setup(struct device *dev, unsigned gpio, unsigned ngpio)

modify the red part

        /* TWL4030_GPIO_MAX + 0 == ledA, EHCI nEN_USB_PWR (out, active low) */
        gpio_request(gpio + TWL4030_GPIO_MAX, "nEN_USB_PWR");
//        gpio_direction_output(gpio + TWL4030_GPIO_MAX, 1);

         gpio_direction_output(gpio + TWL4030_GPIO_MAX, 0);

Then rebuild x-loader uboot and kernel, you can boot the system with right DVI color and USB working well.

Good Luck.

David

Hi all,

   I applied the patches, and now the USB and DVI video output works well. The problem is that disk I/O is extremely slow. I tried to put root fs into the SD card and USB key, but the behaviour is the same.

Any news?

Thank you

Regards,

Riccardo

Dear Riccardo,

Sorry it's taken so long to get a reply to you. I can confirm that the new version of TI Gingerbread release (2.3.4) available: 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

works great "out of the box" on the Beagleboard-xm Rev C (no Red colour, working USB and DVI). Unless you have a specific reason for staying on the older version I do recommend you use this release.

I hope this solves the problem.

All the best,

Toby

Hi Toby,

I have no reason to stay on older version. I'll try the new versione today.

Thank you for the support.

Best regards

Riccardo

Hello All,

Has anyone found a resolution to this problem.  I just got a Beagleboard XM and I am having the same problems: no USB mouse or USB keyboard as well as red on the screen where another color should be.  I have tried two of the prebuilt binaries with the same result: TI Android Froyo Dev kit v2.2 and TI-Android-GingerBread-2.3.4-DevKit-2.1. 

I am new to this platform and I really wanted to start with something working out of the box before starting my own development.  I work in industrial automation I would like to evaluate some next generation concepts with the OMAP processor.

Geoff

Hi Geoff,

Please provide complete boot log so that we  can look into this issue.

If  you are getting log like

Unsupported Chip!

Beagle unknown 0x02

Starting X-loader on MMC

Reading boot sector

then please apply following patches, build source and try booting again.

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

Regards,

Pankaj Bharadiya

Hi Pankaj,

Wow!  Thanks for the quick reply on a Sunday.  I really appreciate your suggestions.  I will work on this next week and let you know how things go.  I will also send you a copy of the log. I dont have the TI development tools yet to do a build.  I still need to download this, and get up to speed. 

Geoff

Hi Pankaj,

Here's the boot log below.  It seems like I have the issues you discussed above, so I will apply the patches you recomended and try again.

Thanks

Geoff

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 #596c00029ff80000016830c405012012
Hit any key to stop autoboot: 10  9  8  7  6  5  4  3  2  1  0
mmc1 is available
reading boot.scr

415 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
reading uImage

2607268 bytes read
***** Kernel: /dev/mmcblk0p1/uImage *****
***** RootFS: /dev/mmcblk0p2 *****
## Booting kernel from Legacy Image at 80200000 ...
   Image Name:   Linux-2.6.32
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2607204 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.
Linux version 2.6.32 (a0393957@swubn01) (gcc version 4.4.3 (GCC) ) #1 Fri Apr 15 09:51:47 IST 2011
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board"capture to file"
Memory policy: ECC disabled, Data cache writeback
OMAP3630/DM3730 ES1.0 (l2cache iva sgx neon isp 192mhz_clk )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Reserving 4194304 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS2,115200n8 androidboot.console=ttyS2 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off mpurate=800 omap_vout.vid1_static_vrfb_alloc=y
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: 256MB = 256MB total
Memory: 249856KB available (4532K code, 825K data, 172K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/400/600 MHz
Reprogramming SDRC clock to 400000000 Hz
dpll3_m2_clk rate change failed: -22
GPMC revision 5.0
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP GPIO hardware version 2.5
OMAP clockevent source: GPTIMER12 at 32768 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 511.52 BogoMIPS (lpj=1998848)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
Unable to get DVI reset GPIO
Target VDD1 OPP = 3, VDD2 OPP = 2
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
i2c_omap i2c_omap.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 normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VPLL2: 1800 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV normal standby
regulator: VAUX3: 1800 mV normal standby
regulator: VAUX4: 1800 mV normal standby
i2c_omap i2c_omap.2: bus 2 rev4.0 at 400 kHz
i2c_omap i2c_omap.3: bus 3 rev4.0 at 100 kHz
Switching to clocksource 32k_counter
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: 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
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
omap-iommu omap-iommu.0: isp registered
NetWinder Floating Point Emulator V0.97 (double precision)
ashmem: initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
yaffs Apr 15 2011 09:51:38 Installing.
msgmni has been set to 488
alg: No test for stdrng (krng)
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
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver cdc_eem
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver smsc95xx
usbcore: registered new interface driver gl620a
usbcore: registered new interface driver net1080
usbcore: registered new interface driver plusb
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbcore: registered new interface driver MOSCHIP usb-ethernet driver
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
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
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: c04c953c
android_bind
android_usb gadget: android_usb ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
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
i2c /dev entries driver
Linux video capture interface: v2.00
mt9v113 2-003c: Registered to v4l2 master omap34xxcam!!
omap-iommu omap-iommu.0: isp: version 1.1
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
mmci-omap-hs mmci-omap-hs.1: err -16 configuring card detect
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 "capture to file" log 'log_radio'
logger: created 64K log 'log_system'
Advanced Linux Sound Architecture Driver Version 1.0.21.
usbcore: registered new interface driver snd-usb-audio
No device for DAI omap-mcbsp-dai-0
No device for DAI omap-mcbsp-dai-1
No device for DAI omap-mcbsp-dai-2
No device for DAI omap-mcbsp-dai-3
No device for DAI omap-mcbsp-dai-4
OMAP3 Beagle SoC init
asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok
ALSA device list:
  #0: omap3beagle (twl4030)
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Power Management for TI OMAP3.
Unable to set L3 frequency (400000000)
Switched to new clocking rate (Crystal/Core/MPU): 26.0/400/800 MHz
IVA2 clocking rate: 660 MHz
SmartReflex driver initialized
omap3beaglelmb: Driver registration complete
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omapdss DPI: Could not find exact pixel clock. Requested 23500 kHz, got 24000 kHz
regulator_init_complete: incomplete constraints, leaving VAUX3 on
regulator_init_complete: incomplete constraints, leaving VDVI on
regulator_init_complete: incomplete constraints, leaving VDAC on
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
mt9v113 2-003c: chip id mismatch read 0x0,                 expecting 0x2280
mt9v113 2-003c: Unable to detect decoder
mt9v113 2-003c: chip id mismatch read 0x0,                 expecting 0x2280
mt9v113 2-003c: Unable to detect decoder
mt9v113 2-003c: chip id mismatch read 0x0,                 expecting 0x2280
mt9v113 2-003c: Unable to detect decoder
mt9v113 2-003c: chip id mismatch read 0x0,                 expecting 0x2280
mt9v113 2-003c: Unable to detect decoder
omapdss DPI error: display already enabled
omap_vout omap_vout: 'dvi' Display already enabled
omapdss DPI error: display already enabled
omap_vout omap_vout: 'dvi' Display already enabled
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 0
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 1
Waiting 1sec before mounting root device...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.67 GiB
 mmcblk0: p1 p2 p3
List of all partitions:
b300         3858432 mmcblk0 driver: mmcblk
  b301           72261 mmcblk0p1
  b302         1927800 mmcblk0p2
  b303         1855507 mmcblk0p3
No filesystem could mount root, tried:  ext3
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)

Your logs seem to suggest that you are using kernel 2.6.32 and the corresponding x-loader and u-boot. We currently have only 2.6.37 kernel and corresponding x-loader/u-boot with xm rev C support.

The sources with beagle xM rev C support builtin is available for download at the link below. There is also a prebuilt gingerbread image available for you to try.

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

Ok great, that fixed it.  The pre-built image is running fine on the board.  

Now I have another problem trying to setup "TI Android GingerBread 2.3.4 DevKit 2.1 Developer"  I followed the instructions according to "TI Android GingerBread 2.3.4 DevKit 2.1 Developer Guide"  but when I go to do the make according to the instructions there is no result.  I first modified the instructions for the omap3evm and substituted omap3beagle for omap3evm because I am using the Beagleboard xM.  This did not work, so I tried to do a make according to the intructions and here is the result I got at the command line:

golson@ubuntu:~/rowboat-android/TI_Android_GingerBread_2_3_4Sources/x-loader$ make CROSS_COMPILE=arm-eabi- distclean
find . -type f \
        \( -name 'core' -o -name '*.bak' -o -name '*~' \
        -o -name '*.o'  -o -name '*.a'  \) -print \
        | xargs rm -f
find . -type f \
        \( -name .depend -o -name '*.srec' -o -name '*.bin' \) \
        -print \
        | xargs rm -f
rm -f  *.bak tags TAGS
rm -fr *.*~
rm -f x-load x-load.map 
rm -f include/asm/proc include/asm/arch
rm -f include/config.h include/config.mk
golson@ubuntu:~/rowboat-android/TI_Android_GingerBread_2_3_4Sources/x-loader$ make CROSS_COMPILE=arm-eabi- omap3evm_config
rm -f include/config.h include/config.mk
Configuring for omap3evm board...
golson@ubuntu:~/rowboat-android/TI_Android_GingerBread_2_3_4Sources/x-loader$ make CROSS_COMPILE=arm-eabi-
make: arm-eabi-gcc: Command not found
arm-eabi-gcc -Wa,-gstabs -D__ASSEMBLY__  -Os  -fno-strict-aliasing  -fno-common -ffixed-r8  -DONE_BIT_ERROR_CORRECT -D__KERNEL__ -DTEXT_BASE=0x40200800 -I/home/golson/rowboat-android/TI_Android_GingerBread_2_3_4Sources/x-loader/include -fno-builtin -ffreestanding -nostdinc -isystem  -pipe  -DCONFIG_ARM -D__ARM__ -march=armv7-a -mabi=apcs-gnu  -c -o cpu/omap3/start.o /home/golson/rowboat-android/TI_Android_GingerBread_2_3_4Sources/x-loader/cpu/omap3/start.S
make: arm-eabi-gcc: Command not found
make: *** [cpu/omap3/start.o] Error 127

Your PATH may not be set correctly. Please follow the instructions in the link to set the path for the toolchain:

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

Hello Vishveshwar,

Wow, I have spent so many hours trying to get this work.  I am not sure what is wrong.  here is where I am at:

1. I couldn't Download the Repo script using this command line: curl https://android.git.kernel.org/repo > ~/bin/repo. I read on the Internet that the site is down, so I found another source for this file, and I downloaded, install and synced according to the instructions. It seems like it is working, but I don't have experience with this.

2. I down-loaded the pre-packaged repo and installed it according to the instructions. This seemed to work ok. However, using this method puts the tool chain at a different path than the alternative, because it adds this directory to the path: TI_Android_GingerBread_2_3_4Sources. I don't understand this.

3. I tried setting the path to the correct location of the tool chain, but this did not work.

4. Then I tried moving all the files to the location they would be in if they were install the alternate way, and setting the tool chain path there, but this still didn't work.

5. The instructions say to set the PATH variable to a relative path at PATH=rowboat-android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin. However this is relative to a path one level above the x-load directory where I run the make command. I am not sure if this makes a difference. Maybe the script moves the current directory up before referencing the tool path file.

6. I tried adding the absolute path of the tool chain to the PATH variable, but still no luck.

Here is some command-line info:

Here is a listing of the Tool chain directory

golson@ubuntu:~/rowboat-android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin$ dir
arm-eabi-addr2line  arm-eabi-cpp    arm-eabi-gcov     arm-eabi-ld.bfd   arm-eabi-ranlib   arm-eabi-strip
arm-eabi-ar        arm-eabi-g++    arm-eabi-gdb     arm-eabi-ld.gold  arm-eabi-readelf
arm-eabi-as        arm-eabi-gcc    arm-eabi-gdbtui  arm-eabi-nm       arm-eabi-run
arm-eabi-c++        arm-eabi-gcc-4.4.3    arm-eabi-gprof     arm-eabi-objcopy  arm-eabi-size
arm-eabi-c++filt    arm-eabi-gccbug    arm-eabi-ld     arm-eabi-objdump  arm-eabi-strings

Setting the PATH variable to the tool chain:

golson@ubuntu:~$ export PATH=rowboat-android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH

Running Make commands

golson@ubuntu:~/rowboat-android/x-loader$ make CROSS_COMPILE=arm-eabi- distclean
make: arm-eabi-gcc: Command not found
find . -type f \
        \( -name 'core' -o -name '*.bak' -o -name '*~' \
        -o -name '*.o'  -o -name '*.a'  \) -print \
        | xargs rm -f
find . -type f \
        \( -name .depend -o -name '*.srec' -o -name '*.bin' \) \
        -print \
        | xargs rm -f
rm -f cpu/omap3/start.o *.bak tags TAGS
rm -fr *.*~
rm -f x-load x-load.map x-load.bin System.map
rm -f include/asm/proc include/asm/arch
rm -f include/config.h include/config.mk
golson@ubuntu:~/rowboat-android/x-loader$ make CROSS_COMPILE=arm-eabi- omap3evm_config
rm -f include/config.h include/config.mk
Configuring for omap3evm board...
Removing folder include/asm/arch
making links between files  arch-omap3 asm/arch
done making links
ARCH  = arm
CPU   = omap3
BOARD = omap3evm
golson@ubuntu:~/rowboat-android/x-loader$ make CROSS_COMPILE=arm-eabi-
make: arm-eabi-gcc: Command not found
arm-eabi-gcc -Wa,-gstabs -D__ASSEMBLY__  -Os  -fno-strict-aliasing  -fno-common -ffixed-r8  -DONE_BIT_ERROR_CORRECT -D__KERNEL__ -DTEXT_BASE=0x40200800 -I/home/golson/rowboat-android/x-loader/include -fno-builtin -ffreestanding -nostdinc -isystem  -pipe  -DCONFIG_ARM -D__ARM__ -march=armv7-a -mabi=apcs-gnu  -c -o cpu/omap3/start.o /home/golson/rowboat-android/x-loader/cpu/omap3/start.S
make: arm-eabi-gcc: Command not found
make: *** [cpu/omap3/start.o] Error 127
golson@ubuntu:~/rowboat-android/x-loader$ cd ..
golson@ubuntu:~/rowboat-android$ prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin
bash: prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin: Is a directory

Apologies for that confusion about setting the PATH correctly.

You downloaded  the toolchain to the following path:
~/rowboat-android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin

Therefore, your PATH is to be modified to:
$ PATH="$HOME/rowboat-android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH"

Basically rowboat-android corresponds to the full absolute path to the top of android sources.
We will update the wiki page to make this more clearer.

Hi Vishveshwar Bhat,

I am not building using Froyo build, but I am building it using the TI 2.3.4 and following the Developers Guide; my machine is Linux 32-Bit but supposedly this shouldn't hold me back from building the pre-packaged repo. But I have been getting the similar error to the previous poster in this thread.

I have modified my PATH to be following:

export PATH="$HOME/rowboat-android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH"

But I still got the following error after "make CROSS_COMPILE=arm-eabi-"

stjo005@stjo005-laptop:~/rowboat-android/TI_Android_GingerBread_2_3_4Sources/x-loader$ make CROSS_COMPILE=arm-eabi-
make: arm-eabi-gcc: Command not found
arm-eabi-gcc -Wa,-gstabs -D__ASSEMBLY__ -Os -fno-strict-aliasing -fno-common -ffixed-r8 -DONE_BIT_ERROR_CORRECT -D__KERNEL__ -DTEXT_BASE=0x40200800 -I/home/stjo005/rowboat-android/TI_Android_GingerBread_2_3_4Sources/x-loader/include -fno-builtin -ffreestanding -nostdinc -isystem -pipe -DCONFIG_ARM -D__ARM__ -march=armv7-a -mabi=apcs-gnu -c -o cpu/omap3/start.o /home/stjo005/rowboat-android/TI_Android_GingerBread_2_3_4Sources/x-loader/cpu/omap3/start.S
make: arm-eabi-gcc: Command not found
make: *** [cpu/omap3/start.o] Error 127

Am i missing something?

Below is what I did:

stjo005@stjo005-laptop:~/rowboat-android/TI_Android_GingerBread_2_3_4Sources$ export PATH="$HOME/rowboat-android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH"

stjo005@stjo005-laptop:~/rowboat-android/TI_Android_GingerBread_2_3_4Sources$ cd x-loader/

stjo005@stjo005-laptop:~/rowboat-android/TI_Android_GingerBread_2_3_4Sources/x-loader$ make CROSS_COMPILE=arm-eabi- distclean
find . -type f \
        \( -name 'core' -o -name '*.bak' -o -name '*~' \
        -o -name '*.o'  -o -name '*.a'  \) -print \
        | xargs rm -f
find . -type f \
        \( -name .depend -o -name '*.srec' -o -name '*.bin' \) \
        -print \
        | xargs rm -f
rm -f  *.bak tags TAGS
rm -fr *.*~
rm -f x-load x-load.map
rm -f include/asm/proc include/asm/arch
rm -f include/config.h include/config.mk

stjo005@stjo005-laptop:~/rowboat-android/TI_Android_GingerBread_2_3_4Sources/x-loader$ make CROSS_COMPILE=arm-eabi- omap3evm_config
rm -f include/config.h include/config.mk
Configuring for omap3evm board...

stjo005@stjo005-laptop:~/rowboat-android/TI_Android_GingerBread_2_3_4Sources/x-loader$ make CROSS_COMPILE=arm-eabi-
make: arm-eabi-gcc: Command not found
arm-eabi-gcc -Wa,-gstabs -D__ASSEMBLY__  -Os  -fno-strict-aliasing  -fno-common -ffixed-r8  -DONE_BIT_ERROR_CORRECT -D__KERNEL__ -DTEXT_BASE=0x40200800 -I/home/stjo005/rowboat-android/TI_Android_GingerBread_2_3_4Sources/x-loader/include -fno-builtin -ffreestanding -nostdinc -isystem  -pipe  -DCONFIG_ARM -D__ARM__ -march=armv7-a -mabi=apcs-gnu  -c -o cpu/omap3/start.o /home/stjo005/rowboat-android/TI_Android_GingerBread_2_3_4Sources/x-loader/cpu/omap3/start.S
make: arm-eabi-gcc: Command not found
make: *** [cpu/omap3/start.o] Error 127

Hi Sucahyo,

Please recheck your $PATH settings. Your sources are at
$HOME/rowboat-android/TI_Android_GingerBread_2_3_4Sources/

So the $PATH needs to be modified as follows:

export PATH="$HOME/rowboat-android/TI_Android_GingerBread_2_3_4Sources/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH"

Hi,

I am also facing the similar problem; color is not proper on the screen.

Can some one please tell me where to look for this problem?

Shall I install from sourc?

Rgrds,

Heshsham  

Last month I got BeagleBoard Xm Rev C(On sticker C1), I'm working with Angtrom and booting from micro SD card. I hope x-loader and u-boot is same for all the OS.

I have downloaded the images from the below link.

X- Loader: https://git.gitorious.org/x-load-omap3/

u-boot - http://www.beagleboard.org/uploads/u-boot_beagle_revb.tar.gz

2.6 Kernel - http://www.beagleboard.org/uploads/2.6_kernel_revb-v2.tar.gz

After successful compilation, I got all the images(MLO, uboot.bin and uimage). and put these images in first partition of micro SD and I have root file system in second partition.

Unfortunately I'm getting ASCII charcters and stopped after "Loading u-boot.bin from mmc".

By verifying your guidelines I found below issues.

the #define REVISION_XMC    0x02 is not present in omap3530beagle.c of /board/omap3530beagle of x-loader

And below defines are not in u-boot/include/configs/oamp3530beagle.h

/* BeagleBoard revisions */
#define REVISION_AXBX    0x7
#define REVISION_CX        0x6
#define REVISION_C4        0x5
#define REVISION_XM        0x0
#define REVISION_XMC    0x02

is not in u-boot oamp3530beagle.h

and the function linesare not in misc_init_r() of  u-boot/board/omap3530beagle/oamp3530beagle.c

case REVISION_XM:
    case REVISION_XMC:
        printf("Beagle xM Rev A/C\n");
        MUX_BEAGLE_XM();
        /* Set VAUX2 to 1.8V for EHCI PHY */
        twl4030_pmrecv_vsel_cfg(TWL4030_PM_RECEIVER_VAUX2_DEDICATED,
                    TWL4030_PM_RECEIVER_VAUX2_VSEL_18,
                    TWL4030_PM_RECEIVER_VAUX2_DEV_GRP,
                    TWL4030_PM_RECEIVER_DEV_GRP_P1);
        setenv("mpurate", "1000");

       break;

I'm not able to get the working source code for the last one week. 

Please send me the link of BeagleBoardXm Rev C working source code of x-loader, u-boot and Kernel.

Regards

Selvam

mr_selvam@rediffmail.com 

Please avoid re-opening old posts with an unrelated query.

selvam krishnan88164 said:

Last month I got BeagleBoard Xm Rev C(On sticker C1), I'm working with Angtrom and booting from micro SD card. I hope x-loader and u-boot is same for all the OS.

I have downloaded the images from the below link.

X- Loader: https://git.gitorious.org/x-load-omap3/

u-boot - http://www.beagleboard.org/uploads/u-boot_beagle_revb.tar.gz

2.6 Kernel - http://www.beagleboard.org/uploads/2.6_kernel_revb-v2.tar.gz

It looks like you are using u-boot/kernel sources for rev-B. Please refer to BeagleBoard.org documentation for information on getting angstrom sources for your board revision.

As far as android is concerned, as per http://processors.wiki.ti.com/index.php/TI-Android-ICS-4.0.3-DevKit-3.0.0_ReleaseNotes, the DevKit sources supports Beagleboard xm -rev C.

Currently, the TI-Android-ICS-4.0.3-DevKit-3.0.0 arm toolchain is 32-bits machine compatible. To prevent errors like "make: arm-eabi-gcc: Command not found" in a 64-bits machine, you must first install the package "ia32-libs" (command: sudo apt-get install ia32-libs).