Hello,
I'm developing a secondary bootloader, for field upgrade, on a F28M36x controlCARD R1.1 and i'm a little confused. See if you guys can guide me.
Right now i'm thinking/developing the following:
- M3 boot from Flash, runs the secondary bootloader (which has a lwIP TFTP server, IPC and Flash drivers) and then jump to the main application;
- C28 wait M3 signal: C28 boot from flash, runs the secondary bootloader (which has IPC and Flash drivers) and then jump to the main application;
- I would use a TFTP client to send updates directly to the M3;
It seems right to me but i was reading the document "F28M35x Firmware Development Package", which describe the TFTP API functions, and I found something about a Ethernet Software Update Module. Appears that this module can operate along with the Ethernet Bootloader and that i could use the LM Flash Programmer to handle the magic packets and flash the .bin into the device remotely.
So i have some questions:
- The way i'm developing is the right/common way to implement a remote update?
- Is the Ethernet Software Update Module working in the F28M36x? Is it a viable/good solution for field upgrades?
- I couldn't find the files "utils/swupdate.c" and "utils/swupdate.h" in the F28M36x MWARE library (neither in the F28M35x).
- I found that these files are present in the TIVA library;
Thank in advance, regards,
Lucas
