date:20070514

RE: [uClinux-dev] RE: jffs2 on MCF5208 custom board

2007-05-14 Thread Teun Grinwis

Hi Greg,
It is no HW fault, since primary I did extended tests on all memory r/w.
Also dBUG boot sw is running correctly.

After some further investigation, the real problem is a NULL ptr function
call, see below:

- in cfi_cmdset_0002.c, do_erase_oneblock
put_chip( map, chip, adr ); is called.

- in cfi_cmdset_0002.c, put_chip
wake_up( &chip->wq ); is called

- in kernel/sched.c, __wake_up
__wake_up_common( q, mode, nr_exclusive, 0, key ) is called

- in kernel/sched.c, __wake_up_common, here ERROR, func == NULL

static void __wake_up_common(wait_queue_head_t *q, unsigned int mode,
 int nr_exclusive, int sync, void *key)
{
struct list_head *tmp, *next;

list_for_each_safe(tmp, next, &q->task_list) {
wait_queue_t *curr;;
unsigned flags;
curr = list_entry(tmp, wait_queue_t, task_list);
flags = curr->flags;
if (curr->func(curr, mode, sync, key) &&

^^  ERROR, curr->func = NULL

(flags & WQ_FLAG_EXCLUSIVE) &&
!--nr_exclusive)
break;
}
}

Why is reason curr->func = NULL? I do not have knowledge about mtd.

Tx for info.

