Home / Browse / gumstix / Mail / Archive

gumstix

Email Archive: gumstix-users (read-only)

Re: [Gumstix-users] Problem with Froyo kernel build

From: Ash Charles <ashcharles@gm...> - 2011-06-25 19:41

Hi SK,

On Sat, Jun 25, 2011 at 7:39 AM, #SIM KAI# <SIMK0018@...> wrote:
> I think the last line shows a valid compiler but the configuration seems wrong - for instance, I don't have /home/jingyu/projects/gcc/... in my file system. Is there a way for me to change this configuration?
This actually looks fine to me---I'm guessing someone named jingyu
made the toolchain (which requires libgmp)---I've got the same thing
in my setup.

Regarding the lack of output, does your kernel command line include
'console=ttyS2,115200n8'---often the kernel looks like it is not
booting when in fact it is, it just doesn't send the output to the
console.

-Ash

Thread View

Thread	Author	Date
[Gumstix-users] Problem with Froyo kernel build	#SIM KAI#

[Gumstix-users] Problem with Froyo kernel build

From: #SIM KAI# - 2011-06-24 09:19

Attachments: Message as HTML

Hi,

I am following the instructions from http://wiki.gumstix.org/index.php?title=RowboatAndroid to build the kernel.

All is fine until I come to: make ARCH=arm overo_android_defconfig

Makefile:304: /home/kai/rowboat-android/kernel/scripts/Kbuild.include: No such file or directory
make: *** empty variable name.  Stop.
make: *** [scripts_basic] Error 2

Similarly, when I try: make ARCH=arm CROSS_COMPILE=arm-eabi- uImage -j8

Makefile:304: /home/kai/rowboat-android/kernel/scripts/Kbuild.include: No such file or directory
/home/kai/rowboat-android/kernel/Makefile:304: /home/kai/rowboat-android/kernel/scripts/Kbuild.include: No such file or directory
make: *** empty variable name.  Stop.
make[1]: *** [scripts_basic] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'.  Stop.
make: *** Waiting for unfinished jobs....
make: *** empty variable name.  Stop.
make: *** [maketools] Error 2

I have done repo sync and all seems to be in order. My development machine is Ubuntu 11.04. Appreciate any help on this. Thanks.

Regards,
SK

Re: [Gumstix-users] Problem with Froyo kernel build

From: Ash Charles <ash@gu...> - 2011-06-25 01:03

Hi,

If you do
$ ls -l /bin/sh
do you get /bin/sh -> dash or /bin/sh -> bash?  If it is 'dash', then
'sudo dpkg-reconfigure dash' and select 'no' and try again.

Otherwise, after you do this step:
$ export PATH=${PWD}/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin:$PATH
type
$ arm-eabi-gcc -v
Does this show a valid compiler appearing on your path?

-Ash


On Fri, Jun 24, 2011 at 2:19 AM, #SIM KAI# <SIMK0018@...> wrote:
> Hi,
>
> I am following the instructions from
> http://wiki.gumstix.org/index.php?title=RowboatAndroid to build the kernel.
>
> All is fine until I come to: make ARCH=arm overo_android_defconfig
>
> Makefile:304: /home/kai/rowboat-android/kernel/scripts/Kbuild.include: No
> such file or directory
> make: *** empty variable name.  Stop.
> make: *** [scripts_basic] Error 2
>
> Similarly, when I try: make ARCH=arm CROSS_COMPILE=arm-eabi- uImage -j8
>
> Makefile:304: /home/kai/rowboat-android/kernel/scripts/Kbuild.include: No
> such file or directory
> /home/kai/rowboat-android/kernel/Makefile:304:
> /home/kai/rowboat-android/kernel/scripts/Kbuild.include: No such file or
> directory
> make: *** empty variable name.  Stop.
> make[1]: *** [scripts_basic] Error 2
> make: *** No rule to make target `include/config/auto.conf', needed by
> `include/config/kernel.release'.  Stop.
> make: *** Waiting for unfinished jobs....
> make: *** empty variable name.  Stop.
> make: *** [maketools] Error 2
>
> I have done repo sync and all seems to be in order. My development machine
> is Ubuntu 11.04. Appreciate any help on this. Thanks.
>
> Regards,
> SK
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense..
> http://p.sf.net/sfu/splunk-d2d-c1
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>

