Ubuntu12.04 compile android4.1 and fl pandaboard

1: Today is a very happy day. Because I have been using android4.0.1 for a while, I just don't know how to enter pandabard's fastboot mode. I also don't know why; last night, the computer was not shut down overnight. The latest Android version "master" was downloaded. It should be the latest android4.1 fruit jelly; it should be downloaded from half past five; down; then I was lucky again: Make-J8 let it compile it by myself; this morning I came to see: It was really an unexpected surprise: there was no error! The compilation is complete, and I'm more pleased that I used this to re-compile and enter the fastboot of pandaboard. Although it was done every day a few days ago, I accidentally went in again; so let's make a conclusion: To avoid forgetting:

A) Hardware: I only connect a USB cable to the host. => NO, as soon as I plug in the power cord, the status2 light on the pandaboard board will go off, and the virtual machine ubuntu12.04 will not be connected to pandaboard;

B) software: I first waited in this status on the host: sudo device/Ti/panda/usbboot device/Ti/panda/bootloader. bin =>;

C) pandaboard Board: Press pwron_reset and gpio_113; => OK; the Board "seems to have succeeded since it started; (I didn't expect it to succeed, so I didn't care about the specific situation );

2: At first, I was excited and forgot to take a few screenshots: The following steps are performed by device/Ti/panda/readme, but the pandaboard power cord is not connected:

3:

4: it means that the flash is completely successful, but my system is completely successful and there is a problem: HDMI has no output: the display is not displayed; and the system has always had the following problem: that is, the device cannot be stopped. You can press enter to enter the terminal. The following information is printed by serial port: I can directly use: ADB shell cannot find the device. We look forward to further solutions:

5: In this case, you can still enter the android4.1 terminal: => note that the serial port is used:

6:

The solution is as follows: Success! Strange problem ......

Error: request_suspend_state: wakeup init: untracked PID 123 exited

Cause: (1) check that this is because the init. RC will re-mount the root file system as read-only, so that init. RC cannot create sub-directories.

(2) If an error such as init: untracked PID is output by serial port during ICS startup, it indicates that the partition permission of the INIT program is insufficient and needs to be modified in the code of telechips.

 

Solution: Modify init. RC and comment out the Mount yaffs2 MTD @ system/system Ro remount statement.

There is a row like this: Mount rootfs/RO remount. Just comment it out.

Bytes ----------------------------------------------------------------------------------------------------------------------------

7: It's an unpredictable problem. I can't get into fastboot again. I got stuck here again. I'm depressed ...... The method in the morning is not good ......

8: the last problem is a good phenomenon: If I am not satisfied with the guarantee that I can enter the fastboot mode of pandaboard at any time, I will not be able to continue with the source code for testing; so, I have been experimenting with how to enter the fastboot of pandaboard from yesterday to today. I have just entered the status: status2 indicator light off; status1 indicator light flashing; (2012/09/13/4 );

What have I done to access fastboot:

A) connect the USB to the host;

B) sudo device/Ti/panda/usbboot device/Ti/panda/bootloader. Bin

C) plugged in the power cord several times;

D) just entered again: press the two keys above pandaboard; failed; re-run the host ...... USB boot; above => step B;

E) Maybe I do know: Step B => press pandaboard: gpio_113 + pwron_reset; (hold gpio_121 and press pwron_reset); => I cannot enter either;

I found that I entered fastboot on this board! Still trying; these are my notes;

Certificate ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

9: the above problem is completely solved: it is actually a reason;

Sudo device/Ti/panda/usbboot device/Ti/panda/bootloader. remove sudo in front of bin. If you want to disable sudo, run CD device/Ti/panda/And then :. /usbboot. /bootloader. bin

My problem is completely solved;

You can also try su root directly as the root device/Ti/panda/usbboot device/Ti/panda/bootloader. bin ......

For details, refer to: the volume may need to go through the wall ......