hwmt2012

6410移植linux3.3.5

分类： linux 2013-09-02 17:10 65人阅读评论(0) 收藏举报

6410 linux linux移植

目录(?)[+]

目录

Linux 3.3.5系统移植    2

LED驱动移植    8

按键驱动移植    9

LCD驱动移植    11

DM9000网卡驱动移植    14

搭建NFS网络文件系统    25

移植触摸屏驱动    38

移植Qt4.8.1    42

tslib移植及测试    42

移植qt-everywhere-opensource-src-4.8.1    45

Linux 3.3.5系统移植

将arch/arm/mach-s3c6410/下的,mach-smdk6410.c cp为mach-my6410.c;
打开arch/arm/mach-s3c6410/下的Kconfig，仿照MACH_SMDK6410做一个菜单项：

config MACH_MY6410

    bool "MY6410"

    select CPU_S3C6410

    select SAMSUNG_DEV_ADC

    select S3C_DEV_HSMMC

    select S3C_DEV_HSMMC1

    select S3C_DEV_I2C1

    select SAMSUNG_DEV_IDE

    select S3C_DEV_FB

    select S3C_DEV_RTC

    select SAMSUNG_DEV_TS

    select S3C_DEV_USB_HOST

    select S3C_DEV_USB_HSOTG

    select S3C_DEV_WDT

    select SAMSUNG_DEV_BACKLIGHT

    select SAMSUNG_DEV_KEYPAD

    select SAMSUNG_DEV_PWM

    select HAVE_S3C2410_WATCHDOG if WATCHDOG

    select S3C64XX_SETUP_SDHCI

    select S3C64XX_SETUP_I2C1

    select S3C64XX_SETUP_IDE

    select S3C64XX_SETUP_FB_24BPP

    select S3C64XX_SETUP_KEYPAD

    help

     Machine support for the Pillar MY6410
打开arch/arm/tools/mach-types文件，这里面存的是机器ID必须要和uboot里面的ID保持一致，将其283行复制添加在后面并修改为：

smdk6410 MACH_SMDK6410 SMDK6410 1626

xx6410 MACH_XX6410 XX6410 1626 这个机器ID和UBOOT里的机器ID相同时才能启动内核；

修改BSP文件mach-my6410.c,内容如下：

将mach-mach-my6410.c文件中的所有smdk6410改成my6410(不要改大写SMDK6410的)

MACHINE_START(MY6410, "MY6410")//这个要和Kconfig里的MACH-MY6410匹配
在当前目录的Makefile最后一行加上 obj-$(CONFIG_MACH_MY6410) += mach-my6410.o
修改顶层的Makefile：

ARCH ?= arm

CROSS_COMPILE ?= /usr/local/arm/4.2.2-eabi/usr/bin/arm-linux-
复制arch/arm/configs/下的s3c6400-defconfig文件，然后将其保存为.config,配置内核支持EABI，再选中XX6410 board这一项，保存退出；
执行make menuconfig对内核进行配置：

执行make编译

执行make zImage生成zImage

将uboot根目录下的mkimage拷贝到/user/bin目录下

执行make uImage生成uImage

通过以上几步linux内核移植完了，剩下就移植驱动了。

这里需要注意，每一次修改Kconfig文件都需要make menuconfig对内核进行配置。

LED驱动移植

Linu内核下drivers/leds/ledsgpio.c实现了一个体系结构无关的GPIO LED驱动，使用此LED 驱动，开发者不需要修改一行代码，只需要在 BSP 的板文件（对于OK6410 为arch/arm/machs3c6410/machmy6410.c）中定义相关的platform设备和数据。在 MY6410开发板上,GPM0~GPM3 实现了四个 LED，因此其对应的platform 信息如下：

arch/arm/machs3c6410/machmy6410.c:

static struct gpio_led my6410_leds[] ={

    [0]= {

        .name = "LED1",

        .gpio = S3C64XX_GPM(0),

        },

    [1]= {

        .name = "LED2",

        .gpio = S3C64XX_GPM(1),

        },

    [2]= {

        .name = "LED3",

        .gpio = S3C64XX_GPM(2),

        },

    [3]= {

        .name = "LED4",

        .gpio = S3C64XX_GPM(3),

        },

};

static struct gpio_led_platform_data my6410_gpio_led_pdata ={

    .num_leds    = ARRAY_SIZE(my6410_leds),

    .leds         =my6410_leds,

};

static struct platform_device my6410_device_led ={

    .name    = "leds-gpio",

    .id        = -1,

    .dev    ={

    .platform_data = &my6410_gpio_led_pdata,

    },

};
将&my6410_device_led添加到static struct platform_device *my6410_devices[] __initdata中。
配置内核：

Device Drivers --->

[*] LED Support --->