Re: [Gumstix-users] Problem with Froyo kernel build

From: #SIM KAI# - 2011-06-25 14:39

Hi Ash,

For the first step, I got:
lrwxrwxrwx 1 root root 4 2011-06-23 14:59 /bin/sh -> bash 

For the second step, I got:
Using built-in specs.
Target: arm-eabi
Configured with: /home/jingyu/projects/gcc/android-toolchain/gcc-4.4.0/configure --prefix=/usr/local --target=arm-eabi --host=i686-unknown-linux-gnu --build=i686-unknown-linux-gnu --enable-languages=c,c++ --with-gmp=/home/jingyu/projects/gcc/toolchain_build/obj/temp-install --with-mpfr=/home/jingyu/projects/gcc/toolchain_build/obj/temp-install --disable-libssp --enable-threads --disable-nls --disable-libmudflap --disable-libgomp --disable-libstdc__-v3 --disable-sjlj-exceptions --disable-shared --disable-tls --with-float=soft --with-fpu=vfp --with-arch=armv5te --enable-target-optspace --with-abi=aapcs --with-gcc-version=4.4.0 --with-binutils-version=2.19 --with-gmp-version=4.2.4 --with-mpfr-version=2.4.1 --with-gdb-version=6.6 --with-arch=armv5te --with-multilib-list=mthumb-interwork,mandroid --with-sysroot=/g/users/jingyu/toolchain/cupcake_rel_root --program-transform-name='s&^&arm-eabi-&'
Thread model: single
gcc version 4.4.0 (GCC) 

I think the last line shows a valid compiler but the configuration seems wrong - for instance, I don't have /home/jingyu/projects/gcc/... in my file system. Is there a way for me to change this configuration? 

Separately, I have also tried to use the pre-built images for the OMAP3530 (x-loader, u-boot, Kernel, Rootfs) using a bootable mini-SD card. However, I keep getting stuck at the stage when the kernel is booting. The output from kermit will always end like this: 

Texas Instruments X-Loader 1.4.2 (Jan 13 2010 - 06:59:23)
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2010.06-1 (Nov 03 2010 - 09:01:44)

OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz
IGEP v2 board + LPDDR/ONENAND
I2C:   ready
DRAM:  128 MiB
OneNAND: 0 Bytes
In:    serial
Out:   serial
Err:   serial
Die ID #77620004000000000403730607006012
Net:   smc911x-0
Hit any key to stop autoboot:  0 
mmc0 is available
reading setup.ini

394 bytes read
## Executing script at 80000000
mmc0 is available
reading uImage

2694096 bytes read
## Booting kernel from Legacy Image at 80200000 ...
   Image Name:   Linux-2.6.32
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2694032 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.

________________________________________
From: Ash Charles [ash@...]
Sent: Saturday, June 25, 2011 9:03 AM
To: General mailing list for gumstix users.
Subject: Re: [Gumstix-users] Problem with Froyo kernel build

Hi,

If you do
$ ls -l /bin/sh
do you get /bin/sh -> dash or /bin/sh -> bash?  If it is 'dash', then
'sudo dpkg-reconfigure dash' and select 'no' and try again.

Otherwise, after you do this step:
$ export PATH=${PWD}/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin:$PATH
type
$ arm-eabi-gcc -v
Does this show a valid compiler appearing on your path?

-Ash

