<div>Hi all,</div>
<div>In Android target mobiles there is a facility called "Ramdump", where the entire Ram image is copied to a file</div>
<div>as the kernel goes to panic.</div>
<div> </div>
<div>Ramdump is implemented like this</div>
<div>1) As the panic() function is called target will be reset.</div>
<div>2) Bootloader boots up in specific mode, where it enables the USB driver in uploading mode.</div>
<div>3) Through USB entire RAM content is copied to a file in the host computer.</div>
<div>4) This file is parsed through different tools and we can get the logs info wat exactly happened just before kernel panic happend.</div>
<div> </div>
<div> </div>
<div>Now here is the interesting part,</div>
<div>While the mobile's RAM image is being uploaded to host computer, our bootloader is still running in the mobile's RAM.</div>
<div>How can it copy its own running region.</div>
<div> </div>
<div>This triggered me the following questions,</div>
<div> </div>
<div>1) When bootloader runs, will it run in a specific reserved region of RAM or it takes entire RAM?</div>
<div>2) When it hands over the control to kernel, will it relinquish the entire RAM or certain part of RAM is reserved for it?</div>
<div>3) Does kernel use the entire RAM while running?</div>
<div>4) When the kernel is running, is ther any chance that, control again be taken back to bootloader?(coz i saw in bootloader code kernel is being called, </div>
<div> after that code also some code is there,some printks and error handling stuff)</div>
<div> </div>
<div>Pls help me out here..</div>
<div> </div>
<div><br clear="all"><br>-- <br>With regards,<br>Sandeep Kumar Anantapalli,<br><br></div>