ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Ltib] EA3250: Touchscreen not functional with 2.6.34 kernel


From: Kevin Wells
Subject: RE: [Ltib] EA3250: Touchscreen not functional with 2.6.34 kernel
Date: Thu, 5 Aug 2010 23:20:14 +0200

Hi Ame & Charles,

 

The u-boot boot storage area did change with the last patch. There is also a possibility the machine ID is wrong.

 

i have tried to boot with the old kernel and now i have another problem:
It doesn't boot anymore...

I have replaced u-boot with the orginal provided u-boot and transferred the old provided kernel via TFTP to my board.
And here is the result:

 

About 6 months ago, the machine IDs used in u-boot changed to match the mainline IDs instead of the

generic LPC3XXX IDs. This means the older kernels compiled with only the LPC3XXX machine ID will no

longer boot with the updated u-boot. However, older versions of u-boot will boot kernels with both the

LPC3XXX and the new machine IDs. I think this is what you are experiencing.

 

Here is the original information on that change:

**snip**

If the kernel is uncompressing and seems to start, but there is no console output, it's possible the machine

IDs used in u-boot and the kernel are different. You can enable the CONFIG_DEBUG_LL option in the

kernel and then try booting the kernel. If the machine IDs are the issue, you'll see a message stating the

difference and the kernel will stop running.

 

The 32x0 kernels recently changed the machine ID from the generic 'LPC3XXX' used for all boards to

PHY3250, EA3250, and FDI3250 depending on which board you use. u-boot was also updated with this

change, so depending on which board's version of u-boot you use, you will get a corresponding

'non-LPC3XXX' machine ID passed via the ATAG list.

 

To allow for some backward compatability, the LPC3XXX is also supported in the kernel here along with the

new machine IDs, so older builds of u-boot with the LPC3XXX machine ID should work fine with the new

kernel builds (as long as the kernel is built via LTIB, the 2.6.34 patches do not have this support!). Note

2.6.34 support is not in LTIB yet.

 

Older build kernels with just the LPC3XXX machine ID support will no longer work with the new version

of u-boot.

 

Just to clear things up, 'older' and 'newer' builds simply refer to u-boot and kernel builds before the machine

ID patch and after the machine ID patch, respectively. The patch that changes these IDs was posted about a

month ago.

 

It's a bit messy, but it needed to be done, I couldn't release all board variants to mainline with the same

machine IDs. There should be some information about this in the deployment.txt file, but I can understand

that existing users probably wouldn't look at this.

 

Here are the build machine IDs:

                old u-boot.bin -> LPC3XXX for Phytec, Embedded Artist, and FDI boards

                new u-boot.bin -> Either PHY3250, EA3250, or FDI3250 based on the LTIB platform selected

                old uImage -> LPC3XXX for Phytec, Embedded Artist, and FDI boards

                new uImage (2.6.27.8) -> LPC3XXX + one of PHY3250, EA3250, or FDI3250 based on the LTIB platform selected

                new uImage (2.6.34) -> Only one of PHY3250, EA3250, or FDI3250

 

Here are the working combinations

                new u-boot.bin (PHY3250, EA3250, or FDI3250 machine IDs) -> Will not boot older kernel with LPC3XXX machines IDs

                new u-boot.bin (PHY3250 machine ID) -> Only boots newer kernel builds with PHY3250 machine ID

                new u-boot.bin (EA3250 machine ID) -> Only boots newer kernel builds with EA3250 machine ID

                new u-boot.bin (FDI3250 machine ID) -> Only boots newer kernel builds with FDI3250 machine ID

                old u-boot.bin (LPC3XXX machine ID, all boards) -> boots older and newer kernel builds

 

This will probably sting a few people in the short term, but it needed to be done.

 

**snip**

 

thanks,

Kevin

 

 

 

 

 

 

 

Subject: Re: [Ltib] EA3250: Touchscreen not functional with 2.6.34 kernel

 

Dear Arne:

When you replace a u-boot one of the things that happens is the environment is re-initialized.

Invariably, what happens is one of the environment strings such as bootcmd or bootargs bytes one in the buttocks.

So, ... one needs to get the original back from EA, *or* work through the now missing details.

It looks like you have a valid bootcmd (or at least a modestly functional one) as it found your uImage at 0x80100000.

Off hand, it could be the definition of ttys0 which is usually part of  bootargs and usually looks like this at the end of bootargs

console=ttyS0,115200

Charles

On Thu, Aug 5, 2010 at 11:02 AM, Burghardt Arne <address@hidden> wrote:

Dear Charles,

i have tried to boot with the old kernel and now i have another problem:
It doesn't boot anymore...

I have replaced u-boot with the orginal provided u-boot and transferred the old provided kernel via TFTP to my board.
And here is the result:

--------------------


Embedded Artist 3250 Board
Build date: May 21 2010 15:12:06
Autoboot in progress, press any key to stop


U-Boot 2009.03-rc1 (Aug 03 2010 - 18:59:39)

