Auto update application in a embedded board

Hello, I've been dealing with U-boot for a couple of months now and I'm still struggling on how to implement an application to execute an auto updateof a kernel image or a root file system. According to this u-boot FAQ, it depends on how you distribute your updates (network or USB mass storage device). How do I achieve this through a USB gadget mode(not the mass storage device but the actual board itself connected to the host pc via usb port)? I made the auto_update.c as a reference to create my own auto update through the board's USB gadget mode but I'm stuck at the update. Any advice or resources will be very helpful. Hoping for your kind reply. Thank you.

I guess the first thing is to define what you mean by 'auto update'. When your system boots, where does it find its kernel and root filesystem? What mechanisms are available to modify those elements? Like most embedded systems issues, these kinds of things are very system-specific, and without knowing details of your system it is hard to know what might be a solution.
--- rod.

Originally Posted by theNbomr I guess the first thing is to define what you mean by 'auto update'. When your system boots, where does it find its kernel and root filesystem? What mechanisms are available to modify those elements? Like most embedded systems issues, these kinds of things are very system-specific, and without knowing details of your system it is hard to know what might be a solution. --- rod.

Thank you for the reply Sir, you've been very helpful to all of my threads . Auto update, in my case, would mean updating the kernel image and/or the root fs without the end user having to type u-boot commands. U-boot supports scripting but the script (I have a script that would erase, write and read through the device's memory) has to be triggered by a command. The kernel image and the root fs already has a specific address, both are already mapped. Uhmm, is it possible to have an application residing in u-boot? If it is, I'm wondering how could it be triggered.

Okay, let me re-state my question. What do you mean by 'update'; never mind the 'auto' part. When your host boots, from where does it load its kernel and filesystem? How does the kernel and filesystem data get to where it is when the system boots? I don't use U-boot, but I assume that it will load from a default place, unless given some alternate interactive instructions. If so, what mechanism populates that 'default place'?

--- rod.