On Fri, Jun 24, 2011 at 2:19 AM, #SIM KAI# <SIMK0018@...> wrote:
> Hi,
>
> I am following the instructions from
> http://wiki.gumstix.org/index.php?title=RowboatAndroid to build the kernel.
>
> All is fine until I come to: make ARCH=arm overo_android_defconfig
>
> Makefile:304: /home/kai/rowboat-android/kernel/scripts/Kbuild.include: No
> such file or directory
> make: *** empty variable name.  Stop.
> make: *** [scripts_basic] Error 2
>
> Similarly, when I try: make ARCH=arm CROSS_COMPILE=arm-eabi- uImage -j8
>
> Makefile:304: /home/kai/rowboat-android/kernel/scripts/Kbuild.include: No
> such file or directory
> /home/kai/rowboat-android/kernel/Makefile:304:
> /home/kai/rowboat-android/kernel/scripts/Kbuild.include: No such file or
> directory
> make: *** empty variable name.  Stop.
> make[1]: *** [scripts_basic] Error 2
> make: *** No rule to make target `include/config/auto.conf', needed by
> `include/config/kernel.release'.  Stop.
> make: *** Waiting for unfinished jobs....
> make: *** empty variable name.  Stop.
> make: *** [maketools] Error 2
>
> I have done repo sync and all seems to be in order. My development machine
> is Ubuntu 11.04. Appreciate any help on this. Thanks.
>
> Regards,
> SK
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense..
> http://p.sf.net/sfu/splunk-d2d-c1
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

Re: [Gumstix-users] Problem with Froyo kernel build

From: Ash Charles <ashcharles@gm...> - 2011-06-25 19:41

Hi SK,

On Sat, Jun 25, 2011 at 7:39 AM, #SIM KAI# <SIMK0018@...> wrote:
> I think the last line shows a valid compiler but the configuration seems wrong - for instance, I don't have /home/jingyu/projects/gcc/... in my file system. Is there a way for me to change this configuration?
This actually looks fine to me---I'm guessing someone named jingyu
made the toolchain (which requires libgmp)---I've got the same thing
in my setup.

Regarding the lack of output, does your kernel command line include
'console=ttyS2,115200n8'---often the kernel looks like it is not
booting when in fact it is, it just doesn't send the output to the
console.

-Ash

Re: [Gumstix-users] Problem with Froyo kernel build

From: #SIM KAI# - 2011-06-28 06:51

Hi Ash, 

How do I look at the kernel command line to see if it includes 'console=ttyS2,115200n8'? 'cos I am only seeing the console output when I use the pre-built images for Froyo booting from a mini-SD card. I am still not having any luck with building Froyo from the source files (same problem, still encountering /home/kai/rowboat-android/kernel/scripts/Kbuild.include:: No such file or directory =(. )

Having no luck with Froyo, I tried the Gingerbread pre-built image. This time round, I got beyond the kernel booting stage and can see the various drivers being loaded on the console. The console output goes all the way until the console itself is suspended (console output pasted below). However, when I tried to connect a monitor to the HDMI output (this is an Overo Fire running on Summit and Tobi boards separately), the HDMI output seems to be blank. Is there any way that I could get the HDMI output up? 

Thanks for your help. 

Regards,
SK  

================================================

Texas Instruments X-Loader 1.4.4ss (Mar 25 2011 - 15:35:41)
OMAP3530-GP ES3.1
Board revision: 0
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2010.09 (Mar 25 2011 - 15:02:51)

OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 mHz
Gumstix Overo board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Board revision: 0
Tranceiver detected on mmc2
No EEPROM on expansion board
Die ID #2dca000400000000040373051000c021
Net:   No ethernet found.
Hit any key to stop autoboot:  0 
mmc1 is available
reading boot.scr

606 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
mmc1 is available
reading uImage

