Quoth Praveen Chandrasekharaiah [EMAIL PROTECTED]:
> While executing an application on a custom M5272C3 board with 16 Meg
> SDRAM, i get a Bad Frame Format error as soon as i execute the
> application. The RAMFS is configured to 1024K. The
> application size is 793780 bytes. I transfer the applicat
I did double check on the application looking for null pointers memory
leaks. It runs perfectly fine on a linux machine but fails to run on
uClinux when cross compiled for m68k.
Gavin Lambert wrote:
Bad Frame Format usually means your app is accessing invalid memory,
whether through a null poin
Quoth Praveen Chandrasekharaiah [EMAIL PROTECTED]:
> I did double check on the application looking for null
> pointers memory leaks. It runs perfectly fine on a linux machine
> but fails to run on uClinux when cross compiled for m68k.
Are you checking for errors from library functions? Don't for
Hi Praveen,
Praveen Chandrasekharaiah wrote:
While executing an application on a custom M5272C3 board with 16 Meg
SDRAM, i get a Bad Frame Format error as soon as i execute the
application. The RAMFS is configured to 1024K. The application size is
793780 bytes. I transfer the application onto
The stack size is 256 k. I presume this i more than sufficient for my
application. I did try increasing to 1Meg.
Greg Ungerer wrote:
Hi Praveen,
What is the stack usage of the program that crashes?
A common cause of application crashes is over runing the stack.
The default is 4k, so it is not
Hi Praveen,
Praveen Chandrasekharaiah wrote:
The stack size is 256 k. I presume this i more than sufficient for my
application. I did try increasing to 1Meg.
Probably not stack size then.
Are you sure you are compiling it for the correct CPU architecture
varient (I don't recall what your targ
Greg,
:) I am compiling with the correct CPU architecture. A snap shot of my
logs are below:
--
/var/tmp> tftp 192.168.10.80
tftp> binary
tftp> get rrh
Received 793780 bytes in 14.2 seconds
tftp> /var/tmp> chmod 777 rrh
/var/tmp> ./rrh&
[22]
/var/tmp>
Show us the compiler output
add the -v flag to get some more diagnostic information.
Phil
Praveen Chandrasekharaiah wrote:
Greg,
:) I am compiling with the correct CPU architecture. A snap shot of my
logs are below:
--
/var/tmp> tftp 192.168.10.
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 :-)
--
/var/tmp> tftp 192.168.10.80
tftp> binary
tftp> get
Phil & Greg,
Attached is the verbose output of the make command.
Please rename .piz to .zip.
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 be
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 Ch
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 f
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/do
Quoth chris brooke:
> Thanks for your previous help. I've now got my system to boot up
> partially before I get a "bad frame format: ".
>
> I'm using the 2.6.19 kernel on a custom 5272 board. I do not have
> RAM at location 0.
>
> What is the significance of this message?
> What is it
Hi Chris,
chris brooke wrote:
Thanks for your previous help. I've now got my system to boot up
partially before I get a "bad frame format: ".
I'm using the 2.6.19 kernel on a custom 5272 board. I do not have RAM
at location 0.
Send you .config to this list, so we can check the RAM
uclinux.org> Subject: Re: [uClinux-dev] bad
frame format: > > Hi Chris,> > chris brooke wrote:> > Thanks for your
previous help. I've now got my system to boot up > > partially before I get a
"bad frame format: ".> > > >
16 matches
Mail list logo
