OK that not it I think.

I've tried to understand when the header is written in the MLO. And it
looks like that it is the mkimage job . ( not sure ) .

the mkimage is call to create the MLO file. I discovered that the
function omapimage_set_header is called to create the header file.

So it's not at all this structure

typedef struct image_header {
        __be32          ih_magic;       /* Image Header Magic Number    */
....................
} image_header_t;

but it's using this header : struct gp_header.


And that where I'm confused, because in the file : common/spl/spl_mmc.c
it's looking at this header :

struct image_header *header;

        header = (struct image_header *)(CONFIG_SYS_TEXT_BASE -
                                         sizeof(struct image_header));


What is wrong Robert Nelson, Where am I wrong ?


Le ven. 17 juin 2016 à 18:50, Micka <[email protected]> a écrit :

> ok
>
> When I compile the uboot, are we using this one ?
>
> arch/arm/cpu/armv7/start.S
>
> Can we add something like that :
>
>         .long   0x27051956              /* U-Boot Magic Number
>      */
>
>
>
> Le ven. 17 juin 2016 à 18:47, Robert Nelson <[email protected]> a
> écrit :
>
>> On Fri, Jun 17, 2016 at 11:31 AM, Micka <[email protected]> wrote:
>> > Lol, ok
>> >
>> > But what went wrong ?  It's checking a magic number to prevent something
>> > broken.
>> >
>> > Can I write back the correct magic number ?
>> >
>> > I found that in this file : arch/powerpc/cpu/mpc8xx/start.S
>> >
>> > it write somewhere the magic number : 0x27051956
>> >
>> > But I don't see where the magic number is written for the beaglebone
>> black
>> > uboot.
>>
>> it's for something generic, but we don't use it.. I'm tempted to just
>> patch it like my joke, as people do ask..
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRtk0acqiw%2Bmx9SO1O_n-ofS3D%3DJr7VOw9U7HbuVif3ErBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to