3049240 bytes read
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Linux-2.6.32
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3049176 Bytes = 2.9 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 (buildslave@...) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Sat Jun 25 03:36:08 PDT 2011
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Gumstix Overo
Memory policy: ECC disabled, Data cache writeback
OMAP3430/3530 ES3.1 (l2cache iva sgx neon isp 720m )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Reserving 12582912 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: mpurate=600 console=ttyS2,115200n8 console=tty0 androidboot.console=ttyS2 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait init=/init vram=12M omapfb.mode=dvi:1024x768MR-16@... omapdss.def_disp=lcd43
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: 128MB 128MB = 256MB total
Memory: 240512KB available (5500K code, 1058K data, 176K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
Reprogramming SDRC clock to 332000000 Hz
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: GPTIMER1 at 32768 Hz
Console: colour dummy device 80x30
console [tty0] enabled
Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696)
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
Target VDD1 OPP = 5, VDD2 OPP = 3
OMAP DMA hardware revision 4.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 rev3.12 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
i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource 32k_counter
musb_hdrc: version 6.0, pio, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at fa0ab000 using PIO, 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
omap-iommu omap-iommu.0: isp registered
ashmem: initialized
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
yaffs Jun 25 2011 03:34:57 Installing. 
msgmni has been set to 470
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
Android kernel panic handler initialized (bind=kpanic)
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit)
cmdlinepart partition parsing not available
Creating 5 MTD partitions on "omap2-nand":
0x000000000000-0x000000080000 : "xloader"
0x000000080000-0x000000240000 : "uboot"
0x000000240000-0x000000280000 : "uboot environment"
0x000000280000-0x000000680000 : "linux"
0x000000680000-0x000010000000 : "rootfs"
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@...>
smsc911x: Driver version 2008-10-21.
smsc911x: Driver version 2008-10-21.
usbcore: registered new interface driver p54usb
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
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.32 ehci_hcd
usb usb1: SerialNumber: ehci-omap.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver ftdi_sio
ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
android init
android_probe pdata: c05c77ec
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
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.32 musb-hcd
usb usb2: SerialNumber: musb_hdrc
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
f_rndis init
android_register_function rndis
mice: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
ads7846 spi1.0: touchscreen, irq 274
ads7846 spi1.0: no device detected, test read result was 0x00000000
input: twl4030_pwrbutton as /devices/platform/i2c_omap.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.
i2c /dev entries driver
Linux video capture interface: v2.00
omap-iommu omap-iommu.0: isp: version 1.1
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Bluetooth: Broadcom Blutonium firmware driver ver 1.2
usbcore: registered new interface driver bcm203x
Bluetooth: Digianswer Bluetooth USB driver ver 0.10
usbcore: registered new interface driver bpa10x
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
Bluetooth: Generic Bluetooth SDIO driver ver 0.1
Registered led device: gpio21
Registered led device: gpio22
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'
Advanced Linux Sound Architecture Driver Version 1.0.21.
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
overo SoC init
asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok
ALSA device list:
  #0: overo (twl4030)
oprofile: using arm/armv7
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
ThumbEE CPU extension supported.
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
fbcvt: 1024x768@...: CVT Name - .786M3-R
Console: switching to colour frame buffer device 60x34
omapdss DPI: Could not find exact pixel clock. Requested 9200 kHz, got 9094 kHz
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new SD card at address b57e
mmcblk0: mmc0:b57e SU02G 1.89 GiB 
regulator_init_complete: incomplete constraints, leaving VDVI on
 mmcblk0:
regulator_init_complete: incomplete constraints, leaving VDAC on
 p1 p2 p3
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:17 UTC (946684817)
omap_vout omap_vout: probed for an unknown device
mmc1: new SDIO card at address 0001
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 176K
Warning: unable to open an initial console.
# warning: `rild' uses 32-bit capabilities (legacy support in use)
enabling adb
adb_open
request_suspend_state: wakeup (3->0) at 24346343996 (2000-01-01 00:00:39.614288329 UTC)
binder: release 1004:1061 transaction 479 in, still active
binder: send failed reply for transaction 479 to 1086:1140
request_suspend_state: sleep (0->3) at 91180418796 (2000-01-01 00:01:46.448332612 UTC)
stop_drawing_early_suspend: timeout waiting for userspace to stop drawing
omaplfb: **** SUSPEND
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.02 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Suspending console(s) (use no_console_suspend to debug)


