MontaVista v3.1 Configuration and Compiling

原创 2007年09月14日 16:26:00
MontaVista v3.1 Configuration and Compiling


Assume MVL was in folder /opt/montavista/, your board is intel ixdp425.
Your cross compiler should set to $PATH first. We use xscale_be-gcc.

Add following lines to /etc/profile.

pathmunge /opt/montavista/common/eclipse
pathmunge /opt/montavista/pro/host/bin
pathmunge /opt/montavista/pro/devkit/arm/xscale_be/bin

1. Prepare your working folder
   #cd /opt
   #mkdir MVL
   #cd MVL
   #mkdir linux-2.4.20_mvl31 app target mkramdisk ramdisk

2. Copy montavista files
   #cd /opt/MVL/linux-2.4.20_mvl31
   #cp -a /opt/montavista/pro/devkit/lsp/intel-ixdp4xx-arm_xscale_be/linux-2.4.20_mvl31/ .
   #cd /opt/MVL/target
   #cp -a /opt/montavista/pro/devkit/arm/xscale_be/target .

   You can export this directory using NFS. Kernel files are 169M, target files are 921M.
3. Apply patch
(1)For frame buffer support
   #cd /opt/MVL/linux-2.4.20_mvl31
   #cp /mvl31-ixp425-fb-support.patch .
   #patch –p0 < mvl31-ixp425-fb-support.patch

(2)For socket reuse
   #cd /opt/MVL/linux-2.4.20_mvl31
   #cp /SO_REUSEPORT.patch .
   #patch –p1 < SO_REUSEPORT.patch

4. Configure Kernel
   #cd /opt/MVL/linux-2.4.20_mvl31
   #make oldconfig
   #make menuconfig

 (1)Support Frame Buffer
   "Character devices"---Enable the "Virtual terminal"
   "Console drivers" --- "Frame-buffer support"--- Enable "Support for frame buffer devices"
    Enable the "Advanced low level driver options", and then enable all sub-options (i.e. Monochrome, 2, 4, 8,…bpp packed pixels) as yes instead of module.
    Enable the "Select compiled-in fonts", and then enable all font types.

    NOTE: You should also change vfb.c in SigmaDesings Driver as below. vfb.c is located in folder

       Static int mambolfb_mmap(……….)
    #ifndef __arm__
        BLOCK A …
        BLOCK B …
        BLOCK C …
        BLOCK D …
    /* Code added start */
    #ifdef CONFIG_ARCH_IXP425
        /* In the IXP425 architecture, the 'videomemory' is located on PCI MEM
           and not mapped to virtual address, so treate 'videomemory'
           as physical memory. */
            if (kc_remap_page_range((struct kc_vm_area_struct *) vma,
                                vma->vm_start, videomemory,
                                (struct kc_pgprot_t *) &vma->vm_page_prot))
                    return -EAGAIN;
            printk("remapped %ld bytes in userland of process %d at address "
            "0x%08lx to 0x%08lx/n",
                   vma->vm_end-vma->vm_start,current->pid,vma->vm_start, videomemory);
    /* Code added end */
    return 0;

After the save the modified source file, the read have to compile the driver module again. Type the command “make” under the directory of which the vfb.c locates in will start the compiling for "mambolfb.o" module.
NOTE: The driver module MUST be compiled after the kernel configuration is changed.

(2)Kernel Command Line
   "General Setup"---"Default Kernel Command String" input:
                 console=ttyS1,115200 root=/dev/ram initrd=0x00800000,2000K mem=128M@0x00000000
   "File Systems"---"Network File Systems"--- Disable "Root file system on NFS"
5. Compile kernel
   #make dep
   #make zImage
   #make modules

   Compiled kernel is in /opt/MVL/kernel/arch/arm/boot/. Copy kernel file zImage to /tftpboot/gdzImage.
   NOTE: If Loadable Module Support is not set, disregard the make modules command and all installation directions for modules.

6. Install Modules

   #make modules_install INSTALL_MOD_PATH=<mod_install_dir>
   This will place the modules into <mod_install_dir>/lib/modules/x.y.z on the host, which can then be transferred to the target machine. The target directory for the modules on the MVL should be /lib/modules/x.y.z.

7. Rebuild ramdisk
   #cd /opt/MVL/mkramdisk
   #cp -a /opt/montavista/pro/devkit/arm/xscale_be/images/mkramdisk .
   #./mkramdisk -r /opt/montavista/pro/ gdramdisk
   #gzip -v9 gdramdisk

   It will create 6M ramdisk with 4.1M contents. You can use command 'mount -o loop gdramdisk /mnt' to see contents.


Illegal Configuration: Compiling IB documents for earlier than iOS 7 is no longer supported.

在网上下载下来开源项目爆出这样的错误 翻译一下:  非法配置:不再早于iOS 7编译IB文档。 选择报错的xib 文件 选择builds for 适合的版本...
  • qq_33856381
  • qq_33856381
  • 2018年01月10日 09:41
  • 91

iOS Compiling IB documents for earlier than iOS 7 is no longer supported

//联系人:石虎  QQ: 1224614774昵称:嗡嘛呢叭咪哄 一、在升级到Xcode9 遇到以下错误:   Compiling IB documents for earlie...
  • shihuboke
  • shihuboke
  • 2017年09月25日 12:05
  • 3603

Xcode报错 Compiling IB documents for earlier than iOS7 is no longer supported.

先贴出报错信息: 解决办法: 将build for的版本改到iOS7.1及以上即可。
  • SpicyBoiledFish
  • SpicyBoiledFish
  • 2017年09月22日 12:45
  • 4630

MontaVista linux介绍

MontaVista Linux专业版(Professional Edition),可以满足用户对可预测性、稳定性以及高级I/O支持的要求。MontaVista Linux是MontaVista软件公...
  • yuanyou
  • yuanyou
  • 2010年10月21日 23:03
  • 2453

Xcode9报错Command /bin/sh failed with exit code 1

升级Xcode9,项目运行失败报错:Command /bin/sh failed with exit code 1     错误详情:报错原因为pod的里的第三方友盟xib版本号问题, ...
  • xiaohe901216
  • xiaohe901216
  • 2017年11月27日 11:24
  • 139

iOS开发之Xcode9报错 Compiling IB documents for earlier than iOS7 is no longer supported.

在我们升级到Xcode9时,最低的编译版本为iOS8,但是在使用一些SDK的时候就会报出Compiling IB documents for earlier than iOS7 is no longe...
  • ziyuzhiye
  • ziyuzhiye
  • 2017年10月19日 16:14
  • 2678


导读:   一、技术规格:   频段:GSM 900/1800/1900 GPRS   区域:全球   技术:WAP 2.0, J2ME, MMS, Magic 4 IM   连接:USB, Blue...
  • yingfox
  • yingfox
  • 2007年11月12日 19:29
  • 596


  • xmmcuduck
  • xmmcuduck
  • 2009年08月05日 15:30
  • 203


Montavista是MontaVista Software公司简称.MontaVista Software公司日前宣布推出新版Mobilinux,可协助移动和无线装置开发者解决关键的设计问题。Mob...
  • dyzok88
  • dyzok88
  • 2014年12月26日 15:02
  • 527

iOS10 配置ATS

iOS10 适配 App Transport Security (ATS) 首先我们需要确定,工程开启ATS后,各个iOS版本是否能正常运行。 iOS9.0及以上的iOS系统是默认开启ATS的,...
  • MickeyChen_
  • MickeyChen_
  • 2017年01月18日 17:40
  • 2755
您举报文章:MontaVista v3.1 Configuration and Compiling