[U-Boot] MACHINE ID

[U-Boot] MACHINE ID

[Marek Vasut]

On Sunday 21 November 2010 07:47:07 hong zhang wrote:
> --- On Sat, 11/20/10, Oliver Schneidewind <oliver-ml@schneidewind-
consulting.de> wrote:
> > From: Oliver Schneidewind <oliver-ml@schneidewind-consulting.de>
> > Subject: Re: MACHINE ID
> > To: linux-arm at lists.infradead.org
> > Date: Saturday, November 20, 2010, 1:58 PM
> > On 19.11.2010 23:40, Russell King -
> > 
> > ARM Linux wrote:
> > > On Fri, Nov 19, 2010 at 01:16:48PM -0800, hong zhang
> > 
> > wrote:
> > >   
> > >
> > >> Uncompressing Linux... done, booting the kernel.
> > >> 
> > >> Error: unrecognized/unsupported machine ID (r1 =
> > 
> > 0x000007d9).
> > 
> > >> Available machine support:
> > >> 
> > >> ID (hex)    NAME
> > >> 00000af0    ti8168evm
> > >> 
> > >> Please check your kernel config and/or
> > 
> > bootloader.
> > 
> > >> I feel the U-boot does not put 0xaf0 to r1 instead
> > 
> > 0x7d9. Actually both
> > 
> > >> of them are listed in arch/arm/tools/mach-types.
> > 
> > Why does not kernel
> > 
> > >> match with 0x7d9?
> > >>
> > >>     
> > >>
> > > 7d9 is 2009:
> > > 
> > > sapphira           
> > 
> >     MACH_SAPPHIRA       
> >    SAPPHIRA         
> >       2009
> > 
> > > which is a 'sapphira' platform, not a ti8168evm. 
> > 
> > Whoever programmed
> > 
> > > your boot loader stole some other platforms ID.
> > > 
> > > I suggest you check whether your version of u-boot
> > 
> > supports changing
> > 
> > > the ID via a script.  I don't know u-boot that
> > 
> > well, so I can't tell
> > 
> > > you how.
> > >
> > >   
> > 
> > for a short work around you can set the Environment
> > Variable
> > "machid" in that case uboot use the value of this Variable
> > as mach id
> > instead of the compiled one.
> 
> Oliver,
> 
> I set arcNumber but no use. What difference between machid and arcNumber?

CCing U-Boot mailing list ...

machid is what you use (if the company that made your board didn't mess up with 
it)
> 
> ---Henry
> 
> > _______________________________________________
> > linux-arm mailing list
> > linux-arm at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm
> 
> _______________________________________________
> linux-arm mailing list
> linux-arm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm

[U-Boot] MACHINE ID

[Bedia, Vaibhav]

-----Original Message-----
From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Marek Vasut
Sent: Tuesday, November 23, 2010 7:49 AM
To: linux-arm at lists.infradead.org
Cc: u-boot at lists.denx.de; hong zhang; Oliver Schneidewind
Subject: Re: [U-Boot] MACHINE ID

On Sunday 21 November 2010 07:47:07 hong zhang wrote:
> --- On Sat, 11/20/10, Oliver Schneidewind <oliver-ml@schneidewind-
consulting.de> wrote:
> > From: Oliver Schneidewind <oliver-ml@schneidewind-consulting.de>
> > Subject: Re: MACHINE ID
> > To: linux-arm at lists.infradead.org
> > Date: Saturday, November 20, 2010, 1:58 PM
> > On 19.11.2010 23:40, Russell King -
> > 
> > ARM Linux wrote:
> > > On Fri, Nov 19, 2010 at 01:16:48PM -0800, hong zhang
> > 
> > wrote:
> > >   
> > >
> > >> Uncompressing Linux... done, booting the kernel.
> > >> 
> > >> Error: unrecognized/unsupported machine ID (r1 =
> > 
> > 0x000007d9).
> > 
> > >> Available machine support:
> > >> 
> > >> ID (hex)    NAME
> > >> 00000af0    ti8168evm
> > >> 
> > >> Please check your kernel config and/or
> > 
> > bootloader.
> > 

