Issues Flashing Bootable Image to S32Z270-DC Board

[raz3l]

As asked by @alejandro_e , I'm reposting this as there was a problem in your internal ticket tracking tool.

Hi everyone,

I'm having some issues flashing a bootable image to the S32Z270-DC board. Here’s the current setup and the steps I’ve followed:

• S32 Design Studio v3.6.2

• Lauterbach debugger (working fine for debugging)

• Using SMU-CM33 core

• Target: blinking the D12 LED as a basic test

Steps I’ve taken so far:

1. Generated a .bin file

   • I modified the project settings to generate a binary file from the LED example. 

2. Created an IVT image using the S32 IVT Tool

   • Selected the LED example application (which works when debugged via Lauterbach).

   • This is the configuration:

• After configuration, I pressed the "Export Image" button in the Application Bootloader section to update the image blob.

1. Flashing the image

   • In the IVT tool, I clicked "Flash Image" and selected the S26HS512.bin algorithm for HyperFlash.

   • Issue: The flashing process is inconsistent. Sometimes it succeeds, but often it fails.

   • When it fails, I get this error: 
   • 

   • I noticed slightly better results after disconnecting the Lauterbach JTAG adapter

2. Board boot configuration

   • After (successful) flashing, I changed the RCON switches to 0x70481804, which I copied from the HyperFlash Lauterbach script.

   • I then power-cycle the board.

I have also tried to flash to the QSPI Flash by connecting to the J119 USB with this configuration:

RCON switches:

J1245 and J125 in serial mode:

I got the same error with the Flash Tool:

After flashing and power-cycling, I expect the D12 LED to blink (as it does when I run it from the debugger), but nothing happens.

Is there anything I'm missing in all of this process? Could the RCON value be incorrect?

Any help or tips would be much appreciated! Thanks in advance.

[alejandro_e]

Hello @raz3l,

Thanks for reposting your question. About your problem, please request access to the following document: S32Z27X EVB User Guide, there you will be able see all needed steps. 

In the mean time, please check this points in particular:

Use the following configuration J124 and J125 for downloading your program:

J124 : Position (2-3)

J125 : Position (1-2)

To boot from the external flash, use:

J124 : Position (1-2)

J125 : Position (2-3)

And for RCON, use the following configuration:

This is to boot from the S22HM576 HyperFlash.

Disable the following check:

Ensure that the RAM start address matches int_sram_text in the linker_ram_m33.ld and that RAM entry pointer matches the intc_vect address in the Siul2_Dio_Ip_Example_S32Z2XX_SMU_2.map file, these may vary depending on your project configuration.

Use the test connection button to check if the board is ready to be flashed before flashing:

If you keep having problems you can get the GreenVIP package in the AUTO-SW-PACKAGE-MANAGER 

It includes flashing scripts for the Lauterbach debug.

Let me know if you need more help.

[raz3l]

Hi @Ale 

First let me thank you for all the help! 

I need to re-apply for the NDA to download that document since it is still not public right? At least I couldn't get it through your link.

Meanwhile I have tried your suggestions which were pretty similar to what I had already did. I will describe here the full procedure and attach the application for reproduction purposes. 

Like I previously mentioned the application works fine using the Lauterbach.

As expected, LED D12 blinks:

Next steps following your suggestions:

1. Creating the IVT. My configuration:

RAM Start pointer:

RAM Entry pointer:

I pressed "Exported Image" and "Align" after filling the data.

2. Flashing the board. Configuration and steps:

Pressed "Test Connection" and then uploaded algorithm with success.

Then, download the app to the hyperflash:

3. Power cycling the board and changing RCON switches and J125/125 to boot from hyperflash.

RCON:

However, I keep not seeing D12 LED blinking with this method. Could the size of the application be a issue? Or what could be wrong?

[alejandro_e]

Hello @raz3l,

I see you are now able to flash the device correctly that is a step in the right direction.

About the document, yes, you do need to apply for an NDA, as you pointed out, it is not public for now.

regarding the size of the, binary, it should not be a problem, the IVT tool should indicate if there is.

