P&E Connection Assistant error occured (in a rush)

cancel
Showing results for 
Search instead for 
Did you mean: 

P&E Connection Assistant error occured (in a rush)

Jump to solution
69 Views
Contributor III

Hi.

123.PNG

( uint8_t my_test[FTFx_PHRASE_SIZE] = {0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u}; )

I pressed F11 Key to debug

and pressed F8 Key to use breakpoint.

But somewhy, the program was stopped by DEV_ASSERT Macro.

I think the value 'ret' was not STATUS_SUCCESS.

so I pressed CTRL+F2 Key to exit debug mode.

and then I tried again. (press F11)

 

캡처.PNG

So this error is occured.....

 

I changed usb plug, and used another s32k144 board.

so, I'm sure this board is stuck in somewhere.

 

I'm trying to connect to external debugger with my board to do a mass erase.

But popup said that my device can't be mass erased. (mass erase disabled)

 

it's weird. because I might have written all 0 to flash configuration field.

and to make mass erase disabled, the MEEN field is to be 10....

 

 

What happend to my board?

and what can i do...?

 

please help me.

 

Thanks,

Best regards,

Phillip.

Labels (1)
0 Kudos
1 Solution
20 Views
NXP TechSupport
NXP TechSupport

Hello @kmh48301,

Getting sparks is always a bad sign, if there's a hardware problem the behaviors will be unpredictable si I will suggest investigating first this issue.

Regarding the lock MCU, this usually happens when you write the flash memory section 0x400, that's the reason in the linker file is preserved in this section so try not to write it with any flash operation.

Best Regards,

Alexis Andalon

View solution in original post

0 Kudos
6 Replies
46 Views
NXP TechSupport
NXP TechSupport

Hello @kmh48301,

Could you try using the P&E recovery utility?

The functionality is explained here:

 Bricking and Recovering FRDM-KL25Z Boards: Reset, SWD Clock and Low Power | MCU on Eclipse 

Best Regards,

Alexis Andalon

0 Kudos
44 Views
Contributor III

Hi

thanks for replying.

 

I've already tried this utility.

 

I'm not sure I understood how to do this utility.

but, when I tried, I selected "OPENSDAUSB" and clicked start,

then, that console said 'please try power cycling'.

so I repeated unplug and replug the usb.

but i couldn't see any response from the utility..

 

 

thanks

Best Regards,

Phillip

0 Kudos
39 Views
NXP TechSupport
NXP TechSupport

Hello @kmh48301,

The power cycling needs to be done until there's a response from the utility if there isn't any reply is probable that is not recoverable.

Also, you could try using the following option:

Alexis_A_0-1599783665974.png

If these two options don't work is probable that this MCU can't be recovered.

Best Regards,

Alexis Andal0on

0 Kudos
31 Views
Contributor III

Hi. Alexis

Thank you for additional advice.

 

It also didn't work..

 

I think my board is gone.

But I need to know the reason...

 

What is your opinion? Is it Hardware problem or the code was bad?

Actually, I pluged and unpluged many times with usb. and i saw spark from junction.

 

and I admit that my program was pretty wrong.

because I used P-Flash block that contains important data such as 

flash configuration field and code and etc..

 

But I'm not sure that the wrong program which i made and put

result in this problem..

 

 

Thanks

Best regards,

Phillip

 

0 Kudos
21 Views
NXP TechSupport
NXP TechSupport

Hello @kmh48301,

Getting sparks is always a bad sign, if there's a hardware problem the behaviors will be unpredictable si I will suggest investigating first this issue.

Regarding the lock MCU, this usually happens when you write the flash memory section 0x400, that's the reason in the linker file is preserved in this section so try not to write it with any flash operation.

Best Regards,

Alexis Andalon

View solution in original post

0 Kudos
63 Views
Contributor III

Plus D1 RED LED is always on..

my co-worker said my board is stuck in reset sequence.. 

0 Kudos