MPC5748G / BAF module does not start MCU when boot header located in addres other than 0x00F8C000

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MPC5748G / BAF module does not start MCU when boot header located in addres other than 0x00F8C000

Jump to solution
3,081 Views
kamelfezzani
Contributor I

Hi there,

 

I can't start my application with boot header located in address other than

0x00F8C000.

 

Application examples (AN4830,

http://cache.freescale.com/files/microcontrollers/doc/app_note/AN4830.pdf)

boot header are all located in 0x00F8C000.

 

Reading MCU manual, it seems to be an issue with HSM module.

 

Consequently, could you please give more details about this:

* Is there any software example code with boot header located in address

other than 0x00F8C000 ?

* How must I proceed if I want to start my application in address

0x00FC0000 for example (this address is recognized by the BAF) ?

* How can I disable HSM (in MCU manual, HSM is always disabled at

power up) ?

 

I am working on automotive ECU with complex SW organization: BOOT +

BSP + APPLI layers.

 

BR

Labels (1)
Tags (1)
1 Solution
2,657 Views
mbu2015
Contributor II

Hi,

are you sure you have a cut 2 device?

Have a look at my post on the differences between cut 1 and cut 2 I stumbled across already:

Summary of differences between MPC5748G cut 1 and cut 2 available?

Best regards

Matthias

View solution in original post

5 Replies
2,658 Views
mbu2015
Contributor II

Hi,

are you sure you have a cut 2 device?

Have a look at my post on the differences between cut 1 and cut 2 I stumbled across already:

Summary of differences between MPC5748G cut 1 and cut 2 available?

Best regards

Matthias

2,657 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

That's very good point. I checked it and there are differences between cut 1 and cut2: these header locations are available only on cut 2:

0x00FC_0000

0x00FD_8000

0x00FE_0000

The rest is the same on both cut 1 and cut 2.

Lukas

2,657 Views
kamelfezzani
Contributor I

Hi Mathias and Lucas,

Thanks for your answers.

I am working with cut1 device. I will get ASAP cut2, and I will modify my SW mapping to bypass cut1/cut2 differences.

However, some more comments/questions to get this indeed solved:

  • I suppose that cut1 is an engineering release and cut2 is the "final" definition intended for mass production. Could you please confirm that ?
  • Is there any document that lists all cut1/cut2 differences ? Such a doc will be very helpful in development step.

BR

Kamel

0 Kudos
Reply
2,657 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Yes, that's correct. Cut 2 is already in mass production.

I have list of differences but it is confidential version that cannot be shared with customers. I will ask if we have version for customers - I'm not really sure.

Lukas

0 Kudos
Reply
2,657 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi,

I did quick test and it works as expected on my side. I just modified my old sample project like this:

pastedImage_0.png

That's the only modification because boot_header is placed at the beginning of this segment.

pastedImage_5.png

And I confirmed in debugger that the boot header is really placed at 0x00FC_0000:

pastedImage_1.png

It works in debug mode and it also works in standalone mode. Could you try it? Project is attached.

Regards,

Lukas