Regards,
Teun
> -Oorspronkelijk bericht-
> Van: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Greg Ungerer
> Verzonden: dinsdag 15 mei 2007 3:31
> Aan: uClinux development list
> Onderwerp: Re: [uClinux-dev] RE: jffs2 on MCF5208 custom board
>
>
> Hi Teun,
>
> Teun Grinwis wrote:
> > Late reply, went away some weeks,
> >
> > I currently do not run apps XIP.
> >
> > Our custom board concerning flash, is equal design as on Intec
> 5208EVB with
> > the diff that the flash is S29GL064AR4 iso AM29BDD160G,
>
> Could this be a hardware fault?
> Has the hardware been validated?
>
> Regards
> Greg
>
>
>
> > My MTD partitions are as follows (btw i did not change flash
> name string):
> >
> > 
> > Am29BDD160G 2.5v flash device (2MB): Found 1 x16 devices at 0x0
> in 16-bit
> > bank
> >  Amd/Fujitsu Extended Query Table at 0x0040
> > cfi_send_gen_cmd():,40 cmd=98 addr=0055 base= build
> > addr=00aa cm
> > d_val=0008
> > cfi_send_gen_cmd():,41 cmd=f0 addr= base= build
> > addr= cm
> > d_val=0040
> > cfi_send_gen_cmd():,42 cmd=ff addr= base= build
> > addr= cm
> > d_val=0040
> > Using buffer write method
> > number of CFI chips: 1
> > cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
> >
> > Creating 3 MTD partitions on "Am29BDD160G 2.5v flash device (2MB)":
> >
> > 0x-0x0004 : "dBUG (256K)"
> > mtd: Giving out device 2 to dBUG (256K)
> >
> > 0x0004-0x000c : "User FS (512K)"
> > mtd: Giving out device 3 to User FS (512K)
> >
> > 0x000c-0x0020 : "Kernel + RootFS (1280K)"
> > mtd: Giving out device 4 to Kernel + RootFS (1280K)
> > m520xevb ram probe(0x40150020,de000,4): de000 at 40150020
> >
> > m520xevb ram probe(0x40150020,de000,4): de000 at 40150020
> > do_map_probe(): name=map_ram <5>Creating 1 MTD partitions on "RAM":
> > 0x-0x000de000 : "Romfs"
> > mtd: Giving out device 5 to Romfs
> > init_m520x: Root filesystem maj:31 mtdblock:5
> > 
> >
> > I mount jffs2 on "User FS", addresses 0x4 - 0xc
> >
> > I can run my image successful on the EVB see attached file
> Log_uclinux_evb.
> >
> > I started all from a clean flash, erase flash, program dBUG, dn
> image.bin,
> > exec image.
> >
> > When starting on EVB, jffs2 is initializing "User FS" by MTD
> > do_erase_oneblock,
> > MTD do_write_oneword(s) 0x..0 - 0x..a for all sectors in "User
> FS", startup
> > successful.
> >
> > When starting on custom board *** ILLEGAL INSTRUCTION ***
> occurs after the
> > first
> > MTD do_erase_oneblock(), see attached file Log_uclinux_ads4010, startup
> > unsuccessful.
> >
> > It seems that the error has something todo with (erase) timing
> ?? since in
> > call trace:
> > ...
> > BUG: pdflush/9, lock held at task exit time!
> >  [403b6446] {alloc_super}
> > .. held by:   pdflush:9 [402b2330, 115]
> > ... acquired at:
> >
> > After further investigation it seems that in
> > cfi_cmdset_0002.c:do_erase_oneblock,
> > the code execution does not reach: spin_unlock(chip->mutex).
> >
> > Any suggestions, are welcome.
> >
> > Thanks in advance,
> > Teun Grinwis
> >
> >
> >> -Oorspronkelijk bericht-
> >> Van: Teun Grinwis [mailto:[EMAIL PROTECTED]
> >> Verzonden: donderdag 10 mei 2007 11:15
> >> Aan: Teun
> >> Onderwerp: jffs2 on MCF5208 custom board
> >>
> >>
> >>
> >> Hi Teun,
> >>
> >> Teun Grinwis wrote:
> >>> Hello all,
> >>> Can someone give hint where to start debug searching ??
> >>>
> >>> I use distribution 20060511 2.16.16-uc0 on custom MCF 5208 board.

Re: [uClinux-dev] Problem linking pthread... undefined referenceto `pthread_create'

2007-05-14 Thread Claudia De Bartolomeis


Hi Daniel,
I have solved my linking problem
making a modification in the Makefile -lpthread
Now It works (almost the compilation does)
Thanks
Claudia
- Original Message - 
From: "Daniel Alomar" <[EMAIL PROTECTED]>

To: "uClinux development list" 
Sent: Tuesday, May 15, 2007 6:37 AM
Subject: Re: [uClinux-dev] Problem linking pthread... undefined referenceto 
`pthread_create'




Hi Claudia,

Have you already enable pthreads inside uClibc?

Regards,

Daniel Alomar

En/na Claudia De Bartolomeis ha escrit:

Hi everybody,
I'm developing an application under uclinux  uclibc 0.9.26 for Coldfire 
m532x,

but I'm having troubles linking pthread
 Thanks in advance for any help
Claudia
 This is the compilation log:
 [EMAIL PROTECTED]:~/ltib-m532xevb-20061117 
> ./ltib -m 
cbuild  -p microwindows.spec

 Processing: microwindows
==
rpmbuild --dbpath /home/claudia/ltib-m532xevb-20061117/rpmdb --define 
'_unpackaged_files_terminate_build 0' --define '_target_cpu 
m68knommu' --define '__strip strip' --define '_topdir 
/home/claudia/ltib-m532xevb-20061117/rpm' --define '_prefix 
/usr' --define '_tmppath 
/home/claudia/ltib-m532xevb-20061117/tmp' --define '_mandir 
/usr/share/man' --define '_sysconfdir /etc' --define '_localstatedir 
/var' -bc --short-circuit 
/home/claudia/ltib-m532xevb-20061117/dist/lfs-5.1/microwindows/microwindows.spec
Executing(%build): /bin/sh -e 
/home/claudia/ltib-m532xevb-20061117/tmp/rpm-tmp.19156

+ umask 022
+ cd /home/claudia/ltib-m532xevb-20061117/rpm/BUILD
+ cd microwindows-0.90
+ cd src
+ make -j1 'HOSTCC=/usr/bin/gcc -B/usr/bin//'
make -C drivers
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/drivers'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/drivers'

make -C mwin
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin'

make -C bmp
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/bmp'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/bmp'

make -C mwobjects
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/mwobjects'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/mwobjects'

make -C winlib
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/winlib'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/winlib'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin'

make -C engine
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/engine'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/engine'

make -C fonts
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/fonts'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/fonts'

make -C nanox
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/nanox'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/nanox'

make -C demos
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos'

make -C mwin
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/mwin'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/mwin'

make -C mwobjects
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/mwobjects'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/mwobjects'

make -C nanowm
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/nanowm'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/nanowm'

make -C nanox
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/nanox'

make -C icoone
make[3]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/nanox/icoone'
Linking 
/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/bin/main 
...
gcc   -I. -I/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/include 
 -Wall -Wpointer-arith  -lpthread  -L/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/lib 
main.o menu_engine.o buttons.o -o 
/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microw

Re: [uClinux-dev] Problem linking pthread... undefined reference to `pthread_create'

2007-05-14 Thread Daniel Alomar


Hi Claudia,

Have you already enable pthreads inside uClibc?

Regards,

Daniel Alomar

En/na Claudia De Bartolomeis ha escrit:

Hi everybody,
I'm developing an application under uclinux  uclibc 0.9.26 for Coldfire  
m532x,

but I'm having troubles linking pthread
 
Thanks in advance for any help

Claudia
 
This is the compilation log:
 
[EMAIL PROTECTED]:~/ltib-m532xevb-20061117 
> ./ltib -m scbuild  
-p microwindows.spec
 
Processing: microwindows

==
rpmbuild --dbpath /home/claudia/ltib-m532xevb-20061117/rpmdb --define 
'_unpackaged_files_terminate_build 0' --define '_target_cpu m68knommu' 
--define '__strip strip' --define '_topdir 
/home/claudia/ltib-m532xevb-20061117/rpm' --define '_prefix /usr' 
--define '_tmppath /home/claudia/ltib-m532xevb-20061117/tmp' --define 
'_mandir /usr/share/man' --define '_sysconfdir /etc' --define 
'_localstatedir /var' -bc --short-circuit  
/home/claudia/ltib-m532xevb-20061117/dist/lfs-5.1/microwindows/microwindows.spec
Executing(%build): /bin/sh -e 
/home/claudia/ltib-m532xevb-20061117/tmp/rpm-tmp.19156

+ umask 022
+ cd /home/claudia/ltib-m532xevb-20061117/rpm/BUILD
+ cd microwindows-0.90
+ cd src
+ make -j1 'HOSTCC=/usr/bin/gcc -B/usr/bin//'
make -C drivers
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/drivers'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/drivers'

make -C mwin
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin'

make -C bmp
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/bmp'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/bmp'

make -C mwobjects
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/mwobjects'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/mwobjects'

make -C winlib
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/winlib'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/winlib'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin'

make -C engine
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/engine'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/engine'

make -C fonts
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/fonts'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/fonts'

make -C nanox
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/nanox'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/nanox'

make -C demos
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos'

make -C mwin
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/mwin'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/mwin'

make -C mwobjects
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/mwobjects'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/mwobjects'

make -C nanowm
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/nanowm'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/nanowm'

make -C nanox
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/nanox'

make -C icoone
make[3]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/nanox/icoone'
Linking 
/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/bin/main 
...
gcc   -I. 
-I/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/include 
-Wall -Wpointer-arith  -lpthread  
-L/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/lib   
main.o menu_engine.o buttons.o -o 
/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/bin/main 
/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/lib/libnano-X.a

menu_engine.o: In function `prova':
menu_engine.c:(.text+0x50): undefined reference to `pthread_create'
menu_engine.c:(.text+0x72): undefined reference to `pthread_create'
menu_engine.c:(.text+0x88): undefined reference to `pthread_join'
menu_engine.c:(.text+0x98): u

[uClinux-dev] reloc type unsupported error when building uclinux-dist

2007-05-14 Thread Sky Ryan


Hi all
When I build the uclinux-dist-20070130

I got the following error when compiling the user apps

eloc type R_ARM_PC24 unsupported in this context

The cross-tool i used is buildroot.
Did anyone know this issue?
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

Re: [uClinux-dev] RE: jffs2 on MCF5208 custom board

2007-05-14 Thread Greg Ungerer


Hi Teun,

Teun Grinwis wrote:

Late reply, went away some weeks,

I currently do not run apps XIP.

Our custom board concerning flash, is equal design as on Intec 5208EVB with
the diff that the flash is S29GL064AR4 iso AM29BDD160G,


Could this be a hardware fault?
Has the hardware been validated?

Regards
Greg




My MTD partitions are as follows (btw i did not change flash name string):


Am29BDD160G 2.5v flash device (2MB): Found 1 x16 devices at 0x0 in 16-bit
bank
 Amd/Fujitsu Extended Query Table at 0x0040
cfi_send_gen_cmd():,40 cmd=98 addr=0055 base= build
addr=00aa cm
d_val=0008
cfi_send_gen_cmd():,41 cmd=f0 addr= base= build
addr= cm
d_val=0040
cfi_send_gen_cmd():,42 cmd=ff addr= base= build
addr= cm
d_val=0040
Using buffer write method
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.

Creating 3 MTD partitions on "Am29BDD160G 2.5v flash device (2MB)":

0x-0x0004 : "dBUG (256K)"
mtd: Giving out device 2 to dBUG (256K)

0x0004-0x000c : "User FS (512K)"
mtd: Giving out device 3 to User FS (512K)

0x000c-0x0020 : "Kernel + RootFS (1280K)"
mtd: Giving out device 4 to Kernel + RootFS (1280K)
m520xevb ram probe(0x40150020,de000,4): de000 at 40150020

m520xevb ram probe(0x40150020,de000,4): de000 at 40150020
do_map_probe(): name=map_ram <5>Creating 1 MTD partitions on "RAM":
0x-0x000de000 : "Romfs"
mtd: Giving out device 5 to Romfs
init_m520x: Root filesystem maj:31 mtdblock:5


I mount jffs2 on "User FS", addresses 0x4 - 0xc

I can run my image successful on the EVB see attached file Log_uclinux_evb.

I started all from a clean flash, erase flash, program dBUG, dn image.bin,
exec image.

When starting on EVB, jffs2 is initializing "User FS" by MTD
do_erase_oneblock,
MTD do_write_oneword(s) 0x..0 - 0x..a for all sectors in "User FS", startup
successful.

When starting on custom board *** ILLEGAL INSTRUCTION *** occurs after the
first
MTD do_erase_oneblock(), see attached file Log_uclinux_ads4010, startup
unsuccessful.

It seems that the error has something todo with (erase) timing ?? since in
call trace:
...
BUG: pdflush/9, lock held at task exit time!
 [403b6446] {alloc_super}
.. held by:   pdflush:9 [402b2330, 115]
... acquired at:

After further investigation it seems that in
cfi_cmdset_0002.c:do_erase_oneblock,
the code execution does not reach: spin_unlock(chip->mutex).

Any suggestions, are welcome.

Thanks in advance,
Teun Grinwis



-Oorspronkelijk bericht-
Van: Teun Grinwis [mailto:[EMAIL PROTECTED]
Verzonden: donderdag 10 mei 2007 11:15
Aan: Teun
Onderwerp: jffs2 on MCF5208 custom board



Hi Teun,

Teun Grinwis wrote:

Hello all,
Can someone give hint where to start debug searching ??

I use distribution 20060511 2.16.16-uc0 on custom MCF 5208 board.
With flash, S29GL064AR4. Debug for mtd, jffs2 set to noisy.

When I mount a mtdblock on jffs2 I got the following error:

See below.
Command: mount -t jffs2 /dev/mtdblock3 /mnt
Command:
Command:
Execution Finished, Exiting
mtdblock: read on "Romfs" at 0x3d400, size 0x200
..

Your root filesystem isn't also on the same flash
as the JFFS2 you are trying to mount is it?

If you where running apps XIP then this would be a problem.

Regards
Greg



___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev


--

Greg Ungerer  --  Chief Software Dude   EMAIL: [EMAIL PROTECTED]
Secure Computing CorporationPHONE:   +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

Re: [uClinux-dev] Bad Frame Format

2007-05-14 Thread Greg Ungerer


Hi Praveen,

Praveen Chandrasekharaiah wrote:

Strange: No where in my application/build have i specified -mcpu=5206.
I used the tool chain binary provided in the below link. Is the tool 
chain specific to a processor or family of processors.

http://www.codesourcery.com/gnu_toolchains/coldfire/download.html
Do i have to build the tool chain for 5307 specifically from the source 
provided. ( I am not sure of the options to select to build this tool 
chain )


No. The one toolchain supports all cpu options for m68k/coldfire.

Regards
Greg




Greg Ungerer wrote:


Hi Praveen,

Praveen Chandrasekharaiah wrote:

Attached is the verbose output of the make command.
Please rename .piz to .zip.


Looks odd to me that the last g++ compile line has "-m5370"
whereas previous too usage has "-mcpu=5206".

Regards
Greg

___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev



--

Greg Ungerer  --  Chief Software Dude   EMAIL: [EMAIL PROTECTED]
Secure Computing CorporationPHONE:   +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

Re: [uClinux-dev] No response after the message "Freeing init memory" on IXP425

2007-05-14 Thread Greg Ungerer


Hi Shuanglin,

Shuanglin Wang wrote:

Yes, I have simpleinit enabled and kernel command line is "console=ttyS0".

My board has only one serial port connecting with the host pc. Firsly, I 
use arm-elf-gcc 3.4.3 and got error:


/*--*/ 


Load /sbin/init: TEXT=2a0040-2a97e0 DATA=2a97e4-2ab394 BSS=2ab394-2bcde4
BINFMT_FLAT: reloc outside program 0x554e47 (0 - 0x1cda4/0x97a0), 
killing init
/*--*/ 


If you are using the IXP425 processor you should not be using the flat
format loader (BINFMT_FLAT). You should be using the standard ELF
program loader.

Regards
Greg





After I switch to the toolchain with arm-linux-gcc 3.4.4, reloc error is 
solved, but console no response at all from userland applications.


/*--kernel 
output---*/

BINFMT_FLAT: Loading file: /sbin/init
Mapping is 2a, Entry point is 44, data_start is 96a0
Load /sbin/init: TEXT=2a0040-2a96a0 DATA=2a96a4-2ab254 BSS=2ab254-2bcca4
start_thread(regs=0x1b3f24, entry=0x2a0044, start_stack=0x2bffb0)

BINFMT_FLAT: Loading file: /bin/sh
Mapping is 2e, Entry point is 44, data_start is ee80
Load /bin/sh: TEXT=2e0040-2eee80 DATA=2eee84-2f1964 BSS=2f1964-2f2ec4
start_thread(regs=0x29ffb0, entry=0x2e0044, start_stack=0x2fff98)

BINFMT_FLAT: Loading file: /bin/sh
Mapping is 2e, Entry point is 44, data_start is ee80
Load /bin/sh: TEXT=2e0040-2eee80 DATA=2eee84-2f1964 BSS=2f1964-2f2ec4
start_thread(regs=0x313fb0, entry=0x2e0044, start_stack=0x2fff90)

BINFMT_FLAT: Loading file: /bin/sh
Mapping is 2e, Entry point is 44, data_start is ee80
Load /bin/sh: TEXT=2e0040-2eee80 DATA=2eee84-2f1964 BSS=2f1964-2f2ec4
start_thread(regs=0x313fb0, entry=0x2e0044, start_stack=0x2fff98)

BINFMT_FLAT: Loading file: /bin/sh
Mapping is 32, Entry point is 44, data_start is ee80
Load /bin/sh: TEXT=320040-32ee80 DATA=32ee84-331964 BSS=331964-332ec4
start_thread(regs=0x307fb0, entry=0x320044, start_stack=0x33ff98)
/*-*/ 



I suspect that my kernel/uClib setting may be wrong;
or I didn't create the stable userland application like "init" and "sh";

Thanks,
Shuanglin




Greg Ungerer wrote:



Hi Shuanglin,

Shuanglin Wang wrote:

I think I meet the similar problem on my ARM946E-S board. My 
toolchain is gcc 3.4.4 and uClinux is the uClinux-dist-20070130 from 
uclinux official website.


My question is about console setup. What should I do to make console 
work for userland applications? I prefer using "core 
applications->enable console shell" .



That is ok. Do you have simpleinit enabled too?

In any case what is the kernel command line?
Do you have a "console=" option on it?

Regards
Greg




Thanks in advance.

Shuanglin


Greg Ungerer wrote:


Hi Srikanth,

Srikanth Chavali wrote:


Hi Greg,
   Just figured out that ADI Engineering is using 
uClinux-dist.




What version?

I looks like a console setup problem...

Regards
Greg




srikanth chavali

On 5/10/07, *Greg Ungerer* < [EMAIL PROTECTED] 
> wrote:


Hi Srikanthn

Srikanth Chavali wrote:
 >I compiled ( 2.6.x kernel) and loaded the zImage and
ramdisk.gz on my
 > board with IXP425. The board seems to be in the process of
loading the
 > kernel when it stops after the messages shown below.

Are you using the uClinux-dist, or something else?
If yes, what version?

Regards
Greg



 > I googled and found people facing similar issues. I ensured 
that

i had
 > CONFIG_FPE_NWFPE=y and CONFIG_FPE_FASTFPE is not set in my 
kernel

configs.
 >
 > Any help would be greatly appreciated.
 >
 > Regards,
 >
 > srikanth chavali
 >
 > Attached are the messages:
 >
 >  Intel/Sharp Extended Query Table at 0x010A
 >  Intel/Sharp Extended Query Table at 0x010A
 >  Intel/Sharp Extended Query Table at 0x010A
 >  Intel/Sharp Extended Query Table at 0x010A
 > Using buffer write method
 > cfi_cmdset_0001: Erase suspend on write enabled
 > Searching for RedBoot partition table in IXP4XX-Flash.0 at 
offset

0xfe
 > 3 RedBoot partitions found on MTD device IXP4XX-Flash.0
 > Creating 3 MTD partitions on "IXP4XX-Flash.0":
 > 0x-0x0006 : "RedBoot"
 > 0x00fe-0x00fff000 : "FIS directory"
 > mtd: partition "FIS directory" doesn't end on an erase block 
-- force

 > read-only
 > 0x00fff000-0x0100 : "RedBoot config"
 > mtd: partition "RedBoot config" doesn't start on an erase block
boundary
 > -- forc
 > e read-only
 > mice: PS/2 mouse device common for all mice
 > i2c /dev entries driver
 > TCP bic registered
 > NET: Registered protocol family 1
 > NET: Registered protocol family 17
 > RAMDISK: Compress

[uClinux-dev] compiling interrupt handlers (__irq)

2007-05-14 Thread Tiberiu Motoc


Hi,

I would like to know what is the arm-elf-gcc compiler options for compiling
files containing interrupt handler functions (prefixed with __irq)?
If I try to compile it with the default Makefile, I get "parse error before
".

Thanks,
Tiberiu
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

Re: [uClinux-dev] No response after the message "Freeing init memory" on IXP425

2007-05-14 Thread Srikanth Chavali


Hi Greg,
   The Pronghorn-Metro version is: 1.0.1

Regards,

srikanth chavali

On 5/13/07, Greg Ungerer <[EMAIL PROTECTED]> wrote:


Hi Srikanth,

Srikanth Chavali wrote:
> Hi Greg,
>Just figured out that ADI Engineering is using uClinux-dist.

What version?

I looks like a console setup problem...

Regards
Greg



> srikanth chavali
>
> On 5/10/07, *Greg Ungerer* < [EMAIL PROTECTED]
> > wrote:
>
> Hi Srikanthn
>
> Srikanth Chavali wrote:
>  >I compiled ( 2.6.x kernel) and loaded the zImage and
> ramdisk.gz on my
>  > board with IXP425. The board seems to be in the process of
> loading the
>  > kernel when it stops after the messages shown below.
>
> Are you using the uClinux-dist, or something else?
> If yes, what version?
>
> Regards
> Greg
>
>
>
>  > I googled and found people facing similar issues. I ensured that
> i had
>  > CONFIG_FPE_NWFPE=y and CONFIG_FPE_FASTFPE is not set in my kernel
> configs.
>  >
>  > Any help would be greatly appreciated.
>  >
>  > Regards,
>  >
>  > srikanth chavali
>  >
>  > Attached are the messages:
>  >
>  >  Intel/Sharp Extended Query Table at 0x010A
>  >  Intel/Sharp Extended Query Table at 0x010A
>  >  Intel/Sharp Extended Query Table at 0x010A
>  >  Intel/Sharp Extended Query Table at 0x010A
>  > Using buffer write method
>  > cfi_cmdset_0001: Erase suspend on write enabled
>  > Searching for RedBoot partition table in IXP4XX-Flash.0 at offset
> 0xfe
>  > 3 RedBoot partitions found on MTD device IXP4XX-Flash.0
>  > Creating 3 MTD partitions on "IXP4XX-Flash.0":
>  > 0x-0x0006 : "RedBoot"
>  > 0x00fe-0x00fff000 : "FIS directory"
>  > mtd: partition "FIS directory" doesn't end on an erase block --
force
>  > read-only
>  > 0x00fff000-0x0100 : "RedBoot config"
>  > mtd: partition "RedBoot config" doesn't start on an erase block
> boundary
>  > -- forc
>  > e read-only
>  > mice: PS/2 mouse device common for all mice
>  > i2c /dev entries driver
>  > TCP bic registered
>  > NET: Registered protocol family 1
>  > NET: Registered protocol family 17
>  > RAMDISK: Compressed image found at block 0
>  > VFS: Mounted root (ext2 filesystem) readonly.
>  > Freeing init memory: 96K
<--
>  > Nothing seems to happen after this
>  > although it does'nt look like the system is frozen.
>  >
>  > --
>  > srikanth chavali
>  >
>  >
>  >
>

>  >
>  > ___
>  > uClinux-dev mailing list
>  > uClinux-dev@uclinux.org 
>  > http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> 
>  > This message was resent by uclinux-dev@uclinux.org
> 
>  > To unsubscribe see:
>  > http://mailman.uclinux.org/mailman/options/uclinux-dev
> 
>
> --
>

> Greg Ungerer  --  Chief Software Dude   EMAIL:
> [EMAIL PROTECTED] 
> Secure Computing CorporationPHONE:   +61 7 3435
> 2888
> 825 Stanley St, FAX: +61 7 3891
3630
> Woolloongabba, QLD, 4102, Australia WEB:
http://www.SnapGear.com
> ___
> uClinux-dev mailing list
> uClinux-dev@uclinux.org 
> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> 
> This message was resent by uclinux-dev@uclinux.org
> 
> To unsubscribe see:
> http://mailman.uclinux.org/mailman/options/uclinux-dev
> 
>
>
>
>
> --
> srikanth chavali
>
>
> 
>
> ___
> uClinux-dev mailing list
> uClinux-dev@uclinux.org
> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> This message was resent by uclinux-dev@uclinux.org
> To unsubscribe see:
> http://mailman.uclinux.org/mailman/options/uclinux-dev

--

Greg Ungerer  --  Chief Software Dude   EMAIL: [EMAIL PROTECTED]
Secure Computing CorporationPHONE:   +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGe

Re: [uClinux-dev] Bad Frame Format

2007-05-14 Thread Praveen Chandrasekharaiah


Strange: No where in my application/build have i specified -mcpu=5206.
I used the tool chain binary provided in the below link. Is the tool 
chain specific to a processor or family of processors.

http://www.codesourcery.com/gnu_toolchains/coldfire/download.html
Do i have to build the tool chain for 5307 specifically from the source 
provided. ( I am not sure of the options to select to build this tool 
chain )


Greg Ungerer wrote:


Hi Praveen,

Praveen Chandrasekharaiah wrote:

Attached is the verbose output of the make command.
Please rename .piz to .zip.


Looks odd to me that the last g++ compile line has "-m5370"
whereas previous too usage has "-mcpu=5206".

Regards
Greg

___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

[uClinux-dev] Compiling m68k-tools-20061214 on gcc 3.4.4 for x86_64-redhat-linux

2007-05-14 Thread Jate Sujjavanich

I am attempting to build the toolchain (m68k-tools-20061214) on an
x86_64 system for the m68k architecture. This is GCC 4.1. I am using gcc
3.4.4 for x86_64-redhat-linux.


The build failed with an ICE error. After some research, I discovered
that revision 117181 of config/m68k/m68k.md had a change for what I
think are some floating point calls
(http://gcc.gnu.org/viewcvs/trunk/gcc/config/m68k/m68k.md?view=log).
Copying this revision of the file in allowed the build process to reach
stage 7.


At this stage, configure for libstdc++-v3 fails with the following error
message:

checking for main in -lm... configure: error: Link tests are not allowed
after GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-libstdc++-v3] Error 1
make[1]: Leaving directory
`/home/jate/test/m68k-tools-20061214/m68k-uclinux-gcc'
make: *** [all] Error 2

This is a vague error message. After much reading of the crossgcc
mailing list, I still do not have a solution. Does anyone have
experience with this error or any suggestions on how to get past this?



- Jate S.
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

Re: [uClinux-dev] No response after the message "Freeing init memory" on IXP425

2007-05-14 Thread Shuanglin Wang


Hi Greg,

Yes, I have simpleinit enabled and kernel command line is "console=ttyS0".

My board has only one serial port connecting with the host pc. Firsly, I 
use arm-elf-gcc 3.4.3 and got error:


/*--*/
Load /sbin/init: TEXT=2a0040-2a97e0 DATA=2a97e4-2ab394 BSS=2ab394-2bcde4
BINFMT_FLAT: reloc outside program 0x554e47 (0 - 0x1cda4/0x97a0), 
killing init

/*--*/

After I switch to the toolchain with arm-linux-gcc 3.4.4, reloc error is 
solved, but console no response at all from userland applications.


/*--kernel 
output---*/

BINFMT_FLAT: Loading file: /sbin/init
Mapping is 2a, Entry point is 44, data_start is 96a0
Load /sbin/init: TEXT=2a0040-2a96a0 DATA=2a96a4-2ab254 BSS=2ab254-2bcca4
start_thread(regs=0x1b3f24, entry=0x2a0044, start_stack=0x2bffb0)

BINFMT_FLAT: Loading file: /bin/sh
Mapping is 2e, Entry point is 44, data_start is ee80
Load /bin/sh: TEXT=2e0040-2eee80 DATA=2eee84-2f1964 BSS=2f1964-2f2ec4
start_thread(regs=0x29ffb0, entry=0x2e0044, start_stack=0x2fff98)

BINFMT_FLAT: Loading file: /bin/sh
Mapping is 2e, Entry point is 44, data_start is ee80
Load /bin/sh: TEXT=2e0040-2eee80 DATA=2eee84-2f1964 BSS=2f1964-2f2ec4
start_thread(regs=0x313fb0, entry=0x2e0044, start_stack=0x2fff90)

BINFMT_FLAT: Loading file: /bin/sh
Mapping is 2e, Entry point is 44, data_start is ee80
Load /bin/sh: TEXT=2e0040-2eee80 DATA=2eee84-2f1964 BSS=2f1964-2f2ec4
start_thread(regs=0x313fb0, entry=0x2e0044, start_stack=0x2fff98)

BINFMT_FLAT: Loading file: /bin/sh
Mapping is 32, Entry point is 44, data_start is ee80
Load /bin/sh: TEXT=320040-32ee80 DATA=32ee84-331964 BSS=331964-332ec4
start_thread(regs=0x307fb0, entry=0x320044, start_stack=0x33ff98)
/*-*/

I suspect that my kernel/uClib setting may be wrong;
or I didn't create the stable userland application like "init" and "sh";

Thanks,
Shuanglin




Greg Ungerer wrote:



Hi Shuanglin,

Shuanglin Wang wrote:

I think I meet the similar problem on my ARM946E-S board. My 
toolchain is gcc 3.4.4 and uClinux is the uClinux-dist-20070130 from 
uclinux official website.


My question is about console setup. What should I do to make console 
work for userland applications? I prefer using "core 
applications->enable console shell" .



That is ok. Do you have simpleinit enabled too?

In any case what is the kernel command line?
Do you have a "console=" option on it?

Regards
Greg




Thanks in advance.

Shuanglin


Greg Ungerer wrote:


Hi Srikanth,

Srikanth Chavali wrote:


Hi Greg,
   Just figured out that ADI Engineering is using 
uClinux-dist.




What version?

I looks like a console setup problem...

Regards
Greg




srikanth chavali

On 5/10/07, *Greg Ungerer* < [EMAIL PROTECTED] 
> wrote:


Hi Srikanthn

Srikanth Chavali wrote:
 >I compiled ( 2.6.x kernel) and loaded the zImage and
ramdisk.gz on my
 > board with IXP425. The board seems to be in the process of
loading the
 > kernel when it stops after the messages shown below.

Are you using the uClinux-dist, or something else?
If yes, what version?

Regards
Greg



 > I googled and found people facing similar issues. I ensured 
that

i had
 > CONFIG_FPE_NWFPE=y and CONFIG_FPE_FASTFPE is not set in my 
kernel

configs.
 >
 > Any help would be greatly appreciated.
 >
 > Regards,
 >
 > srikanth chavali
 >
 > Attached are the messages:
 >
 >  Intel/Sharp Extended Query Table at 0x010A
 >  Intel/Sharp Extended Query Table at 0x010A
 >  Intel/Sharp Extended Query Table at 0x010A
 >  Intel/Sharp Extended Query Table at 0x010A
 > Using buffer write method
 > cfi_cmdset_0001: Erase suspend on write enabled
 > Searching for RedBoot partition table in IXP4XX-Flash.0 at 
offset

0xfe
 > 3 RedBoot partitions found on MTD device IXP4XX-Flash.0
 > Creating 3 MTD partitions on "IXP4XX-Flash.0":
 > 0x-0x0006 : "RedBoot"
 > 0x00fe-0x00fff000 : "FIS directory"
 > mtd: partition "FIS directory" doesn't end on an erase block 
-- force

 > read-only
 > 0x00fff000-0x0100 : "RedBoot config"
 > mtd: partition "RedBoot config" doesn't start on an erase block
boundary
 > -- forc
 > e read-only
 > mice: PS/2 mouse device common for all mice
 > i2c /dev entries driver
 > TCP bic registered
 > NET: Registered protocol family 1
 > NET: Registered protocol family 17
 > RAMDISK: Compressed image found at block 0
 > VFS: Mounted root (ext2 filesystem) readonly.
 > Freeing init memory: 96K 
<--

 > Nothing seems to happen after this
 > a

Re: [uClinux-dev] Bad Frame Format

2007-05-14 Thread Greg Ungerer



Hi Praveen,

Praveen Chandrasekharaiah wrote:

Attached is the verbose output of the make command.
Please rename .piz to .zip.


Looks odd to me that the last g++ compile line has "-m5370"
whereas previous too usage has "-mcpu=5206".

Regards
Greg





Greg Ungerer wrote:

Hi Praveen,

Praveen Chandrasekharaiah wrote:
:) I am compiling with the correct CPU architecture. A snap shot of 
my logs are below:


