Re: LAB almost booting from HaRET - then to move on to flash!

Hi,

I also worked with the LAB and it boots for me from the Haret. The only
thing is
that I can't communicate with it on the FFUART. It gives me the prompt but
that's all.
I wrote this to you already, didn't I?

--
Szabolcs
On Tue, 21 Sep 2004 00:42:21 -0400, Joshua Wise <joshua@joshuawise.com>  
wrote:
> Hi folks,
>
> I expect that today or tomorrow I will get LAB working with HaRET, then  
> I willb e able to move on to flashing it.
>
> Here is the output I am getting right now.
>
> joshua
>
> ¡*Ö.--«..W/.Y'HL¼.0000155
>                           Running interactively
>                                                Kernel stack at:  
> 0xA0074BC0
>     Going to run kernel from 0x00000000
>                                        Setting up tagged list...
>                                                                 Command  
> line: cachepolicy=writethrough forcecli
>
> Probing RAM size:
>                   BANK 00@A0000000: 0x40Mb
>                                           BANK 01@A4000000: NO RAM
>                                                                   BANK  
> 02@A8000000: NO RAM
>                     BANK 03@AC000000: NO RAM
>                                             Finished building tags
>                                                                   ***  
> Jumping into kernel
>                    Uncompressing Linux............................ .
>                                                                    4
>
> CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE)
>
> CPU: D undefined 5 cache
>
> CPU: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
>
> CPU: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
>
> Machine: HP iPAQ H2200
>
> Memory policy: ECC disabled, Data cache writethrough
>
> <6>Memory clock: 99.53MHz (*27)
>
> <6>Run Mode clock: 398.13MHz (*4)
>
> <6>Turbo Mode clock: 398.13MHz (*1.0, inactive)
>
> --++> Serial cable detected <++--
>
> <7>On node 0 totalpages: 16384
>
> <7>  DMA zone: 16384 pages, LIFO batch:4
>
> <7>  Normal zone: 0 pages, LIFO batch:1
>
> <7>  HighMem zone: 0 pages, LIFO batch:1
>
> Built 1 zonelists
>
> Kernel command line: cachepolicy=writethrough forcecli
>
> lab: Skipping autoboot due to forcecli parameter.
>
> <7>Relocating machine vectors to 0xffff0000
>
> PID hash table entries: 512 (order 9: 4096 bytes)
>
> Console: colour dummy device 80x30
>
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
>
> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
>
> <6>Memory: 64MB = 64MB total
>
> <5>Memory: 63856KB available (651K code, 208K data, 56K init)
>
> Calibrating delay loop... 397.31 BogoMIPS
>
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
>
> <6>CPU: Testing write buffer coherency: ok
>
> <6>Linux NoNET1.0 for Linux 2.6
>
> ipaq shamcop: using irq 104-130
>
> <7>IRQ28 (GPIO5): falling edges
>
> <3>shamcop adc: cannot find resource 2 in platform resources
>
> <7>IRQ27 (GPIO4): rising falling edges
>
> ttyS0 at MMIO 0x40100000 (irq = 15) is a FFUART
>
> _______________________________________________
> H2200-port mailing list
> H2200-port@handhelds.org
> https://handhelds.org/mailman/listinfo/h2200-port
>
-- 
Szabolcs Gyurko