BUG MX-Cube cannot allocate any analog inputs without hanging (N657)

[matt-crc]

When I try to allocation any available analog inputs, Cube-MX hangs!!!!

Attached is the .ioc file... To replicate, try to allocate any available Single ended analog input....

sad....

[Ghofrane GSOURI]

Hello @matt-crc 

Thank you for your valuable contribution.

The issue has been escalated to our development team under internal ticket number 220572 for resolution.

I will keep you updated on any progress.

THX

Ghofrane

[Ghofrane GSOURI]

Hello @matt-crc 

Did you use CubeMX 6.15.0 to create the IOC file, or did you use an older version and then migrate to 6.15.0 before encountering the issue?
If you migrated from an earlier version, could you please specify which version you migrated from?

THX

Ghofrane

[matt-crc]

Hi @Ghofrane GSOURI 

The project was started with CubeMX 6.15.0

Matt

[Ghofrane GSOURI]

Hello @matt-crc 

After several attempts to reproduce the issue you encountered using CubeMX 6.15.0, including creating a new IOC from scratch and enabling all the IPs present in your IOC, I was unable to observe the same problem. CubeMX 6.15.0 continued to function correctly, with no crashes or exceptions. This suggests that the issue may be specific to the IOC file you provided.

Upon further review of your IOC, I noticed that the parameter" isbadioc=false" is present. This indicates that the IOC was originally created with an older version of CubeMX and later migrated to version 6.15.0. In light of this, I kindly recommend creating a new IOC file from scratch using CubeMX 6.15.0 and I would appreciate it if you could share your feedback with me after trying this , so we can ensure the issue is fully resolved.

I am sharing my IOC file with you so that you can review it and provide me with guidance.
Your feedback and recommendations will be greatly appreciated.

Ghofrane

[matt-crc]

Hi @Ghofrane GSOURI 

1- I'm absolutely sure that the project was started using CubeMX 6.15.  It was a new clean installation on a new machine.   We typically don't use CubeMX, but rather start the project in CubeIDE instead which calls CubeMX.

2- The other thing is that the original project was started using your STM32N6570-DK project example.  (for your STM32N6570-DK development board).  Not sure if that makes a difference.

3- I will check the TEST_FMC.ioc file that you provided and see if we can use it instead.

Matthew