DRAM:  64 MB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
        HW MAC address:  00:1A:F1:00:00:00
ENET:auto-negotiation complete#$
ENET:FULL DUPLEX
ENET:100MBase
TFTP from server 192.168.123.27; our IP address is 192.168.123.42
Filename 'uImage'.
Load address: 0x80100000
Loading: #################################################################
         #############################################
done

Bytes transferred = 1604744 (187c88 hex)


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

   Image Name:   Linux-2.6.27.8


   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    1604680 Bytes =  1.5 MB


   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux....................................................................... done, booting the kernel.

----------------
And that's all, it waits forever...
Is this due to the updated Kickstart & S1 loader ? Any other ideas ?

  Arne


-----Ursprüngliche Nachricht-----
Von: Charles Krinke [mailto:address@hidden]
Gesendet: Do 05.08.2010 19:08
An: Burghardt Arne
Cc: address@hidden
Betreff: Re: [Ltib] EA3250: Touchscreen not functional with 2.6.34 kernel



Dear Arne:

One of the things that I would do would be to carefully compare the boot
messages from the original functioning kernel with the newly compiled on to
see what differences there may be.

Another would be to contact your vendor and see if you can get the .config
for the original kernel compile and use that for your newly compiled kernel.

Charles

On Thu, Aug 5, 2010 at 2:22 AM, Burghardt Arne <address@hidden>wrote:

