Porting Andoid on A1200 MING

[biggerstone]

Hi all:
With your help, i can telnet to my phone. There are some mistakes i took.
(1)"/root/android_nfs "is inclued in my phone's kernel CMD_LINE , but root NFS directory is "/home/android_nfs" on my ubuntu host which is not the same diretory with CMD_LINE.
So my phone mount NFS failed and return error -13.

(2)I ping 192.168.1.1 OK, but i can't telnet to my phone because telnet's port is closed. Just because my ROOT NFS file have error and no telnet server started.
This error cause by bunzip2 android-nfs-root-m5r14.bz2. When bunzip2 android_nfs_root-m5-r14.bz2 in porting package to /root/android_nfs, i get the below error:
tar: android_nfs/dev/binder: Cannot mknod: Operation not permitted
tar: android_nfs/dev/fb0: Cannot mknod: Operation not permitted
tar: android_nfs/dev/block/ram0: Cannot mknod: Operation not permitted
tar: android_nfs/dev/block/ram1: Cannot mknod: Operation not permitted
tar: android_nfs/dev/block/ram2: Cannot mknod: Operation not permitted
tar: android_nfs/dev/block/ram3: Cannot mknod: Operation not permitted
....//more Operation not permitted

Everybody should check your bunzip2 tool , your destination partition type and access permission if get this error. an solution is:
duplicating different filesystem - Linux Forums

(3)when telnet server is not starter in A1200 phone, the boot log looks like:
VFS: mounted root(file system)
Waring: unable to open an initial console. //just because the android_nfs/dev/ directory is NULL

Now i can telnet to my phone, and Run ‘./init’ execute after telnet into phone, But i can't see Android string(the LCD is white)?
According by the PDF guide, you can see this sentence: "F. Run ‘./init’ execute after telnet into phone, you will see Android string".
If i take a mistake?? I am a rookie for Linux.

The below is the output information when run './init' after telnet into phon. Then i
# ./init
init: HOW ARE YOU GENTLEMEN
init: reading config file
init: device init
init: mtd partition -1,


PS: I am ready to poting the latest android kernel to my A1200(just for interesting and to learning linux OS),
if any links can help me? Please tell me, thank you very much!

[sabrod]

Congrats!
(1) right (i repeat this 2 or 3 times to you in my posts!!)
(2) partially wrong, i told you to be root, this is enough (su ???)
(3) totally wrong, you don't understand. Please PM!! Create another thread in devellopment forum! People want to learn here, so do not help without knowledge.
(4) stop watching reality TV shows...saying you are ready made me laugh, or maybe porting means playing a bit with some screen garglings for you? If so, yes, i guess you're almost done, courage!
(5) For any help ask privatly, i'll try (as a self made linuxer) to reply. I don't know any link to easily learn everything, but Let me google that for you

