Giving control to standalone app.
Dear all,
At the moment U-Boot branches to the OS entry point, U-Boot is dead and no longer exists, does this property hold also when u-boot loads a standalone application.
In fact, I want to 'give control' to a standalone application, what does exactly the word 'give control' mean? e.g. 'giving control' is established by implementing an infinite loop in the standalone such that the body of the loop executes continuously specific tasks or responding to particular interrupts? in such case what happens to u-boot? what if after a particular event in the standalone app I want to return to u-boot?
Please excuse me for this beginner question.
Best wishes.
--
View this message in context: http://u-boot.10912.n7.nabble.com/Giving-control-to-standalone-app-tp183635.html
Sent from the U-Boot mailing list archive at Nabble.com.
Quoted 6 lines · mazen.e
Dear all,
At the moment U-Boot branches to the OS entry point, U-Boot is dead and no longer exists, does this property hold also when u-boot loads a standalone application.
Quoted 10 lines
In fact, I want to 'give control' to a standalone application, what does exactly the word 'give control' mean? e.g. 'giving control' is established by implementing an infinite loop in the standalone such that the body of the loop executes continuously specific tasks or responding to particular interrupts? in such case what happens to u-boot? what if after a particular event in the standalone app I want to return to u-boot?
Please excuse me for this beginner question.
Yes you loop as long as you want to keep doing something, when you return you should end up in u-boot again.
Regards,
Jeroen
Dear
Many thanks for your reply.
But what if mistakenly or accidentally the standalone application write to the memory where u-boot resides, would that cause the standalone application to crash? Otherwise (in case the standalone application has written to u-boot memory without crash ) what happens if the standalone app exit the loop.
Regards,
--
View this message in context: http://u-boot.10912.n7.nabble.com/Giving-control-to-standalone-app-tp183635p183637.html
Sent from the U-Boot mailing list archive at Nabble.com.
Hi mazen.e,
Quoted 9 lines · mazen.e
Dear
Many thanks for your reply.
But what if mistakenly or accidentally the standalone application write to the memory where u-boot resides, would that cause the standalone application to crash? Otherwise (in case the standalone application has written to u-boot memory without crash ) what happens if the standalone app exit the loop.
You're actually asking the very general question "what happens if some code behaves badly", and the very general answer is "then bad things happen".
Specifically, you do realize already that if an application overwrites the U-Boot code in RAM, then upon returning it'll give control back to a corrupted U-Boot, which can have all sorts of bad effects.
Quoted 1 line
Regards,
Amicalement,
Signature · 1 line
Albert.
OK, my best thanks for your great answer.
--
View this message in context: http://u-boot.10912.n7.nabble.com/Giving-control-to-standalone-app-tp183635p183639.html
Sent from the U-Boot mailing list archive at Nabble.com.