Hi Patrick,

Many thanks for your 20070214-2 kernel.

Unfortunately, the serial port stops working after it has initialised  
bluetooth. So I still cannot get access via the serial port  :(

A good thing is that it appears to boot further than your previous release,  
however this might be because you can now see the boot messages on the 
screen... I do not see the OE graphics though, just text output.

I also noticed is that once the screen is initialised, you see more 
information on the screen than you do on the serial port output. Maybe you 
need to film the screen and then slowly playback the messages to debug!

A very good thing is that when I plug it into the USB dock, the screen on the 
axim shows a USB reset and the axim attempting to initialise the USB network, 
so the kernel must be running. But all my attempts to ping the axim don't 
work, I have tried both 10.0.0.2 and 192.168.0.202 as possible IPs for the 
axim.

It's very strange that the serial port turns off while the axim boots - do you 
know why this might be ? Have any of the port assignments or descriptions 
changed ?

Many thanks for your work,

Jake

PS Here is the output I captured from the serial port before the serial port 
stops working

Uncompressing 
Linux............................................................................
 
do.
Linux version 2.6.19-hh11 ([EMAIL PROTECTED]) (gcc version 4.1.1) #1 PREEMPT 
Wed Feb 14 18:15:18 CET 2007
CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=0000397f
Machine: Dell Axim X50/X51(v)
Memory policy: ECC disabled, Data cache writeback
Run Mode clock: 208.00MHz (*16)
Turbo Mode clock: 624.00MHz (*3.0, active)
Memory clock: 208.00MHz (/2)
System bus clock: 208.00MHz
CPU0: D VIVT undefined 5 cache
CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
Built 1 zonelists.  Total pages: 16256
Kernel command line: 
ip=10.0.0.2:10.0.0.1:10.0.0.1:255.255.255.0:axim:usb0:none 
console=ttyS0,115200n8 console=tty0 ramdisk_size=16384 e
PID hash table entries: 256 (order: 8, 1024 bytes)
start_kernel(): bug: interrupts were enabled early
Console: colour dummy device 80x30
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: 53948KB available (1964K code, 359K data, 84K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
checking if image is initramfs... it is
Freeing initrd memory: 8511K
NET: Registered protocol family 16just 
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: -1, 2048 bytes)
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 2048 bind 1024)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
pxa2xx-fb pxa2xx-fb: machine LCCR0 setting contains illegal bits: 00300879
pxa2xx-fb pxa2xx-fb: machine LCCR3 setting contains illegal bits: 00300000
Console: switching to colour frame buffer device 60x40
SA1100 Real Time Clock driver v1.03
pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 22) is a FFUART
pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 21) is a BTUART
pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a STUART
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
PPP generic driver version 2.4.2
pxa27x_udc: version 21-Jul-2005
USB cmd disconnect
ether gadget: using random self ethernet address
usb0: Ethernet Gadget, version: May Day 2005
usb0: using pxa27x_udc, OUT Bulk-out-2 IN Bulk-in-1
usb0: MAC 2a:ca:19:f1:b1:ab
USB cmd connect
I2C: i2c-0: PXA I2C adapter
TCP cubic registered
NET: Registered protocol family 1
Freeing init memory: 84K
mmcblk0: mmc0:0d93 SH256 249856KiB
 mmcblk0: p1
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
NET: Registered protocol family 23
IrCOMM protocol (Dag Brattli)
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
-- 
_______________________________________________
Aximx50-port mailing list
[email protected]
https://www.handhelds.org/mailman/listinfo/aximx50-port

Reply via email to