• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 100 subscribers
  • Views 2066 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Ducati failure message for blaze board

priyan ob
Intellectual 305 points

Hi,

I am trying to load Android Jellybean 4.2.0 to Blazeboard. Somehow I compiled the image and now I am trying to boot from SD Card. The boot log stops at a point where it shows a message

[62.008911] omap-rproc omap-rproc.1: rproc_loader_cont: failed to load ducati-m3.bin

But I could found 'ducati-m3.bin' file inside system/vendor/firmware'. What can be the reason for this?

I am attaching the complete log file with this post.


Thanks

Priyan

  • 0
    TI__Guru**** 161600 points

    Hello Priyan,

    Here is a link with the tested android and ducati sources (note that there are also release notes for compiling your android kernel in case you need to make modifications):

    http://omappedia.org/wiki/Android:_Working_with_pre-built_binaries#Blaze

    Note that ducati can be installed after you flash your board with android. 

    Hope this helps.

    Best Regards,

    Yordan

  • 0 in reply to Yordan Kovachev
    Intellectual 305 points

    Hi Yordan,

    I have already followed the procedures in the release notes of Android Jellybean for Blaze from omappedia.org (instead of prebuilt image). Thus, I built the MLO, u-boot.bin, uImage and Android File system.

    I have solved the above mentioned error by changing the mode of certain .prop and .rc files under system folder of the file system. But, now on booting, the blaze board shows the android logo and stops there. Meanwhile, I am getting some 'untracked pid' errors. Am I missing any files in the Android File System which I have built? I have viewed the logcat, but  I couldn't figure out anything from that.

    Thanks

    Priyan.

  • 0 in reply to priyan ob
    TI__Guru**** 161600 points

    Hello Priyan,

    Could you please try the solution described here:

    http://e2e.ti.com/support/omap/f/849/t/215322.aspx

    The steps for AJ4.2.0 should be similar.

    Best Regards,

    Yordan

  • 0 in reply to Yordan Kovachev
    Intellectual 305 points

    Hello Yordan,

    As per your opinion, I decided to flash the pre-built image to blaze4430. I have downloaded the required files from omappedia (Now I am trying Android 4.2.5 ). I had a look at the link you gave me. Still I am confused!!!

    Can you please elaborate about the following, or describe step wise instructions that I need to do

    1) SD card partitions (types) [ I have a FAT 'boot' partition and an ext4 'rootfs' partition]

    2) Which all files are to be copied to 'rootfs' partition. [I have copied u-boot.bin and MLO files to 'boot' partition]

    3) When the blaze board goes into fastboot mode, the green LED blinks . I waited for 10 minutes. Nothing is on the display!!

    Thanks

    Priyan

  • 0 in reply to priyan ob
    TI__Guru**** 161600 points

    Hello Priyan,

    To answer your question:

    Since you've been able to enter fastboot mode on your blaze board your first steps were correct.

    1) SD card partitions (types) [ I have a FAT 'boot' partition and an ext4 'rootfs' partition] 

    This is correct.

    2) Which all files are to be copied to 'rootfs' partition. [I have copied u-boot.bin and MLO files to 'boot' partition]

    This is also correct.

    Once you've managed to make blaze board enter fastboot mode  you should do the following to boot from the sdcard (as described in the e2e link I gave you):

    Note that when executing the below commands your pwd should be the directory where your image files are located.
     - from your host pc run   sudo ./fastboot oem format

     - from your host pc run sudo ./fastboot.sh

     - reboot your board

    Best Regards,

    Yordan

  • 0 in reply to Yordan Kovachev
    Intellectual 305 points

    But Yordan, I cannot issue the aforementioned commands from my PC. The console display is stuck after displaying "Fastboot entered".

    I am using USB Mini cable for serial port and a micro cable for this process. Shown below the console output.

    ==========================================

    Texas Instruments Inc X-Loader 1.41.0-jenkins-JB_xloader_mr1-1^0 (Apr  3 2013 - 04:03:17)
    mmc read: Invalid size
    Starting OS Bootloader from MMC/SD1 ...


    U-Boot 1.1.4-jenkins-JB_uboot_mr1-294^0 (Apr  3 2013 - 04:03:48)

    Load address: 0x80e80000
    DRAM:  1024 MB
    Flash:  0 kB
    Using default environment

    In:    serial
    Out:   serial
    Err:   serial
    Battery not detected
    Initializing SD(0) Slot.
    ptbl slot: SD:(0).
    efi partition table not found
    efi partition table:
    ptbl slot: EMMC:(1).
         256     128K xloader
         512     256K bootloader
        1024     128K misc
        2048      16M efs
       34816      16K crypto
       34848       8M recovery
       51232       8M boot
       67616     512M system
     1116192     256M cache
     1640480    6774M userdata
    Net:   KS8851SNL
    Hit any key to stop autoboot:  0
    OMAP44XX SDP # fastboot
    I2C read: I/O error
    I2C read: I/O error
    Device Serial Number: 0A3BC3AA0801500D
    Fastboot entered...

    ==================

    Thanks

    Priyan

  • 0 in reply to priyan ob
    TI__Guru**** 161600 points

    I guess that is the console displaying the status of your board.

    You should open another console and execute the commands from there.

    Best Regards,

    Yordan

  • 0 in reply to priyan ob
    Intellectual 305 points

    Hi Yordan,

    I was mistaken about the concept of Fastboot. Now, I have flashed Android 4.2.5 to my Blaze4430. I selected S2 switches to boot from EMMC. I could see the bootloader coming up. See the following output. Why does not the kernel bring up?

      I have used all of the necessary files from omappedia. In my blaze, the MLO file (https://gforge.ti.com/gf/download/frsrelease/1046/6490/Blaze_OMAP4470_HS_ES1.0_MLO)  didn't work for me. I have tried it by changing its name to 'MLO' instead of 'Blaze_OMAP4470_HS_ES1.0_MLO'. Still it didn't work. Later then, I took one of the MLO files ('Blaze_OMAP4430_GP_ES2.3_MLO') in the emmc folder downloaded and renamed it to 'MLO' and tried. This worked for me. I have tried the flashing command ./fastboot.sh --pwd and the flashing was successful. Then, what can be the error?

    Output:

    =========

    Texas Instruments Inc X-Loader 1.41.0-jenkins-JB_xloader_mr1-1^0 (Apr  3 2013 - 04:03:17)
    Starting OS Bootloader from EMMC ...


    U-Boot 1.1.4-jenkins-JB_uboot_mr1-294^0 (Apr  3 2013 - 04:03:48)

    Load address: 0x80e80000
    DRAM:  1024 MB
    Flash:  0 kB
    Using default environment

    In:    serial
    Out:   serial
    Err:   serial
    Battery not detected
    efi partition table:
    ptbl slot: EMMC:(1).
         256     128K xloader
         512     256K bootloader
        1024     128K misc
        2048      16M efs
       34816      16K crypto
       34848       8M recovery
       51232       8M boot
       67616     512M system
     1116192     256M cache
     1640480    6774M userdata
    Net:   KS8851SNL

     reboot command [�*K�������M��D)J�S�
                                         ENzo�w��p/��R��;�U�u��/oUu߭]B���$�c��%�,
                                                                                       ��Y����4�%a��N<��e�����;��(�c8j��（�m2N��r�o����&���7<��c���G/����О��σH��j�"M��g����h��Cxv�u]
    Hit any key to stop autoboot:  0
    kernel   @ 80008000 (4895472)
    ramdisk  @ 81000000 (185156)
    I2C read: I/O error

    Starting kernel ...

    Uncompressing Linux... done, booting the kernel.
    =================

  • 0 in reply to priyan ob
    Intellectual 305 points

    Hi,

    At last, I built Android Jellybean 4.2.5P2 and successfully ported to Blaze4430 board!!!  I flashed the image and the device is running perfectly.

    The one and only one issue I am facing is the WiFi connectivity. I might have missed anything. I will check it. Anyways, thanks Yordan for your key inputs.

    Thanks

    Priyan O B.

  • 0 in reply to priyan ob
    TI__Guru**** 161600 points

    Hello Priyan,


    For the wi-fi you can try the following (bellow commands are from http://omappedia.org/wiki/4AJ.2.5P2_OMAP4_Jelly_Bean_Release_Notes#Building_WLAN_driver_WiLink7)

    try executing the following commands on your board:

    # su
# wilink7.sh

    Best Regards, 
    Yordan