<*> LED Support for GPIO connected LEDs

下载内核后开发板上的四个LED这时候已经全部都亮了

按键驱动移植

Linux内核下的drivers/input/keyboard/gpio_keys.c 实现了一个体系结构无关的 GPIO 按键驱动,使用此按键驱动,开发者不需要修改一行代码，只需要在BSP 的板文件（对于 MY6410为arch/arm/machs3c6410/machmy6410.c）中定义相关的platform 设备和数据。在 MY6410开发板上,用 GPN0~GPN5实现了DOWN、ENTER、HOME、UP、TAB、END 六个按键，因此其对应的 platform 信息如下：

arch/arm/machs3c6410/machmy6410.c:

static struct gpio_keys_button my6410_buttons[] = {

    {

        .gpio        = S3C64XX_GPN(0),

        .code        = KEY_UP,

        .desc        = "Up",

        .active_low    = 1,

        .wakeup        = 0,

    },

    {

        .gpio        = S3C64XX_GPN(1),

        .code        = KEY_DOWN,

        .desc        = "Down",

        .active_low    = 1,

        .wakeup        = 0,

    },

    {

        .gpio        = S3C64XX_GPN(2),

        .code        = KEY_LEFT,

        .desc        = "Left",

        .active_low    = 1,

        .wakeup        = 0,

    },

    {

        .gpio        = S3C64XX_GPN(3),

        .code        = KEY_RIGHT,

        .desc        = "Right",

        .active_low    = 1,

        .wakeup        = 0,

    },

    {

        .gpio        = S3C64XX_GPN(4),

        .code        = KEY_ENTER,

        .desc        = "Enter",

        .active_low    = 1,

        .wakeup        = 0,

    },

    {

        .gpio        = S3C64XX_GPN(5),

        .code        = KEY_ESC,

        .desc        = "Esc",

        .active_low    = 1,

        .wakeup        = 0,

    }

};

static struct gpio_keys_platform_data my6410_button_data ={

    .buttons    =my6410_buttons,

    .nbuttons    =ARRAY_SIZE(my6410_buttons),

};

static struct platform_device my6410_device_button    = {

    .name        ="gpio-keys",

    .id            = -1,

    .dev        = {

    .platform_data =&my6410_button_data,

    },

};
将& my6410_device_button添加到static struct platform_device *my6410_devices[] __initdata中
配置linux内核

Device Drivers --->

    Input device support --->

        [*] Keyboards --->

             <*> GPIO Buttons

在移植按键驱动时候可能出现一下错误：

arch/arm/mach-s3c64xx/mach-my6410.c:298: error: array type has incomplete element type

arch/arm/mach-s3c64xx/mach-my6410.c:300: error: field name not in record or union initializer

arch/arm/mach-s3c64xx/mach-my6410.c:300: error: (near initialization for 'my6410_buttons')

arch/arm/mach-s3c64xx/mach-my6410.c:301: error: field name not in record or union initializer

arch/arm/mach-s3c64xx/mach-my6410.c:301: error: (near initialization for 'my6410_buttons')

arch/arm/mach-s3c64xx/mach-my6410.c:302: error: field name not in record or union initializer

arch/arm/mach-s3c64xx/mach-my6410.c:302: error: (near initialization for 'my6410_buttons')

arch/arm/mach-s3c64xx/mach-my6410.c:303: error: field name not in record or union initializer

arch/arm/mach-s3c64xx/mach-my6410.c:303: error: (near initialization for 'my6410_buttons')

arch/arm/mach-s3c64xx/mach-my6410.c:304: error: field name not in record or union initialize

………………..

………………………

……………………………………

可以看出这个错误提示的意思是没有找到定义的数组，然后其他的就引起一连串的错误，解决的办法很简单就是把

#include <linux/gpio_keys.h>

这个头文件添加进去就可以了。

今天已经就做这么多吧，人都快累垮了。。。。。。明天继续。。。。。。

LCD驱动移植

向mach-my6410.c里面填入相应的平台信息：

static struct s3c_fb_pd_win my6410_fb_win0 = {

    /* this is to ensure we use win0 */

    .win_mode    = {

        .left_margin    = 2,

        .right_margin    = 2,

        .upper_margin    = 2,

        .lower_margin    = 2,

        .hsync_len    = 41,

        .vsync_len    = 10,

        .xres        = 480,

        .yres        = 272,

    },

    .max_bpp    = 32,

    .default_bpp    = 16,

};

pixclock = 1000000 / DCLK = 1000000 / 9 = 111111

left_margin = Thb = 2

right_margin = Thf = 2

hsync_len = Thp = 41

upper_margin = Tvb = 2

lower_margin = Tvf = 2

vsync_len = Tvp = 10

xres = Thd = 480

Yres = Tvd = 272

