STM32N6 cubeMX bugs and function portability problems

[TheImmortal]

With new and fast N6 MCU comes new CubeMX package which is full of bugs and errors, I spending hours to find and solve such problems, now I cant trust cubeMX at all, every function must be checked after code generation !
ADC rank must be 7, but cubeIDE generate 1:

I spent a lot of time trying to enable SPI DMA, when I tried to choose DMA handle I got unknown errors in almost all enabled interfaces (I2C, SPI, UART... ), and in some way after some changes elsewhere, closing, opening .ioc file form cubeIDE, and after next try the error is gone and I finally enabled !
I trying to enable LSE, but because of some error with frequency settings which I cant set, I cant enable !

There I cant find the way to enable DCMI DMA transfer, DMA handle for DCMI is not active, maybe I dont know some things there !?
To get VDDCORE voltage and avoid errors every time after cubeMX generate code I added additional variable ADC_CHANNEL_VCORE, because cube generate ADC_CHANNEL_VCORE, but the correct variable is ADC_CHANNEL_VDDCORE:

There I got more errors, but I dont have a lot of time to post every problem, there I stuck now with DCMI, maybe in next update this problem will be solved, and until this time I have where to work with this MCU, in any way I disappointed, but MCU looks good and have everything for good product.

 

[TDK]

Include your IOC file if you're having issues.

I wasn't able to replicate any issues you describe.

 

 

 

[TheImmortal]

I attached IOC file.

There is one more error, error with FMC sdram initialization, cubeMX do not generate initialization correctly and I getting error: undefined reference to `FMC_SDRAM_Timing_Init', I had to disable  HAL_SDRAM_Init(&hsdram1, &SdramTiming) to work further with my code, with H7 mcu I dont had any problems anywhere and have fully working device, I upgraded/changed to N6 and there I cant move forward...

 

[Mahmoud Ben Romdhane]

Hello @TheImmortal ,

 

First let me thank you for posting and bringing this issue to our attention.

An internal ticket is submitted to the Development Team (Ticket Number: 212870).

 

Thanks.

Mahmoud