fpiSTM wrote: ↑Fri Feb 25, 2022 8:11 am
Hi,
first which core you used ?
What is the requirement for proteus simulation?
Maybe you need to enable debug symbol?
Hi
I don't understand what exactly you mean by CORE. I am new to STM32 and used to work with mega328 most of the time.
As far as I know, the BlackPill F401 is Cortex M4 and I chose the Debug -g for optimization but there is no difference and the simulation doesn't work
By not working simulation I mean that the program runs the simulation but the aim of program which is blinking LED connected to pin 13 of GPIO C doesn't show up. If I use the HEX file produced by STM32cubeIDE, the simulation runs and the LED blinks accordingly.
I brought here the simulation limitation in Proteus from Labcenter Electronics website:
The following is a listing of known limitations in the current version of the ARM® Cortex™-M4:
x Clock security system is not implemented.
x SPI doesn't support IrDA and I2S audio protocols
x I2C::TRISE is not implemented
x I2C doesn't support SMBus protocol
x Tamper detection and backup functionality are not implemented
x Flash programming algorithm is not implemented.
x USB OTG Host capabilities and HNP protocol are not implemented.
x RTC doesn't perform reference clock detection
x RTC doesn't support calibration (RTC_CALR register)
x SDIO is not implemented
x Pins VCAP_1 and VCAP_2 are not modeled
x USART doesn't support Smartcard, LIN, IrDA protocols
Is it possible that one of the aforementioned limitations be the source of the weird Proteus behavior?
Thanks for your attention