How i can migrate from F4/L1 to L4?

[cionu]

Hi. I want to connect a STM32L475RG board with an shield,

(S2868A1) which comunicated on SPI protocol. More that, i want to connect these 2 components with another Stm32L4 and S2868a1, via S2-LP mode.

Can somebody offer me a code or explain how i can migrate from F4/L1 to L4?

[Imen.D]

Hello,

You can start with X-CUBE-SUBG1 expansion software package to start developing using S2-LP and S2868A1 expansion boards.

There are these application notes available regarding the migration from STM32F4 and STM32L1 to STM32L4 that can help you on the migration.

• AN4616 Application note Migrating from STM32F401 and STM32F411 lines to STM32L4 Series and STM32L4+ Series microcontrollers

https://www.st.com/content/ccc/resource/technical/document/application_note/group0/87/fc/79/9d/3c/cc/49/84/DM00144612/files/DM00144612.pdf/jcr:content/translations/en.DM00144612.pdf

• AN4821 Application note Migrating from STM32F405/415 line and STM32F407/417 line to STM32L4 Series and STM32L4+ Series microcontrollers

https://www.st.com/content/ccc/resource/technical/document/application_note/group0/02/46/be/cf/31/75/4e/de/DM00263732/files/DM00263732.pdf/jcr:content/translations/en.DM00263732.pdf

• AN4612 Application note Migrating from STM32L1 Series to STM32L4 Series and STM32L4+ Series microcontrollers

https://www.st.com/content/ccc/resource/technical/document/application_note/group0/4b/2a/a4/df/99/31/49/71/DM00141025/files/DM00141025.pdf/jcr:content/translations/en.DM00141025.pdf

Kind Regards,

Imen

[Tesla DeLorean]

Porting is one of those staples of embedded development.

Find a like-for-like type platform moving from one NUCLEO to another typically involves less pin changes. The F4 and L4 have some architectural differences.

Make a scratch or donor project on the target board, get USART, SWV an basic functionality working. Mod the code in a way that simplifies the reception of the original code.

Use a good merge tool. Pull in code a section at a time. The code doesn't have to execute, at some level you are trying to insure the project continues to build, and address syntax errors/changes in the API, or pin usage. How much you bring in at a time depends on how overwhelming the changes are.

I migrated the LoRa code to L4 and F7 platform via NUCLEO boards, I also went from NUCLEO-64 to NUCLEO-144 within the same families, this allowed changes in pin/USART usage to be understood, addressed and refactored within a platform that was still buildable. For the NUCLEO in a given platform it was then an easier port to DISCO or custom boards.

[LCout]

Hello,

Have you managed to connect your two STM32L4 ?

I have the same issue, your help would be very great !

[waclawek.jan]

Start a new thread stating what's exactly your problem.

JW