NOR FLASH boot for M7 FAIL

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

NOR FLASH boot for M7 FAIL

Jump to solution
1,473 Views
ofer-bahar-guardknox
Contributor IV

 

Hello

I'm unable to boot from M7, Target is GoldBox RDGB2, application M7 single core works in debug, flashed OK to the QSPI NOR flash, but does not being boot !

Steps I do

1. Building and checking a M7 application from the examples Siul2_Port_ToggleLed_S32G274A_M7

2. Did all steps from: HOWTO: Use IVT Tool To Create A Blob Image S32G274... - NXP Community

3. for the DCD i imported the one from the project, only exported it as binary

4. for the application bootloader RAM entry pointer I put the intc_vector

oferbaharguardknox_0-1688631199101.png

5. for the application bootloader RAM start pointer I put the int_sram from the linker file

oferbaharguardknox_1-1688631312888.png

6. I tried either with or without QuadSpi parameters file e.g. mx25_sim200ddr.bin, or mx25_sim133sdr.bin

7. export a blob, looks OK

oferbaharguardknox_4-1688631616182.png

 

8. flash the target, it completed OK

oferbaharguardknox_3-1688631582660.png

 

9. set the switched to boot from NOR flash, make power off, power on

oferbaharguardknox_2-1688631492549.png

Result : Nothing!, the LED should have been blinking 

what am I missing ?

thanks

0 Kudos
Reply
1 Solution
1,366 Views
ofer-bahar-guardknox
Contributor IV

Look like the RAM entry pointer is different between few documents

Trying the one in the enablement doc works

 

View solution in original post

5 Replies
1,443 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

On the 8th step, we are seeing that you are selecting the "ivt_blob_image", which is the default option provided, not the blob you have created.

Where are you saving the blob image? You should point to the blob image you have created.

Please, let us know.

 

0 Kudos
Reply
1,438 Views
ofer-bahar-guardknox
Contributor IV

Hi Daniel

I saw that as well and of-coarse tried the blob image I created, but => the same result 

maybe it's the DCD? is there a ready & good DCD binary, suitable for the RDB2, that I can download or you can send me ?

what else can be the reason ?

0 Kudos
Reply
1,430 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

We create our IVT without the need of the DCD following the Software Enablement Guide, we modify the linker as shown in the guide and just select the QSPI interface instead of the SD card. We are not seeing any issues on this regard. You can access this guide under the RDB2 product page (link: S32G2 Vehicle Networking Reference Design | NXP Semiconductors)

As for a pre-built DCD, there should be one provided under the HSE DEMOAPP or the integration reference examples, if needed.

Please, let us know.

0 Kudos
Reply
1,424 Views
ofer-bahar-guardknox
Contributor IV

OK

I will try the same procedure as in the software enablement guide as well, through its for SD card, hope it works, and if so i will configure to NOR QSPI FLASH and let you know how it works 

 

0 Kudos
Reply
1,367 Views
ofer-bahar-guardknox
Contributor IV

Look like the RAM entry pointer is different between few documents

Trying the one in the enablement doc works