S32K144 EVB : flashing Application on Unified Bootloader, but, its failing at flash erase

[RasikaB]

Dear Team,
I am trying to flash an application[simple LED blink] on top of Bootloader given by NXP using ECU bus tool with the jSON provided attached herewith. 
After successful download of Flash driver API, For 31 01 FF 00 Flash erase step, control is going to DefaultISR, callstack image has been attached. JSON and Flash driver bin has been shared for reference.
Also find below snap for reference:

Kindly help me out asap.

[RasikaB]

Thanks @Senlent for sharing the information. 
I have tried with the unmodified linker which NXP has shared, but still, the same issue. Unable to erase the flash. any pointers on this??

also it would be great if you can share simple s32k144 demo project which is used to erase and then write 4k Sector flash as I need to confirm that weather flash erase works or not.
Thanks!

[RasikaB]

Thanks @Senlent for sharing the information. 
I have tried with the unmodified linker which NXP has shared, but still, the same issue. Unable to erase the flash. any pointers on this??

also it would be great if you can share simple s32k144 demo project which is used to erase and then write 4k Sector flash as I need to confirm that weather flash erase works or not.

[Senlent]

Hi@RasikaB

"flash_partitioning_s32k144" can be found in S32 DS.

I've tested all these demos before, and I haven't found any problems. If there are any issues, you should first question what modifications you've made to them. I even saved my previous test records (although it's for S32K142, it's almost identical to S32K144).

[Senlent]

Hi@RasikaB

Is there a problem downloading the app bin file that comes with this example?

If there's no problem, then the issue is most likely with your app itself. You need to check if you've correctly modified the app's linker files.

[RasikaB]

Hello @Senlent, Thanks for the quick reply. I am facing this issue while erasing the flash. I am able to download flash driver successfully. even checksum is also verified by sending 31 01 02 02 and getting positive response with 00 as 5th byte. After downloading flash driver, I am sending 31 01 FF 00, there its failing. sharing trace snapshot for reference

also, sharing boot as well as application linker for reference here. I request you to kindly review and please share your guidance asap

[Senlent]

Hi@RasikaB

I can only guide you to run this routine successfully. If you want to modify it in any way, I'm sorry, that's not within our scope of support.

“Unified bootloader shared on the community is only unofficial demo provided AS IS with no guarantees and no support. Currently we do not have resources to support this demo. We apologize for any inconvenience.”

The left side is what we provided, and the right side is what you modified.

What is the point of making these modifications?

This is incorrect because you haven't finished modifying it; you haven't made any further definitions for m_flash_driver and m_exchange_info.