If you send your build command lines I will believe you :-)







___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev



--

Greg Ungerer  --  Chief Software Dude   EMAIL: [EMAIL PROTECTED]
SnapGear -- a Secure Computing Company  PHONE:   +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

[uClinux-dev] Problem linking pthread... undefined reference to `pthread_create'

2007-05-14 Thread Claudia De Bartolomeis

Hi everybody,
I'm developing an application under uclinux  uclibc 0.9.26 for Coldfire  m532x,
but I'm having troubles linking pthread 

Thanks in advance for any help
Claudia

This is the compilation log:

[EMAIL PROTECTED]:~/ltib-m532xevb-20061117> ./ltib -m scbuild  -p 
microwindows.spec

Processing: microwindows
==
rpmbuild --dbpath /home/claudia/ltib-m532xevb-20061117/rpmdb --define 
'_unpackaged_files_terminate_build 0' --define '_target_cpu m68knommu' --define 
'__strip strip' --define '_topdir /home/claudia/ltib-m532xevb-20061117/rpm' 
--define '_prefix /usr' --define '_tmppath 
/home/claudia/ltib-m532xevb-20061117/tmp' --define '_mandir /usr/share/man' 
--define '_sysconfdir /etc' --define '_localstatedir /var' -bc --short-circuit  
/home/claudia/ltib-m532xevb-20061117/dist/lfs-5.1/microwindows/microwindows.spec
Executing(%build): /bin/sh -e 
/home/claudia/ltib-m532xevb-20061117/tmp/rpm-tmp.19156
+ umask 022
+ cd /home/claudia/ltib-m532xevb-20061117/rpm/BUILD
+ cd microwindows-0.90
+ cd src
+ make -j1 'HOSTCC=/usr/bin/gcc -B/usr/bin//'
make -C drivers
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/drivers'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/drivers'
make -C mwin
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin'
make -C bmp
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/bmp'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/bmp'
make -C mwobjects
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/mwobjects'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/mwobjects'
make -C winlib
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/winlib'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin/winlib'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/mwin'
make -C engine
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/engine'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/engine'
make -C fonts
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/fonts'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/fonts'
make -C nanox
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/nanox'
make[1]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/nanox'
make -C demos
make[1]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos'
make -C mwin
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/mwin'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/mwin'
make -C mwobjects
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/mwobjects'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/mwobjects'
make -C nanowm
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/nanowm'
make[2]: Leaving directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/nanowm'
make -C nanox
make[2]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/nanox'
make -C icoone
make[3]: Entering directory 
`/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/demos/nanox/icoone'
Linking 
/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/bin/main 
...
gcc   -I. 
-I/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/include 
-Wall -Wpointer-arith  -lpthread  
-L/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/lib   
main.o menu_engine.o buttons.o -o 
/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/bin/main 
/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/lib/libnano-X.a
menu_engine.o: In function `prova':
menu_engine.c:(.text+0x50): undefined reference to `pthread_create'
menu_engine.c:(.text+0x72): undefined reference to `pthread_create'
menu_engine.c:(.text+0x88): undefined reference to `pthread_join'
menu_engine.c:(.text+0x98): undefined reference to `pthread_join'
collect2: ld returned 1 exit status
make[3]: *** 
[/home/claudia/ltib-m532xevb-20061117/rpm/BUILD/microwindows-0.90/src/bin/main] 
Error 1
make[3]: Leaving directory 
`

