0xdroid boot problem

[sarasini]

Hi all. I have compiled gingerbread for beagleboard-xm following these
instructions: http://code.google.com/p/0xdroid/wiki/0x7_leb_gingerbread

the system stops during kernel booting.

Here is my output:

reading boot.scr
462 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
reading uImage
3502776 bytes read
reading uInitrd
173707 bytes read
## Booting kernel from Legacy Image at 80200000 ...
Image Name: Linux-2.6.38.6-g3298421-dirty
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3502712 Bytes = 3.3 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 81600000 ...
Image Name: Android Ramdisk Image
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 173643 Bytes = 169.6 KiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...
Uncompressing Linux... done, booting the kernel.
<5>Linux version 2.6.38.6-g3298421-dirty (sarasini@sarasini-64bit)
(gcc version 4.5.4 20110505 (prerelease) (Linaro GCC 4.5-2011.05-0) )
#6 Mon Jan 2 21:02:10 CET 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: OMAP3 Beagle Board
<6>Reserving 33554432 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
<5>Truncating RAM at a0000000-bfffffff to -afffffff (vmalloc region
overlap).
<6>OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk )
<6>SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x10000

No more output. all leds on the board are turned on. Any help?

thanks
Francesco

[Julian Chu]

Hi,

On Tue, Jan 3, 2012 at 6:56 PM, sarasini <sara...@gmail.com> wrote:

Hi all. I have compiled gingerbread for beagleboard-xm following these
instructions: http://code.google.com/p/0xdroid/wiki/0x7_leb_gingerbread

the system stops during kernel booting.

is the pre-built bootable?

No more output. all leds on the board are turned on.  Any help?

what is your boot parameter at u-boot?

ttyS2 or ttyO2?

-Ju1ian
--
Julian Chu.  a.k.a. WalkingIce -- 會走路的冰塊

[Francesco Sarasini]

Hi, thanks for the reply

I'm not using prebuilt images (I know that they work)
I'm using linaro-android-media-create generated boot parameters


Thanks
Francesco

2012/1/5 Julian Chu <walki...@0xlab.org>

--
You received this message because you are subscribed to the Google Groups "0xlab-discuss" group.
To post to this group, send email to 0xlab-...@googlegroups.com.
To unsubscribe from this group, send email to 0xlab-discus...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/0xlab-discuss?hl=en.

[Francesco Sarasini]

Using linaro sources the system boots without problems. Now I have a problem with the touchscreen (ads7846)

ads7846 spi3.0: no device detected, test read results was 0x00000000
...
regulator_init_complete: vads7846: incomplete constraints, leaving on

and it doesn't work. Any suggestions?

Thanks
Francesco

2012/1/5 Francesco Sarasini <sara...@gmail.com>

[Francesco Sarasini]

Any help?

2012/1/8 Francesco Sarasini <sara...@gmail.com>

[sarasini]

Now I have:
ads7846 spi3.0: touchscreen, irq 322
input: ADS7846 Touchscreen as /devices/platform/omap/omap2_mcspi.3/
spi3.0/input/input0

but the touchscreen doesn't work.

If I do
cat /proc/interrupts
I see GPIO ads7846 incrementing.

# getevent
add device 1: /dev/input/event4
name: "HID 04d9:0499"
could not get driver version for /dev/input/mouse2, Not a typewriter
add device 2: /dev/input/event3
name: "Fake Touchscreen"
could not get driver version for /dev/input/mouse1, Not a typewriter
could not get driver version for /dev/input/mice, Not a typewriter
add device 3: /dev/input/event2
name: "gpio-keys"
add device 4: /dev/input/event0
name: "ADS7846 Touchscreen"
could not get driver version for /dev/input/mouse0, Not a typewriter
add device 5: /dev/input/event1
name: "twl4030_pwrbutton"

I can see mouse events, but nothing for touch


Thanks
Francesco

On Jan 17, 10:56 am, Francesco Sarasini <saras...@gmail.com> wrote:
> Any help?
>

> 2012/1/8 Francesco Sarasini <saras...@gmail.com>

>
>
>
>
>
>
>
>
>
> > Using linaro sources the system boots without problems. Now I have a
> > problem with the touchscreen (ads7846)
>
> > ads7846 spi3.0: no device detected, test read results was 0x00000000
> > ...
> > regulator_init_complete: vads7846: incomplete constraints, leaving on
>
> > and it doesn't work. Any suggestions?
>
> > Thanks
> > Francesco
>

> > 2012/1/5 Francesco Sarasini <saras...@gmail.com>

>
> >> Hi, thanks for the reply
>
> >> I'm not using prebuilt images (I know that they work)
> >> I'm using linaro-android-media-create generated boot parameters
>
> >> Thanks
> >> Francesco
>

> >> 2012/1/5 Julian Chu <walking...@0xlab.org>
>
> >>> Hi,

[Girish prasad]

Hi,
Check weather it is using the "tslib" for touch calibration, if
using disable it and test it. And also check weather events are
reaching the up to "EventHub.cpp", where all kings of events red from
input subsystem.

Thanks
Girish

2012/2/7 sarasini <sara...@gmail.com>:

--
Thanks & Regards
Girishprasad GM
+91-9663584129

[Francesco Sarasini]

in logcat I have

I/InputManager-Callbacks( 1071): No input device calibration properties found for device ADS7846 Touchscreen.


Francesco

2012/2/8 Girish prasad <girishp...@gmail.com>

[Francesco Sarasini]

I verified that touchscreen events are not reaching EventHub.cpp (mouse events are reaching correctly).

What can I do?


Thanks
Francesco

2012/2/11 Francesco Sarasini <sara...@gmail.com>