• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 102 subscribers
  • Views 4360 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.

Newly built Rowboat Android 2.1 for AM3517EVM - boot issue

Gerry Simmons
Intellectual 875 points
Other Parts Discussed in Thread: AM3517

This should be relatively easy for one of you to answer.

This weekend I downloaded the Rowboat GIT sources and after installing a few missing packages, I built the kernel, SGX support, and rootfs with no issues.

I have a working AM3517EVM that I've verified with the Rotating Cube demo from the AM3517 workshop. I re-initialized one of my 2GB SD cards with this Android build, but when I boot from SD Card I get the following "Kernel panic - not syncing: No init found. Try passing init= option to kernel." 

My SD Card already had MLO, uboot.bin, and the rotating cube kernel, and I replaced it with the Android kernel. This uboot is version is "2009.08-dirty (Jan 05 2010 - 10:21:46)"  The Rowboat Android wiki for the AM3517 recommends uboot version from the TI PSP SDK release 3_00_00_03 . I'm downloading that now, but I have the feeling that is NOT my problem, and my problem is related to the uboot bootcmd or mmcargs.

Can someone tell me what bootcmd and mmcargs should be set to to get android up and running?

Also, my SD card was partitioned and formatted using:

Disk /dev/sdd: 1967 MB, 1967128576 bytes 
255 heads, 63 sectors/track, 239 cylinders 
Units = cylinders of 16065 * 512 = 8225280 bytes 
Disk identifier: 0x00000000 
 
Device         Boot      Start         End      Blocks   Id  System 
/dev/sdb1         *              1           15      120456   c  W95 FAT32 (LBA)

/dev/sdd2                      16         239     1799280   83  Linux

and not,

Disk /dev/sdd: 1977 MB, 1977614336 bytes 
64 heads, 63 sectors/track, 957 cylinders 
Units = cylinders of 4032 * 512 = 2064384 bytes 
Disk identifier: 0x00000000 
 
Device Boot      Start         End      Blocks   Id  System 
/dev/sdd1            1          30       60448+   b  W95 FAT32

/dev/sdd2           31         957     1868832   83  Linux

Now, I don't think this will be a problem, but someone smarter than me should please comment!

  • 0
    TI__Intellectual 1790 points

    Gerry,

    Have you looked at our TI Android Devkit release,

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/01_00_00/index_FDS.html

    The user guide and release notes should answer most of the questions, we have also packaged pre-built binaries for x-loader, u-boot and uImage with necessary bootargs.

    Regards,

    Khasim

  • 0
    TI__Intellectual 1195 points

    Gerry,

    It looks like you need to add init=/init to your bootargs. This is what my command line looks like on a beagleboard rev XM, booting from MMC.

    Kernel command line: console=ttyS2,115200n8 androidboot.console=ttyS2 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootd
    elay=1 init=/init ip=off omap_vout.vid1_static_vrfb_alloc=y

    Carlos.

     

  • 0 in reply to Carlos Hernandez
    Intellectual 875 points

    OK. Great feedback fellas!   I got my board up!

    I downloaded the docs from the TI URL that Khasim provided . The User Manual suggested that I delete the preset uboot bootargs on the board. I use this board for other things, so I didn't want to do that. It also suggested the following procedure upon interrupting u-boot:

    AM3517# mmc init
    AM3517# fatload mmc 0 0x82000000 boot.scr
    AM3517# source 0x82000000

    I had to get boot.scr from the pre-built images (kernel and bootstraps,) and put in on my SD Card, but I left the kernel and rootfs that I had built from Rowboat. Board came up beautifully!

    One issue I do have is that after Android comes up, if I bring up an Android application, like Search, or Browser, I can't seem to figure out how to close it!  (On my wife's Droid phone there is an <Up Arrow> and <CR Arrow> that is NOT part of the touchscreen to do that.

    Suggestions?

    Oh! And I'm trying to get the 802.11 radio on the EVM initialized. Any help with that would be appreciated!

  • 0 in reply to Gerry Simmons
    TI__Intellectual 1790 points

    You can connect USB Keyboard to the board and use the keys to move back and forth on UI. In FroYo google has fixed this, we should be able to get you this release shortly.

    Regards,

    Khasim

  • 0 in reply to Gerry Simmons
    Intellectual 875 points

    Through a complete set of coincidences, I happened to meet the primary developer of the Rowboat Android release. (Turns out, I've known her for 4 months! The world is getting WAY too small for me!)

    She showed me that by connecting a USB Mouse to the board before Android boots, the kernel will load support for the mouse, and a cursor comes up on the LCD Panel. It is much easier to navigate Android using a mouse - closing applications, running the menus and windows, etc. There is also support for a USB Keyboard.

    She also showed me the Froyo release running on My Board!  Way cool!  I didn't realize that Eclair, and previous versions, were using a Java Interpreter and my understanding is that Froyo uses a Java Compiler. Huge increase in performance!