Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

Wi-Fi Combo Forum Discussions

user_2177781
Level 5
Level 5
25 likes received 10 likes received 5 likes given

Hello,

I'm trying to generate a single DFU file to use wuth the onboard DFU flashing method of a STM32F4xx MCU.

I want to create a DFU file which contains all elements, such as bootloader, DCT and application.

I have previous, with success, generated DFU files containing DCT and application, so my objective now is to add the bootloader at the front. But my problem comes when I go into the build folder and determines that my bootloader file (bootloader-NoOS-NoNS-STM32F427-SDIO.bin) is 128MB . What is happening here ?

- Regards

Renejos

0 Likes
2 Replies
user_2177781
Level 5
Level 5
25 likes received 10 likes received 5 likes given

To info the console shows the following

waf_bootloader-NoOS-NoNS-STM32F427

----------------------------------|---------|---------|

                                  |         |  Static |

              Module              |  Flash  |   RAM   |

----------------------------------+---------+---------|

efs_STM32F427                     |   11160 |   32956 |

Host MCU-family library           |    8362 |     208 |

Interrupt Vectors                 |     424 |       0 |

libc                              |    5766 |    6172 |

Other                             |     576 |   69632 |

platform                          |    1496 |      96 |

RAM Initialisation                |    2132 |       0 |

Ring_Buffer                       |      36 |       0 |

SPI_Flash_Library_STM32F427       |     720 |       0 |

Startup Stack & Link Script fill  |       2 |       0 |

WWD                               |     198 |       4 |

----------------------------------+---------+---------|

TOTAL (bytes)                     |   28740 |  109068 |

----------------------------------|---------|---------|

0 Likes

Hi Renejos,

Try a make "clean" and it will remove any unnecessary files. Did you add any additional drivers? That might pull in some other libraries it uses and bloat up the bootloader as well. You can check the resource allocation of the bootloader in /build/bootloader.log. Hope this helps.

Thanks,

Jaeyoung

0 Likes