• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 100 subscribers
  • Views 1874 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.

OMAP4430SDP tablet can NOT bring up on 4AI.1.3 release

Leo Du
Prodigy 50 points

I'm updating my codebase from L27.IS.1 to 4AI.1.3.
I have already bring up my OMAP4430SDP tablet on L27.IS.1 release successfully, but after I ported all the changes to 4AI.1.3, and then compiled the eMMC images by following the release note, I can NOT bring up it then.

When my tablet power on with the 4AI.1.3 release, there is a strange thing that the bootcmd is changed to "booti mmc0", but acturally it's defined in omap44XXtablet.h as "#defined CONFIG_BOOTCOMMAND "booti mmc1"", why would this happen?

Then, I workaround this by hard-coding the bootcmd to be "booti mmc1" in the uboot, so that to make it go ahead...

It failed to open the property directory when initialize the android:
"init: Unable to open persistent property directory /data/property errno: 2"

I attached the log files FYR.:
0419-L27.IS.1-ATD-1.log is the logs that power up successfully on L27.IS.1
0424-4AI.1.3-ATD-3.log is the logs that can NOT power up on 4AI.1.3

Can any body get me some suggestions about this?

log file.7z
  • 0
    TI__Expert 8055 points

    Hi Leo,

    I noticed from your logs that in the L27.IS.1 release, you were using:

         Machine: OMAP4 blaze board

    And in the 4AI.1.3 release, you are using:

         Machine: ATD Tablet

    Did you change mach types?  Are you still using omap44XXtablet.h?  This may explain why the bootcmd changed.

    Your error about "init: Unable to open persistent property directory" could point to some issue in your init.*.rc files or bootargs.  Are you using the same init.*.rc files and bootargs as on Blaze?  (and that boots correctly on your Blaze or Tablet?)  Here are pre-built binaries for the 4AI.1.3 release on Blaze and Blaze Tablet if you want to test: http://www.omappedia.com/wiki/Android:_Working_with_pre-built_binaries

    Regards,

    Gina

  • 0 in reply to Gina Glaser
    Prodigy 50 points

    Hi Gina,

    Yes, I changed the mach types from "OMAP4 blaze board" to "ATD Tablet" when moving to 4AI.1.3 release.

    And I still using the omap44xxtablet.h in u-boot, just adding some my own macro definitions.

    The init.*.rc that I used in L27.IS.1 release and the 4AI.1.3 release is no difference.

    The OMAP4430SDP tablet I'm bringing up now is a customized hardware built in our factory, not the TI Blaze Tablet.

    We do have a TI Blaze board in hand(OMAP4430), but it also can NOT power up with the pre-built binaries of 4AI.1.3 release, we are now clarifiing this with our TI supporting window...

  • 0 in reply to Leo Du
    TI__Expert 8055 points

    Leo,

    Are you using the 4AI.1.3 pre-built binaries here http://www.omappedia.com/wiki/Android:_Working_with_pre-built_binaries

    Make sure to take the binaries for your correct platform - Blaze or Blaze Tablet.

    What is the issue you are seeing in boot-up?

    Regards,

    Gina

  • 0 in reply to Gina Glaser
    Prodigy 50 points

    Hi Gina,

    Now, my tablet can power up with the 4AI.1.3 release, but it is in safe mode same as it is by using L27.IS.1 release.

    Can you tell me what condition that can make the android power up into safe mode?

    Thanks.

    Leo

  • 0 in reply to Leo Du
    TI__Expert 8055 points

    Leo,

    Systems are typically programmed to boot into safe mode when a certain combination of keys is pressed during power on.  Are any of your keys stuck, or have you made any changes to the key mapping, such that it thinks these keys are being pressed?  The Blaze Tablet enters safe mode if the browser key is pressed during bootup.  (The home key is for Fastboot, and the back key is for Recovery.)  If you have started with the Blaze Tablet codebase in porting to your platform, how is the browser key mapped?

    Regards,

    Gina

  • 0 in reply to Gina Glaser
    TI__Expert 8055 points

    Leo,

    Did this solve your issue?

    Another possible cause of booting up in safe mode is that you have some mis-match in the files used for boot.  Double-check if your SYSBOOT switches are set for booting up from eMMC or SD card and that the correct bootargs and files are used.

    Regards,

    Gina