>  Hi,
>
> i have a problem with my touchscreen on my EA3250 CPU module. It is not
> sending any data, you can't use it with e.g. ts-calibrate (no reaction, if
> you press the touchscreen). Here is a brief history of my activities:
>
> 1) Setup the board with the original 2.27 kernel provided by EA. The
> touchscreen was working fine (->no hardware defect on the board)
> 2) Flashed the latest Kickstart and S1 loader (V2.0) onto my board
> 3) Pulled ltib via CVS from the repository (3 days ago) and used the
> standard settings for the EA3250 target, except that i have disabled audio
> 4) Compile went smoothless and i have flashed the new u-boot loader onto my
> board
> 5) Setup TFTP & NFS and startet the booting process
> 6) Everything is fine, but i have no functional touchpad... :-(
>
> I have checked, that CONFIG_INPUT_TOUCHSCREEN and
> CONFIG_TOUCHSCREEN_ADS7846 are set.
> The device node /dev/input/event0 does exist (with the parameters c 13 64).
> I have attached the boot messages at the end of this mail.
>
> Does anyone has an idea, which configuration is missing or where i should
> look to debug and/or enable the touchscreen ?
> Thanks a lot for your help :-)
>
> Best regards
>
>   Arne
>
> Embedded Artist 3250 Board
> Build date: May 21 2010 15:12:06
> Autoboot in progress, press any key to stop
>
>
> U-Boot 2009.03-rc1 (Aug 03 2010 - 18:59:39)
>
> DRAM:  64 MB
> NAND:  128 MiB
> In:    serial
> Out:   serial
> Err:   serial
> Hit any key to stop autoboot:  0
>         HW MAC address:  00:1A:F1:00:00:00
> ENET:auto-negotiation complete#$
> ENET:FULL DUPLEX
> ENET:100MBase
> TFTP from server 192.168.123.27; our IP address is 192.168.123.42
> Filename 'uImage'.
> Load address: 0x80100000
> Loading: #################################################################
>          #################################################################
>          ##
> done
> Bytes transferred = 1923776 (1d5ac0 hex)
> ## Booting kernel from Legacy Image at 80100000 ...
>    Image Name:   Linux-2.6.34
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    1923712 Bytes =  1.8 MB
>    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.34 (address@hidden) (gcc version
> 4.1.2) #5 PREEMPT Thu Aug 5 10:32:34 CEST 2010
> CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
> CPU: VIVT data cache, VIVT instruction cache
> Machine: Embedded Artists LPC3250 OEM board with the LPC3250
> Microcontroller
> Memory policy: ECC disabled, Data cache writeback
> Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
> Kernel command line: root=/dev/nfs rw nfsroot=192.168.123.27:/home/user/ltib/rootfs
> ip=192.168.123.42 ethaddr=00:1a:f1:00:00:00 console=ttyS0,115200n8
> PID hash table entries: 256 (order: -2, 1024 bytes)
> Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
> Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
> Memory: 64MB = 64MB total
> Memory: 60900k/60900k available, 4636k reserved, 0K highmem
> Virtual kernel memory layout:
>     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
>     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
>     DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
>     vmalloc : 0xc4800000 - 0xf0000000   ( 696 MB)
>     lowmem  : 0xc0000000 - 0xc4000000   (  64 MB)
>     modules : 0xbf000000 - 0xc0000000   (  16 MB)
>       .init : 0xc0008000 - 0xc0027000   ( 124 kB)
>       .text : 0xc0027000 - 0xc03b1000   (3624 kB)
>       .data : 0xc03b2000 - 0xc03d6640   ( 146 kB)
> Hierarchical RCU implementation.
> NR_IRQS:96
> Console: colour dummy device 80x30
> Calibrating delay loop... 103.83 BogoMIPS (lpj=519168)
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> NET: Registered protocol family 16
> LPC32XX unique ID: 0006291c75701b6e58dc8cb710b8e000
> 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
> Switching to clocksource lpc32xx_clksrc
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 2048 (order: 2, 16384 bytes)
> TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
> TCP: Hash tables configured (established 2048 bind 2048)
> 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.
> NetWinder Floating Point Emulator V0.97 (double precision)
> NTFS driver 2.1.29 [Flags: R/W].
> JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
> msgmni has been set to 118
> alg: No test for stdrng (krng)
> io scheduler noop registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
> serial8250.0: ttyS0 at MMIO 0x40090000 (irq = 9) is a 16550A
> console [ttyS0] enabled
> brd: module loaded
> loop: module loaded
> NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V
> 8-bit)
> Scanning device for bad blocks
> Bad eraseblock 100 at 0x000000c80000
> Bad eraseblock 574 at 0x0000047c0000
> Bad eraseblock 707 at 0x000005860000
> Bad eraseblock 871 at 0x000006ce0000
> Creating 5 MTD partitions on "lpc32xx_nand":
> 0x000000000000-0x000000320000 : "ea3250-boot"
> 0x000000320000-0x000000fa0000 : "ea3250-uboot"
> 0x000000fa0000-0x000000fe0000 : "ea3250-ubt-prms"
> 0x000000fe0000-0x0000013e0000 : "ea3250-kernel"
> 0x0000013e0000-0x000008000000 : "ea3250-jffs2"
> lpc_mii_bus: probed
> eth0: using RMII interface
> eth0: LPC mac at 0x31060000 irq 29
> eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1)
> usbmon: debugfs is not available
> ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
> ISP1301 Vendor ID  : 0x04cc
> ISP1301 Product ID : 0x1301
> ISP1301 Version ID : 0x0210
> usb-ohci usb-ohci: at 0xf3120000, irq 0
> usb-ohci usb-ohci: pnx4008 OHCI
> usb-ohci usb-ohci: new USB bus registered, assigned bus number 1
> usb-ohci usb-ohci: irq 59, io mem 0xf3120000
> usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
> usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb1: Product: pnx4008 OHCI
> usb usb1: Manufacturer: Linux 2.6.34 ohci_hcd
> usb usb1: SerialNumber: usb-ohci
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 2 ports detected
> Initializing USB Mass Storage driver...
> usbcore: registered new interface driver usb-storage
> USB Mass Storage support registered.
> usbcore: registered new interface driver libusual
> mice: PS/2 mouse device common for all mice
> rtc-lpc32xx rtc-lpc32xx: rtc core: registered rtc-lpc32xx as rtc0
> i2c /dev entries driver
> PNX4008-WDT: PNX4008 Watchdog Timer: heartbeat 19 sec
> cpuidle: using governor ladder
> cpuidle: using governor menu
> TCP cubic registered
> NET: Registered protocol family 17
> ssp-pl022 dev:ssp0: ARM PL022 driver, device ID: 0x00041022
> pl022: mapped registers from 0x20084000 to c4882000
> ads7846 spi0.0: touchscreen, irq 64
> input: ADS7846 Touchscreen as /class/input/input0
> CLCD: Embedded Artists 3.2 inch LCD hardware, QVGA portrait display
> Console: switching to colour frame buffer device 30x40
> VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 1
> rtc-lpc32xx rtc-lpc32xx: setting system clock to 1971-08-27 18:55:09 UTC
> (52167309)
> IP-Config: Guessing netmask 255.255.255.0
> IP-Config: Complete:
>      device=eth0, addr=192.168.123.42, mask=255.255.255.0,
> gw=255.255.255.255,
>      host=192.168.123.42, domain=, nis-domain=(none),
>      bootserver=255.255.255.255, rootserver=192.168.123.27, rootpath=
> Looking up port of RPC 100003/2 on 192.168.123.27
> Looking up port of RPC 100005/1 on 192.168.123.27
> VFS: Mounted root (nfs filesystem) on device 0:10.
> Freeing init memory: 124K
> init started: BusyBox v1.11.2 ()
> starting pid 339, tty '': '/etc/rc.d/rcS'
> Mounting /proc and /sys
> Setting the hostname to photon-bc
> Mounting filesystems
> Booted NFS, not relocating: /tmp /var
> mount: mounting usbfs on /proc/bus/usb failed: No such file or directory
> Starting syslogd and klogd
> Running sysctl
> Setting up networking on loopback device:
> Setting up networking on eth0:
> Adding static route for default gateway to 192.168.123.27:
> Setting nameserver to 192.168.123.27 in /etc/resolv.conf:
> Starting inetd:
> starting pid 397, tty '': '-/bin/sh'
> address@hidden /]#
>
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib
>
>

 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]