I am new to Mbed but would really like to master this interesting operating system and development environment. This is my first post on this forum and site!
Mbed interested me primarily in the fact that I can do complex things simply!
One of the tasks is to update the firmware over the network (IAP).
Searching the forum gives links to Flash IAP which in turn gives a link to Mbed Stress Test
I tried compiling this code under https://ide.mbed.com/
and the code did not compile absolutely correctly, since there is no file main.cpp and function main.
There is a usage description in the README.md file, but it’s probably for Linux, and I’m using Windows.
How can this example be compiled under Windows for board types Nucleo-F411+Net shield or/and Nucleo-F767, both with external memory card?
How can I test the example over the network?
What do you recommend to read on this site and beyond on this topic?
Thanks for the links to the documentation and code examples.
The documentation is really very helpful for understanding how Mbed works.
However, in your examples, there is a code for writing one of the files on demand from an SD card. In this case, the software update via Ethernet will be in two stages:
Accept the firmware file using one of the file transfer protocols and write it to the SD card.
On command, write the firmware file from the SD card to the memory of the target controller and restart the program.
In the example from ST, an update is implemented without an intermediate file storage, this is more interesting, because there is not always an SD card or external SPI memory of the required size. STM32Cube Ethernet IAP example
I don’t know how correct this is from the point of view of the integrity of the firmware. Is it possible to implement such an algorithm in Mbed?
I studied the Mbed Stress Test example, it was an unforgettable few hours with a Linux-style command line.
But I managed to install and configure the CLI, connect the compiler from Keil MDK ARM, compile the Mbed Stress Test project and understand what its meaning is and what it is for. I’ve never heard of automated testing in embedded systems before, it’s really cool!
What would you recommend to read about testing in general and its application in embedded systems?
Thanks for the useful information.
I will continue to study the issue, if there are interesting results - I will share.
I looked at the option with Pelion, but I was confused by the option with a paid service and transferring firmware through a third party.
In fact, not always.
You can see the \bootloader folder and mbed_app.json in the Pelion example.
The loader, the application and the update candidate can be placed in the built-in memory, if this memory is enough, this is not the case for my F411.