________________________________________
From: Ash Charles [ashcharles@...]
Sent: Sunday, June 26, 2011 3:40 AM
To: General mailing list for gumstix users.
Subject: Re: [Gumstix-users] Problem with Froyo kernel build

Hi SK,

On Sat, Jun 25, 2011 at 7:39 AM, #SIM KAI# <SIMK0018@...> wrote:
> I think the last line shows a valid compiler but the configuration seems wrong - for instance, I don't have /home/jingyu/projects/gcc/... in my file system. Is there a way for me to change this configuration?
This actually looks fine to me---I'm guessing someone named jingyu
made the toolchain (which requires libgmp)---I've got the same thing
in my setup.

Regarding the lack of output, does your kernel command line include
'console=ttyS2,115200n8'---often the kernel looks like it is not
booting when in fact it is, it just doesn't send the output to the
console.

-Ash

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

Re: [Gumstix-users] Problem with Froyo kernel build

From: #SIM KAI# - 2011-06-28 07:31

Ok - I missed the part on changing the boot.scr for a dvi output. Android now shows up fine on my screen.
________________________________________
From: #SIM KAI# [SIMK0018@...]
Sent: Tuesday, June 28, 2011 2:50 PM
To: General mailing list for gumstix users.
Subject: Re: [Gumstix-users] Problem with Froyo kernel build

Hi Ash,

How do I look at the kernel command line to see if it includes 'console=ttyS2,115200n8'? 'cos I am only seeing the console output when I use the pre-built images for Froyo booting from a mini-SD card. I am still not having any luck with building Froyo from the source files (same problem, still encountering /home/kai/rowboat-android/kernel/scripts/Kbuild.include:: No such file or directory =(. )

Having no luck with Froyo, I tried the Gingerbread pre-built image. This time round, I got beyond the kernel booting stage and can see the various drivers being loaded on the console. The console output goes all the way until the console itself is suspended (console output pasted below). However, when I tried to connect a monitor to the HDMI output (this is an Overo Fire running on Summit and Tobi boards separately), the HDMI output seems to be blank. Is there any way that I could get the HDMI output up?

Thanks for your help.

Regards,
SK

================================================

Texas Instruments X-Loader 1.4.4ss (Mar 25 2011 - 15:35:41)
OMAP3530-GP ES3.1
Board revision: 0
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2010.09 (Mar 25 2011 - 15:02:51)

OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 mHz
Gumstix Overo board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Board revision: 0
Tranceiver detected on mmc2
No EEPROM on expansion board
Die ID #2dca000400000000040373051000c021
Net:   No ethernet found.
Hit any key to stop autoboot:  0
mmc1 is available
reading boot.scr

606 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
mmc1 is available
reading uImage