Re: [uClinux-dev] Re: uclinux with RAM size problem

2007-05-14 Thread Greg Ungerer

Hi Will,

Will Huang wrote:

Thanks for your kindness of helping me.

One more stupit question:

I have subscribed uClinux-dev Digest and I can recieve the digest, but I 
cannot

find any reply message to my topic in my mailbox.

I don't recall, maybe no one replied though.

So I cannot reply any message to tell the list sort my message in 
correct thread.

I replied message from the digest now.

Would you mind telling me how to use mail list correctly?

As far as I can tell you did the right thing. I guess nobody
has any further answers to help you out.

 > > will wrote:

 > > I have used 2x32M SDRAM on my board, the loader did chip select 
well and

I think you need to check your SDRAM further.
It is the most likely culprit.

Make sure you test it with CPU cache on as well.
And the full 64MB too.

Regards
Greg

 > > I think it is not neccesory to do chip select again > > > > in 
kernel, is that right?

 > > Normally that is right, the boot loader sets up chip selects and > 
SDRAM.

ÏÖÔÚ¹ºÂò21CNÆóÒµÓÊÏä,¼´¿ÉÓÃ100Ôª»»5000Ôª! 

ÖíÄêÐÐ´óÔË£¬²ÂÍ¼Ó®»°·Ñ£¡ 