Hi,

This error is due to an incorrect machid being passed to the kernel.

This can be fixed using the following commands:

TI8168_EVM# setenv machid af0
TI8168_EVM# saveenv
TI8168_EVM# reset

Next time the EVM boots, correct machid will be passed to the kernel and this issue will go away.

Regards,
Vaibhav

[U-Boot] MACHINE ID

[Wolfgang Denk]

Dear "Bedia, Vaibhav",

In message <FCCFB4CDC6E5564B9182F639FC356087035ED455CE@dbde02.ent.ti.com> you wrote:
>
> This error is due to an incorrect machid being passed to the kernel.
> 
> This can be fixed using the following commands:
> 
> TI8168_EVM# setenv machid af0

Note that is is a workaround at best, not a fix. For a fix the
incorrect value needs to be substituted in the board config file.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The explanation requiring the fewest assumptions is the  most  likely
to be correct.                                    -- William of Occam

[U-Boot] MACHINE ID

[Bedia, Vaibhav]

On Wednesday, November 24, 2010 1:24 AM, Wolfgang Denk wrote:
> Dear "Bedia, Vaibhav",
> 
> In message
> <FCCFB4CDC6E5564B9182F639FC356087035ED455CE@dbde02.ent.ti.com> you
> wrote:  
>> 
>> This error is due to an incorrect machid being passed to the kernel.
>> 
>> This can be fixed using the following commands:
>> 
>> TI8168_EVM# setenv machid af0
> 
> Note that is is a workaround at best, not a fix. For a fix the
> incorrect value needs to be substituted in the board config file. 
> 
This issue was only with the first version of the code.
This was fixed in the subsequent versions and we will be submitting the patches to the U-Boot list for review.

Regards,
Vaibhav

[U-Boot] Machine ID

[Vic]

Hi All.

I'm having difficulty with getting a board booting Linux from U-boot. 
This is an existing unit, so I don't get much choice over changing 
versions of kernel of U-boot.

bdinfo gives me the machine ID I expect, but when I try to boot my 
newly-built kernel, I get an "unsupported machine ID" error; the vlaue 
it prints is not what U-boot gives me, and not what I expect. The 
supported types for this kernel do include the machine ID I'm tryin to 
use...

Would someone walk me through the process by which U-boot sends the 
machine ID to the kernel, please? That's clearly gone wrong somewhere.

Many thanks,

Vic.

[U-Boot] Machine ID

[Chris Packham]

On Fri, May 12, 2017 at 9:53 PM, Vic <vic@chamsys.co.uk> wrote:
> Hi All.
>
> I'm having difficulty with getting a board booting Linux from U-boot. This
> is an existing unit, so I don't get much choice over changing versions of
> kernel of U-boot.
>
> bdinfo gives me the machine ID I expect, but when I try to boot my
> newly-built kernel, I get an "unsupported machine ID" error; the vlaue it
> prints is not what U-boot gives me, and not what I expect. The supported
> types for this kernel do include the machine ID I'm tryin to use...
>
> Would someone walk me through the process by which U-boot sends the machine
> ID to the kernel, please? That's clearly gone wrong somewhere.
>

You haven't specified which u-boot or Linux versions you're using so
I'm going to assume a recent version of each.

The machid is passed to the kernel in r1 see boot_jump_linux[1], it is
possible to override it with the "machid" environment variable.

Most arm platforms supported by Linux these days use a device-tree
which basically makes the machid redundant, but it does mean u-boot
needs to be passing a device-tree blob for the platform. If you are
using a version of u-boot that can't pass a device-tree blob to the
kernel you will need to build your kernel with
CONFIG_ARM_APPENDED_DTB.

--
[1] - http://git.denx.de/?p=u-boot.git;a=blob;f=arch/arm/lib/bootm.c;hb=HEAD#l390