Issues while flashing the code through s32 design studio using PE micro

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

Issues while flashing the code through s32 design studio using PE micro

Jump to solution
931 Views
vinaychitturi
Contributor III

                In our project we are using s32k312 microcontroller, Currently I am facing some issues while flashing the code through s32 design studio using PE micro. In our project we have first bootloader(Fbl), second bootloader(sbl), and Application code

Currently as per linker files for FBL we are using from 0x400000 to 0x43ffff , SBL we are using 0x440000 to 0x47ffff and for App we are using from 0x480000 to end of the pflash section.

I am merging the srec files I got from fbl, sbl, app and flashing that merged srec file to have the complete app,fbl,sbl code in pflash section.

In the s32 design studio with the attached screenshots we are flashing the srec file as shown below. In the advanced options we are not preserve any range of memory while flashing the srec file.

vinaychitturi_0-1739409401597.png

 

vinaychitturi_1-1739409401629.png

 

vinaychitturi_2-1739409401661.png

 

 

vinaychitturi_3-1739409401690.png

But while flashing the srec files we are seeing the following errors while flashing the srec files . After tried to flash for few more times then sometimes it is flashing the srec file.

vinaychitturi_4-1739409401712.png

Once the srec file is flashed,we are flashing the elf file for debugging the code. But while flashing that app elf file using the following settings shown below

vinaychitturi_5-1739409401735.png

 

vinaychitturi_6-1739409401795.png

 

 

vinaychitturi_7-1739409401821.png

In the settings we added the preserve memory range from 0x400000 to 0x47ffff to not override the code of FBL and SBL code. When we tried to flash with these settings it is still erasing the whole section and overriding the FBL and SBL as shown below

vinaychitturi_8-1739409401868.png

So can you please help us to identify why we seeing these errors while flashing the srec files and elf files. Because of these issues currently we ae unable to go for the debugging mode using the elf file.

 

0 Kudos
Reply
1 Solution
906 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @vinaychitturi 

I answered something very similar here two days ago:

https://community.nxp.com/t5/MPC5xxx/linking-single-elf-file-for-multiple-bootloader-and-application...

This will work also for S32K3. You can either create single file or you can simply define more object files to load together with elf file of your application.

Regarding your procedure: when loading the srec file, I would disable "Load Symbols" and "Run on reset" in Startup tab. This has no meaning when srec file is loaded, that's for elf file. Not sure if this will help but you can try...

Preserve memory feature works like this: Pemicro reads define area, erases everything and then it loads the data back. It does not simply keep the data in flash for some reason. The question is why it fails...

Anyway, I would use rather methods described in the mentioned post above. I think it's more convenient solution.

Regards,

Lukas

View solution in original post

0 Kudos
Reply
2 Replies
907 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @vinaychitturi 

I answered something very similar here two days ago:

https://community.nxp.com/t5/MPC5xxx/linking-single-elf-file-for-multiple-bootloader-and-application...

This will work also for S32K3. You can either create single file or you can simply define more object files to load together with elf file of your application.

Regarding your procedure: when loading the srec file, I would disable "Load Symbols" and "Run on reset" in Startup tab. This has no meaning when srec file is loaded, that's for elf file. Not sure if this will help but you can try...

Preserve memory feature works like this: Pemicro reads define area, erases everything and then it loads the data back. It does not simply keep the data in flash for some reason. The question is why it fails...

Anyway, I would use rather methods described in the mentioned post above. I think it's more convenient solution.

Regards,

Lukas

0 Kudos
Reply
852 Views
vinaychitturi
Contributor III

hi @lukaszadrapa , Thanks for your reply

0 Kudos
Reply