___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

--

Greg Ungerer  --  Chief Software Dude   EMAIL: [EMAIL PROTECTED]
SnapGear -- a Secure Computing Company  PHONE:   +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

Re: [uClinux-dev] No response after the message "Freeing init memory" on IXP425

2007-05-14 Thread Greg Ungerer



Hi Shuanglin,

Shuanglin Wang wrote:
I think I meet the similar problem on my ARM946E-S board. My toolchain 
is gcc 3.4.4 and uClinux is the uClinux-dist-20070130 from uclinux 
official website.


My question is about console setup. What should I do to make console 
work for userland applications? I prefer using "core 
applications->enable console shell" .


That is ok. Do you have simpleinit enabled too?

In any case what is the kernel command line?
Do you have a "console=" option on it?

Regards
Greg




Thanks in advance.

Shuanglin


Greg Ungerer wrote:


Hi Srikanth,

Srikanth Chavali wrote:


Hi Greg,
   Just figured out that ADI Engineering is using uClinux-dist.



What version?

I looks like a console setup problem...

Regards
Greg




srikanth chavali

On 5/10/07, *Greg Ungerer* < [EMAIL PROTECTED] 
> wrote:


Hi Srikanthn

Srikanth Chavali wrote:
 >I compiled ( 2.6.x kernel) and loaded the zImage and
