topic Re: Project compiled by S32 2017.R1 is not working with booloader in MPC5xxx

Project compiled by S32 2017.R1 is not working with booloader

jeromeli — Mon, 15 Jan 2018 12:11:28 GMT

Hi,

My project that compiled in S32DS 2017.R1 is not working with my CAN bootloader. While the bootloader is fine with projects that are compiled in S32DS v1.1/v1.2.

MCU: MPC5748G

SDK: EAR 0.8.1

Any suggestion on how to study the cause of the problem? Thanks!

Re: Project compiled by S32 2017.R1 is not working with booloader

martin_kovar — Tue, 16 Jan 2018 12:29:01 GMT

Hello Jerome,

could you please specify, what does it mean application is not working? I need to know as much details as possible.

Just quick question, do you place anything into custom RAM section?

Regards,

Martin

Re: Project compiled by S32 2017.R1 is not working with booloader

jeromeli — Wed, 17 Jan 2018 05:44:35 GMT

Hello Martin,

Thanks for the reply.

I've managed to get rid of this problem already, though I'm not quite sure about the real cause. The thing is that I use pit in the bootloader, if I disable pit before jumping to app, then it works fine. But the situation is not the same when I use S32DS v1.1/v1.2. Do you have any idea?

Re: Project compiled by S32 2017.R1 is not working with booloader

martin_kovar — Thu, 18 Jan 2018 08:54:09 GMT

Hello Jerome,

unfortunately, I do not have enough information, so I do not have any idea, what could be wrong.

I can recommend you some general points.

If your bootloader runs the application directly without microcontroller reset, please ensure that bootloader cleans up all resources which it used.

Also, you did not explain the behavior. Does it mean that bootloader does not run the application at all, or application does not run correct, or...?

Please write me back as much details as possible.

Regards,

Martin