My suggestion when you port from F7 to H7:
- check the pinmux table of both:
it can be that they differ on which pins are populated, which functions the pin can have etc.
You should never rely on "same pins still with same features" - find the difference via comparing both datasheets. - it is quite likely, that you find the same signal, e.g. SPI1_SCLK, but on a different pin
- If you setup a project for a new MCU - always go with the correct HAL drivers:
Never try to reuse HAL code, drivers, intended for a different MCU. At least all the HAL, CubeMX, ... has to be the "correct" one. - Look if you have BSP files:
Also the BSP files have to be changed. Check carefully that you go with the "correct" BSP for your new board.
At the end, with all the "correct" H-files - you should be able to use the "same" register again, even it would be on a different address. As long as the H-Files are the right ones - a "symbolic register' name should be mapped properly, even it would be a different address.
BUT: there is no guarantee, that with "new" HAL and BSP files - there could be a name change (on API calls, on typedefs, on register and pin names). Just be smart.
And it also happen, that something, e.g. a register, a member in a structure, is not available anymore or it works now slightly different.
Best approach is:
look for examples for this new board (in HAL, BSP) and adapt your code: mainly you have features, like SPI, I2C: do not expect a 1:1 code compatibility. But to bring up SPI, I2C again with new HAL drivers and examples as reference will help you.
Embedded FW is very dependent on the HW: do not expect full code compatibility when changing from one MCU to another. But the features should be possible as before, maybe a bit differently to configure and use.