3049240 bytes read
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Linux-2.6.32
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3049176 Bytes = 2.9 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 (buildslave@...) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Sat Jun 25 03:36:08 PDT 2011
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Gumstix Overo
Memory policy: ECC disabled, Data cache writeback
OMAP3430/3530 ES3.1 (l2cache iva sgx neon isp 720m )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Reserving 12582912 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: mpurate=600 console=ttyS2,115200n8 console=tty0 androidboot.console=ttyS2 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait init=/init vram=12M omapfb.mode=dvi:1024x768MR-16@... omapdss.def_disp=lcd43
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: 128MB 128MB = 256MB total
Memory: 240512KB available (5500K code, 1058K data, 176K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
Reprogramming SDRC clock to 332000000 Hz
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: GPTIMER1 at 32768 Hz
Console: colour dummy device 80x30
console [tty0] enabled
Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696)
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
Target VDD1 OPP = 5, VDD2 OPP = 3
OMAP DMA hardware revision 4.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 rev3.12 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
i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource 32k_counter
musb_hdrc: version 6.0, pio, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at fa0ab000 using PIO, 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
omap-iommu omap-iommu.0: isp registered
ashmem: initialized
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
yaffs Jun 25 2011 03:34:57 Installing.
msgmni has been set to 470
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
Android kernel panic handler initialized (bind=kpanic)
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit)
cmdlinepart partition parsing not available
Creating 5 MTD partitions on "omap2-nand":
0x000000000000-0x000000080000 : "xloader"
0x000000080000-0x000000240000 : "uboot"
0x000000240000-0x000000280000 : "uboot environment"
0x000000280000-0x000000680000 : "linux"
0x000000680000-0x000010000000 : "rootfs"
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@...>
smsc911x: Driver version 2008-10-21.
smsc911x: Driver version 2008-10-21.
usbcore: registered new interface driver p54usb
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
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.32 ehci_hcd
usb usb1: SerialNumber: ehci-omap.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver ftdi_sio
ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
android init
android_probe pdata: c05c77ec
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
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.32 musb-hcd
usb usb2: SerialNumber: musb_hdrc
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
f_rndis init
android_register_function rndis
mice: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
ads7846 spi1.0: touchscreen, irq 274
ads7846 spi1.0: no device detected, test read result was 0x00000000
input: twl4030_pwrbutton as /devices/platform/i2c_omap.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.
i2c /dev entries driver
Linux video capture interface: v2.00
omap-iommu omap-iommu.0: isp: version 1.1
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Bluetooth: Broadcom Blutonium firmware driver ver 1.2
usbcore: registered new interface driver bcm203x
Bluetooth: Digianswer Bluetooth USB driver ver 0.10
usbcore: registered new interface driver bpa10x
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
Bluetooth: Generic Bluetooth SDIO driver ver 0.1
Registered led device: gpio21
Registered led device: gpio22
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'
Advanced Linux Sound Architecture Driver Version 1.0.21.
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
overo SoC init
asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok
ALSA device list:
  #0: overo (twl4030)
oprofile: using arm/armv7
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
ThumbEE CPU extension supported.
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
fbcvt: 1024x768@...: CVT Name - .786M3-R
Console: switching to colour frame buffer device 60x34
omapdss DPI: Could not find exact pixel clock. Requested 9200 kHz, got 9094 kHz
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new SD card at address b57e
mmcblk0: mmc0:b57e SU02G 1.89 GiB
regulator_init_complete: incomplete constraints, leaving VDVI on
 mmcblk0:
regulator_init_complete: incomplete constraints, leaving VDAC on
 p1 p2 p3
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:17 UTC (946684817)
omap_vout omap_vout: probed for an unknown device
mmc1: new SDIO card at address 0001
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 176K
Warning: unable to open an initial console.
# warning: `rild' uses 32-bit capabilities (legacy support in use)
enabling adb
adb_open
request_suspend_state: wakeup (3->0) at 24346343996 (2000-01-01 00:00:39.614288329 UTC)
binder: release 1004:1061 transaction 479 in, still active
binder: send failed reply for transaction 479 to 1086:1140
request_suspend_state: sleep (0->3) at 91180418796 (2000-01-01 00:01:46.448332612 UTC)
stop_drawing_early_suspend: timeout waiting for userspace to stop drawing
omaplfb: **** SUSPEND
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.02 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Suspending console(s) (use no_console_suspend to debug)

________________________________________
From: Ash Charles [ashcharles@...]
Sent: Sunday, June 26, 2011 3:40 AM
To: General mailing list for gumstix users.
Subject: Re: [Gumstix-users] Problem with Froyo kernel build

Hi SK,

