topic Re: Strange problem with LTIB in ColdFire/68K Microcontrollers and Processors

Strange problem with LTIB

JimDon — Wed, 25 Jun 2008 01:49:11 GMT

I am using the version that comes with the M2277EVM BSP.

It keeps forgetting the path to the complier. It seems to save it in the config file, but when I go back to config mode again, it is blank, so I would say it fails to read it back.

It does remember the compiler prefix ok.
I am using the compiler that comes with CW for Linux, so the path is pretty long. Is there a length limit?

Re: Strange problem with LTIB

mwaddel — Wed, 25 Jun 2008 02:31:26 GMT

Is there an entry in the config/platform/m5227xevb/defconfig.dev
file after you save the configuration? When I select the custom
toolchain option and save this is what I see in the that file:

...
#
# Toolchain selection.
#
# CONFIG_TOOLCHAIN_68KNOMMU_UCLIBC1 is not set
CONFIG_TOOLCHAIN_68KNOMMU_CUSTOM=y
CONFIG_CUSTOM_TOOLCHAIN=y
CONFIG_TOOLCHAIN_PATH="/opt/freescale/usr/local/gcc-4.2.20-uclibc-0.9.20/m68k-uclinux/"
CONFIG_CUSTOM_TOOLCHAIN_PREFIX="m68k-uclinux-"
CONFIG_TOOLCHAIN_PREFIX="m68k-uclinux-"
CONFIG_TOOLCHAIN_CFLAGS=""
...

If the CONFIG_TOOLCHAIN_PATH isn't correct then there could be a problem
in LTIB.

--Matt

Re: Strange problem with LTIB

JimDon — Wed, 25 Jun 2008 02:36:23 GMT

Yes, it goes into the config file and the build works.
And it does seem to be in the config file if you look.
I just have to put it back each time I go into config, as it is blank.

Re: Strange problem with LTIB

JimDon — Thu, 29 Oct 2020 09:14:58 GMT

Code:

#
# Choose your toolchain
#
# CONFIG_TOOLCHAIN1 is not set
CONFIG_TOOLCHAIN_CUSTOM=y
CONFIG_TOOLCHAIN_PATH="/opt/freescale/usr/local/gcc-4.2.47-uclibc-0.9.47/m68k-uclinux"
CONFIG_CUSTOM_TOOLCHAIN_PREFIX="m68k-uclinux-"
CONFIG_TOOLCHAIN_PREFIX="m68k-uclinux-"
CONFIG_TOOLCHAIN_CFLAGS="-mcpu=5329 -DCONFIG_COLDFIRE"

And after running --config

# Choose your toolchain
#
# CONFIG_TOOLCHAIN1 is not set
CONFIG_TOOLCHAIN_CUSTOM=y
CONFIG_TOOLCHAIN_PATH=""
CONFIG_CUSTOM_TOOLCHAIN_PREFIX="m68k-uclinux-"
CONFIG_TOOLCHAIN_PREFIX="m68k-uclinux-"
CONFIG_TOOLCHAIN_CFLAGS="-mcpu=5329 -DCONFIG_COLDFIRE"

BTW Should I clear the CFLAGS like you did?

Re: Strange problem with LTIB

JimDon — Thu, 29 Oct 2020 09:15:00 GMT

Well, here is part of the problem:
If I enter the path as:

/opt/freescale/usr/local/gcc-4.2.47-uclibc-0.9.47/m68k-uclinux/
It remembers it.
However then the build fails:

Code:

Found m68k-uclinux-gcc through your PATH at:/opt/freescale/usr/local/gcc-4.2.47-uclibc-0.9.47/m68k-uclinux/bin/m68k-uclinux-gccExpected to find it at:/opt/freescale/usr/local/gcc-4.2.47-uclibc-0.9.47/m68k-uclinux//bin/m68k-uclinux-gcc

If I leave off the '/' at the end the build works...but it forgets the path.
On the other hand, if I use:
/home/myusername/CodeSourcery/Lite
(where I installed the download from CodeSourcery)
It both remembers it and works, so something is up with LTIB and the path name.

Message Edited by JimDon on 2008-06-24 10:32 PM

Message Edited by JimDon on 2008-06-24 10:39 PM

Re: Strange problem with LTIB

mwaddel — Wed, 25 Jun 2008 22:53:03 GMT

Hi Jim,

With these instructions I was able to duplicate the failure you are seeing. I
also noticed, the TOOLCHAIN_CFLAGS setting disappears also.

I think I've found the problem and I've sent a solution to the LTIB developer.
I want to make sure the fix doesn't break something else. I'll let you know
as soon as it's ready.

In case you're interested, there is a specific LTIB developers mailing list at:
http://savannah.nongnu.org/projects/ltib/

Regards,
Matt

Re: Strange problem with LTIB

JimDon — Wed, 25 Jun 2008 23:03:55 GMT

Wow! Thank you!!!!

I do subscribe to that list, but I thought since it was a Freescale distro, somebody here might be more interested in looking at it.

Now I am a little paranoid that other settings might have been changed from the default. I am new to this, and it is a bit overwhelming at first, so I have been just trying to duplicate the original images with default settings.

Please advise when and where I can get the update for this.