no generated PEx files

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

no generated PEx files

Jump to solution
866 Views
oleglavrukhin
Contributor IV

Hello, community! at now i studying Processor Expert, i think it's very convient development tool! but i have some question about use Processor Expert in Kinetis Design Studio with KSDK.

I make a new project for FRDM-K64F: at first, i select a "board -> Kinetis ->FRDM-K64F", then i select "Kinetis SDK" and "Processor Expert" in "Rapid Application Development" tab, because i want to use KSDK librarys and PEx "component selector" together. When  i generated PEx code, and try to added some component (I2C and very interesting component "ExternalFile") and make some troubles:

1) component "fsl_I2C":

i found example code for I2C in KDSK "demos" folder and create my own project based on this example. After  i added "fsl_I2C" and make a setting, i write simply code for read registers from built-in accelerometer, but program don't work.  I found the missing file "fsl_i2c_irq.c" in my project, but that was present in Demo project. after i copy this file to my project, program start working. of course, I2c need IRQ!

MY QUESTION:  why when generating code for the component (fsl_I2C), code for additional components that are required for it to work NOT generated?

 

2) component "ExternalFile":

after build i have errors: unknown type name 'dword', "byte", i.e. this component need a definition from "PE_Types.h". i added this file to project (in "source" folder and in EFil1.h (#include PE_Types.h) . now project building is OK.

MY QUESTION:  why when generating code for the component (ExternalFile), code for additional components that are required for it to work NOT generated?

Thanks,

Oleg

Labels (1)
Tags (1)
0 Kudos
1 Solution
456 Views
oleglavrukhin
Contributor IV

Thanks for Eduardo Umana and Jorge_Gonzalez,Technical Support Engineer, who answered on my question in  Processor Expert Generated Interrupts

Really, "Right now PEx + KSDK does not generate ISR functions". but why this fact is not in present in KDS User Guide or another Freescale document ???!!!

What other secrets hides Freescale company from developers?

Now I spend time on the study of examples ....:smileyangry:

View solution in original post

0 Kudos
4 Replies
456 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

hi Oleg,

can you please upload the demo project you worked with, thus I can check the problem directly here?

thanks!

Best Regards,

Zhang Jun

0 Kudos
456 Views
oleglavrukhin
Contributor IV

Hello, Zhang Jun!

in attached  first_step.zip you can see structure of my project, which i make as written above. it does not contain fsl_i2c_irq.c after generated code. But in Demo project (SDK_Demo) this file is present. when i debugging, application is hanging, because it does not process the interrupt. After i add this file manually from C:\Freescale\KSDK_1.0.0\platform\drivers\i2c\fsl_i2c_irq.c, application is work.

Demo project i found in C:\Freescale\KSDK_1.0.0\demos\i2c_comm\master\kds\frdmk64f120m.

some situation with component "ExternalFile".

So, to start using the components I need to thoroughly examine not only documentation, but also find all the necessary files for it to work using examples.

now I understand why Erich Styger uses its own components which describes in detail on his website "MCU on Eclipse | Everything on Eclipse, Microcontrollers and Software"

Regards, Oleg

p.s. now i try to use fsl_sai and I hope that it will be less of a problem

0 Kudos
457 Views
oleglavrukhin
Contributor IV

Thanks for Eduardo Umana and Jorge_Gonzalez,Technical Support Engineer, who answered on my question in  Processor Expert Generated Interrupts

Really, "Right now PEx + KSDK does not generate ISR functions". but why this fact is not in present in KDS User Guide or another Freescale document ???!!!

What other secrets hides Freescale company from developers?

Now I spend time on the study of examples ....:smileyangry:

0 Kudos
456 Views
vfilip
NXP Employee
NXP Employee

Hello,

both 1) 2) issues are already fixed in 1.1.0-GA release.

1) We still do not add these file in 1.1.0-GA but PEx now generates these routines and they are available in Events.c file either as ISR or callback functions. This is general improvement in 1.1.0-GA for all PEx SDK components included in this release.

(only exception is pit driver, for this driver is irq.c file included in library so we add it always, this exception should be removed in next release)

2) External file does not need the PE_Types.h in 1.1.0-GA SP.

We are sorry for inconvenience.

best regards

Vojtech Filip

0 Kudos