E: chip type dosen't fir for the binary (using Customer Module Evaluation Tool)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

E: chip type dosen't fir for the binary (using Customer Module Evaluation Tool)

1,359 Views
swhyun
Contributor I

Hi. 

I'm going to test RF performance for K32W041.

so, I flash the customer module evaluation tool on K32W041.

but I don't start the test program with error message.

[E: chip type dosen't fir for the binary]

please help

swhyun_0-1688462684554.png

 

Labels (3)
Tags (1)
0 Kudos
Reply
7 Replies

1,326 Views
swhyun
Contributor I

@EduardoZamora 
Thank you for your answer.

However, the results are the same.

I wonder if K32W041 chipset also supports that firmware.

0 Kudos
Reply

1,305 Views
EduardoZamora
NXP TechSupport
NXP TechSupport

Hi,

You can try re-building CMET for K32W061 with a modification. For instructions on how to rebuild CMET, please consult JN-AN-1242 > Docs > JN-AN-1242-Customer-Module-Eval-Tool document, Section 3 Downloading the Application.

For the modification, open ANxxxx_CustomerModuleEvalTool.c and search the following portion of the code: 

EduardoZamora_0-1688590376020.png

Here, change the condition to:

if( (u32ChipType != CHIP_K32W061) && (u32ChipType != CHIP_K32W041) ) 

EduardoZamora_1-1688590376020.png

After this, re-build the project, flash the new binary into your device and test the application. Please, let me know your findings.

Regards,
Eduardo.

0 Kudos
Reply

1,268 Views
swhyun
Contributor I

swhyun_0-1688632468532.png

The suggested modification point is that you told me the build method for K32W041 instead of K32W041A, K32W041AM, right?

CHIP_K32W041 seems to mean that.

 

0 Kudos
Reply

1,241 Views
EduardoZamora
NXP TechSupport
NXP TechSupport

Hi,

Please, try using CMET for K32W061, this project should work as base for the K32W041. When importing the project to your workspace, select JN-AN-1242-K32W061

EduardoZamora_0-1688657531733.png

After this, open ANxxxx_CustomerModuleEvalTool.c and search the following portion of the code:

EduardoZamora_1-1688657531735.png

Change the condition to

if( (u32ChipType != CHIP_K32W061) && (u32ChipType != CHIP_K32W041) )

EduardoZamora_2-1688657531736.png

Then, build the project and flash the binary to your device. This modification should allow you use CMET on K32W041.

Regards,
Eduardo.

0 Kudos
Reply

1,179 Views
swhyun
Contributor I

Thank you. It was very helpful.

I built and tested it the way you told me, and I checked that it works normally on the K32W041 product.

swhyun_0-1688970359518.png

 

0 Kudos
Reply

1,275 Views
swhyun
Contributor I

Thank you for your support.

I am using K32W041, not K32W041A and K32W041AM. There is no list of K32W041 in CMET, is it not possible to support it? Or can I use the bin of K32W041A?

0 Kudos
Reply

1,337 Views
EduardoZamora
NXP TechSupport
NXP TechSupport

Hello @swhyun

Hope you are doing well.

Could you please try using the binary located inside JN-AN-1242 > K32W061_mcux (Debug/Release) folder?

Also, if needed, you can use the K32W RF System Evaluation Report for BLE and IEEE 802.15.4. This document provides the K32W RF evaluation tests results for Bluetooth Low Energy (Bluetooth LE) applications (2FSK modulation) and 802.15.4 applications (OQPSK modulation).

Regards,
Eduardo.

0 Kudos
Reply