-
|
Hello, I found the following schematic for the DAPLink debugger with NXP MK20DX128VFM5: I also found the source code that I was able to compile without problem with Keil uVision: However looking on the "IO_config.h" header file...
What are those pins for ? The LEDs are also not defined at the same pins but I guess those are regular GPIO pins that can me mapped to any pins. Thanx in advance ! Best regards Eric |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment · 1 reply
-
|
These extra signals are present on the NXP OpenSDA version of the schematic (OpenSDA is what the Mbed HDK circuit was derived from), and are used for voltage translator control. You can see this circuit in the schematic for the NXP FRDM-K64F board, available here: I didn't actually realise that the Mbed HDK version of the K20 circuit was missing the voltage translators. Apparently it will still work, just with some toggling of unconnected pins. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot for your answer Chris ! |
Beta Was this translation helpful? Give feedback.
These extra signals are present on the NXP OpenSDA version of the schematic (OpenSDA is what the Mbed HDK circuit was derived from), and are used for voltage translator control.
You can see this circuit in the schematic for the NXP FRDM-K64F board, available here:
https://www.nxp.com/design/development-boards/freedom-development-boards/mcu-boards/freedom-development-platform-for-kinetis-k64-k63-and-k24-mcus:FRDM-K64F
I didn't actually realise that the Mbed HDK version of the K20 circuit was missing the voltage translators. Apparently it will still work, just with some toggling of unconnected pins.