logo

Could not compile stylesheet for simplistic. Using last compiled stylesheet.
Question

igepv2 RB and kernel 3.x

posted in IGEPv2
Sunday, February 15 2015, 12:38 AM
chh
chh
Offline
0
Hi!

I am having an igepv2 RB board. I read that it is possible to boot igepv2 RC4 board with kernel 3.18.2 on Enide!.

Now I'm trying to boot u-boot from SD card and then a precompiled kernel zImage-3.18.2 from link above, but on serial console it stops at "Starting kernel ..."


What I did is compiling compile u-boot (from git Feb 05 2015) an put MLO and u-boot.img on a SD card.

Booting u-boot seems to work. Output on serial console is
U-Boot SPL 2015.04-rc1-00004-g7f641d5 (Feb 05 2015 - 22:03:55)
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
reading u-boot.img
reading u-boot.img


U-Boot 2015.04-rc1-00004-g7f641d5 (Feb 05 2015 - 22:03:55)

OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 MHz
IGEPv2 + LPDDR/ONENAND
I2C:   ready
DRAM:  512 MiB
NAND:  Muxed OneNAND(DDP) 512MB 1.8V 16-bit (0x58)
OneNAND version = 0x0031
Chip support all block unlock
Chip has 2 plane
block = 2048, wp status = 0x2
Scanning device for bad blocks
onenand_bbt_wait: ecc error = 0x2222, controller = 0x2400
Bad eraseblock 814 at 0x065c0000
onenand_bbt_wait: ecc error = 0x2222, controller = 0x2400
Bad eraseblock 2862 at 0x165c0000
OneNAND: 512 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment

Die ID #4588000400000000040365fa1401b012
Net:   smc911x-0
Error: smc911x-0 address not set.

Hit any key to stop autoboot:  1


If I start kernel 2.x provided by isee (put the zImage on SD card), the boot process continues after "Starting kernel ..." I see more output on serial console as expected.

Now I tried to boot precompiled kernel 3.18.2 (with corrosponding omap3-igep0020.dtb file) downloaded from above site.


copy downloaded zImage-3.18.2 and omap3-igep0020.dtb on SD-Card
created uEnv.txt on SD card with the following content:


loadaddr=0x82000000
fdtaddr= 0x81600000
kernel_file=zImage-3.18.2
fdtfile=omap3-igep0020.dtb
bootargs='console=ttyO2,115200n8 console=tty0 video=DVI-D-1:1440x900MR-16@60 omapfb.mode=dvi:1440x900MR-16@60 omapdss.def_disp=dvi omapfb.vram=0:8M,1:8M,2:8M vram=24M smsc911x.mac=0x5c,0xda,0xd4,0x3d,0x2f,0x08 mpurate=800 root=/dev/mmcblk0p2 rw rootwait rootfstype=ext4 fixrtc'

loadzimage=load mmc 0:1 ${loadaddr} ${kernel_file}
loadfdt=load mmc 0:1 ${fdtaddr} ${fdtfile}
setenvargs=setenv bootargs ${bootargs}

uenvcmd=run loadzimage; run loadfdt; run setenvargs; bootz ${loadaddr} - ${fdtaddr}


now zImage and the dtb file are loaded automatically but stops after "Starting kernel ...".

The following output is seen on serial conosle:

40
U-Boot SPL 2015.04-rc1-00004-g7f641d5 (Feb 05 2015 - 22:03:55)
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
reading u-boot.img
reading u-boot.img


U-Boot 2015.04-rc1-00004-g7f641d5 (Feb 05 2015 - 22:03:55)

OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 MHz
IGEPv2 + LPDDR/ONENAND
I2C:   ready
DRAM:  512 MiB
NAND:  Muxed OneNAND(DDP) 512MB 1.8V 16-bit (0x58)
OneNAND version = 0x0031
Chip support all block unlock
Chip has 2 plane
block = 2048, wp status = 0x2
Scanning device for bad blocks
onenand_bbt_wait: ecc error = 0x2222, controller = 0x2400
Bad eraseblock 814 at 0x065c0000
onenand_bbt_wait: ecc error = 0x2222, controller = 0x2400
Bad eraseblock 2862 at 0x165c0000
OneNAND: 512 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment

Die ID #4588000400000000040365fa1401b012
Net:   smc911x-0
Error: smc911x-0 address not set.

Hit any key to stop autoboot:  1  0 
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
reading uEnv.txt
590 bytes read in 4 ms (143.6 KiB/s)
Importing environment from mmc ...
Running uenvcmd ...
reading zImage-3.18.2
4608920 bytes read in 349 ms (12.6 MiB/s)
reading omap3-igep0020.dtb
65023 bytes read in 10 ms (6.2 MiB/s)
Kernel image @ 0x82000000 [ 0x000000 - 0x465398 ]
## Flattened Device Tree blob at 81600000
   Booting using the fdt blob at 0x81600000
   Loading Device Tree to 8ffed000, end 8ffffdfe ... OK

Starting kernel ...


On DVI, no output is seen.

Any ideas why boot process doesn't continue?

Thanks in advanced,
Chris
Responses (1)
  • Accepted Answer

    egavinc
    egavinc
    Offline
    Tuesday, February 17 2015, 12:24 PM - #permalink
    0
    Hello CHH, at this moment the IgepV2 RB doesn't have support for kernel with dtb, the latest kernel that has been validated for this board is 2.6.37.
    Best Regards
    Eduard
    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