Page 1 of 2
Problem with first test application on MPC5643L
Posted: Wed Feb 19, 2014 4:12 pm
by Oleg
Hello All.
Several days in row i'll tryed to compile RT-Druid test project, but I have a problem with compilation.
I create project this way: File -> New RT-Druid OIL and C/C++ Project -> set "CygwinGCC" -> Create a Project using one of these templates - set "e200z4" -> task_demo
Project is generate ok, but compilation filed with a problem
/bin/sh: /usr/bin/PA_Tools/Command_Line_Tools/mwcceppc: No such file or directory
make: *** [obj/obj/pkg/mcu/freescale_mpc5643l/src/ee_boot_asm.o] Error 127
I using IDE and compiler, downloaded from ERIKA site:
1)Eclipse IDE for C/C++ Developers
Version: Juno Release
Build id: 20120614-1722
2)eeCygwin_1_7_9
Why It can'n find compiler? May be I do some thing wrong?
Can someone help me solve this problem?
Many thanks
Re: Problem with first test application on MPC5643L
Posted: Wed Feb 19, 2014 4:43 pm
by fesposito
Dear Oleg,
as stated in
http://erika.tuxfamily.org/wiki/index.p ... (MPC_56xx), we currently support "CodeWarrior Development Studio for MCU version 10.2" under Win.
Please can you provide your compiler version and the Freescale web page from which you have downloaded the compiler. Please specify the exact version of the compiler you are currently
using (e.g. Evaluation, Special Edition, Classic, etc)
Regards
Re: Problem with first test application on MPC5643L
Posted: Thu Feb 20, 2014 9:54 am
by Oleg
Thanks for the answer,
The article said that Windows supports CodeWarrior v2.7 and CodeWarrior v10.2 under linux. But you said, that you use CW 10.2 under windows, I understood correctly?
quote from this link:
http://erika.tuxfamily.org/wiki/index.p ... (MPC_56xx)
Supported compilers
WindRiver DIAB C Compiler 5.5.1 and 5.8.0.
Freescale CodeWarrior:
Windows: CodeWarrior Development Studio for MPC55xx/56xx 2.7
Linux: CodeWarrior Development Studio for MCU 10.2
But the problem is that on the Freescale website (
http://www.freescale.com/webapp/sps/sit ... Tools_Tab#) No download links v10.2 or v2.7, there are only v10.3.3, v10.5 and v2.1.
Please show me where to get the version 10.2 or maybe 10.3.3 is suitable too?
Re: Problem with first test application on MPC5643L
Posted: Thu Feb 20, 2014 12:02 pm
by fesposito
Dear Oleg,
Freescale compiler versions are constantly updated. This solution works for me:
1) Download the CW_MCU_v10.5 Special Edition (Eclipse based - No time limitation, only size limitation) for Windows environment
2) Run your RT-Druid, click on Window -> Preferences -> RT-Druid
In this sub-menu check the following: "cygwin path" and "compiler path". For instance in my case:
Cygwin Installation C:\cygwin
Under Oil -> e200ZX -> Codewarrior Compiler Path C:\Freescale\CW MCU v10.5\MCU
There is also a license issue, to solve the problem please modify this RT-Druid file (it will be fixed in the next RT-Druid Release, but now modify the file manually):
C:\eclipse_rtdruid\plugins\com.eu.evidence.ee_2.1.0.20130518_2201\ee_files\pkg\cfg\arch\cc_ppc_codewarrior.mk (your path is slightly different probably...)
This is the line to be modified:
# OPT_AR: options for library generation
OPT_AR = -library -o
In this way:
# OPT_AR: options for library generation
OPT_AR = -library $(OPT_TARGET) -o
This configuration works ok. Thanks for your notes, we will modify the wiki soon.
Let me know
Ciao
Re: Problem with first test application on MPC5643L
Posted: Fri Feb 21, 2014 9:35 am
by Oleg
Thanks for answer. I will try do it.
Recently I installed CW 10.3.3 Evalution. I have modified the makefile string, put this
C:\Freescale\CW_PA_v10.3.3\PA
instead
C:/default/path
in
$(eval $(call check_and_set_cygwin_compiler_path,PPC_CW_BASEDIR,C:/default/path))
So we get
$(eval $(call check_and_set_cygwin_compiler_path,PPC_CW_BASEDIR,C:\Freescale\CW_PA_v10.3.3\PA))
Now RT-Druid eclipse use CW 10.3.3 compiler, and the build succeeds.
What do you think this configuration can be used?
Re: Problem with first test application on MPC5643L
Posted: Fri Feb 21, 2014 9:45 am
by paolo.gai
Well ... if it works why not !
The reason why we list only specific versions of a compiler is because that is the version we tested in our setups.
Could you add a few lines to the PPC wiki explaining what you did?
Ciao,
PJ
Re: Problem with first test application on MPC5643L
Posted: Fri Feb 21, 2014 9:57 am
by fesposito
Hi Oleg,
it works ok but such makefile is auto-generated, hence you have to modify it manually every time you change your oil configuration. If you set it up on RT-Druid IDE, the makefile will be "auto-generated" properly.
Another question, did you experience any license issue with such evaluation compiler? ...i suppose you did not modify the cc_ppc_codewarrior.mk as i previously reported, please let me know since we are collecting all possible feedbacks.
Regards
Francesco
Re: Problem with first test application on MPC5643L
Posted: Fri Feb 21, 2014 3:22 pm
by Oleg
Hello Francisco. As you advised:
fesposito wrote:...
Under Oil -> e200ZX -> Codewarrior Compiler Path C:\Freescale\CW MCU v10.5\MCU
There is also a license issue, to solve the problem please modify this RT-Druid file (it will be fixed in the next RT-Druid Release, but now modify the file manually):
C:\eclipse_rtdruid\plugins\com.eu.evidence.ee_2.1.0.20130518_2201\ee_files\pkg\cfg\arch\cc_ppc_codewarrior.mk (your path is slightly different probably...)
This is the line to be modified:
# OPT_AR: options for library generation
OPT_AR = -library -o
In this way:
# OPT_AR: options for library generation
OPT_AR = -library $(OPT_TARGET) -o
Ciao
I Did all of this, but there is new problem - Build faults:
C:\eclipse\plugins\COMEUE~4.201\ee_files\pkg\cpu\e200zx\inc\ee_regs.h:112: "Unknown CPU"
C:\eclipse\plugins\COMEUE~4.201\ee_files\pkg\cpu\e200zx\src\ee_ivor.S:66: "Unknown CPU"
C:\eclipse\plugins\COMEUE~4.201\ee_files\pkg\cpu\e200zx\src\ee_ivor.S:108: Instruction is not legal in a PowerPC VLE section
C:\eclipse\plugins\COMEUE~4.201\ee_files\pkg\cpu\e200zx\src\ee_ivor.S:113: Unknown identifier, E200ZX_IRQ_VECTOR_BASE_ALIGN
C:\eclipse\plugins\COMEUE~4.201\ee_files\pkg\cpu\e200zx\src\ee_ivor.S:115: Unknown identifier, E200ZX_IRQ_ENTRY_ALIGN
What may cause this faults?
Regards
Re: Problem with first test application on MPC5643L
Posted: Fri Feb 21, 2014 3:45 pm
by fesposito
Dear Oleg,
Are those errors introduced by your last patch? I mean, after:
1) Under Oil -> e200ZX -> Codewarrior Compiler Path C:\Freescale\CW MCU v10.5\MCU
2) OPT_AR = -library $(OPT_TARGET) -o
What if you remove points "1 and 2" one at a time.
Please consider that my compiler is different from your one, if the problem persists i need additional time to set up your environment.
Francesco
Re: Problem with first test application on MPC5643L
Posted: Fri Feb 21, 2014 4:56 pm
by Oleg
fesposito wrote:Dear Oleg,
Are those errors introduced by your last patch? I mean, after:
1) Under Oil -> e200ZX -> Codewarrior Compiler Path C:\Freescale\CW MCU v10.5\MCU
2) OPT_AR = -library $(OPT_TARGET) -o
What if you remove points "1 and 2" one at a time.
Please consider that my compiler is different from your one, if the problem persists i need additional time to set up your environment.
Francesco
I rename
C:\Freescale\CW MCU v10.5\MCU to
C:\Freescale\CW_MCU_v10.5\MCU, but there is error - No such file or directory. Also I treed C:\Freescale\CW_MCU_v10.5\MCU\PA_Tools, but it dose not work anyway.
I tried to return the items 1 and 2 back, but it did not work with the compiler version 10.5 SE. Then again unpacked RT-Druid and prescribed path to the compiler version 10.3.3 - the project is successfully built.
Re: Problem with first test application on MPC5643L
Posted: Mon Feb 24, 2014 8:47 am
by fesposito
Dear Oleg,
if your setup works, feel free to use it. But, can you confirm the following:
1) you are using the latest version of RT-Druid
2) You are using the 10.3.3 Evaluation Version Codewarrion for Power Architecture
3) after makefile generation, you manually modify such makefile as you reported in one of your post: $(eval $(call check_and_set_cygwin_compiler_path,PPC_CW_BASEDIR,C:\Freescale\CW_PA_v10.3.3\PA))
4) You didn't setup PPC_CW_BASEDIR
Please let me know
Francesco
Re: Problem with first test application on MPC5643L
Posted: Mon Feb 24, 2014 1:48 pm
by Oleg
Hello everyone.
So, I decided to stay at the working configuration - CW 10.3.3 + RT_DRUID_Eclipse. As such, the project builds without any problems.
I have a board TRK-USB-MPC5643L with OSBDM debugger, I'm trying to debug, but it pops up an error message:
Error while launching command: - version
I understand that there must be some debugging program, but either it is not installed with RT_DRUID_Eclipse assembly or version is not suitable, or the path to it is registered incorrectly.
What am I doing wrong, how do I start debugging?
Thank you for help
Re: Problem with first test application on MPC5643L
Posted: Mon Feb 24, 2014 2:06 pm
by Oleg
fesposito wrote:
if your setup works, feel free to use it. But, can you confirm the following:
1) you are using the latest version of RT-Druid
2) You are using the 10.3.3 Evaluation Version Codewarrion for Power Architecture
3) after makefile generation, you manually modify such makefile as you reported in one of your post: $(eval $(call check_and_set_cygwin_compiler_path,PPC_CW_BASEDIR,C:\Freescale\CW_PA_v10.3.3\PA))
4) You didn't setup PPC_CW_BASEDIR
Please let me know
Francesco
Hello, Francesco
1) I use RT-Druid v.2.2.0.20131218_1320. If it necessary, I wiil install latest version.
2) YES
3) No, I made changes to the settings (Windows - Preferences - RT-Druid - OIL - E200Zx), and the file itself is generated correctly.
4) No, I didn't. I dont know where to setup PPC_CW_BASEDIR and how.
Re: Problem with first test application on MPC5643L
Posted: Mon Feb 24, 2014 2:18 pm
by fesposito
Dear Oleg,
unfortunately we provide debug support only for Lauterbach. But i encountered a problem similiar to the one you are experiencing with your debugger right now. In my case the debugger was the P&E solution provided by Freescale with their EVBs. In order to set up a suitable debugging environment we had to import the debug configuration generated by Freescale Codewarrior for a dummy project into our project. Do you have a dummy project for your debug system? In general they are provided by the vendor, try to start from it. Sorry for my poor response, but it is very difficult for me replicate the issue here without debugger.
Try to open a new topic in our forum.
Concerning point 4) PPC_CW_BASEDIR is not always necessary, depends on how you configure your environment. Hence no problem....
Ciao
Francesco
Re: Problem with first test application on MPC5643L
Posted: Tue Feb 25, 2014 10:49 am
by Oleg
Many thanks!
I continue attempts launch the project with Debug Using OSBDM Debuger