static struct map_desc my6410_iodesc[] = {

{

/* LCD support */

.virtual = (unsigned long)S3C_VA_LCD,

.pfn = __phys_to_pfn(S3C_PA_FB),

.length = SZ_16K,

.type = MT_DEVICE,

};

然后将28内核中的drviers/video/samsung拷贝到drviers/video/目录下
修改drviers/video/的Kconfig文件，在文件中加入

source "drivers/video/samsung/Kconfig"
修改修改drviers/video/的Makefie文件,再最后一行添加：

obj-$(CONFIG_FB_S3C_EXT) += samsung/
在arch/arm/plat-samsung/include/plat/map-base.h里面添加

#define S3C_VA_LCD S3C_ADDR(0x01100000) /* LCD */

在include/generated/atuoconfig.h里面添加

#define CONFIG_FB_S3C_EXT_NUM 4
把drivers/video/samsung/s3cfb_fimd4x.c里面的

第1417行：

s3c6410_pm_do_save(s3c_lcd_save, ARRAY_SIZE(s3c_lcd_save));

改成

s3c_pm_do_save(s3c_lcd_save, ARRAY_SIZE(s3c_lcd_save));

第1438行

s3c6410_pm_do_restore(s3c_lcd_save, ARRAY_SIZE(s3c_lcd_save));

改成

s3c_pm_do_restore(s3c_lcd_save, ARRAY_SIZE(s3c_lcd_save));

配置内核：

Device Drivers --->

Graphics support --->

<*> Support for frame buffer devices ---> （里面的都空选）

<*> Support for frame buffer devices --->

[ ] Backlight & LCD device support --->

<*> S3C Framebuffer Support (eXtended)（修改Kconfig之后才有这个选）

Select LCD Type (4.3 inch 480x272 TFT LCD) --->

(X) 4.3 inch 480x272 TFT LCD

<*> Advanced options for S3C Framebuffer

Select BPP(Bits Per Pixel) (16 BPP) --->

(4) Number of Framebuffers

[ ] Enable Virtual Screen

[*] Enable Double Buffering

Console display driver support --->

<*> Framebuffer Console support

[*] Bootup logo --->（显示小企鹅）

[*] Standard 224-color Linux logo

如果驱动移植成功内核启动的时候会打印一下信息：

S3C_LCD clock got enabled :: 133.000 Mhz

LCD TYPE :: LTE480WV will be initialized

Window[0] - FB1: map_video_memory: clear ffd80000:0007f800

FB1: map_video_memory: dma=5f900000 cpu=ffd80000 size=0007f800

Window[0] - FB2: map_video_memory: clear ffdbfc00:0003fc00

FB2: map_video_memory: dma=5f93fc00 cpu=ffdbfc00 size=0003fc00

Console: switching to colour frame buffer device 60x34

fb0: s3cfb frame buffer device

Window[1] - FB1: map_video_memory: clear ffd00000:0007f800

FB1: map_video_memory: dma=5f980000 cpu=ffd00000 size=0007f800

Window[1] - FB2: map_video_memory: clear ffd3fc00:0003fc00

FB2: map_video_memory: dma=5f9bfc00 cpu=ffd3fc00 size=0003fc00

fb1: s3cfb frame buffer device

Window[2] - FB1: map_video_memory: clear ffcc0000:0003fc00

FB1: map_video_memory: dma=5fa00000 cpu=ffcc0000 size=0003fc00

fb2: s3cfb frame buffer device

Window[3] - FB1: map_video_memory: clear ffc80000:0003fc00

FB1: map_video_memory: dma=5fa40000 cpu=ffc80000 size=0003fc00

fb3: s3cfb frame buffer device

在LCD还会显示小企鹅：

相应的驱动程序都在

drviers/video/Samsung/s3cfb.c目录下

今天就为这驱动搞了一天，其实早就可以成功的，TMMD的不知道是不是手贱还是怎么的，

竟然把System Type --->

[* ] SMDK6400

选上了，最后系统一直打印都是SMDK6400的信息。幸好我靠

printk(KERN_INFO "DEBUG\n\n\n\n");

找到了原因。

以后有时间好好对LCD驱动做一下分析。

DM9000网卡驱动移植

Linux内核里面已经支持了dm9000的网卡驱动，所以驱动程序我们不需要写了，只需要添加相应的平台信息。在linux-3.3.5/arch/arm/mach-s3c64xx/mach-my6410.c里面添加都文件#include <linux/dm9000.h>
在linux-3.3.5/arch/arm/mach-s3c64xx/mach-my6410.c里面添加以下平台信息：

#define S3C64XX_PA_DM9000 (0x18000000)

#define S3C64XX_SZ_DM9000 SZ_1M

static struct resource my6410_dm9000_resources[] = {

[0] = {

.start= S3C64XX_PA_DM9000,

.end= S3C64XX_PA_DM9000 + 3,

.flags= IORESOURCE_MEM,

},

[1] = {

.start= S3C64XX_PA_DM9000 + 4,

.end= S3C64XX_PA_DM9000 + S3C64XX_SZ_DM9000 - 1,

.flags= IORESOURCE_MEM,

},

[2] = {

.start= IRQ_EINT(7),

.end= IRQ_EINT(7),

.flags= IORESOURCE_IRQ | IRQF_TRIGGER_HIGH,

},

};

static struct dm9000_plat_data my6410_dm9000_platdata = {

.flags= DM9000_PLATF_16BITONLY,

.dev_addr= { 0x08, 0x90, 0x00, 0xa0, 0x90, 0x90 },

};

static struct platform_device my6410_device_dm9000 = {

.name= "dm9000",

.id= 0,

.num_resources= ARRAY_SIZE(my6410_dm9000_resources),

.resource= my6410_dm9000_resources,

.dev= {

.platform_data = &my6410_dm9000_platdata,

}

};

然后在static struct platform_device *my6410_devices[] __initdata =里面添加

&my6410_device_dm9000,

配置内核，这里网络配置的选项很多，但都要根据实际选对：

出现的问题及解决方案：
1. 编译的时候出现：
  
