Gustav
The USBDM includes a USB-CDC to UART bridge to the KL25 and so the KL25 is communicating via UART. This means that the USBDM is not a design reference in this sense.
In the uTasker project you would send a sample to the UART output by changing the code from your version (although preferably not located in the IRQ):
Your code:
AD1_Measure(TRUE);
AD1_GetValue16(&leitura);
Term1_SendNum(leitura);
Term1_SendStr("\r\n");
to
uTasker code:
AD1_Measure(TRUE);
AD1_GetValue16(&leitura);
fnDebugHex(leitura, (sizeof(leitura) | WITH_CR_LF)); // per default this is sent to the UART debug output
To send it to a USB-CDC output instead USB-CDC would be added to the project using the defines:
#define USB_INTERFACE
#define USE_USB_CDC
#define USB_CDC_COUNT 1 (can be 1 to 7 on the Kinetis)
Then the code would redirect to a USB-CDC interface instead by doing:
DebugHandle = USBPortID_comms[0]; // where there can be up to 7 to choose from
AD1_Measure(TRUE);
AD1_GetValue16(&leitura);
fnDebugHex(leitura, (sizeof(leitura) | WITH_CR_LF)); // this is now set to the defined USB-CDC connection
So to use USB-CDC in the uTasker project you need to add one line of code to set the output to be used (after enabling the framework support with three defines).
See also the FRDM-KL25Z binaries at µTasker Kinetis FRDM-KL25Z support which includes a 3 way USB-CDC composite UART bridge configuration that you can try on your FRDM-KL25Z.
Regards
Mark
Kinetis: µTasker Kinetis support
KL26: µTasker Kinetis FRDM-KL26Z support / µTasker Kinetis Teensy LC support
ADC/DAC: http://www.utasker.com/docs/uTasker/uTaskerADC.pdf
USB User's Guide: http://www.utasker.com/docs/uTasker/USB_User_Guide.PDF
Composite USB: µTasker USB Device Configuration
For the complete "out-of-the-box" Kinetis experience and faster time to market