Create Account
Search
You are here: TDG Forum  >>  Texas Instruments SOMs and Development Kits  >>  OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit  >>  u-boot init image change crashes system during boot?

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 05 Jun 2015 03:32 PM by  Adam Ford
u-boot init image change crashes system during boot?
 7 Replies
Sort:
You are not authorized to post a reply.
Author Messages
mvly
Basic Member
Basic Member
Posts:104


--
04 Jun 2015 10:32 AM

    I just changed the default u-boot image and after rebuilding the image, I cannot get it to boot. Just FYI, the image is much larger than the logicPD one because it includes color and more images. Resolution is 480x272 image. Again this is for the android 2.3.4 build.

     

    It stops after loading the kernel. Here is the serial read out:

    Loading uImage from mmc to 0x81000000]...

    bootargs=console=ttyO0,115200 display=480:640:5:5:2:2:5:2:25888:0x100033:16 root=/dev/mmcblk0p2 rw rootwait init=/init androidboot.console=ttyO0 omap_vout.vid1_static_vrfb_alloc=y vram=32M omapfb.vram=0:16M

    reading uImage

     

    3917256 bytes read

    ## Booting kernel from Legacy Image at 81000000 ...

       Image Name:   Linux-3.0.8-gb2874c8-dirty

       Image Type:   ARM Linux Kernel Image (uncompressed)

       Data Size:    3917192 Bytes = 3.7 MiB

       Load Address: 80008000

       Entry Point:  80008000

       Verifying Checksum ... OK

       Loading Kernel Image ... OK


    Any help would be appreciated. I can do without the image change, but I would prefer it worked
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    04 Jun 2015 10:51 AM
    If I were to send you a private e-mail, would you be willing to share the image with me?

    I'd like to see what's happening.

    adam
    mvly
    Basic Member
    Basic Member
    Posts:104


    --
    04 Jun 2015 11:09 AM

    glad to.

     

    I will send you the jpg, the bmp, and the .h I generated following the instruction.

     

    Thanks,
    mvly
    Basic Member
    Basic Member
    Posts:104


    --
    04 Jun 2015 11:28 AM

    I just sent the email using another email account because it was easier than the login email account.

     

    Thanks!
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    04 Jun 2015 03:28 PM
    It looks like it might be an image size issue. I was able to get it working with your logo after a few attempts, but I had to make it small. I am still waiting to hear back from the u-boot developer.

    adam
    mvly
    Basic Member
    Basic Member
    Posts:104


    --
    04 Jun 2015 04:27 PM

    Great. Sounds like I need to make it smaller. But I would be interested in seeing if there is a better fix without a memory limitation.

     

    Thanks,

    -Larry
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    05 Jun 2015 08:02 AM
    I asked on of the developers and he didn't know what the max size was, and the other developer is out of the office, so I'm going to open a ticket to have it investigated.

    I can't promise anything will get fixed, I will keep you posted when I get some more information.

    adam
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    05 Jun 2015 03:32 PM
    It seems like there was already a ticket entered for this bug.

    As one alternative, you could try making your logo tiny, then using u-boot to load the splash off the sd card. It doesn't stay on the screen long, but it's there while the kernel is loaded.

    You could modify the boot sequence to load the splash from SD card:

    mmc init
    fatload mmc 1 $loadaddr splash.bmp
    bmp display $loadaddr

    boot



    adam
    You are not authorized to post a reply.

    Forums Texas Instruments SOMs and Development Kits OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit