Error: unrecognized/unsupported machine ID (r1 = 0x000008f0)

This forum is for users of Atmel's SAM Series and who are interested in using Linux OS.

Moderator: nferre

cali90
Posts: 8
Joined: Tue Mar 03, 2015 10:54 am

Error: unrecognized/unsupported machine ID (r1 = 0x000008f0)

Wed Jan 18, 2017 7:23 pm

Hi all,
I build a new kernel (4.4) with device tree support for board based on sam9g20ek archithecture.

I refer me to linux4sam web site and I had follow this procedure.

1st : load new software on my board :
incluing on zip file : linux4sam-buildroot-at91sam9g20ek_linux4sam_4.2.zip
Ok my board boot correctlly.
2nd step : test build kernel.
git clone git://github.com/linux4sam/linux-at91.git
git checkout origin/linux-3.6.9-at91 -b linux-3.6.9-at91
[*]this kernel version is the same than the version implemented on zip file (refer 1 st step)
make at91_dt_defconfig
adding with menuconfig for debug :

Code: Select all

CONFIG_DEBUG_LL=y
CONFIG_AT91_DEBUG_LL_DBGU0=y
CONFIG_EARLY_PRINTK=y
make zImage 
make dtbs
3th step
I load my kernel and my dtb file on the board
and I have this feedback

Code: Select all

AT91Bootstrap 3.8.7-00007-g5457e9c (Fri Dec  9 13:30:01 UTC 2016)

NAND: ONFI not supported
NAND: Manufacturer ID: 0x98 Chip ID: 0xda
WARNING: Fail to disable On-Die ECC
NAND: Press the recovery button (BP4) to recovery
NAND: Using Software ECC
NAND: Image: Copy 0x80000 bytes from 0x40000 to 0x21f00000
NAND: Done to load image


U-Boot 2016.09.01 (Dec 15 2016 - 16:09:54 +0000)

CPU: AT91SAM9G20
Crystal frequency:   18.432 MHz
CPU clock        :  396.288 MHz
Master clock     :  132.096 MHz
DRAM:  64 MiB
WARNING: Caches not enabled
NAND:  256 MiB
MMC:   mci: 0
In:    serial
Out:   serial
Err:   serial
Net:   macb0
Error: macb0 address not set.

Hit any key to stop autoboot:  0 

NAND read: device 0 offset 0x200000, size 0x25fcb0
 2489520 bytes read: OK
Kernel image @ 0x22000000 [ 0x000000 - 0x25fcb0 ]

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x000008f0).

Available machine support:

ID (hex)        NAME
ffffffff        Atmel AT91SAM (Device Tree)
ffffffff        Atmel SAMA5 (Device Tree)
I never configured a Device tree support on a board. and i don't understand why the id is ffffff and how can i remedy this problem
thank for your help

Cali.
blue_z
Location: USA
Posts: 1505
Joined: Thu Apr 19, 2007 10:15 pm

