Hi Erwin,
Good News, I load in the RAM memory separately the linux.text and
the linux.data according System.map addresses and the kernel runs!!!!!
> go 0x2210000
Jump to uClinux Kernel at: 0x2210000
Linux version 2.4.32-uc0 ([EMAIL PROTECTED]) (gcc version 3.4.4) #26 Mon Feb 26
15:04:44 CET 2007
Processor: Atmel AT91M40xxx revision 0
Architecture: EB01
Ignoring unrecognised tag 0x54410001
Ignoring unrecognised tag 0x54410002
On node 0 totalpages: 512
zone(0): 0 pages.
zone(1): 512 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/rom0
Calibrating delay loop... 4.05 BogoMIPS
Memory: 2MB = 2MB total
Memory: 1360KB available (461K code, 155K data, 36K init)
Dentry cache hash table entries: 512 (order: 0, 4096 bytes)
Inode cache hash table entries: 512 (order: 0, 4096 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 1024 (order: 0, 4096 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Atmel USART driver version 0.99
ttyS0 at 0xfffd0000 (irq = 2) is a builtin Atmel APB USART
ttyS1 at 0xfffcc000 (irq = 3) is a builtin Atmel APB USART
Blkmem copyright 1998,1999 D. Jeff Dionne
Blkmem copyright 1998 Kenneth Albanowski
Blkmem 1 disk images:
0: 1000000-FFFFFF [VIRTUAL 1000000-FFFFFF] (RO) <NONE>
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Blkmem: bad access: block=2, count=2 (pos=800, len=0)
end_request: I/O error, dev 1f:00 (Blkmem), sector 2
EXT2-fs: unable to read superblock
Blkmem: bad access: block=0, count=2 (pos=400, len=0)
end_request: I/O error, dev 1f:00 (Blkmem), sector 0
romfs: unable to read superblock
Kernel panic: VFS: Unable to mount root fs on 1f:00
Now I'm working in the romfs.
Thanks
-----Mensaje original-----
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
En nombre de rflores
Enviado el: lunes, 26 de febrero de 2007 12:39
Para: 'uClinux development list'
Asunto: RE: [uClinux-dev] uClinux on AT91 (Simulated Data abort in
__wake_up)
Hi Erwin,
I have noticed that the .data section is wrongly generated; many
global variables are ZERO if the variables are assigned in the declaration,
but if the variable is initialized in execution time then it works
correctly.
This problem causes that many variables and structures are filled
with zero when they need a correct initial value.
I have probed with the arm-elf-2003-2004 toolchains and the arm-
linux-2005 toolchain but none of then works in this case.
Thanks.
-----Mensaje original-----
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
En nombre de Erwin Authried
Enviado el: viernes, 23 de febrero de 2007 20:00
Para: uClinux development list
Asunto: RE: [uClinux-dev] uClinux on AT91 (Simulated Data abort in
__wake_up)
Hi,
you can simply output the output of printk_buf, after it has been
processed by vsnprintf in the printk function. I wonder why there are
those "ignoring unrecognized tag" messages, I can't remember that I have
seen them with ARM7TDMI cpus. The Kernel BUG message doesn't sound good,
either.
Regards,
Erwin
Am Freitag, den 23.02.2007, 13:39 +0100 schrieb rflores:
> Hi Erwin,
>
> I have changed the processor ID and the execution of the kernel goes to
> "calibration delay" (with errors in tags recognition) and at this point
> crashes.
>
> The output of printk() to memory is:
>
> "Linux Version 2.4.32-uc0 ([EMAIL PROTECTED]) (gcc version 3.4.4) #23
> sab feb 24 09:07:40 CET 2007.Processor: %revision
> %.Architecture:%.<4>Ignoring unrecognised tag 0x%.:%.<4>Ignoring
> unrecognised tag 0x%. 0x%.On node %totalpages: 0.zone(0): 0
pages..zone(1):
> 512 pages..zone(2): 0 pages..Kernel command line: %.<2>Kernel BUG at
> %:%.Calibrating delay loop"
>
> But, if I restore the printk() to send the output via serial port, it
> crashes at the __wait_up function, as before.
>
> I'm trying to print the value of the variables to view the "%" in the
printk
> output to memory.
>
> I think that the kernel does not call correctly to the serial drivers or
> does not configure them.
>
> Regards, Ramón
>
>
> -----Mensaje original-----
> De: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> En nombre de Erwin Authried
> Enviado el: miércoles, 21 de febrero de 2007 16:26
> Para: uClinux development list
> Asunto: RE: [uClinux-dev] uClinux on AT91 (Simulated Data abort in
> __wake_up)
>
> Am Mittwoch, den 21.02.2007, 15:22 +0100 schrieb rflores:
> > Hi,
> >
> > I changed the printk() function to write in memory (external RAM) in
> > order to view the output of the kernel messages.
> >
> > The result is that the new printk() writes the following:
> >
> > "Linux version 2.4.32-uc0 ([EMAIL PROTECTED]) (gcc version 3.4.4) #11
> jue
> > feb 22 12:03:12 CET 2007.
> >
> > CPU configuration botched (ID %), unable to continue.."
> >
> > What could be wrong? I've passed to kernel the architecture used in R1
> > assuming that it should be 224 for an ARCH_ATMEL. Is this correct?.
> >
> > Thanks in advance,
>
> Hi,
>
> that brings us much closer to the solution for your problem. It doesn't
> seem to have anything to do with the mentioned __wake_up function,
> however. This means that there is no matching entry in the proc_info
> table. What is the processor id of your cpu? Probably you have to add a
> new entry for your cpu in arch/armnommu/mm/proc-arm6,7.S.
>
> Regards,
> Erwin
>
>
> _______________________________________________
> uClinux-dev mailing list
> [email protected]
> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> This message was resent by [email protected]
> To unsubscribe see:
> http://mailman.uclinux.org/mailman/options/uclinux-dev
>
> _______________________________________________
> uClinux-dev mailing list
> [email protected]
> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> This message was resent by [email protected]
> To unsubscribe see:
> http://mailman.uclinux.org/mailman/options/uclinux-dev
--
Dipl.-Ing. Erwin Authried
Softwareentwicklung und Systemdesign
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
