Recent Posts

Pages: [1] 2 3 ... 10
µTasker general / Re: output the system CLK
« Last post by mark on June 28, 2020, 01:43:16 PM »

1. The KL03 has the MCG Lite with has an internal oscillator (IRC) that can operate at either 2MHz or 8MHz (in addition to the IRC48M).
The output of this IRC can be divided down by 1, 2, 4, 8,..128.
If SLOW_CLOCK_DIVIDE is defined it should be oe of these values and the clock initiaisation then programs the FCRDIV accordingly. If it is not defined a divide by 1 is defaulted to.
The code that does it is:
    #if defined SLOW_CLOCK_DIVIDE                                        // if a slow clock output divider is specified
    MCG_SC = SLOW_CLOCK_DIVIDE_VALUE;                                    // select the output divider ratio

2. The TPM (used for PWM signal generation) can be clocked from MCGPCLK, OSCERCLK or MCGIRCLK and as long as the chosen clock remains operational  in low power modes the operation continues.

3. The SPI is operated from the bus clock and can continue operation in low power modes that don't stop the bus clock.

4. I don't know whether the IRC48M is disabled automatically when not used, but in the MCG Lite module there is no specific way to disable this clock's operation.



µTasker general / Re: output the system CLK
« Last post by Raffaele on June 26, 2020, 07:06:36 PM »
That worked easily, thanks.

A few quick questions:

1) where is SLOW_CLOCK_DIVIDE used?

2) Can I generate a PWM using the PWM_INTERRUPT_SETUP  but in low power mode (32kHz clock) instead of using the 48MHz?
3) Does low power mode still supports SPI?
4) Can I actually "shut down" the 48MHz clock source?

My goal is to generate a PWM with the lowest power possible and sometimes use SPI.
µTasker general / New Guide to enabling uTasker Serial Loader to update itslef
« Last post by mark on June 21, 2020, 01:59:40 AM »
Hi All

This new guide shows how combining the uTasker Serial Loader with the "Bare-Minimum Loader can allow serial loader updates with a code size overhead as low as 2k Bytes:


µTasker general / Re: output the system CLK
« Last post by mark on June 20, 2020, 11:29:49 AM »

The routine
extern int fnClkout(int iClockSource);
allows controlling the clock out and defaults to PTA12 on the KL03.
However it is not possible to connect the system clock to it; only the BUS clock, IRC48M clock and some low frequency clocks.
To output the bus clock (equal to the Flash clock)
is used.



µTasker general / output the system CLK
« Last post by Raffaele on June 19, 2020, 11:08:26 PM »
simple question, how can I output the system clock on the KL03? Also I am assuming that I can only use PTA4 and PTA12 since they are the only two that have an ALT function called CLKOUT, right?
NXPTM M522XX, KINETIS and i.MX RT / Re: KL27 ROM Bootloader with KDS
« Last post by Phil on June 16, 2020, 06:15:46 AM »
Thank you, Mark.

Most appreciated!
NXPTM M522XX, KINETIS and i.MX RT / Re: KL27 ROM Bootloader with KDS
« Last post by mark on June 16, 2020, 12:22:00 AM »
Hi Phil

When using the KL27's ROM Loader you can load the uTaskerV1.4_FLASH target with the KBOOT utility. The uTaskerV1.4_BM_FLASH target has an offset which the ROM loader doesn't use.


NXPTM M522XX, KINETIS and i.MX RT / KL27 ROM Bootloader with KDS
« Last post by Phil on June 16, 2020, 12:00:23 AM »
Mark, et al,

I am writing firmware for a KL27 with embedded ROM bootloader using KDS.

When writing directly directly into the KL27 using my SEGGER JLINK I using the build configuration uTaskerV1.4_FLASH. Everything works fine.

When using the ROM bootloader, I would think the build configuration changes to uTaskerV1.4_BM_FLASH. When I try to use the ROM bootloader with the newly created BM_FLASH image everything seems to load fine but the KL27 goes into a watchdog-type reset loop upon startup.

Again, when I load using the uTasker1.4_FLASH build configuration using my SEGGER JLINK debugger everything works fine.

Any ideas?


µTasker general / Re: Momentarily disable interrupt routine
« Last post by Raffaele on May 29, 2020, 08:41:58 PM »
I had notifications off for this post.

Always very helpful Mark
µTasker general / Re: Kinestis UART responds 0x17 (DEVICE CONTROL) when receiving
« Last post by mark on May 28, 2020, 10:06:16 PM »
As long as
is enabled the TTY queues can be flushed with

fnFlush(serial_handle, FLUSH_RX);
fnFlush(serial_handle, FLUSH_TX);

The flush is only of SW queues and not the HW peripheral.


Pages: [1] 2 3 ... 10