Tag Archives: Tips&Tricks

About things you might not know, or could make your life easier.

Segger J-Link OpenSDA Firmware with Virtual MSD

Posted on by
3

Sometimes it is very convenient to load a new firmware to a board without the need for a hardware debugger. This is usually done with a bootloader. The NXP Freedom and Tower evaluation boards have on-board debug device/microcontroller (OpenSDA) which can load different firmware implementations like CMSIS-DAP/mbed, P&E Multilink or a Segger J-Link OpenSDA applications. Both mbed and P&E implemenations support to program the board with drag&drop: simply send a file to a virtual MSD (Mass Storage Device) to get it programmed. The latest Segger OpenSDA firmware has this ability added now too: Programming the board with a virtual MSD device:

Virtual MSD Device

Virtual MSD Device

Continue reading →

Tutorial: BBQ Pulled Pork

Posted on by
8

So this is my current week-end BBQ project: Pulled Pork out of the BBQ smoker :-). As a teaser, this is how the result looks like: tender, juicy slow-cooking smoked pork meat out of the smoker:

Pulling the pork

Pulling the pork

Pulled Pork Sandwich

Pulled Pork Sandwich

Continue reading →

Combining Multiple NXP Kinetis SDKs into One

Posted on by
6

My wife tells me that I have too many boards on my desk. That is only *partially* correct: there are many, but not *too* many. But I’m working on too many tasks, but that’s a different aspect :-). I’m using more and more the Kinetis SDK V2.0, and as a result of this I have multiple SDKs installed on my machine. Because with the SDK V2.0 I get a download for each device/board installed (see “First NXP Kinetis SDK Release: SDK V2.0 with Online On-Demand Package Builder“). So my list of SDK folders is growing, as shown with the ‘New SDK 2.x’ wizard in Kinetis Design Studio:

Multiple Kinetis SDKs

Multiple Kinetis SDKs

The same time, the amount of free disk space is reducing. What if I could combine all these SDK’s?

Continue reading →

Tutorial: Muxing with the New NXP Pins Tool

Posted on by
26

I don’t know if it is the same for you. But for me, configuring the pins on these new ARM microcontroller is a challenge: Most pins can do multiple functions, such as be used as I²C, UART or GPIO pins.

Configuring the pins ‘by hand’ is difficult, error-prone and usually the first thing I need to do for a new project/device. NXP developed a new tool for this task and previewed it at FTF 2016. It is available now both as web (online) and desktop (locally installed) tool. At FTF it was possible to play with an engineering release: time to get my hands on the public release :-). And as more and more student projects will start using that tool for their boards, I better have a tutorial for it :-).

Desktop Version of Pins Tool

Desktop Version of Pins Tool

Continue reading →

Daylight beating my Jetlag

Posted on by
1

Air travel and especially across many time zones is no fun. I returned from the NXP FTF conference in Austin, Texas. Travelling to the west works pretty good, but travelling east is a beast.

My best tip beating timezone tiredness is to get out and tank as much sunlight as I can after. It has been a beautiful day today, I got a lot of sunlight, so here is a share of that:

Sun against Jetlag

Sun against Jetlag (click to enlarge)

Continue reading →

NXP FlexIO Generator for the WS2812B LED Stripe Protocol

Posted on by
19

The challenge with the selection of a microcontroller for a project is: which one has the required number of UART, I2C, SPI? Combine this with the desired package (48pins, 64pins? LQFN?), the needed FLASH and RAM size and then even the hundreds of available microcontroller shrink to a handful only. And many times I need to make compromises: such as I need two hardware I2C, but the microcontroller matching all my other needs has only one I2C hardware. So I might end up with bit-banging the slower I2C bus. Doable, but not ideal.

What is cool that some of the newer NXP Kinetis microcontroller come with an interesting hardware: FlexIO. A peripheral hardware which allows me to implement a custom protocol, including driving WS2812B (Adafruit NeoPixel) LEDs with a FRDM-KL43Z board:

Four NeoPixels with FlexIO

Four NeoPixels with FlexIO

Continue reading →