2018-02-01 02:50 AM
Hello,
I am already using stm32f030c8t6 in various projects. And for larger flash controller i decided to opt for stm32f030cct6.
when i read my target device having stm32f030cct6(printed on IC), it responds the message
16:21:42 : ST-LINK SN : 56FF73066772565605300567
16:21:42 : ST-LINK Firmware version : V2J21S416:21:42 : Connected via SWD.16:21:42 : Connection mode : Normal.16:21:42 : Device ID:0x442 16:21:42 : Device flash Size : 256KBytes16:21:42 : Device family :STM32F09xx.Please note the family(STM32F09xx) read from micro using st-link utility is different from printed part number(stm32f030cct6).
Now i am confused that which ic i am using and what are the feature of it. whether it belong to
stm32f030xx family or stm32f09xx family.
Also difficult to decide which .asm file i should use, either startup_stm32f030.s or startup_stm32f091.s. Because both beth to different family and different peripherals also.
Please guide me asap.
2018-02-01 03:08 AM
maybe they are indeed from the same die but spec's (officially) differently. it has been fairly common among st's mcus. some have more space than spec'd, some non-USB mcus have indeed USB, ...
what does the uid say about your chip?
2018-02-01 04:18 AM
He said he is not aware of this and after his research he did not gave me a valid reason. Also he did not clear me which .asm file i should use. Currently i am using
startup_stm32f030.s
in my project. I made my project with bootloader and application code. Now I am facing too much problem of uC like auto-ressetting randomly in some systems and PC14 pin used as input not working properly in other ones.2018-02-02 09:52 PM
any one help will be appreciated.
Actually it is very important for me to solve this issue.
Most of my system are misbehaving sometimes like DIDO pins auto triggering UART receiving unkown data and sometime get auto reset. It really a danger non identifiable symptoms , i cant be able to declare whether it is hardware issue or software. Please guide me.