ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Ltib] Problem adding new board


From: Amit Hergass
Subject: [Ltib] Problem adding new board
Date: Fri, 27 Aug 2010 16:19:46 +1000

Hi,

 

I am trying to add a new board to the latest LTIB linux 2.6.34.

I followed the instructions on: http://svn.buglabs.net/svn/!source/4559/trunk/com.freescale.ltib2/doc/LtibCreateNewTarget

 

 

And allocated new machine in: http://www.arm.linux.org.uk/developer/machines/

1.       Machine type number was added to: /ltib/rpm/BUILD/u-boot-2009.03-rc1/include/configs/dgm3240.h

2.       Added DGM3240 to Makefile in: /ltib/rpm/BUILD/u-boot-2009.03-rc1/Makefile

3.       New board directory added for dgm3240 in: /ltib_34/rpm/BUILD/u-boot-2009.03-rc1/board/dgm3240

4.       New Platform file was added to: /ltib/config/platform/dgm3240

 

I also read Kevin’s changes to the u-boot regarding the necessity of match between boot version and kernel.

However, I loading the new kernel using the same version of u-boot  still does not recognize the new board id.

Looking at the generated files I can see that the parameter MATCH_TYPE_PHY3250 (the original platform) still appears as the active one.

 

The LTIB was configured to build the kernel and u-boot for the new board.

Where am I miss setting the new configuration?

Please find the uboot and kernel output.

 

Thanks,

Amit

 

U-Boot 2009.03-rc1 (Aug 27 2010 - 13:05:13)

 

DRAM:  64 MB

Flash:  2 MB

NAND:  64 MiB

.

.

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK

 

Starting kernel ...

 

Uncompressing Linux... done, booting the kernel.

 

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

 

Available machine support:

 

ID (hex)        NAME

000002e0        Phytec 3250 board with the LPC3250 Microcontroller

000009cf        Phytec 3250 board with the LPC3250 Microcontroller

 

Please check your kernel config and/or bootloader.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]