• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 377 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Android bootup failing after firmware upgarde

Harman Kalra
Prodigy 150 points

Hi

I created the update.zip as per the document (System Update and Factory Reset) provided by TI.

When I tried to upgrade my Blaze mdp with this update.zip, upgrade went successfully. But nothing got displayed after the updated version booted up.

On logging into the board via blaze debug console, I saw the following messages in an infinite loop:

[   48.832092] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4835, drivers/gpu/pvr/bridged_pvr_bridge.c]
[   49.368408] init: untracked pid 303 exited
[   49.410919] init: untracked pid 310 exited

As per the error messages, I think it may be because the kernel compatibility, its failing to load the sgx driver (no module displayed on lsmod).

I gave the following argument:

 TARGET_PREBUILT_KERNEL=/home/hkalra/sources/blaze/base/kernel/                            (it is the location of our kernel source tree)             

Hope its correct. Even we tried copying zImage to a particular location and gave that path as the above argument.

Please help us out from this situation.

  • 0
    TI__Genius 10545 points

    I found the definition for that variable in

    /4ai17/mydroid/device/ti/blaze/device.mk

    ifeq ($(TARGET_PREBUILT_KERNEL),)
    LOCAL_KERNEL := device/ti/blaze_tablet/boot/zImage
    else
    LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL)
    endif

    it is defined in the same place for Blaze tablet but for Tablet director.

    /4ai17/mydroid/device/ti/blaze_tablet/device.mk

    This variable is used to point to the files that are used to build boot.img and this boot.img is used in the output .zip file. You can try removing the export from the arguments list and replace the file in this directory boot inside blaze or blaze_tablet directories then the build system will take it from it's original place. The LOCAL_KERNEL variable is used in this same file to copy it to out/target/product/blaze/boot directory to be used to create boot.img.

    #Need to revisit the fastboot copy files
    PRODUCT_COPY_FILES += \
        $(LOCAL_KERNEL):kernel \

    The other file that talks for recovery is ota_update_master_reset_generic.pdf, it described a little more in detail about the source of the files used in recovery procedure, I think it is available with a TI representative, I compared both files and the one you mentioned is the most complete, this second one describes and gives some more samples to use.

  • 0 in reply to Manuel Contreras
    Prodigy 150 points

    Thanks Manuel your suggestion worked for us. Android is booted successfully now.