I have to say (it's ridiculous as i' m french and speak also an awfull english ) your english is not perfect, far from perfect (easy...i agree ).
I noticed a lot of misunderstood. You need to re-read if you cannot understand the first time (don't take that as an insult, I feel myself very long to understand sometimes... It DEPENDS).

i already helped you for the nfsroot problem. You could ask another thread (basic linux. kernel compilation related) and have the same replies and help.
You need to know more on linux, first, then more on ezx devices, then more on openezx and android.
If you have the time, just study! the net is full of howto. Even the READMEs and man pages, without the net are helpful.
Sorry to say so.
Good luck.

[cout]

I have successfully built a kernel from the git sources and applied the android core patch. I did not apply any of the other patches. I did modify the configuration for root over nfs.

I boot using boot_usb:

$ sudo ../a780/ezx_boot_usb arch/arm/boot/zImage 1740 "root=/dev/nfs nfsroot=192.168.1.1:/home/android_nfs rw ip=192.168.1.2:192.168.1.1:192.168.1.1:255.255.255.0:ezx:usb0ff mem=32M@0xA0000000 mem=16M@0xAC000000"

The kernel boots, but gives me a message:

hub 1-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?
hub 1-0:1.0: unable to enumerate USB devices on port 3
rbcbind: server 192.168.1.1 not responding, timed out

On the server side, the nfs server is running, but I don't think that matters, since the usbnet interface won't come up (when I'm running the original kernel, it comes up automatically). I cannot bring up the interface by hand, either:

# ifconfig usb0 192.168.1.1 netmask 255.255.255.0 mtu 900
SIOCSIFADDR: No such device
usb0: unknown interface: No such device
SIOCSIFNETMASK: No such device
SIOCSIFMTU: No such device

Is there something wrong in my boot cmdline? Or maybe a driver that needs to be enabled in the kernel?

[sabrod]

I have successfully built a kernel from the git sources and applied the android core patch. I did not apply any of the other patches. I did modify the configuration for root over nfs.

I boot using boot_usb:

Good to see that patch and build OK...
Did you used genblob before? Follow this:
Getting Started - OpenEZX

$ sudo ../a780/ezx_boot_usb arch/arm/boot/zImage 1740 "root=/dev/nfs nfsroot=192.168.1.1:/home/android_nfs rw ip=192.168.1.2:192.168.1.1:192.168.1.1:255.255.255.0:ezx:usb0ff mem=32M@0xA0000000 mem=16M@0xAC000000"

With thoses new kernels (2.6.28RC8 ), bootusb(0.3 needed http://openezx.org/download/boot_usb-0.3.tar.gz)
you don't need mem params.
Can you explain me what is :ezx:usb0ff (see ~linux/Documentation/filesystems/nfsroot.txt ) I just never saw such params...

The kernel boots, but gives me a message:

hub 1-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?
hub 1-0:1.0: unable to enumerate USB devices on port 3
rbcbind: server 192.168.1.1 not responding, timed out

I never saw that (android related maybe ? )
edit: USB port 3 is BP, so not the port we plug to the pc... should be solved now on 2009, most of these drivers are new and work.
Compile usb with debug...

On the server side, the nfs server is running, but I don't think that matters, since the usbnet interface won't come up (when I'm running the original kernel, it comes up automatically).

What is the original kernel ?? You means a fully traditionnal openezx configured one? Stock moto's kernel?

I cannot bring up the interface by hand, either:

# ifconfig usb0 192.168.1.1 netmask 255.255.255.0 mtu 900
SIOCSIFADDR: No such device
usb0: unknown interface: No such device
SIOCSIFNETMASK: No such device
SIOCSIFMTU: No such device

Is there something wrong in my boot cmdline? Or maybe a driver that needs to be enabled in the kernel?

no usb0 on the box sounds normal as it's udev that probably need a connection to create the usb0 device.

Anyway this could be due to the command line (maybe mem= ?, ip= ?) but always use genblob for loading a recent kernel (with bootusb, used in 2 times, not necessary to flash genblob for testing it) .
You can always disable usb on kernel, and copy this rootfs on the sd with "root=/dev/mmcblk0p1" (2nd part of sd card) , well see the defonfig-ezx file for that, and hope the rootfs will work on sd as well :s
You should can find openezx patches separately there :
Index of /wyrm/images/latest/patches
i suggest you the openezx git revision cacec205c17b9924db3ca625347a33d0ddd2b694
just because i'm sure it works like a charm on a1200 and a910, I know this is only 2.6.28rc3 but it's enough as bp, sound, RTC, ... works. you could even be able to test alsa and phone calls.
Note that i'm a newbie, but i do know no huges changes has been made, (in git), and it's the one i use most of the time.
On the openezx mailing list, you'll sometimes find some more patches , the newests, like fm radio and bluetooth...
Good luck.

[cout]

Good to see that patch and build OK...
Did you used genblob before? Follow this:
Getting Started - OpenEZX

I'm using boot_usb rather than flashing genblob. One step at a time -- I'd like to see the phone boot over usb before I flash.

With thoses new kernels (2.6.28RC8 ), bootusb(0.3 needed http://openezx.org/download/boot_usb-0.3.tar.gz)
you don't need mem params.
Can you explain me what is :ezx:usb0ff (see ~linux/Documentation/filesystems/nfsroot.txt ) I just never saw such params...

I used the same parameters that androidezx used in his config, just specified them to boot_usb rather than building them into the kernel.

According to the "getting started" page on the wiki, the parameters have the following meaning:

ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>

Omitting the last 3 parameters does not have any discernible effect.

I never saw that (android related maybe ? )
Compile usb with debug...

Interesting idea, I may try that. I think the "cannot enable port" error is the source of my problem now.

Maybe I should just put the rootfs on the mmc card instead of trying to fool with nfs.

no usb0 on the box sounds normal as it's udev that probably need a connection to create the usb0 device.

I am getting usb0 now; I'm not sure what's changed except time passing and some kernel modules being unloaded (maybe I had an extra module loaded that I wasn't supposed to have?)

Anyway this could be due to the command line (maybe mem= ?) but always use genblob for loading a recent kernel (with bootusb, used in 2 times, not necessary to flash genblob for testing it) .
You should can find openezx patches separately there :
Index of /wyrm/images/latest/patches
i suggest you the openezx git revision cacec205c17b9924db3ca625347a33d0ddd2b694
just because i'm sure it works like a charm on a1200 and a910, I know this is only 2.6.28rc3 but it's enough as bp, sound, RTC, ... works. you could even be able to test alsa and phone calls.
Note that i'm a newbie, but i do know no huges changes has been made, (in git), and it's the one i use most of the time.
On the openezx mailing list, you'll sometimes find some more patches , the newests, like fm radio and bluetooth...
Good luck.

I'm using latest git HEAD; I think that should work (except Porting Android to a new device indicates that I need 2.6.25).

[sabrod]

Ok, please read again my post, as i edited it the same time you were writing...
For ip , yes i always omit the 3 lasts params
Latest head at git.openezx.org maybe works, i just know there has been changes due to last .28 submission, and that maybe the revision i gave you were the last stable I KNEW. As i didn't test the very lasts changes...
I though you were downloading the kernel.org, with no patches (i was surprised you booted...)

If you have usb0, then you maybe don't need to re-compile with pxa-udc with debug...
edited:
When you don't have/have probs with network, the most efficient is to setup /network/interface or the network stuff in your distro.
This way, you don't have to push some commands at boot time (ifconfig usb0 192.168.... is long to write...) .
Maybe an unplug/plug can solve the enumeratiton problem sometimes, too

ps: sorry if i edit my post all the time

[biggerstone]

[QUOTE=cout;172494]I have successfully built a kernel from the git sources and applied the android core patch. I did not apply any of the other patches. I did modify the configuration for root over nfs.

I boot using boot_usb:

$ sudo ../a780/ezx_boot_usb arch/arm/boot/zImage 1740 "root=/dev/nfs nfsroot=192.168.1.1:/home/android_nfs rw ip=192.168.1.2:192.168.1.1:192.168.1.1:255.255.255.0:ezx:usb0ff mem=32M@0xA0000000 mem=16M@0xAC000000"

The kernel boots, but gives me a message:

hub 1-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?
hub 1-0:1.0: unable to enumerate USB devices on port 3
rbcbind: server 192.168.1.1 not responding, timed out


/////////First, please check if you can find usb device after download by "lsusb"? if YES, you can ingore this complain.

Secondly, please check the firewall on your host. if you get error (return -5) when mount VFS, maybe the firewall blocks the connection.
please refence: USB Networking - Openmoko.

if you get the return value -13, mayby your ROOT NFS configurated failed. To be sure nfs-server works well, you should mount your ROOT NFS by loopback test..
Rootfs on NFS - OpenEZX


On the server side, the nfs server is running, but I don't think that matters, since the usbnet interface won't come up (when I'm running the original kernel, it comes up automatically). I cannot bring up the interface by hand, either:

# ifconfig usb0 192.168.1.1 netmask 255.255.255.0 mtu 900
SIOCSIFADDR: No such device
usb0: unknown interface: No such device
SIOCSIFNETMASK: No such device
SIOCSIFMTU: No such device
//Please to disconnect your eth0, and configurate the usb0' ip address in /etc/network/interfaces.

[wyrm]

hub 1-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?
hub 1-0:1.0: unable to enumerate USB devices on port 3

This is not related, PXA usb port 3, is connected to the Neptune chip (BP). This error is expected if you use OpenEZX with the BP on flash mode.
The mini usb port is pxa usb port 2.

I'm using boot_usb rather than flashing genblob. One step at a time -- I'd like to see the phone boot over usb before I flash.

You can use gen-blob without flashing. It will solve the issue you are having with usb. There is a bug on the mainline pxa27x-udc driver, it cant handle the USB Device Controller already enabled case (the motorola bootloader enables the UDC and leaves it enabled), gen-blob will properly disable the UDC before giving control to kernel.

[sabrod]

Oh!! now things will go smoothly with Wyrm!

I just can add that genblob cannot be used to place calls as long as you don't flash it.
It don't really quit the flash mode, but _just_ does what Wyrm explained (and coded!) : reset to zero, the USB controler, so that the (so buggy, but lovely) pxa-udc driver don't "panic" the kernel.

Of course if you used genblob, heh... it can be another story related to android or not...
Note: Don't forget to use the last bootusb, it have the Ram command line built-in.

I wish you luck with your experiments.

[cout]

You can use gen-blob without flashing. It will solve the issue you are having with usb. There is a bug on the mainline pxa27x-udc driver, it cant handle the USB Device Controller already enabled case (the motorola bootloader enables the UDC and leaves it enabled), gen-blob will properly disable the UDC before giving control to kernel.

Ah, thanks, I didn't realize that. I think I'm still doing something wrong, though:

- I start phone in flash mode
- I hold down Vol+ and use boot_usb to run gen_blob
- The phone says "USB ready"
- I unplug the USB cable and then plug it back in (otherwise the next step fails with "FAILED: RQSN")
- I use boot_usb to upload the zImage to the phone
- It finds gen_blob and claims to successfully upload
- The phone still says "USB ready"

Is the pxa27x-udc bug fixed in another branch? Could I merge it into my local android branch?