ramdisk.gz on my
 > board with IXP425. The board seems to be in the process of
loading the
 > kernel when it stops after the messages shown below.

Are you using the uClinux-dist, or something else?
If yes, what version?

Regards
Greg



 > I googled and found people facing similar issues. I ensured that
i had
 > CONFIG_FPE_NWFPE=y and CONFIG_FPE_FASTFPE is not set in my kernel
configs.
 >
 > Any help would be greatly appreciated.
 >
 > Regards,
 >
 > srikanth chavali
 >
 > Attached are the messages:
 >
 >  Intel/Sharp Extended Query Table at 0x010A
 >  Intel/Sharp Extended Query Table at 0x010A
 >  Intel/Sharp Extended Query Table at 0x010A
 >  Intel/Sharp Extended Query Table at 0x010A
 > Using buffer write method
 > cfi_cmdset_0001: Erase suspend on write enabled
 > Searching for RedBoot partition table in IXP4XX-Flash.0 at offset
0xfe
 > 3 RedBoot partitions found on MTD device IXP4XX-Flash.0
 > Creating 3 MTD partitions on "IXP4XX-Flash.0":
 > 0x-0x0006 : "RedBoot"
 > 0x00fe-0x00fff000 : "FIS directory"
 > mtd: partition "FIS directory" doesn't end on an erase block 
