Using script I flash linux demo from CDROM (which came with at91sam9263-ek) to board.

After that press reset button,
and booting process begin,
but on line
ads7846 spi0.3: touchscreen, irq 31

the process hangup,

I reflash it again, but this didn't helps.

Any idea how to fix this?

Hello Dave,

If you are intrested only in running demo linux you can download the
"softpack-1.2-at91sam9263-ek-web" package from the ATMEL site
It contains many demo projects.

After decompressing it
you will find the Linux archive in /html/demo folder
and the installation instructions in /html/Linux4SAM

just follow the mentioned procedure and you will have a running Angstrom linux.

Regards,
Devendra

You can also go to :
http://www.linux4sam.org

The demo there should work.

Nicolas,

the same problems here.
I have a AT91SAM9263-EK Rev. B with an AT91SAM9263 Rev B µC.

2.6.19 Kernel:
Starting kernel ...

Linux version 2.6.19 (nferre@penfret.rfo.atmel.com) (gcc version 3.4.4) #3 Thu Dec 14 11:05:09 CET 2006
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Atmel AT91SAM9263-EK
Ignoring unrecognised tag 0x54410008
.......
USB Mass Storage support registered.
udc: at91_udc version 3 May 2006
mice: PS/2 mouse device common for all mice
ads7846 spi0.3: touchscreen, irq 31

And now the kernel hangs.

All other kernel versions (.20/.22/.24 build with oe) have a noisy touchscreen. It's impossible to use the stylus.

ts_test during pressing the stylus in the middle of the screen:
root@at91sam9263ek:~$ ts_test
3309.817143: -70 430 7500
3309.827108: 120 160 7500
3309.827108: 120 160 7500
3309.867092: -70 430 7500
3309.867092: -70 430 7500
3309.937110: 214 24 7500
3309.947105: 405 -245 7500
3309.947105: 405 -245 7500
....
3310.397110: 405 -245 7500
3310.417107: 405 -245 7500
3310.527103: 405 -245 7500
3310.567095: 215 24 7500
3310.577112: 120 160 7500
3310.587114: 405 -245 7500
3310.587114: 405 -245 7500
3310.607116: 405 -245 7500
3310.617111: 405 -245 7500
3310.637109: 405 -245 7500
3310.666985: -70 430 0


Any ideas what's going wrong here?

Thanks,
Dirk

Btw. A second board shows the same behaviour