This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Problem with Craneboard booting the kernel

Hi, 

I've some problems with booting the kernel. I've compiled x-load and u-boot manually, as well as kernel, but it seems kernel either won't run, or it's not properly configured to printk messages to ttyS2 ( I had to manually turn on Device Driver -> Graphics Support ->Console Display Support -> Framebuffer console support ) 

I don't know if either kernel does not run correctly ( although I know that decompress_kernel from kernel sources is called ), or I have something wrongly configured. 

I've also tried prebuild kernel image from TI SDK, but it won't start due to device id being different.  

My u-boot env: 

AM3517_CRANE # pri
bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else if run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run nandbooti
bootdelay=10
baudrate=115200
bootfile=uImage
loadaddr=0x82000000
console=ttyS2,115200n8
mmcargs=setenv bootargs console=${console} root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait eth=${ethaddr} ip=dhcp
nandargs=setenv bootargs console=${console} root=/dev/mtdblock4 rw rootfstype=jffs2 eth=${ethaddr} ip=dhcp
loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
loaduimage=fatload mmc 0 ${loadaddr} uImage
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 280000 400000; bootm ${loadaddr}
dieid#=68ec000100000000015da3961501101d
ethact=DaVinci EMAC
ethaddr=80:02:81:06:5f:2

Environment size: 889/131068 bytes

U-boot booting kernel:

AM3517_CRANE # run mmcboot
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-2.6.32
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2083068 Bytes = 2 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

do_bootm_linux
## Transferring control to Linux (at address 80008000) ...

Starting kernel ...
Uncompressing Linux................................................................................................................................... done 

And that's all I can see through minicom. 
  • Hi Bartek,

    Hope you have downloaded images and followed the procedure mentioned here: http://processors.wiki.ti.com/index.php/Building_images_for_CraneBoard 

    Looking the console log, I strongly suspect the kernel image you have built.

    Regards,

    N.S.SriHarsha

  • Hi, 

    yes I followed those instructions, but while compiling u-boot I'm running into linking errors:

    lib_arm/board.c:299: undefined reference to `register_diagnostics'
    armv4t/libgcc.a(_bswapsi2.o):(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0'
    
    
    The first error is fixed by commenting the line in which call to register_diagnostics occurs, the second is fixed by patch ( http://lists.denx.de/pipermail/u-boot/2010-May/071363.html ) 
    
    
    Is my necessary modifications causes kernel not to boot properly?
    __aeabi_unwind_cpp_pr0
  • Hi Bartek,

    You can comment "lib_arm/board.c:299" as this is pointing to register diagnostics routine in the ITBOK and i reckon that is not of no interest here.

    However you can download the same here: http://processors.wiki.ti.com/index.php/Building_images_for_CraneBoard#Integrating_and_Building_ITBOK

    Apart from downloading the sources you should also be tweaking the Makefile in u-boot to accomodate ITBOK, more details on the same is mentioned here: https://github.com/craneboard/craneboard-itbok/wiki/Integrating-and-building-ITBOK

    Regards,

    N.S.SriHarsha

  • Hi, 

    So I've built with ITBOK itegration, but kernel still won't boot ( or perhaps it's running, I can't verify this really, since there's no output from kernel ) 

  • Hi, 

    problem was solved by switching SD/MMC card.