So I worked out I was using the wrong addresses and should have used the ones
at the bottom in the [].
Below is the output from the crash and subsequent symbols
0x0005bc0c -- 0x0005bb88 + 0x0084 do_mount
0x00010027 -- 0x0001 + 0x0027 _text
0x0001 -- 0x0001 + 0x _text
0x0001
Thanks for the tip on backtrace. Very handy
Is it common to have so many stacks frames to have 0x as the address?
That seems a bit odd to me.
x0026b02c -- 0x0016f878 + 0xfb7b4 _end
0x -- unknown address
0x -- unknown address
0x -- unknown address
0x0003 -- u
On Mar 2, 2010, at 12:02 AM, Greg Hulands wrote:
> I tried to enable the Full Symbolic/Source Debugging support option in the
> kernel hacking section, but no new info was displayed in the crash. Is this
> only if I connect via gdb to get the symbolic stack?
> I would actually like to work ou
: uclinux-dev-boun...@uclinux.org
> [mailto:uclinux-dev-boun...@uclinux.org] On Behalf Of Greg Hulands
> Sent: Sunday, February 28, 2010 9:55 PM
> To: uClinux development list
> Subject: Re: [uClinux-dev] First timer
>
> Thanks for the reply Greg.
>
> I added
>
> show_stac
sing the M5271 for my project)
>
> - Dan
>
> -Original Message-
> From: uclinux-dev-boun...@uclinux.org
> [mailto:uclinux-dev-boun...@uclinux.org] On Behalf Of Greg Hulands
> Sent: Sunday, February 28, 2010 9:55 PM
> To: uClinux development list
> Subject: Re: [u
ubject: Re: [uClinux-dev] First timer
Thanks for the reply Greg.
I added
show_stack(NULL, (unsigned long *)(fp + 1));
to traps.c. I also ran m68k-uclinux-flthdr on both binaries. Here is the output.
dBUG> go 0x1
Linux version 2.6.29-uc0 (ghula...@office-desktop) (gcc version 4.2.4) #8 Sun
Thanks for the reply Greg.
I added
show_stack(NULL, (unsigned long *)(fp + 1));
to traps.c. I also ran m68k-uclinux-flthdr on both binaries. Here is the output.
dBUG> go 0x1
Linux version 2.6.29-uc0 (ghula...@office-desktop) (gcc version 4.2.4) #8 Sun
Feb 28 20:500
uClinux/COLDFIRE(m528
Dan Snyder wrote:
Greg -
I'm not sure why this is not posted on the web site, but Greg Ungerer posted
the following links on 8/19/2009:
http://www.uclinux.org/pub/uClinux/m68k-elf-tools/m68k-uclinux-tools-20080626.sh
Source here:
http://www.uclinux.org/pub/uClinux/m68k-elf-tools/tools-200806
Hi Greg,
Greg Hulands wrote:
Thanks Gavin. I went searching for where that would be set in a file, but
couldn't see any file stand out in drivers/char that would contain it. Where is
that defined?
I did work out it was 115200 by just testing different baud rates in dBug.
So the kernel boots,
Thanks Gavin. I went searching for where that would be set in a file, but
couldn't see any file stand out in drivers/char that would contain it. Where is
that defined?
I did work out it was 115200 by just testing different baud rates in dBug.
So the kernel boots, but I get the following excepti
Quoth Greg Hulands:
> So I was able to build my first 2.6 kernel using all the defaults - just
> setting freescale and
> mcf5282lite.
>
> When I download the image and then do a go 0x1 all I get is a bit of
> jibberish as if the image is
> corrupt.
Don't forget to check that the serial term
So I was able to build my first 2.6 kernel using all the defaults - just
setting freescale and mcf5282lite.
When I download the image and then do a go 0x1 all I get is a bit of
jibberish as if the image is corrupt.
Do I need to convert the image to a different format first?
THanks,
Greg
O
Looks like I needed to use uC-libc, not glibc (oops!) or uClibc.
What is the difference between uC-libc and uClibc?
Cheers,
Greg
On Feb 26, 2010, at 12:55 PM, Greg Hulands wrote:
> Thanks Dan,
> That helped tremendously. When building the kernel, I now see this error
>
> m68k-uclinux-gcc -m53
Thanks Dan,
That helped tremendously. When building the kernel, I now see this error
m68k-uclinux-gcc -m5307 -DCONFIG_COLDFIRE ../sysdeps/wordsize-32/divdi3.c -c
-std=gnu99 -DEMBED -D__linux__ -D__uClinux__ -Dlinux -Dunix -O2 -Wall -Winline
-Wstrict-prototypes -Wwrite-strings -fgnu89-inline -g
Greg -
I'm not sure why this is not posted on the web site, but Greg Ungerer posted
the following links on 8/19/2009:
http://www.uclinux.org/pub/uClinux/m68k-elf-tools/m68k-uclinux-tools-20080626.sh
Source here:
http://www.uclinux.org/pub/uClinux/m68k-elf-tools/tools-20080626/
Using this vers
Thanks for the reply Adal.
Adding the -n didn't help. I then tried to delete the script at the top of the
file so I was just left with the archive in it. I made sure the first 2 bytes
was the gzip header and then changed the name to elf.tar.gz. Running gzip on it
still produced the same error.
On Fri, Feb 26, 2010 at 04:32, Gregory Hulands wrote:
> I've got a MCF5282 LITE board that I am wanting to teach myself embedded
> programming on. I've been following the steps here to setup the toolchain
> (http://www.uclinux.org/get_started/uClinuxbeginner.html). All of the
> versions of the
On Fri, 2010-02-26 at 04:32 +0100, Gregory Hulands wrote:
> All of the versions of the versions of the tools I've tried to install
> have complained that it isn't a valid bzip2 archive
I'm not sure, but I think something similar had happened to me.
I have to use this:
- m68k-elf-tools-20031003.sh
18 matches
Mail list logo
