Add STM32F303DExx and STM32VExx Variants#3016
Conversation
- Add missing ldscript to correct variants folder for above processor variants
fpistm
left a comment
There was a problem hiding this comment.
Thanks for the PR.
Please, reference new mcu support in the README.md.
| # Generic F303VEHx | ||
| GenF3.menu.pnum.GENERIC_F303VEHX=Generic F303VEHx | ||
| GenF3.menu.pnum.GENERIC_F303VEHX.upload.maximum_size=524288 | ||
| GenF3.menu.pnum.GENERIC_F303VEHX.upload.maximum_data_size=65536 | ||
| GenF3.menu.pnum.GENERIC_F303VEHX.build.board=GENERIC_F303VEHX | ||
| GenF3.menu.pnum.GENERIC_F303VEHX.build.product_line=STM32F303xE | ||
| GenF3.menu.pnum.GENERIC_F303VEHX.build.variant=STM32F3xx/F303V(D-E)(H-T) | ||
| GenF3.menu.pnum.GENERIC_F303VEHX.debug.svd_file={runtime.tools.STM32_SVD.path}/svd/STM32F3xx/STM32F303.svd | ||
|
|
||
| # Generic F303VDTx | ||
| GenF3.menu.pnum.GENERIC_F303VDTX=Generic F303VDTx | ||
| GenF3.menu.pnum.GENERIC_F303VDTX.upload.maximum_size=393216 | ||
| GenF3.menu.pnum.GENERIC_F303VDTX.upload.maximum_data_size=65536 | ||
| GenF3.menu.pnum.GENERIC_F303VDTX.build.board=GENERIC_F303VDTX | ||
| GenF3.menu.pnum.GENERIC_F303VDTX.build.product_line=STM32F303xE | ||
| GenF3.menu.pnum.GENERIC_F303VDTX.build.variant=STM32F3xx/F303V(D-E)(H-T) | ||
| GenF3.menu.pnum.GENERIC_F303VDTX.debug.svd_file={runtime.tools.STM32_SVD.path}/svd/STM32F3xx/STM32F303.svd |
There was a problem hiding this comment.
Reorder by alphabetical order.
| # Generic F303VEHx | |
| GenF3.menu.pnum.GENERIC_F303VEHX=Generic F303VEHx | |
| GenF3.menu.pnum.GENERIC_F303VEHX.upload.maximum_size=524288 | |
| GenF3.menu.pnum.GENERIC_F303VEHX.upload.maximum_data_size=65536 | |
| GenF3.menu.pnum.GENERIC_F303VEHX.build.board=GENERIC_F303VEHX | |
| GenF3.menu.pnum.GENERIC_F303VEHX.build.product_line=STM32F303xE | |
| GenF3.menu.pnum.GENERIC_F303VEHX.build.variant=STM32F3xx/F303V(D-E)(H-T) | |
| GenF3.menu.pnum.GENERIC_F303VEHX.debug.svd_file={runtime.tools.STM32_SVD.path}/svd/STM32F3xx/STM32F303.svd | |
| # Generic F303VDTx | |
| GenF3.menu.pnum.GENERIC_F303VDTX=Generic F303VDTx | |
| GenF3.menu.pnum.GENERIC_F303VDTX.upload.maximum_size=393216 | |
| GenF3.menu.pnum.GENERIC_F303VDTX.upload.maximum_data_size=65536 | |
| GenF3.menu.pnum.GENERIC_F303VDTX.build.board=GENERIC_F303VDTX | |
| GenF3.menu.pnum.GENERIC_F303VDTX.build.product_line=STM32F303xE | |
| GenF3.menu.pnum.GENERIC_F303VDTX.build.variant=STM32F3xx/F303V(D-E)(H-T) | |
| GenF3.menu.pnum.GENERIC_F303VDTX.debug.svd_file={runtime.tools.STM32_SVD.path}/svd/STM32F3xx/STM32F303.svd | |
| # Generic F303VDTx | |
| GenF3.menu.pnum.GENERIC_F303VDTX=Generic F303VDTx | |
| GenF3.menu.pnum.GENERIC_F303VDTX.upload.maximum_size=393216 | |
| GenF3.menu.pnum.GENERIC_F303VDTX.upload.maximum_data_size=65536 | |
| GenF3.menu.pnum.GENERIC_F303VDTX.build.board=GENERIC_F303VDTX | |
| GenF3.menu.pnum.GENERIC_F303VDTX.build.product_line=STM32F303xE | |
| GenF3.menu.pnum.GENERIC_F303VDTX.build.variant=STM32F3xx/F303V(D-E)(H-T) | |
| GenF3.menu.pnum.GENERIC_F303VDTX.debug.svd_file={runtime.tools.STM32_SVD.path}/svd/STM32F3xx/STM32F303.svd | |
| # Generic F303VEHx | |
| GenF3.menu.pnum.GENERIC_F303VEHX=Generic F303VEHx | |
| GenF3.menu.pnum.GENERIC_F303VEHX.upload.maximum_size=524288 | |
| GenF3.menu.pnum.GENERIC_F303VEHX.upload.maximum_data_size=65536 | |
| GenF3.menu.pnum.GENERIC_F303VEHX.build.board=GENERIC_F303VEHX | |
| GenF3.menu.pnum.GENERIC_F303VEHX.build.product_line=STM32F303xE | |
| GenF3.menu.pnum.GENERIC_F303VEHX.build.variant=STM32F3xx/F303V(D-E)(H-T) | |
| GenF3.menu.pnum.GENERIC_F303VEHX.debug.svd_file={runtime.tools.STM32_SVD.path}/svd/STM32F3xx/STM32F303.svd | |
|
I'm also looking at the generic_clock.c file (I didn't change it before, so was running at the default) but I have a question: On the wiki, it states use the HSI for the PLL Mux, however doing this in CubeMX, it tells me PLL Source Mux must use HSE as input - what do I do here? |
|
It is an advice when you configure the USB. HSE is more stable. |
|
Okay, so I've tried that, and the code that it generates doesn't work - the processor doesn't appear to run If I disable the USB, the generated clock init code works fine. I'll look at creating the usb clock init manually, instead of using cubeMX |

Summary
This PR fixes/implements the following bugs/features
Adds support for new processors, currently missing from the 'Board Part Number' Menu
Validation
Closing issues
closes #3013