Re: [coldfire-gnu-discuss] uClinux & ColdFire pthread debugging using CodeSourcery 4.4-53

[Maxim Kuvyrkov <maxim@xxxxxxxxxxxxxxxx>]

On 3/9/10 9:11 AM, Harry Gunnarsson wrote:
...
> Now I am trying to get the latest uclinux.org <http://uclinux.org>
> distro from 2009 running (kernel 2.6.[29-31]). The main reason is to
> look into improvements (kernel, busybox etc) in general (stability) and
> JFFS2 enhancements in general.
> - uClinux 2009 distro
> - CodeSourcery 4.4-53

How do you build your applications (especially the ones that you trying 
to debug with CodeSourcery's tools)?

To get a reliable uClinux system you need to build the binaries with the 
same tools you then try to debug them with.

> My port seems to work well in all aspects except for debugging
> multi-thread user apps.
> I have tried many permutations of target build flags (-mcpu, -m etc),
> and according to CS website it seems recommended to -m5208 runtime with
> M5272 ColdFire. Therefore, I have lately tried '-mcpu=5272' for .c
> sources and '-m5208' during link.

A side note: just specifying -mcpu=<your cpu, 5272 in this case> 
consistently to the compiler is the best approach.  Also, it is highly 
recommended to use the compiler driver (m68k-uclinux-gcc or 
m68k-uclinux-g++) to link the programs -- that way the driver will 
invoke the linker with the correct set of utility libraries; using the 
linker directly is error-prone to picking up the libraries for a 
different CPU.

Regards,

--
Maxim Kuvyrkov
CodeSourcery
maxim@xxxxxxxxxxxxxxxx
(650) 331-3385 x724