2021-05-08 07:44 PM
Hi Community,
I am starting my first project with CubeIDE with GCC.
I am really impressed and appreciative of the integration of tools.
My Setup: CubeID: Version 1.6.1, Build: 9958_20210326_1446 (UTC
I am configured for a stm32f412
I want to use a SPI interface as a master that will not use the MISO line but I do NOT want to configure the device as a Master w/ 'receive-only' because the clock behaves differently in that mode (always clocking when spi is enabled).
I want to be able to transmit dummy bytes to clock the receive data in.
My code generation for both SPI and GPIO is set to LL api's. via Project Manager->Advanced Settings.
Here is the problem:
CubeIDE doesn't allow me to have an unassigned MISO line and still have the SPI block enabled.
Perhaps a possible (but ugly) workaround is to have another pin wrongly assigned as MISO in CubeIDE and reassign the MISO line in the user code section at the end of the spi.
If this is indeed a bug, what is the proper way to report bugs in CubeIDE?
Thanks in advance,
Eric
2021-05-08 11:32 PM
> If this is indeed a bug,
Cube, as any other "library", and CubeMX as its clicky configurator, inevitably cover only a tiny fraction of the virtually unlimited possible combination of how the hardware can be configured and used. A "most used" subset of features is selected by the authors, and as long as you fit into that group, you are OK with clicking; otherwise Cube mostly gets into your way.
Feel free to report it as a bug and demand correction, but then others can see other combinations of settings as bug, and there's only that much time and effort which can be spent on the clicky. ST refuses to provide normal examples (see Amel's response there) on grounds of "it's too much work", and allocating more and more resources on the clicky is the main reasons.
JW