  SYSMAP System.map
  
  SYSMAP .tmp_System.map
  
  Inconsistent kallsyms data
  
  This is a bug - please report about it
  
  Try make KALLSYMS_EXTRA_PASS=1 as a workaround
  
  make: *** [vmlinux] 错误 1

这样的错误没有任何提示，经过总结，我发现这样的错误出现的原因就是内核中有些设备没有配置但是在BSP里面却定义了，或者是 BSP里面定义了，但是内核没有配置。

解决方法是把static struct platform_device *my6410_devices[] __initdata里面一些三星的东西去掉，其实如果从一个空模版移植是不会出现这类问题的，这里我还是有些偷懒。修改以后的内容如下：

static struct platform_device *my6410_devices[] __initdata = {

#ifdef CONFIG_SMDK6410_SD_CH0

&s3c_device_hsmmc0,

#endif

&my6410_device_button,

&my6410_device_led,

&my6410_device_dm9000,

#ifdef CONFIG_SMDK6410_SD_CH1

&s3c_device_hsmmc1,

#endif

&s3c_device_i2c0,

//&s3c_device_i2c1,

&s3c_device_fb,

&s3c_device_ohci,

&s3c_device_usb_hsotg,

&samsung_asoc_dma,

//&s3c64xx_device_iisv4,

//&samsung_device_keypad,

#ifdef CONFIG_REGULATOR

//&my6410_b_pwr_5v,

#endif

//&my6410_lcd_powerdev,

//&my6410_smsc911x,

//&s3c_device_adc,

//&s3c_device_cfcon,

&s3c_device_rtc,

&s3c_device_ts,

//&s3c_device_wdt,

};

启动过程中出现这样的问题：

smsc911x: failed to claim resource 0（这个提示原来在这儿我怎么没有发现）

------------[ cut here ]------------

WARNING: at drivers/base/core.c:194 device_release+0x74/0x80()

Device 'platform-lcd.0' does not have a release() function, it is broken and must be fixed.

Modules linked in:

[<c0013e1c>] (unwind_backtrace+0x0/0xf8) from [<c001d968>] (warn_slowpath_common+0x4c/0x64)

[<c001d968>] (warn_slowpath_common+0x4c/0x64) from [<c001da14>] (warn_slowpath_fmt+0x30/0x40)

[<c001da14>] (warn_slowpath_fmt+0x30/0x40) from [<c0175d6c>] (device_release+0x74/0x80)

[<c0175d6c>] (device_release+0x74/0x80) from [<c0126ac0>] (kobject_release+0x44/0x78)

[<c0126ac0>] (kobject_release+0x44/0x78) from [<c0179910>] (platform_add_devices+0x54/0x68)

[<c0179910>] (platform_add_devices+0x54/0x68) from [<c03826c4>] (customize_machine+0x20/0x30)

[<c03826c4>] (customize_machine+0x20/0x30) from [<c00087a8>] (do_one_initcall+0x11c/0x170)

[<c00087a8>] (do_one_initcall+0x11c/0x170) from [<c037f564>] (kernel_init+0x84/0x128)

[<c037f564>] (kernel_init+0x84/0x128) from [<c000f28c>] (kernel_thread_exit+0x0/0x8)

---[ end trace 1b75b31a2719ed1c ]---

------------[ cut here ]------------

WARNING: at drivers/base/core.c:194 device_release+0x74/0x80()

Device 'samsung-keypad' does not have a release() function, it is broken and must be fixed.