Some customers have had some issues with the flashing algorithm, I will send you some information in a private message to solve it.

regarding the GreeVIP, are you able to download it, the flashing issue I mention is not present when using the Lauterbach to flash the chip.

Best regards

[raz3l]

Hi @alejandro_e ,

I just tried flashing the board using the provided flash algorithm binary. The flashing process completes successfully, but the issue persists.

I dumped the flash memory using the Flash Tool and compared it with the application binary (attached). There are no differences, so it seems the application was correctly downloaded.

I also tried attaching to the CM33 core using Lauterbach to check if it was running or stuck, using the script below. However, TRACE32 reports that the core is powered down .

SYStem.CPU S32Z270-M33-COMMSA
SYStem.CONFIG.DEBUGPORTTYPE JTAG
SYStem.Option DUALPORT ON
SYStem.MemAccess DAP
SYStem.JtagClock 10MHz
Trace.DISable
ETM.OFF
ITM.OFF
STM.OFF
SYStem.Mode.Attach
Data.LOAD.Elf "Dio_Example_S32Z2XX_SMU.elf" /NoClear

[alejandro_e]

Hello @raz3l,

Thanks for the information, regarding the memory dump, did you got it just after trying to boot?

I think the best now is to share your project so I can check it in detail. You mentioned that you attached it before, but I was not able to see any file attached to that message.

Thanks in advance.

[raz3l]

regarding the memory dump, did you got it just after trying to boot?

Yes, I dumped the memory after trying to boot the board. 

You mentioned that you attached it before, but I was not able to see any file attached to that message.

Ups, guess it didn't uploaded correctly. Attached now to this reply.

Thanks once again!

[alejandro_e]

Hello @raz3l,

Thanks for all the info, I was able to perform all the tests I needed and I was able to find the root cause of the problem, it was not the binary, it is the board jumper configuration, please check the following to boot from QSPI (you should already have some of this configured correctly):

J124 and J125:

RCON:

J247 and J248

JP3 (the only JPx selected)

Any deviation from this configuration will cause problems.

This is a photo of the complete board so you can copy the configuration of any other jumper if needed:

I would recommend you to request access to the S32Z2 secure files and the GreenVIP software package, which I mentioned earlier, since you will find them very useful during the development of your project.

Please let me know if this information solved your problem.

Thanks!

[raz3l]

Hi @alejandro_e ,

Unfortunately, it still didn’t do the trick.

Could you try flashing the binary of the app I’m attempting to flash? I’ve attached it to this message.

Below is the configuration I used to set up the board after successfully flashing it using the GreenVIP flash algorithm. It seems to match yours, right? Despite the jumpers of J37 which I has using for a secondary UART. Neverthless, I placed the jumpers on that pins and it didn't work

[alejandro_e · Accepted solution]

Hello @raz3l,

I must have gotten my images mixed up. Keep RCON, JP3,  J124 and J125 as they are, just change the following to boot:

To boot:

J248 3-2

J247 3-2

I tested with the previous binary and the new one, both blink D12 as expected.

Sorry for the confusion,

please let me know if you are now able to boot your program correctly.

[raz3l]

Awesome! It's working @alejandro_e .

Let me just ask one quick thing:
We intend for the SMU-CM33 to boot the RTU0 cores. In this case, is it expected that the CM33 is responsible for loading the RTU application into memory?

[alejandro_e]

The short answer is yes. However configuring a bootloader in the SMU/M33, can be a complicated task. Please check the SMU_LA or SMU_LAV projects in GreenVIP.

If you need more support please create a new post, since you already selected an accepted solution, I won't receive proper notifications regarding the updates of this post.

Thanks

[raz3l]

I see. Thanks for all the help @lejandro_e. If I have any further questions I will create a new post.

[raz3l]

I would recommend you to request access to the S32Z2 secure files and the GreenVIP software package, which I mentioned earlier, since you will find them very useful during the development of your project.

Yes, I'm in the process to have access to the secure files. I have also installed the GreenVIP software package to get the flash algorithm as you mentioned.