logo

Could not compile stylesheet for simplistic. Using last compiled stylesheet.
0
Hello forum! I am trying to build a microSD card to boot IGEPv2, using xloader 2.4.0-2 (MLO signed file), and zImage build using poky-image-minimal target (with poky v3.2.1-0. This poky builds an uImage, but also generates the zImage in the arch/arm/boot/zImage directory) for the new x-loader. The problem is with my microSD card: always I boot my IGEPv2 with the microSD card connected, I get this output on the debug console: IGEP-X-Loader 2.3.0-1 (Dec 7 2011 - 09:07:55) XLoader: Processor DM3730 - ES1.2 XLoader: IGEPv2 : kernel boot ... Uncompressing Linux................................................. And nothing more happens... I never see the green led enabled, only the red is switch on, and after few miliseconds, it is switched off. I think the custom MLO x-loader (2.4.0-2) installed on the microSD card should be used instead of the x-loader installed in nand flash. I have tryied to build the microSD card following steps explained in different sources: [url=http://labs.isee.biz/index.php/How_to_boot_from_MicroSD_Card]http://labs.isee.biz/index.php/How_to_b ... croSD_Card[/url] [url=http://www.sakoman.com/OMAP/a-script-for-partitioningformatting-a-bootable-sdmicrosd-card.html]http://www.sakoman.com/OMAP/a-script-fo ... -card.html[/url] [url=http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat]http://code.google.com/p/beagleboard/wi ... DiskFormat[/url] Also, having into account some comments that seem to be important on the last link (+50M, fdisk -c -u, ...), but without any success. It seems I never get a working microSD card... Can some of you give me an advice, please? Thanks a lot in advance! The steps followed in my last retry withoy success are copyied & pasted below: 1. Delete partition table: $ sudo dd if=/dev/zero of=/dev/sdg bs=1024 count=1024 2. Create the partitions: $ fdisk /dev/sdg Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel with disk identifier 0xa4dbc571. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable. Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) WARNING: DOS-compatible mode is deprecated. It's strongly recommended to switch off the mode (command 'c') and change display units to sectors (command 'u'). Command (m for help): x Expert command (m for help): h Number of heads (1-256, default 125): 255 Expert command (m for help): s Number of sectors (1-63, default 62): 63 Warning: setting sector offset for DOS compatiblity Expert command (m for help): c Number of cylinders (1-1048576, default 1017): 490 <-- [4035969024 / 255 / 63 / 512 = 490.677734375] Command (m for help): p Disk /dev/sdg: 4035 MB, 4035969024 bytes 255 heads, 63 sectors/track, 490 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xa4dbc571 Device Boot Start End Blocks Id System Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-490, default 1): Using default value 1 Last cylinder, +cylinders or +size{K,M,G} (1-490, default 490): +100M Command (m for help): t Selected partition 1 Hex code (type L to list codes): b Changed system type of partition 1 to b (W95 FAT32) Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 2 First cylinder (15-490, default 15): Using default value 15 Last cylinder, +cylinders or +size{K,M,G} (15-490, default 490): Using default value 490 Command (m for help): a Partition number (1-4): 1 Command (m for help): p Disk /dev/sdg: 4035 MB, 4035969024 bytes 255 heads, 63 sectors/track, 490 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xa4dbc571 Device Boot Start End Blocks Id System /dev/sdg1 * 1 14 112423+ b W95 FAT32 /dev/sdg2 15 490 3823470 83 Linux Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. WARNING: If you have created or modified any DOS 6.x partitions, please see the fdisk manual page for additional information. Syncing disks. 3. Format the two recently created partitions: $ mkfs.msdos -F 32 /dev/sdg1 -n Boot $ mkfs.ext4 -L Rootfs /dev/sdg2 4. Copy MLO, igep.ini and zImage into /dev/sdg1, $ ls -l /media/boot/ total 2342 -rwxr-xr-x 1 root root 1962 2012-05-19 16:29 igep.ini -rwxr-xr-x 1 root root 63320 2012-05-19 16:29 MLO -rwxr-xr-x 1 root root 2331772 2012-05-19 16:29 zImage 5. The igep.ini contents: $ cat igep.ini |grep -v "; " [kernel] kaddress=0x80008000 serial.low=00000001 serial.high=00000000 revision=0003 kImageName=zImage MachineID=2344 [kparams] console=ttyO2,115200n8 mem=430M boot_delay=0 nocompcache=1 omapfb.mode=dvi:hd720-16@60 vram=40M omapfb.vram=0:12M,1:16M,2:12M smsc911x.mac=0xb2,0xb0,0x14,0xb5,0xcd,0xde root=/dev/mmcblk0p2 rw rootwait 6. Cross-compiler used to build MLO (installed on /usr/local/poky/eabi-glibc/bin/): $ arm-none-linux-gnueabi-gcc --version arm-none-linux-gnueabi-gcc (GCC) 4.3.3 Copyright (C) 2008 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Responses (4)
  • Accepted Answer

    Saturday, May 19 2012, 07:36 PM - #permalink
    0
    Hi, The 3.2.x version is too old and has no support for IGEP x-loader, please try with v3.3.1-11 which is the latest stable version, or better, if you want experimenting with latest developments try to downloading the Yocto/OE-core denzil branch and the meta-isee layer.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, May 20 2012, 12:42 PM - #permalink
    0
    Hello forum! The problem seems not being related with my microSD card building process. It is an issue related with the MLO image I have built with your provided cross-compiler: poky-eabi-glibc-i586-arm-toolchain-sdk-3.2.1.tar.bz2 $ arm-none-linux-gnueabi-gcc --version arm-none-linux-gnueabi-gcc (GCC) 4.3.3 Copyright (C) 2008 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Replacing the MLO on my microSD with the one you provide here solves the problem: poky-image-sato-igep00x0-20120301104515.tar.gz However, I am interested in building my own 'MLO' image. Attached is the MLO building process I have done. Is it something wrong with this process? $ export PATH=/usr/local/poky/eabi-glibc/bin/:$PATH $ arm-none-linux-gnueabi-gcc --version arm-none-linux-gnueabi-gcc (GCC) 4.3.3 Copyright (C) 2008 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ git clone [url=git://git.igep.es/pub/scm/igep-x-loader.git]git://git.igep.es/pub/scm/igep-x-loader.git[/url] $ cd igep-x-loader $ git checkout -b release-2.4.0-2 release-2.4.0-2 $ make igep00x0_config $ CROSS_COMPILE=arm-none-linux-gnueabi- make $ contrib/signGP x-load.bin $ cp x-load.bin.ift MLO And then copy 'MLO' to the 'boot' partition on microSD, and boot the IGEPv2 board with microSD card connected, what reproduces the problem previously explained. Thanks a lot in advance!
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, May 20 2012, 01:50 PM - #permalink
    0
    I have already solved this problem, following the x-loader build procedure that ISEE explains on this link: [url=http://labs.isee.biz/index.php/The_IGEP_X-loader]http://labs.isee.biz/index.php/The_IGEP_X-loader[/url] In fact, my problem seems not being related with the procedure I followed to build the MLO, but with the cross-compiler I used to build it. It seems that cross-compiler 4.3.3 provided in this tarball: poky-eabi-glibc-i586-arm-toolchain-sdk-3.2.1.tar.bz2 is not building a working MLO image. However, using the Ubuntu cross-compiler gcc 4.5.2 to build it, solves this issue. So, my questions: It would be nice to have a unique cross-compiler (SDK) to build all the firmware and software (MLO, zImage and all userspace applications). Does some of you know if that is possible with the Ubuntu 4.5.2 cross-compiler? Cross-compiler 4.3.3 does not works to get a working MLO image. But, can the cross-compiler that generates latest Poky branch (3.3.1-11) be used to build a working MLO image? Or MLO must be always built with Ubuntu 4.5.2 cross-compiler? Does some of you know the "key feature" that makes Ubuntu 4.5.2 cross-compiler different from the 4.3.3 cross-compiler provided in the tarball?
    The reply is currently minimized Show
  • Accepted Answer

    mcaro
    mcaro
    Offline
    Sunday, May 20 2012, 06:22 PM - #permalink
    0
    Hi, The problem with gcc 4.3.3 it's related to the binary size, the MLO it's limited to 60KBytes if the compiler generates any binary with a bigger size the processor cannot load it. We're working for upgrade our SDK to latest version with gcc 4.6, actually you can access to our beta release from our git repositories: [url=http://git.isee.biz/?p=pub/scm/meta-isee.git;a=shortlog;h=refs/heads/denzil]http://git.isee.biz/?p=pub/scm/meta-ise ... ads/denzil[/url] I guess in a short time it could be available ... the other option it's use the ubuntu/linaro compiler version 4.5.3 (NOT 4.6.x) Cheers Manel
    The reply is currently minimized Show
Your Reply

SUPPORT


This email address is being protected from spambots. You need JavaScript enabled to view it.
This email address is being protected from spambots. You need JavaScript enabled to view it.
IGEP Community Wiki
IGEP Community Forum
IGEP Community Online Chat