On Sat, Jun 25, 2011 at 7:39 AM, #SIM KAI# <SIMK0018@...> wrote:
> I think the last line shows a valid compiler but the configuration seems wrong - for instance, I don't have /home/jingyu/projects/gcc/... in my file system. Is there a way for me to change this configuration?
This actually looks fine to me---I'm guessing someone named jingyu
made the toolchain (which requires libgmp)---I've got the same thing
in my setup.

Regarding the lack of output, does your kernel command line include
'console=ttyS2,115200n8'---often the kernel looks like it is not
booting when in fact it is, it just doesn't send the output to the
console.

-Ash

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

Re: [Gumstix-users] Problem with Froyo kernel build

From: Ash Charles <ash@gu...> - 2011-06-28 16:48

Hi,

Glad to hear that Gingerbread came up for you :).  To see the boot
parameters from linux, just do a 'cat /proc/cmdline'.
-Ash

On Mon, Jun 27, 2011 at 11:50 PM, #SIM KAI# <SIMK0018@...> wrote:
> How do I look at the kernel command line to see if it includes 'console=ttyS2,115200n8'? 'cos I am only seeing the console output when I use the pre-built images for Froyo booting from a mini-SD card. I am still not having any luck with building Froyo from the source files (same problem, still encountering /home/kai/rowboat-android/kernel/scripts/Kbuild.include:: No such file or directory =(. )

Re: [Gumstix-users] Problem with Froyo kernel build

From: #SIM KAI# - 2011-06-30 10:37

Thanks Ash. Now that I am playing with Gingerbread, there are a couple of issues that I am facing:

- There seems to be some delay in Android's response to my commands. I am not sure whether this is due to a) nature of Android GUI, b) I am loading Android from the mini-SD card. When I boot Linux Angstrom from the flash memory, there is no such delay. Would the response improve if I boot Android from the flash memory?
- Wifi apparently does not seem to work for this Gingerbread version. Uh oh. If I really need wifi, I'd guess I should revert to Froyo?

Cheers,
SK
________________________________________
From: Ash Charles [ash@...]
Sent: Wednesday, June 29, 2011 12:48 AM
To: General mailing list for gumstix users.
Subject: Re: [Gumstix-users] Problem with Froyo kernel build

Hi,

Glad to hear that Gingerbread came up for you :).  To see the boot
parameters from linux, just do a 'cat /proc/cmdline'.
-Ash

On Mon, Jun 27, 2011 at 11:50 PM, #SIM KAI# <SIMK0018@...> wrote:
> How do I look at the kernel command line to see if it includes 'console=ttyS2,115200n8'? 'cos I am only seeing the console output when I use the pre-built images for Froyo booting from a mini-SD card. I am still not having any luck with building Froyo from the source files (same problem, still encountering /home/kai/rowboat-android/kernel/scripts/Kbuild.include:: No such file or directory =(. )

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

Re: [Gumstix-users] Problem with Froyo kernel build

From: Ash Charles <ashcharles@gm...> - 2011-07-05 20:03

Hi,

On Thu, Jun 30, 2011 at 3:32 AM, #SIM KAI# <SIMK0018@...> wrote:
> - There seems to be some delay in Android's response to my commands. I am not sure whether this is due to a) nature of Android GUI, b) I am loading Android from the mini-SD card. When I boot Linux Angstrom from the flash memory, there is no such delay. Would the response improve if I boot Android from the flash memory?
The Android Gingerbread port for Overo is not well optimized---it is a
best effort to get something working so users have something to build
on although I'll happily take any patches :).  Some slowness is due to
Android being a little slow at certain types of operations.  Other
slowness in particular comes from the SGX drivers which have had a bug
which I believe is fixed in the new version.
> - Wifi apparently does not seem to work for this Gingerbread version. Uh oh. If I really need wifi, I'd guess I should revert to Froyo?
Others have had some success with Wifi on similar platforms running
Gingerbread so I believe it is possible but out of the box, this
Gingerbread port has some issues with Wifi.

-Ash