topic Re: M7 Build code and Flash tool download to norflash Fail in S32G

M7 Build code and Flash tool download to norflash Fail

tzeng015 — Wed, 09 Feb 2022 08:04:35 GMT

Hi NXP support

M7 Build code and Flash tool download to norflash Fail. Please see the attach file and the SOP can't work well.

Please see the attach file and help me to solve the question.

thank you

Jeffrey

Re: M7 Build code and Flash tool download to norflash Fail

bpe — Wed, 09 Feb 2022 12:05:44 GMT

What I see in the attached document is, that you are putting an ELF file onto the bootable Flash. ELF executable is not a valid format for that. You have to convert your code into a format recognized by S32G2 Boot ROM in order to directly boot into it. Study S32DS User Guide section titled "Debugging with S32 Debug Probe from flash for all other targets" on page 100 on how to debug an application from Flash. Study S32G2RM, Sections 30.4 and 30.13 to understand how your processor boots and what it expects in the boot Flash.

Best Regards,
Platon

Re: M7 Build code and Flash tool download to norflash Fail

tzeng015 — Wed, 09 Feb 2022 13:10:39 GMT

I will try it ASAP .

thank you

Re: M7 Build code and Flash tool download to norflash Fail

tzeng015 — Thu, 10 Feb 2022 01:26:30 GMT

Can you help me where to download "S32DS User Guide" ? I find the webside but I still can't find it . please help me ...

thaank you

Re: M7 Build code and Flash tool download to norflash Fail

tea1 — Thu, 10 Feb 2022 02:48:11 GMT

If S32DS is installed in the default path, it should be found here.

C:\NXP\S32DS.3.4\S32DS\help\pdf\S32DS_User_Guide.pdf

Re: M7 Build code and Flash tool download to norflash Fail

tzeng015 — Thu, 10 Feb 2022 07:29:10 GMT

Hi NXP supports

According the NXP's agent FAE of Taiwan, here is the SOP.

1: Generate S-Record/Intel HEX/Binary file
https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Generate-S-Record-Intel-HEX-Binary-file/ta-p/1105838

2: Use DCD Tool To Create A Device Configuration Data Image
https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Use-DCD-Tool-To-Create-A-Device-Configuration-Data-Image/ta-p/1106170

3: Use IVT Tool To Create A Blob Image S32G274A
https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Use-IVT-Tool-To-Create-A-Blob-Image-S32G274A/ta-p/1125675

Please see the last page's error message of attach file. The attach picture (2022-02-10_151954.jpg) is the error message , too.

Please Kindly help me to go next step .

thank you

Re: M7 Build code and Flash tool download to norflash Fail

bpe — Thu, 10 Feb 2022 12:37:16 GMT

You are trying to put together different recommendations without understanding
of what you are actually doing. The result is that the both approaches fail.

Your IVT tool fails because you are giving it a wrong file as the bootloader
image. Besides that, you are generating an S-rec file which is useless in your case.

Follow the steps specified in S32DS User Manual strictly. If you want to
follow the alternative approach, contact the person who have given you that
sequence for further guidance. There is nothing wrong in it, but you have to
follow it correctly.

And last, but not the least: Study your processor Reference Manual to understand the
role and the logic of the structures you are trying to manipulate: IVT, DCD, application
image, as well as the boot flow. The references to the related sections of the document
are given above.

Best Regards,
Platon

Re: M7 Build code and Flash tool download to norflash Fail

tzeng015 — Tue, 15 Feb 2022 07:45:23 GMT

thank you help me. The attach file is download OK sample but the function is not Ok. Can you help me again ?

thank you

Re: M7 Build code and Flash tool download to norflash Fail

bpe — Wed, 16 Feb 2022 06:30:59 GMT

It is very difficult to comment the materials you attach because you are using
a local language S32DS. Note that NXP Technical Support is an international
service with engineering teams located worldwide. It is always better to
use an international S32DS installation if you are planning to exchange any
materials with us.

One visible potential problem is that you set your binary entry point at the
start of the image. Usually it is not the case. See this document, slide 21
on how to find and fill the correct values. You may also need to modify
your linker file as to avoid overwriting the reserved SRAM areas. Slide 18
of the same document gives you an idea.

Another potential problem appears on slides 17 and 18 of your report. This does not
seem to match your boot device:

Best Regards,
Platon