What is the correct procedure to apply a cube patch when using CubeIDE?

[heke]

Hi,

I downloaded the STM32CubeN6 for my STM32N6570-DK, version 1.1.0. from https://www.st.com/en/embedded-software/stm32cuben6.html.

I noticed that there is a newer version 1.1.1 available, but that is a patch, not a package. I haven't found an explanation how that patch should be applied.

Asking that because automatically generated template code with 1.1.0. won't run successfully. DK crashes when calling 

HAL_ICACHE_ConfigAssociativityMode()

Any advice to share is appreciated.

Cheers, heke

[STTwo-32]

Hello @heke and welcome to the ST community.

The easiest way is to download the standalone version of the STM32CubeMX V6.14.1. Go to Help > Connection & Updates > Connection Parameters and check your Connection using the "Check Connection" button. If it works fine, go to myST and connect to your profile. If this works fine, go to the INSTALL / REMOVE button and check the STM32N6 menu. You will find all Cube Package versions (including patch). Click on the package you want to use and install. After that, the STM32CubeMX will do the job.

Best Regards.

STTwo-32

[heke]

Hi @STTwo-32 ,

Thank you for your quick response.

My machine is air-gapped, thus I cannot do on-line install.

I'll install the standalone MX to see if it can consume locally stored patches.

Cheers, heke

[heke]

Hi @STTwo-32 ,

My sincere apologies for bothering you with this issue, but I hope this helps other fellow geeks with a similar situation.

I installed the standalone version of MX and attempted to update the 1.1.0 .to 1.1.1. off-line with the patch provided (Win10, AMD Ryzen, etc.).

MX was not happy at all. Refused to do anything with the 1.1.1. patch.

I wonder, could you kindly test that the patch is accepted by the MX on your rig? That would narrow down the possible culprit.

Finest Salutations, heke

[Pavel A.]

While waiting for authoritative reply:

Unpack the patch zip file to a temporary directory. The zip should contain the same structure as the firmware 1.1.0.

Then just copy the whole content onto the firmware 1.1.0 directory; let it overwrite existing files.

(keep backup of the 1.1.0 dir to be safe)

To check - open the firmware manager of the Cube, it should detect the patch. (the version is actually in the file package.xml)

Done.

[heke]

Hi @Pavel A. 

Many thanks. I appreciate your advice.

Copied the patch, file by file to the existing 1.1.0 structure. CubeIDE did not like it.

Anyway, as the patch seems to be adding only one GPIO pin definition, it is easier just the edit the .c file. It is kind of interesting that although the actual diff is only one line in a .c file, the patch size is 45.8MB!

So it seems that the updating 1.1.0 to 1.1.1 won't fix the problem that I was having (i.e. the automatically created template code does not execute, but get stuck reading instruction cache status). Will open another post if reverse-engineering fails.