cancel
Showing results for 
Search instead for 
Did you mean: 

I have to do the porting from a MCU STM32F429 to a MCU STM32F767.. How do you see the effort in doing the porting? Which are the tricky parts I should consider.. ? The project was designed with sw4stm32

SGasp.1
Senior
4 REPLIES 4

Devil is of course in the details, but for a basic guideline, read AN4660.

JW

SGasp.1
Senior

Ok without reading all the datasheet.. pinout should be the same... what about the memory map and the registers ?

>>How do you see the effort in doing the porting?

Depends if you write portable code, or if your code has a lot of register/bit level minuta of the chips internals.

Are you using register level code, or HAL/SPL?

Watch for caching, and your relationship with memory.

For DMA perhaps use the DTCM RAM to avoid coherency issues.

Familiarize yourself with the MPU and how you can describe memory attributes for different areas.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
SofLit
ST Employee

The most tricky point is the cache usage and its maintenance.

I would suggest to read:

  • AN4667 STM32F7 Series system architecture and performance.
  • AN4839 Level 1 cache on STM32F7 Series and STM32H7 Series
  • AN4838 Managing memory protection unit in STM32 MCUs
  • AN4660 Migration of microcontroller applications from STM32F42xxx/F43xxx devices to STM32F7 Series devices --> mostly for HW part.
  • AN4861 LCD-TFT display controller (LTDC) on STM32 MCUs / section 4.6 Special recommendations for Cortex-M7 (STM32F7/H7)

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.