Re: Error: unrecognized/unsupported machine ID (r1 = 0x00000

Thu Jan 19, 2017 2:08 am

cali90 wrote:I build a new kernel (4.4) with device tree support for board based on sam9g20ek archithecture.
So you start off by mentioning version 4.4, but that's the only time you refer to this version.
cali90 wrote:2nd step : test build kernel.
git clone git://github.com/linux4sam/linux-at91.git
git checkout origin/linux-3.6.9-at91 -b linux-3.6.9-at91
[*]this kernel version is the same than the version implemented on zip file (refer 1 st step)
If you wanted to rebuild the kernel using the same code base, you should have used the kernel release tarball instead of checking-out from the github.
cali90 wrote:I load my kernel and my dtb file on the board
What board is this?
What dtb file did you install, and where?
cali90 wrote:

Code: Select all

NAND read: device 0 offset 0x200000, size 0x25fcb0
 2489520 bytes read: OK
Kernel image @ 0x22000000 [ 0x000000 - 0x25fcb0 ]

Starting kernel ...
That looks like U-Boot has only loaded a kernel image into memory.
There's no second load for a Device Tree blob.

Stop the autoboot, and display the U-Boot environment using `printenv`.

Regards
cali90
Posts: 8
Joined: Tue Mar 03, 2015 10:54 am

Re: Error: unrecognized/unsupported machine ID (r1 = 0x00000

Thu Jan 19, 2017 11:10 am

Hi blue_z,
Thank you for your feedback.

concerning linux kernel version : I had tested with version 3.6.9-at91 not 4.4 for the moment.
blue_z wrote:
cali90 wrote:I build a new kernel (4.4) with device tree support for board based on sam9g20ek archithecture.
So you start off by mentioning version 4.4, but that's the only time you refer to this version.
blue_z wrote:
cali90 wrote:2nd step : test build kernel.
git clone git://github.com/linux4sam/linux-at91.git
git checkout origin/linux-3.6.9-at91 -b linux-3.6.9-at91
[*]this kernel version is the same than the version implemented on zip file (refer 1 st step)
If you wanted to rebuild the kernel using the same code base, you should have used the kernel release tarball instead of checking-out from the github.
where can I found the kernel realease tarball ? On http://kernel.org/ I think ?

[*]Today I check the boot sequence with kernel realease found on http://kernel.org/
I had check with kernel 3.6.9 from kernel.org and I had the same result.
I had rebuilt u-boot with same compilation chain than the kernel
same result
see copy after :

Code: Select all

NAND read: device 0 offset 0x200000, size 0x1ea978
 2009464 bytes read: OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x000008f0).

Available machine support:

ID (hex)        NAME
ffffffff        Atmel AT91SAM (Device Tree)

Please check your kernel config and/or bootloader.
blue_z wrote:
cali90 wrote:I load my kernel and my dtb file on the board
What board is this?
What dtb file did you install, and where?
I work on custom board based on at91sam9g20ek-2mmc.
I using dtb file generate with the kernel built. located ./linux-at91/arch/arm/boot/dts/at91sam9g20ek_2mmc.dtb
and a zImage located ./inux-at91/arch/arm/boot/zImage

Files is loaded at adress bellow :
  • set bootStrapAddr 0x00000000 // Bottstrap address
  • set ubootAddr 0x00040000 // uboot address
  • set ubootEnvAddr 0x000c0000 // uboot Environement address
  • set dtbAddr 0x00180000 // dtb address
  • set kernelAddr 0x00200000 // Kernel address
  • set rootfsAddr 0x00800000 // root file system address.
blue_z wrote:
cali90 wrote:

Code: Select all

NAND read: device 0 offset 0x200000, size 0x25fcb0
 2489520 bytes read: OK
Kernel image @ 0x22000000 [ 0x000000 - 0x25fcb0 ]

Starting kernel ...
That looks like U-Boot has only loaded a kernel image into memory.
There's no second load for a Device Tree blob.

Stop the autoboot, and display the U-Boot environment using `printenv`.

Regards
feedback display of printenv command :
printenv
baudrate=115200
bootargs=console=ttyS0,115200 mtdparts=atmel_nand:256k(bootstrap)ro,512k(uboot)ro,256k(env),256k(env_redundant),256k(spare),512k(dtb),6M(kernel)ro,-(rootfs) rootfstype=ubifs ubi.mtd=7 root=ubi0:rootfs rw
bootcmd=nand read 0x22000000 0x00200000 0x00376A30; bootz 0x22000000
bootdelay=1
ethact=macb0
stderr=serial
stdin=serial
stdout=serial

for complementary information bootcmd is auto computing in script load file

Regards
Cali.


PROBLEM FOUND :
uboot environment variable don't define adress of dtb file configuration.
for tested : I had adding dtb file on zImage with command bellow :

Code: Select all

cat zImage <filename>.dtb > zImage_w_dtb
now kernel boot correctly. I need just to correct a kernel panic

Additional question :
on AT91SAM9G20-EK can I add dtb adress after kerenel address ?
for example : bootz 0x22000000 - 0xXXXXXXX

Many thank at blue_z for your help which allowed me to understand the problem on the variables of uboot.

Cali
blue_z
Location: USA
Posts: 1505
Joined: Thu Apr 19, 2007 10:15 pm

Re: Error: unrecognized/unsupported machine ID (r1 = 0x00000

Fri Jan 20, 2017 3:10 am

cali90 wrote:I had adding dtb file on zImage with command bellow :

Code: Select all

cat zImage <filename>.dtb > zImage_w_dtb
Yes, that's a workaround in the kernel to support old boot programs that couldn't load a separate dtb file.
cali90 wrote:can I add dtb adress after kerenel address ?
for example : bootz 0x22000000 - 0xXXXXXXXi
Yes, you can specify a memory location for the dtb, so long as you also remember to put space, hyphen, space between the addresses,

Try updating the U-Boot environment with this definition for the boot command:

Code: Select all

setenv bootcmd nand read 0x20080000 0x200000 0x600000\; nand read 0x22000000 0x180000 0x80000\; bootz 0x20080000 - 0x22000000
(Notice the backslash preceding each semicolon.)

Regards
cali90
Posts: 8
Joined: Tue Mar 03, 2015 10:54 am

Re: Error: unrecognized/unsupported machine ID (r1 = 0x00000

Fri Jan 20, 2017 7:03 pm

Many thank for your help blue_z,
this command line work perfectly

Code: Select all

setenv bootcmd nand read 0x20080000 0x200000 0x600000\; nand read 0x22000000 0x180000 0x80000\; bootz 0x20080000 - 0x22000000
for me this post is closed.
Thank you

Return to “Linux”

Who is online

Users browsing this forum: No registered users and 1 guest