Blaze

Blaze is based on the K22FN1M0VLH12 which is a 120MHz device from the performance and integration K22 Kinetis family with Cortex-M4 core and USB. This K22 device has 1M Flash and 128k SRAM and is in a 64 pin LQFP, whereby the K22 is also available in 80, 121 or 144 pin housings and its memory ranges from 128k...1M Flash with 24k...128k SRAM (100MHz and 120MHz parts). There is an 16MHz crystal on the board for clocking the part. The K22 supports crystal-less FS USB device based on its internal 48MHz IRC48M oscillator and USB clock recovery.

Full details and documentation for this board can be obtained from the Blaze web site: Blaze. Blaze is a Kickstart crowd-funded project detailed at Blaze Kickstarter.

To configure the µTasker project for this board simply enable the define BLAZE_K22 in the project's config.h file. The compiler needs to be set to build for Cortex M4 (and not Cortex M0+) and the linker script K_1M_128.ld should be selected [K_1M_128_Blaze.ld for downloadable version] {the linker script extension may vary for different compilers, whereby *.ld is valid for GCC}

Blaze Binaries

Blaze framework and composite USB

This binary shows various features of the Blaze hardware and the µTasker project, with emphasis on composite USB operation:

The binary image can be loaded to Blaze using the Blaze Firmware Updater uTaskerV1.4.12_Blaze.bin [134k]

The configuration was configured using the following defines:

  • BLAZE_K22 to select the hardware platform (TFT and touch are enabled by default)
  • SDCARD_SUPPORT to enable utFAT and SD-card operation
  • USB_INTERFACE to enable general USB device support
  • USE_USB_CDC and USB_CDC_VCOM_COUNT 1 to enable USB-CDC class with a single virtual COM port
  • USE_USB_MSD to enable USB-MSD class operation
  • USB_CDC_RNDIS to enable RNDIS class
  • USB_TO_TCP_IP to enable RNDIS operation together with the internal TCP/IP stack and its services

Note that RNDIS requires a manual installation of the USB device as described in chapter 10 of µTasker - RNDIS
No driver is required for USB-CDC with Windows 10.For previous operating systems the following drivers can be used



Blaze USB Audio

This binary shows the Blaze operating as a USB audio device. When connected to a PC the Blaze appears as an audio output and sound is passed via it to drive its DAC output EXT.DAC. When there is no sound the output is at 1.6V (half-rail). It can be connected (prefereably through a capacitor) to an external amplifier and speaker in order to hear music or other audio signals.

The binary image can be loaded to Blaze using the Blaze Firmware Updater uTaskerV1.4.12_Blaze_USB_Speaker.bin [60.6k]

The configuration was configured using the following defines:

  • BLAZE_K22 to select the hardware platform (TFT and touch are enabled by default)
  • USB_INTERFACE to enable general USB device support
  • USE_USB_AUDIO to enable USB-Audio class with its output connected to DAC0
Technical notes:
- Asynchrous audio synchronisation is performed, based on PIT0, so that there is no drift as described in µTasker - USB Audio
- The received 16 bit PCM data is converted on-the-fly to 12 bit with level shift to match the DAC and then transferred to the DAC using free-running DMA.

- No USB driver is required for USB-Audio on the PC.

This second binary image performs the same USB-audio function but uses the display to show the waveform similar to an oscilloscope (timebase of screen width is 10ms) in the upper half of the screen. The lower half of the screen shows an FFT (frequency spectrum 0..24kHz) of the same signal which is updated in real-time to display the complete audio information of the signal being listened to - uTaskerV1.4.12_Blaze_USB_Speaker_analyser.bin [83k]



Blaze Digital Watch

This binary shows the Blaze operating as a simple digital watch, with time and date display. When connected to a PC the Blaze appears as vitual COM port with a command line menu, including the possibility to configure the date and time in its administrator menu.

The binary image can be loaded to Blaze using the Blaze Firmware Updater [left display] uTaskerV1.4.12_Blaze_digital_watch.bin [67.5k]
A second binary image with larger font [right display] uTaskerV1.4.12_Blaze_digital_watch_1.bin [67.5k]

The configuration was configured using the following defines:

  • BLAZE_K22 to select the hardware platform (TFT and touch are enabled by default)
  • USB_INTERFACE to enable general USB device support
  • USE_USB_CDC to enable CDC class with command line interface
  • SUPPORT_RTC to enable RTC support in the project
  • BLAZE_DIGITAL_WATCH to enable the digital watch operation
Technical notes:
- The RTC loses its time when the power is removed. Since the power supply (or battery) needs to remain attached, a complete application would need to set the processor to a very low power mode to preserve power but allow the clock to be maintained. Very low power modes can be set in the administrator menu for test purposes.



Blaze Simulation

A Blaze simulation showing GLCD emulation mode, USB, SD card and UART operations can be executed by unzipping the following package. The program uTaskerV1.4.11_Blaze.exe can be executed by double-clicking on it and no further installation is required.


Return to the Kinetis landing page


µTasker Kinetis Blaze support. Copyright (c) 2004..2016 M.J.Butcher Consulting