topic Re: K32W041 - Unnable do debug and SDK bug in MCUXpresso IDE

K32W041 - Unnable do debug and SDK bug

adrian_chmiel — Mon, 28 Dec 2020 19:04:57 GMT

Hi,

I started working with K32W041 and at the beginning I found bug in SDK.

When I create new project for K32W041, MCUxpresso incorrectly generates files and you cannot use e.g. Pin Tools or Clock Tools (there are inform, that MCu is not selected). Also, don't add files board_utility.c/.h in "board" catalog, it's not exist.

For K32W061 everything is ok. Since these are the same processors (only *041 has no NFC) I currently use the SDK for K32W061.

Second thing, there is some problem with debug, sometimes MCU is stuck and I cannot debug any more. In console I see:

NXP: K32W061
DAP stride is 4096 bytes (1024 words)
Inspected v.2 On-chip Flash Memory QN9090_640K.cfx
Image 'QN9090_Internal Flash Sep 25 2020 10:48:22'
Opening flash driver QN9090_640K.cfx
Sending VECTRESET to run flash driver
AFTER driver startup timeout (302 5ms retries)
Driver Addresses
Start: 04000000
Entry: 0400009D
End: 04000828
Stack: 04001028
Mailbox:04003C28
Driver Register State
R0: 00000005
R1: 040007B0
R2: 00000000
R3: 80000000
R4: 40009000
R5: 0400079C
R6: 00000000
R7: 00000000
R8: 00000000
R9: 00000000
R10: 00000000
R11: 00000000
R12: 00000000
SP: 04000FF0
LR: 04000459
PC: 0400045C
xPSR: 81000000
MSP: 04000FF0
PSP: 04001028
CFBP: 00000001 (CONTROL=0x0, FAULTMASK=0x0, BASEPRI=0x0, PRIMASK=0x1)
Flash Driver V.2 startup failed - rc Ef(34): Timed-out initializing flash.
chip initialization failed - Ef(34): Timed-out initializing flash.
failed to initialize flash driver QN9090_640K.cfx

And at this moment I don't know how too fix it. I use custom board, not eval board, with LPC-Link

Re: K32W041 - Unnable do debug and SDK bug

adrian_chmiel — Mon, 28 Dec 2020 19:49:37 GMT

Additional information:

When I use LPC-Link as a J-Link, debugging work correct.

Re: K32W041 - Unnable do debug and SDK bug

mario_castaneda — Wed, 30 Dec 2020 17:37:53 GMT

Hi @adrian_chmiel,

I hope you are doing great.

When I create new project for K32W041, MCUxpresso incorrectly generates files and you cannot use e.g. Pin Tools or Clock Tools (there are inform, that MCU is not selected). Also, don't add files board_utility.c/.h in "board" catalog, it's not exist.

The wireless examples are not compatible with the Pin and Clock Tools, you could change your configuration and after that, you could copy them into your code.

Now, what are the MCU settings that you have?

Did you try with a hello world example?

Regards,

Mario

Re: K32W041 - Unnable do debug and SDK bug

adrian_chmiel — Wed, 30 Dec 2020 21:59:38 GMT

Hi Mario,

Examples and "New project..." button work correctly but only for k32W061.

For K32W041 there are no examples and "New project..." generate incorrect project.

For example:

New project... -> K32W041 -> default settings

and Finish.

When I try build:

And when I try open Pins or clock perspective:

The same procedure for K32W061 works fine.

MCUXpresso IDE v11.2.1 [Build 4149] [2020-10-07]

SDK for K32W 2.6.2

Re: K32W041 - Unnable do debug and SDK bug

mario_castaneda — Mon, 04 Jan 2021 18:02:20 GMT

Hi Adrian,

I hope you are doing great. I recommend selecting the UART interface instead of semihost as the debug interface.

You can try to add the board_utility.c and board_utility.h to the "board" folder. The new Application is not released now, but we will release it later.

Regards,

Mario

Re: K32W041 - Unnable do debug and SDK bug

adrian_chmiel — Tue, 12 Jan 2021 10:16:35 GMT

Hi,

I doesn't have free fins for USART interface, but problem was with debuging not only with checking register but completely in communication programmer <-> MCU (debugger cannod connect to MCU).

When I use JLINK problem is gone, but still exist if we use LPClink.