In the FAT/MBR mode, rom code searches for MLO file in the root directory,
that's all it needs. In the raw mode, it searches for Configuration Header
at the sectors #0, 256, 512, 768 first, to detect the raw mode valid image.
Do you put CH at sector 256? Not just your MLO. If you put only MLO fi
It looks new BBG uses "raw mode" of rom code's memory booting. MLO goes at
the sector #256 (in fact at #257, CH goes at #256). Configuration Header
(CH) directs the rom code to load the "raw" image from the next sector,
where GH and your image come. In fact all this thing is abysmally and
incor
четвер, 18 серпня 2016 р. 01:49:56 UTC+3 користувач john3909 написав:
>
> I recommend you ask your question on Texas Instruments E2E website
>
> e2e.ti.com
>
> I’m not sure anyone here would have this level of detailed knowledge.
>
> Regards,
> John
>
>
Thank you for the recommendation. I did so
Hi, all. My question is that:
I need to make use a Rom code's raw mode of reading its payloads from both
SD cards and eMMC.
My question is whether the CH (Configuration Header) needed in this case?
TI's TRM on Sitara am335x states CH *must* be located at the sector #0,
and says it might be void (
пʼятниця, 15 квітня 2016 р. 17:18:08 UTC+3 користувач Joshua Datko написав:
>
> Last I looked into this, there is a HS (high security) version of the
> processor that supports the features you mention. Or, at least secure
> boot. I have never been able to find the guy that knows the guy to get
Hi, sorry for my english.
Suppose I want to implement my own firmware for BBB (particularly),
specifically - UEFI. (In fact, I am working on it, but by now I am to far
from the hardware part yet.) And also I want at least to try to implement
my own Secure world software stack (It's not necessar
