On 11/4/2016 7:50 AM, Paul Plankton wrote: > OK just to understand this: > > To clarify, the 512 bytes is just for the first sector of the MBR that has > the partition table in it. We actually skip by that to an offset of 128k. > Based on Robert's instructions, 256 *k*bytes (384-128) is reserved for the > MLO. Of course, MLO needs to fit in the internal RAM of the processor > since > this is the first place the DDR is configured, so your MLO would never get > to be that large. > > First 512 Bytes are the MBR including the partition table and some other > "magic" > things. Then the MLO-file is appended (directly at 512 bytes or with an > offset > of 128k?). > > But: who is responsible to jump into the MLO-"file" at it's position in > flash? > Isn't there a special MBR-code needed that knows where to continue?
This is not an x86 system that runs code from the MBR to boot-strap the system. The code that loads and executes MLO is in the on-chip ROM, details are in chapter 26 "Initialization" of the TRM. Read through section 26.1.7.5 "MMC / SD Cards". -- Charles Steinkuehler char...@steinkuehler.net -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/9a454233-eadb-78f0-8a95-94f9e347097a%40steinkuehler.net. For more options, visit https://groups.google.com/d/optout.