-- force

 > read-only
 > 0x00fff000-0x0100 : "RedBoot config"
 > mtd: partition "RedBoot config" doesn't start on an erase block
boundary
 > -- forc
 > e read-only
 > mice: PS/2 mouse device common for all mice
 > i2c /dev entries driver
 > TCP bic registered
 > NET: Registered protocol family 1
 > NET: Registered protocol family 17
 > RAMDISK: Compressed image found at block 0
 > VFS: Mounted root (ext2 filesystem) readonly.
 > Freeing init memory: 96K 
<--

 > Nothing seems to happen after this
 > although it does'nt look like the system is frozen.
 >
 > --
 > srikanth chavali
 >
 >
 >



 >
 > ___
 > uClinux-dev mailing list
 > uClinux-dev@uclinux.org 
 > http://mailman.uclinux.org/mailman/listinfo/uclinux-dev

 > This message was resent by uclinux-dev@uclinux.org

 > To unsubscribe see:
 > http://mailman.uclinux.org/mailman/options/uclinux-dev


--


Greg Ungerer  --  Chief Software Dude   EMAIL:
[EMAIL PROTECTED] 

Secure Computing CorporationPHONE:   +61 7 3435
2888
825 Stanley St, FAX: +61 7 
3891 3630
Woolloongabba, QLD, 4102, Australia WEB: 
http://www.SnapGear.com

___
uClinux-dev mailing list
uClinux-dev@uclinux.org 
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev

This message was resent by uclinux-dev@uclinux.org

