Hi everyone,
I am using KDS IDE 3.0 and I am using PE to disable a pull up on PTA4, but I am monitoring this PIN and its pulled up.
I made sure I don't have a that pin pulled in my circuit, so that discounts that it a hardware/physical issue. I would like
to view the actual code that PE is generating to disable the pullup, but I can't find it? In what file is this located?
Hi Neil,
Can you please share which device are you using? also, are you using KSDK software or just PEX without KSDK?
Regards,
Adrian
Hi Adrian,
At this point, I am not really sure what I am using? I don't know if I am using PEX (what is this???) or KSDK?
What I can tell you for sure is that I am working with the KDS 3.0.
I am so confused with all this naming conventions KDS....KSDK....PE....PEX.... sorry but this whole thing is alien to me.
Thank you.
Hi,
Yes, I know there so many acronyms for our products that you can easily get confused. Just to clarify:
You can find more information about this difference HERE
Some devices are only supported by the PEx + KSDK but some others are supported by the two PEx options. Which microcontroler are you using?.
Regards,
Adrian
So, then
In my case I am using : PEx+SDK 3.0 and the processor MK64FX512VLL12.
The colleague David Seymour has given you the hints to find the configurations done by PEx to configure the pin. Please let us know if that answer your questions.
Regards,
Adrian
Ok,
On the KDS 3.0 Help->Installation Details->Processor Expert for Kinetis (3.0.0.RT7_b1515-0427).
Under Processor Expert for Kinetis->Processor Expert Kinetis SDK Support (1.2.0.RT7_b1515-0427).
Hope this helps.
Hi Neil,
KDS = Kinetis Design Studio which is eclipse based IDE and uses ARM GNU GCC compiler tools.
KSDK = Kinetis Software Development Kit.....it has the static peripheral software to access the Kinetis on-chip peripherals at low and high levels.
PE (Processor Expert) is integrated into KDS. It is a GUI based initialization tools. In general it will be used to generate configuration information to be used with the KSDK peripheral software. PE does have some legacy support for a few devices and in those cases the KSDK is not being used.
PEX is a standalone version of the PE.
When using PE to configure your GPIO pin, after you configure components, then generate the code, in your Generated_Code folder you should have a file that has the code to initialize the pin.
My test code was based on KDS_3.0, KSDK_1.2, PE....I added a fsl_gpio Component and configured the PTB1 to first have pull resistor enabled and had it configured for pull-down. The generated code looks like:
const gpio_input_pin_user_config_t gpio1_InpConfig0[] = {
{
.pinName = B77,
.config.isPullEnable = true,
.config.pullSelect = kPortPullDown,
.config.isPassiveFilterEnabled = true,
.config.isDigitalFilterEnabled = true,
.config.interrupt = kPortIntDisabled
},
{
.pinName = ptb1_test,
.config.isPullEnable = true, <- Pull enabled
.config.pullSelect = kPortPullDown,
.config.isPassiveFilterEnabled = true,
.config.isDigitalFilterEnabled = true,
.config.interrupt = kPortIntDisabled
},
{
.pinName = GPIO_PINS_OUT_OF_RANGE,
}
};
Then when I disable the pull resistor (the PE terminology is Pull enable) the code changes to following:
const gpio_input_pin_user_config_t gpio1_InpConfig0[] = {
{
.pinName = B77,
.config.isPullEnable = true,
.config.pullSelect = kPortPullDown,
.config.isPassiveFilterEnabled = true,
.config.isDigitalFilterEnabled = true,
.config.interrupt = kPortIntDisabled
},
{
.pinName = ptb1_test,
.config.isPullEnable = false, <- Pull disabled
.config.pullSelect = kPortPullDown,
.config.isPassiveFilterEnabled = true,
.config.isDigitalFilterEnabled = true,
.config.interrupt = kPortIntDisabled
},
{
.pinName = GPIO_PINS_OUT_OF_RANGE,
}
};
Adrian was asking you what Kinetis device you are using? Example: K60.
If you are using a Freedom or Tower board please mention it specifically as it allows others to help you more easily.
Regards,
David
Thank you David.
I don't know if you had replied before seeing my reply above: MK64FX512VLL12