S32K146 EVB does not flash *.bin anymore (MAC & Windows10)

[jimmy_mathew]

Hi All,

I am new to NXP community and appreciate your time to have a look at this issue.

I have S32K146 EVB which was working till yesterday. I mean, it was getting mounted as /S32K146EVB and I was able to drag & drop custom built *.bin (for flashing an LED)  file and it was upgrading to the new software & was working fine. I was using MAC & cp utility to copy file.

From yesterday, it gives OpenSDA LED error indication, without any reason (When I drag & drop *.bin file) . It pauses for 2 Sec, and blinks 8 times  and pauses again for 2 sec. According to Open SDS LED error code, this seems to be an OpenSDA Application Error. 

When I press the reset button and go to bootloader mode, everything seems alright. It mounts BOOTLOADER and I can drag and drop 'BOOTUPDATEAPP_Pemicro_v111.SDA' and 'MSD-DEBUG-S32K146EVB-Q144_Pemicro_v121.SDA'

So I believe the OpenSDA application is good 

======================================================================

 Here is the PEMicro SDA info (when mounted as  /S32K146EVB) :

Board Name is: S32K146EVB-Q144
MicroBoot Kernel Version is: 1.08
Bootloader Version is: 1.11
Installed Application: PEMicro S32K146EVB-Q144 Mass Storage/Debug App
Application Version is: 1.21
DUID is: 12933938-0FC481A4-3750A81C-D259E678
EUID is: 0C11A239-9DA6872A-184FCA07-F86268D6
TUID is: 74823938-47328196-8467AE16-223C9857
TOA is: 86B6E505-D8943659-79B2A114-606084A3
TOA2 is: 86B6E505-932E8830-AF6E54B6-91E65FF0
SUID is: 86B6E505-5BA18877-37239804-8003EC65

=================================================================

Thank you for your time.

[danielmartynek]

Hi JImmy,

The blinking means an error, but it could be anything.

Have you tried to flash a project directly from S32 Design Studio?

As described in the S32K146 EVB QSG p. 24 Create a new project in S32 Sesign Studio.

Thanks,

BR, Daniel

[jimmy_mathew]

Hi Daniel,

Thank you for your reply. 

While trying flashing a S32 DS provided application (which was working earlier) using the 'flash' symbol from the IDE, It gives me a P&E connection assistant error telling that it cannot connect to the interface hardware. Please see the image attached.

Regards,

Jimmy

[danielmartynek]

Hi,

Can you confirm 5V at VDD_MCU (J15)?

How do you power the MCU (J10)?

Thanks,

Daniel

[jimmy_mathew]

J10 is in 2-3 position (VDD connected to 5V)

Also J107 in 2-3 position (Powered by USB micro connector) 

I measured the VDD tap point  (near to J10) on the board and it is 4.8 V

[danielmartynek]

So, the MCU is powered (VDD_MCU) and it is not damaged (it is not heating).

What application did you load the last time? Did you reprogram the JTAG/SWD pins?

Is there an application running on the MCU or is the MCU resetting itself (D1 LED)?

Can you provide the .bin file?

[jimmy_mathew]

Hi Daniel,

Thank you for your reply.

No. The MCU is not heating.

It seems that the MCU is resetting. It has D1 LED always turned RED.

Please see the *.bin I am trying to flash attached here. This binary was working earlier.

We do not have a compatible JTAG debugger/programmer here. 

[danielmartynek]

Hi,

Thanks for the binary file. Yes, it works just fine. 

I don't know what could have gone wrong.

You can try the Emergency Kinetis Device Recovery option.

Or use the PE recovery utility as described in this article:

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

This utility can halt the execution just after power-on-reset.

And if successfully halted, maybe it can be reprogrammed.

BR, Daniel

[jimmy_mathew]

Hi Daniel,

Thank you for your mail.

I tried option 1 : Emergency Kinetis Device Recovery option, but it could not flash it and gave me P&E Connection assistant error as shown in my previous message on May 12.

Option 2 : It seems that I need to have 'PEmicro’s USB Multilink ' and I do not have one. 

Is there any other option without using a JTAG device? 

If we need to buy a JTAG programmer, can you suggest which works best for both OpenSDA Chip on my board (K20 I assume) and S32K146. From PE Micro website I can see that the Multilink works for S32 as well; But just wanted to ask your suggestion.

Note:

I see a comment on that page where,

------------------------------------------------------------------

Adam S on August 4, 2014 at 05:28 said:

I had a similar issue. I mapped SWD_CLK, SWD_DIO, and RESET all to GPIO pins.
I was able to recover it by shorting NMI to ground during boot up. While NMI was pulled low execution stopped, and during that time I was able to do a mass erase. No Multilink needed, just OpenSDA on the FRDM board.

---------------------------------------------------------------------------------------------------------------------------

I wanted to check whether this could solve issue, but need to know how I can short NMI to GND.

can you please let me know your opinion?

Regards,

Jimmy

[danielmartynek]

Hi Jimmy,

NMI_b is a function of PTD3 pin but unlike RESET_b (PTA5), it is not enabled by default.

Please refer to S32K146_IO_Signal_Description_Input_Multiplexing.xlsx (IO Signal Table) that is attached to the RM.

I'm not sure if the kinetis recovery utility with the PE Multilink can recover the MCU in this case, just an idea.

PE Mutilink can be used for both. There are other options, some of them are listed here:

32-bit Automotive General Purpose MCUs | NXP 

S32 Design Studio:

S32 Design Studio IDE for Arm® based MCUs | NXP 

BR, Daniel

[jimmy_mathew]

Hi Daniel,

Sorry for the late reply. I was on other tasks.

Thank you very much for your suggestion on potential debugger/flasher(s). We have to look in to it.

Just a question. Can NXP send another S32K146 EVB such that we continue evaluating this without interruption? We consider this chip set seriously for our next version of Hardware. It will be great if you can replace this with a working one and later we can ship this one back for your analysis.

Please let me know.

Regards,

Jimmy

[danielmartynek]

Hi Jimmy,

As discussed, the best option would be to submit a Tool Warranty Request (Return for Replacement).

Returns and Warranty Information | NXP 

Thanks,

BR, Daniel

[jimmy_mathew]

Thank you Daniel

[jimmy_mathew]

Hi Daniel,

I had submitted a return for replacement form request on last week; But did not hear anything back from NXP. Can you please suggest what I need to do next?

Regards,

Jimmy