To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev





--
srikanth chavali




___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev




___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/ma

RE: [uClinux-dev] why init/do_mounts.c/mount_block_root sys_mountreturn -EFAULT(-14)?

2007-05-14 Thread rui.zhou

hi
 
I am thinking  that why my romfs is unable to be mounted as a root
device.
 
my kernel command line:(I have linked the romfs into the kernel
image,the address below is calculated automatically :)
 
root=/dev/ram0 initrd=0x0c0a235c,139k keepinitrd
 
and I have modified the makefile in which /dev/ram0 will be created.
 
what else I have missed?
 
and just read a article via
http://www.ucdot.org/article.pl?sid=03/01/11/1049210&mode=thread
 
(Phil Wilshire SDCS System Design & Consulting Services
[EMAIL PROTECTED]   )
 
so I am wondering that the /dev/root(ROOT_DEV) was not created
successfully?because no blkmem.c in kernel 2.6,must I enable the MTD
option to make the kernel support romfs?they have any relation?
 
I will appreciate your comments!
 
thanks®ards
rui
 




From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Monday, May 14, 2007 5:31 PM
To: uclinux-dev@uclinux.org
Subject: [uClinux-dev] why init/do_mounts.c/mount_block_root
sys_mountreturn -EFAULT(-14)?


hi guys
 
I got the problem in the init/do_mounts.c
 
static void __init mount_block_root(char *name, int flags)

retry:
for (p = fs_names; *p; p += strlen(p)+1) {
int err = sys_mount(name, "/root", p, flags,
root_mount_data);
printk("VFS: tried fs_name = <%s> err= %d\n",p,err);
 
switch (err) {
case 0:
printk("case 0\n");
goto out;
case -EACCES:
printk("case -EACCESS\n");
flags |= MS_RDONLY;
goto retry;
case -EINVAL:
case -EBUSY:
printk("case -EBUSY &
EINVAL\n");
continue;
}
/*
 * Allow the user to distinguish between failed
open
 * and bad superblock on root device.
 */
printk ("VFS: Cannot open root device \"%s\" or
%s\n",
root_device_name, kdevname (ROOT_DEV));
...
 
well,in a normal 2.4 kernel will get this result:
 
***
VFS: test name =  
VFS: fs_name =  
VFS: fs_name =  
VFS: root name <1f:00> 
***

VFS: tried fs_name =  err= -22(-EINVAL,so it continue to
try mount romfs)
case -EBUSY & EINVAL
VFS: tried fs_name =  err= 0
case 0
 
but in a 2.6.9 kernel have this result:
 
***
 
VFS: test name =  
 
VFS: fs_name =  
 
VFS: fs_name =  
 
VFS: tried fs_name =  err= -14 (-EFAULT,it directly go to
the failure handle)
 
VFS: Cannot open root device "ram0" or unknown-block(0,0)
 
Please append a correct "root=" boot option
 
Kernel panic - not syncing: 1VFS: Unable to mount root fs on
unknown-block(0,0)
 
***
thanks!
rui

___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

[uClinux-dev] why init/do_mounts.c/mount_block_root sys_mount return -EFAULT(-14)?

2007-05-14 Thread rui.zhou

hi guys
 
I got the problem in the init/do_mounts.c
 
static void __init mount_block_root(char *name, int flags)

retry:
for (p = fs_names; *p; p += strlen(p)+1) {
int err = sys_mount(name, "/root", p, flags,
root_mount_data);
printk("VFS: tried fs_name = <%s> err= %d\n",p,err);
 
switch (err) {
case 0:
printk("case 0\n");
goto out;
case -EACCES:
printk("case -EACCESS\n");
flags |= MS_RDONLY;
goto retry;
case -EINVAL:
case -EBUSY:
printk("case -EBUSY & EINVAL\n");
continue;
}
/*
 * Allow the user to distinguish between failed open
 * and bad superblock on root device.
 */
printk ("VFS: Cannot open root device \"%s\" or %s\n",
root_device_name, kdevname (ROOT_DEV));
...
 
well,in a normal 2.4 kernel will get this result:
 
***
VFS: test name =  
VFS: fs_name =  
VFS: fs_name =  
VFS: root name <1f:00> 
***

VFS: tried fs_name =  err= -22(-EINVAL,so it continue to try mount
romfs)
case -EBUSY & EINVAL
VFS: tried fs_name =  err= 0
case 0
 
but in a 2.6.9 kernel have this result:
 
***
 
VFS: test name =  
 
VFS: fs_name =  
 
VFS: fs_name =  
 
VFS: tried fs_name =  err= -14 (-EFAULT,it directly go to the
failure handle)
 
VFS: Cannot open root device "ram0" or unknown-block(0,0)
 
Please append a correct "root=" boot option
 
Kernel panic - not syncing: 1VFS: Unable to mount root fs on
unknown-block(0,0)
 
***
thanks!
rui
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

RE: [uClinux-dev] RE: jffs2 on MCF5208 custom board

Re: [uClinux-dev] Problem linking pthread... undefined referenceto `pthread_create'

Re: [uClinux-dev] Problem linking pthread... undefined reference to `pthread_create'

[uClinux-dev] reloc type unsupported error when building uclinux-dist

Re: [uClinux-dev] RE: jffs2 on MCF5208 custom board

Re: [uClinux-dev] Bad Frame Format

Re: [uClinux-dev] No response after the message "Freeing init memory" on IXP425

[uClinux-dev] compiling interrupt handlers (__irq)

Re: [uClinux-dev] No response after the message "Freeing init memory" on IXP425

Re: [uClinux-dev] Bad Frame Format

[uClinux-dev] Compiling m68k-tools-20061214 on gcc 3.4.4 for x86_64-redhat-linux

Re: [uClinux-dev] No response after the message "Freeing init memory" on IXP425

Re: [uClinux-dev] Bad Frame Format

[uClinux-dev] Problem linking pthread... undefined reference to `pthread_create'

Re: [uClinux-dev] Re: uclinux with RAM size problem

Re: [uClinux-dev] No response after the message "Freeing init memory" on IXP425

RE: [uClinux-dev] why init/do_mounts.c/mount_block_root sys_mountreturn -EFAULT(-14)?

[uClinux-dev] why init/do_mounts.c/mount_block_root sys_mount return -EFAULT(-14)?

18 matches

Site Navigation

Mail list logo

Footer information