stlink/config/chips/F302_F303_F358.chip

# Chip-ID file for STM32F3xx device (F302xBxC, F303xB/C, F358)
#
dev_type STM32F302_F303_358
ref_manual_id 0365           // also RM0316
chip_id 0x422                // STM32_CHIPID_F3
flash_type F0_F1_F3
flash_size_reg 0x1ffff7cc
flash_pagesize 0x800         // 2 KB
sram_size 0xa000             // 40 KB
bootrom_base 0x1ffff000
bootrom_size 0x800           // 2 KB
option_base 0x1ffff800       // STM32_F0_OPTION_BYTES_BASE
option_size 0x10             // 16 B
flags swo
[refactoring] Clean-up & update for chipid files - F0, F1, F2, F3, F4, F7 - G0, G4 - H7 - L0, L5, U5 - WB, WL 2022-01-06 18:30:49 +00:00			`# Chip-ID file for STM32F3xx device (F302xBxC, F303xB/C, F358)`
Update chip config files from the library structs In general, the chip config files should be kept in sync with the old library structs. Regenerate the files (using an ad hoc script) from the current library. The file name is generated from the chip description, all non-alphanumeric characters are replaced with underscores. It turns out some files have to have their names changed. 2021-08-21 14:43:26 +00:00			`#`
[refactoring] Clean-up & update for chipid files - F0, F1, F2, F3, F4, F7 - G0, G4 - H7 - L0, L5, U5 - WB, WL 2022-01-06 18:30:49 +00:00			`dev_type STM32F302_F303_358`
			`ref_manual_id 0365 // also RM0316`
[refactoring] Clean-up for headers & defines - Removed additional extern "C" linkage specs - Removed commented sections - Moved out further device specific defines - Renamed defines STM32_CHIP_ID_* 2022-01-16 18:31:22 +00:00			`chip_id 0x422 // STM32_CHIPID_F3`
Updated device parametres - Human-readable FLASH_TYPE in .chip files - Added enum for STM32_CORE_IDs 2022-01-20 22:19:10 +00:00			`flash_type F0_F1_F3`
[refactoring] Clean-up & update for chipid files - F0, F1, F2, F3, F4, F7 - G0, G4 - H7 - L0, L5, U5 - WB, WL 2022-01-06 18:30:49 +00:00			`flash_size_reg 0x1ffff7cc`
			`flash_pagesize 0x800 // 2 KB`
			`sram_size 0xa000 // 40 KB`
Update chip config files from the library structs In general, the chip config files should be kept in sync with the old library structs. Regenerate the files (using an ad hoc script) from the current library. The file name is generated from the chip description, all non-alphanumeric characters are replaced with underscores. It turns out some files have to have their names changed. 2021-08-21 14:43:26 +00:00			`bootrom_base 0x1ffff000`
[refactoring] Clean-up & update for chipid files - F0, F1, F2, F3, F4, F7 - G0, G4 - H7 - L0, L5, U5 - WB, WL 2022-01-06 18:30:49 +00:00			`bootrom_size 0x800 // 2 KB`
			`option_base 0x1ffff800 // STM32_F0_OPTION_BYTES_BASE`
			`option_size 0x10 // 16 B`
Update chip config files from the library structs In general, the chip config files should be kept in sync with the old library structs. Regenerate the files (using an ad hoc script) from the current library. The file name is generated from the chip description, all non-alphanumeric characters are replaced with underscores. It turns out some files have to have their names changed. 2021-08-21 14:43:26 +00:00			`flags swo`