MCUXpresso IDE with freeMASTER

[mishrarishabh31]

Hi everyone,

I'm a student and recently i start using a nxp controller mkm33z128aclh5 for a metering project but when i move to MCUXpresso IDE for code correction and development i did not found the controller in selection option. so anyone can suggest me what should i do ?

my second question from free master, actually yet im beginner for freemaster so i just wanted to know recorder and oscilloscope both can save graph data in .txt or binary file so that the difference between them. if anyone can suggest how to use recorder that will be very helpful for me.

Thank And Regards

Rishabh Mishra    

[mishrarishabh31]

Thank you everyone for you wonderful reply now i'm able to use freemaster.

[brendonslade]

Unfortunately the KM33 parts are not supported by MCUXpresso SDK 2.x. The newer KM 34 and KM 35 75MHz parts are supported, if they are an option for you.

[iulian_stan · Accepted solution]

Hi mishrarishabh3133@gmail.com‌,

Please check this article Communication Driver (MCUXpresso SDK section). You need to get SDK package corresponding to your MCU. The SDK includes FreeMASTER demo project that you can use as reference for Recorder usage. Regarding FreeMASTER Driver usage a useful resource is the following Driver User Guide. 

In order to use the recorder functionality you need to take the following 2 thing into account (on the embedded side):

1. Recorder configuration (Driver User Guide chapter 2.4.1 - recorder options are described on page 12).
2. Explicit Recorder function call from the embedded code. This call triggers data collection (Driver User Guide chapter 2.7).

Recorder usage on the host (PC) side is described in FreeMASTER User Guide chapter 4.1.1.3.

Regards,

Iulian

[iulian_stan]

Regarding the difference between text and binary formats. The text option is basically a human readable format that stores data in plain text like this:

# Recorder Data

# Time[sec] var8 var16 var32
-0.120000 99 16995 1679421100
-0.100000 99 16995 1679421100
-0.080000 99 16995 1679421100
-0.060000 99 16995 1679421100
-0.040000 99 16995 1679421100
-0.020000 99 16995 1679421100
0.000000 100 16996 1679421200
0.020000 100 16996 1679421200
0.040000 100 16996 1679421200
0.060000 100 16996 1679421200
0.080000 100 16996 1679421200‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

As you can see it will print each recorded variable value with a corresponding time stamp (negative time stamps mark data collected before the trigger event, positive - after). Binary option stores the same data in a serialized form.

I'm not sure how the binary serializer  works, so I will ask one of my colleagues to provide more technical details on that one.

[MichalH]

Hello,

the binary capture format is a series of 8-byte floating point numbers ('double' type) in the same order as in the text format. The first entry is the time in seconds followed by a set of N data samples. In the Iulian's example given above (N=3), there would be three entries for var8, var16 and var32 in the set. Be aware that 'double' conversion does not allow to capture 64-bit integer values in the full resolution.

Regards,

Michal