www.久久久久|狼友网站av天堂|精品国产无码a片|一级av色欲av|91在线播放视频|亚洲无码主播在线|国产精品草久在线|明星AV网站在线|污污内射久久一区|婷婷综合视频网站

當前位置:首頁 > 嵌入式 > 嵌入式軟件
[導讀] ======================= 第一節(jié) ===========================這里簡單的介紹了Android的java環(huán)境基礎,在后面一節(jié)中會結合具體的實例來理解這一節(jié)的內容。一、Dalvik虛擬

 ======================= 第一節(jié) ===========================

這里簡單的介紹了Android的java環(huán)境基礎,在后面一節(jié)中會結合具體的實例來理解這一節(jié)的內容。

一、Dalvik虛擬機

Dalvik是Android的程序的java虛擬機,代碼在dalvik/下,

./

|-- Android.mk

|-- CleanSpec.mk

|-- MODULE_LICENSE_APACHE2

|-- NOTICE

|-- README.txt

|-- dalvikvm 虛擬機的實現(xiàn)庫

|-- dexdump

|-- dexlist

|-- dexopt

|-- docs

|-- dvz

|-- dx

|-- hit

|-- libcore

|-- libcore-disabled

|-- libdex

|-- libnativehelper 使用JNI調用本地代碼時用到這個庫

|-- run-core-tests.sh

|-- tests

|-- tools

`-- vm

二、Android的java框架

Android層次中第3層是java框架,第四層就是java應用程序。

Android的java類代碼,主要是在frameworks/base/core/java/下,

./

|-- Android

|-- com

|-- jarjar-rules.txt

`-- overview.html

我們再看一下frameworks/base/目錄

./

|-- Android.mk

|-- CleanSpec.mk

|-- MODULE_LICENSE_APACHE2

|-- NOTICE

|-- api

|-- awt

|-- build

|-- camera

|-- cmds

|-- common

|-- core

|-- data

|-- docs

|-- graphics

|-- include

|-- keystore

|-- libs

|-- location

|-- media

|-- native

|-- obex

|-- opengl

|-- packages

|-- preloaded-classes

|-- sax

|-- services

|-- telephony

|-- test-runner

|-- tests

|-- tools

|-- vpn

`-- wifi

這里也有Android的java框架代碼。

三、JNI

在Android中,通過JNI,java可以調用C寫的代碼,主要的實現(xiàn)是在frameworks/base/core/jni,通過查看Android.mk,我們可以看到最后生成了libandroid_runtime.so,具體實現(xiàn)JNI功能需要上面我們介紹的libnativehelper.so,

四、系統(tǒng)服務之java

1、binder,提供Android的IPC功能

2、servicemanager,服務管理的服務器端

3、系統(tǒng)進程zygote,負責孵化所有的新應用

======================= 第二節(jié) ==========================

在我平時工作中主要是進行l(wèi)inux網(wǎng)絡子系統(tǒng)的模塊開發(fā)、linux應用程序(C/C++)開發(fā)。在學習和從事驅動模塊開發(fā)的過程中,如果你對linux系統(tǒng)本身,包括應用程序開發(fā)都不了解,那么讀內核代碼就如同天書,毫無意義,所以我分析框架也是從基本系統(tǒng)api開始的,當然也不會太多涉及到應用程序開發(fā)。

好,開始這節(jié)主要是講一個簡單的adnroid應用程序,從應用程序出發(fā),到框架代碼。

分析的應用程序我們也奉行拿來主義:froyo/development/samples/HelloActivity

./

|-- Android.mk

|-- AndroidManifest.xml

|-- res

|-- src

`-- tests

其他的就多說了,看代碼

/**

* Copyright (C) 2006 The Android Open Source Project

*

* Licensed under the Apache License, Version 2.0 (the "License");

* you may not use this file except in compliance with the License.

* You may obtain a copy of the License at

*

* http://www.apache.org/licenses/LICENSE-2.0

*

* Unless required by applicable law or agreed to in writing, software

* distributed under the License is distributed on an "AS IS" BASIS,

* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

* See the License for the specific language governing permissions and

* limitations under the License.

*/

package Android.util;

import com.Android.internal.os.RuntimeInit;

import java.io.PrintWriter;

import java.io.StringWriter;

/**

* API for sending log output.

*

*

Generally, use the Log.v() Log.d() Log.i() Log.w() and Log.e()

* methods.

*

*

The order in terms of verbosity, from least to most is

* ERROR, WARN, INFO, DEBUG, VERBOSE. Verbose should never be compiled

* into an application except during development. Debug logs are compiled

* in but stripped at runtime. Error, warning and info logs are always kept.

*

*

Tip: A good convention is to declare a TAG constant

* in your class:

*

*

private static final String TAG = "MyActivity";

 

*

* and use that in subsequent calls to the log methods.

*

 

*

*

Tip: Don't forget that when you make a call like

*

Log.v(TAG, "index=" + i);

 

* that when you're building the string to pass into Log.d, the compiler uses a

* StringBuilder and at least three allocations occur: the StringBuilder

* itself, the buffer, and the String object. Realistically, there is also

* another buffer allocation and copy, and even more pressure on the gc.

* That means that if your log message is filtered out, you might be doing[!--empirenews.page--]

* significant work and incurring significant overhead.

*/

public final class Log {

/**

* Priority constant for the println method; use Log.v.

*/

public static final int VERBOSE = 2;

/**

* Priority constant for the println method; use Log.d.

*/

public static final int DEBUG = 3;

/**

* Priority constant for the println method; use Log.i.

*/

public static final int INFO = 4;

/**

* Priority constant for the println method; use Log.w.

*/

public static final int WARN = 5;

/**

* Priority constant for the println method; use Log.e.

*/

public static final int ERROR = 6;

/**

* Priority constant for the println method.

*/

public static final int ASSERT = 7;

/**

* Exception class used to capture a stack trace in {@link #wtf()}.

*/

private static class TerribleFailure extends Exception {

TerribleFailure(String msg, Throwable cause) { super(msg, cause); }

}

private Log() {

}

/**

* Send a {@link #VERBOSE} log message.

* @param tag Used to identify the source of a log message. It usually identifies

* the class or activity where the log call occurs.

* @param msg The message you would like logged.

*/

public static int v(String tag, String msg) {

return println_native(LOG_ID_MAIN, VERBOSE, tag, msg);

}

/**

* Send a {@link #VERBOSE} log message and log the exception.

* @param tag Used to identify the source of a log message. It usually identifies

* the class or activity where the log call occurs.

* @param msg The message you would like logged.

* @param tr An exception to log

*/

public static int v(String tag, String msg, Throwable tr) {

return println_native(LOG_ID_MAIN, VERBOSE, tag, msg + '/n' + getStackTraceString(tr));

}

/**

* Send a {@link #DEBUG} log message.

* @param tag Used to identify the source of a log message. It usually identifies

* the class or activity where the log call occurs.

* @param msg The message you would like logged.

*/

public static int d(String tag, String msg) {

return println_native(LOG_ID_MAIN, DEBUG, tag, msg);

}

/**

* Send a {@link #DEBUG} log message and log the exception.

* @param tag Used to identify the source of a log message. It usually identifies

* the class or activity where the log call occurs.

* @param msg The message you would like logged.

* @param tr An exception to log

*/

public static int d(String tag, String msg, Throwable tr) {

return println_native(LOG_ID_MAIN, DEBUG, tag, msg + '/n' + getStackTraceString(tr));

}

/**

* Send an {@link #INFO} log message.

* @param tag Used to identify the source of a log message. It usually identifies

* the class or activity where the log call occurs.

* @param msg The message you would like logged.

*/

public static int i(String tag, String msg) {

return println_native(LOG_ID_MAIN, INFO, tag, msg);

}

/**

* Send a {@link #INFO} log message and log the exception.

* @param tag Used to identify the source of a log message. It usually identifies

* the class or activity where the log call occurs.

* @param msg The message you would like logged.

* @param tr An exception to log

*/

public static int i(String tag, String msg, Throwable tr) {

return println_native(LOG_ID_MAIN, INFO, tag, msg + '/n' + getStackTraceString(tr));

}

/**

* Send a {@link #WARN} log message.

* @param tag Used to identify the source of a log message. It usually identifies

* the class or activity where the log call occurs.

* @param msg The message you would like logged.

*/

public static int w(String tag, String msg) {

return println_native(LOG_ID_MAIN, WARN, tag, msg);

}

/**

* Send a {@link #WARN} log message and log the exception.

* @param tag Used to identify the source of a log message. It usually identifies

* the class or activity where the log call occurs.

* @param msg The message you would like logged.

* @param tr An exception to log

*/

public static int w(String tag, String msg, Throwable tr) {

return println_native(LOG_ID_MAIN, WARN, tag, msg + '/n' + getStackTraceString(tr));

}

/**

* Checks to see whether or not a log for the specified tag is loggable at the specified level.

*

* The default level of any tag is set to INFO. This means that any level above and including[!--empirenews.page--]

* INFO will be logged. Before you make any calls to a logging method you should check to see

* if your tag should be logged. You can change the default level by setting a system property:

* 'setprop log.tag. '

* Where level is either VERBOSE, DEBUG, INFO, WARN, ERROR, ASSERT, or SUPPRESS. SUPPRESS will

* turn off all logging for your tag. You can also create a local.prop file that with the

* following in it:

* 'log.tag.='

* and place that in /data/local.prop.

*

* @param tag The tag to check.

* @param level The level to check.

* @return Whether or not that this is allowed to be logged.

* @throws IllegalArgumentException is thrown if the tag.length() > 23.

*/

public static native boolean isLoggable(String tag, int level);

/**

* Send a {@link #WARN} log message and log the exception.

* @param tag Used to identify the source of a log message. It usually identifies

* the class or activity where the log call occurs.

* @param tr An exception to log

*/

public static int w(String tag, Throwable tr) {

return println_native(LOG_ID_MAIN, WARN, tag, getStackTraceString(tr));

}

/**

* Send an {@link #ERROR} log message.

* @param tag Used to identify the source of a log message. It usually identifies

* the class or activity where the log call occurs.

* @param msg The message you would like logged.

*/

public static int e(String tag, String msg) {

return println_native(LOG_ID_MAIN, ERROR, tag, msg);

}

/**

* Send a {@link #ERROR} log message and log the exception.

* @param tag Used to identify the source of a log message. It usually identifies

* the class or activity where the log call occurs.

* @param msg The message you would like logged.

* @param tr An exception to log

*/

public static int e(String tag, String msg, Throwable tr) {

return println_native(LOG_ID_MAIN, ERROR, tag, msg + '/n' + getStackTraceString(tr));

}

/**

* What a Terrible Failure: Report a condition that should never happen.

* The error will always be logged at level ASSERT with the call stack.

* Depending on system configuration, a report may be added to the

* {@link Android.os.DropBoxManager} and/or the process may be terminated

* immediately with an error dialog.

* @param tag Used to identify the source of a log message.

* @param msg The message you would like logged.

*/

public static int wtf(String tag, String msg) {

return wtf(tag, msg, null);

}

/**

* What a Terrible Failure: Report an exception that should never happen.

* Similar to {@link #wtf(String, String)}, with an exception to log.

* @param tag Used to identify the source of a log message.

* @param tr An exception to log.

*/

public static int wtf(String tag, Throwable tr) {

return wtf(tag, tr.getMessage(), tr);

}

/**

* What a Terrible Failure: Report an exception that should never happen.

* Similar to {@link #wtf(String, Throwable)}, with a message as well.

* @param tag Used to identify the source of a log message.

* @param msg The message you would like logged.

* @param tr An exception to log. May be null.

*/

public static int wtf(String tag, String msg, Throwable tr) {

tr = new TerribleFailure(msg, tr);

int bytes = println_native(LOG_ID_MAIN, ASSERT, tag, getStackTraceString(tr));

RuntimeInit.wtf(tag, tr);

return bytes;

}

/**

* Handy function to get a loggable stack trace from a Throwable

* @param tr An exception to log

*/

public static String getStackTraceString(Throwable tr) {

if (tr == null) {

return "";

}

StringWriter sw = new StringWriter();

PrintWriter pw = new PrintWriter(sw);

tr.printStackTrace(pw);

return sw.toString();

}

/**

* Low-level logging call.

* @param priority The priority/type of this log message

* @param tag Used to identify the source of a log message. It usually identifies

* the class or activity where the log call occurs.

* @param msg The message you would like logged.

* @return The number of bytes written.

*/

public static int println(int priority, String tag, String msg) {

return println_native(LOG_ID_MAIN, priority, tag, msg);

}

/** @hide */ public static final int LOG_ID_MAIN = 0;

/** @hide */ public static final int LOG_ID_RADIO = 1;

/** @hide */ public static final int LOG_ID_EVENTS = 2;[!--empirenews.page--]

/** @hide */ public static final int LOG_ID_SYSTEM = 3;

/** @hide */ public static native int println_native(int bufID,

int priority, String tag, String msg);

}

我們看到所有代碼都是調用public static native int println_native(int bufID,

int priority, String tag, String msg);來實現(xiàn)輸出的,這個函數(shù)的實現(xiàn)就是C++,調用的方式就是JNI

我們看一下對應的jni代碼froyo/frameworks/base/core/jni/Android_util_Log.cpp,最終調用的輸出函數(shù)是

/*

* In class Android.util.Log:

* public static native int println_native(int buffer, int priority, String tag, String msg)

*/

static jint Android_util_Log_println_native(JNIEnv* env, jobject clazz,

jint bufID, jint priority, jstring tagObj, jstring msgObj)

{

const char* tag = NULL;

const char* msg = NULL;

if (msgObj == NULL) {

jclass npeClazz;

npeClazz = env->FindClass("java/lang/NullPointerException");

assert(npeClazz != NULL);

env->ThrowNew(npeClazz, "println needs a message");

return -1;

}

if (bufID < 0 || bufID >= LOG_ID_MAX) {

jclass npeClazz;

npeClazz = env->FindClass("java/lang/NullPointerException");

assert(npeClazz != NULL);

env->ThrowNew(npeClazz, "bad bufID");

return -1;

}

if (tagObj != NULL)

tag = env->GetStringUTFChars(tagObj, NULL);

msg = env->GetStringUTFChars(msgObj, NULL);

int res = __Android_log_buf_write(bufID, (android_LogPriority)priority, tag, msg);

if (tag != NULL)

env->ReleaseStringUTFChars(tagObj, tag);

env->ReleaseStringUTFChars(msgObj, msg);

return res;

}

當然我們發(fā)現(xiàn)最終輸出是

? 1int res = __Android_log_buf_write(bufID, (android_LogPriority)priority, tag, msg);

用力grep了一下代碼,結果如下

./system/core/include/cutils/log.h:int __Android_log_buf_write(int bufID, int prio, const char *tag, const char *text);

./system/core/liblog/logd_write.c:int __Android_log_buf_write(int bufID, int prio, const char *tag, const char *msg)

./system/core/liblog/logd_write.c: return __Android_log_buf_write(bufID, prio, tag, buf);

這個就是和Android專用驅動進行通信的方式,這個分析下去就有點深了,后面分析。

本站聲明: 本文章由作者或相關機構授權發(fā)布,目的在于傳遞更多信息,并不代表本站贊同其觀點,本站亦不保證或承諾內容真實性等。需要轉載請聯(lián)系該專欄作者,如若文章內容侵犯您的權益,請及時聯(lián)系本站刪除。
換一批
延伸閱讀

LED驅動電源的輸入包括高壓工頻交流(即市電)、低壓直流、高壓直流、低壓高頻交流(如電子變壓器的輸出)等。

關鍵字: 驅動電源

在工業(yè)自動化蓬勃發(fā)展的當下,工業(yè)電機作為核心動力設備,其驅動電源的性能直接關系到整個系統(tǒng)的穩(wěn)定性和可靠性。其中,反電動勢抑制與過流保護是驅動電源設計中至關重要的兩個環(huán)節(jié),集成化方案的設計成為提升電機驅動性能的關鍵。

關鍵字: 工業(yè)電機 驅動電源

LED 驅動電源作為 LED 照明系統(tǒng)的 “心臟”,其穩(wěn)定性直接決定了整個照明設備的使用壽命。然而,在實際應用中,LED 驅動電源易損壞的問題卻十分常見,不僅增加了維護成本,還影響了用戶體驗。要解決這一問題,需從設計、生...

關鍵字: 驅動電源 照明系統(tǒng) 散熱

根據(jù)LED驅動電源的公式,電感內電流波動大小和電感值成反比,輸出紋波和輸出電容值成反比。所以加大電感值和輸出電容值可以減小紋波。

關鍵字: LED 設計 驅動電源

電動汽車(EV)作為新能源汽車的重要代表,正逐漸成為全球汽車產業(yè)的重要發(fā)展方向。電動汽車的核心技術之一是電機驅動控制系統(tǒng),而絕緣柵雙極型晶體管(IGBT)作為電機驅動系統(tǒng)中的關鍵元件,其性能直接影響到電動汽車的動力性能和...

關鍵字: 電動汽車 新能源 驅動電源

在現(xiàn)代城市建設中,街道及停車場照明作為基礎設施的重要組成部分,其質量和效率直接關系到城市的公共安全、居民生活質量和能源利用效率。隨著科技的進步,高亮度白光發(fā)光二極管(LED)因其獨特的優(yōu)勢逐漸取代傳統(tǒng)光源,成為大功率區(qū)域...

關鍵字: 發(fā)光二極管 驅動電源 LED

LED通用照明設計工程師會遇到許多挑戰(zhàn),如功率密度、功率因數(shù)校正(PFC)、空間受限和可靠性等。

關鍵字: LED 驅動電源 功率因數(shù)校正

在LED照明技術日益普及的今天,LED驅動電源的電磁干擾(EMI)問題成為了一個不可忽視的挑戰(zhàn)。電磁干擾不僅會影響LED燈具的正常工作,還可能對周圍電子設備造成不利影響,甚至引發(fā)系統(tǒng)故障。因此,采取有效的硬件措施來解決L...

關鍵字: LED照明技術 電磁干擾 驅動電源

開關電源具有效率高的特性,而且開關電源的變壓器體積比串聯(lián)穩(wěn)壓型電源的要小得多,電源電路比較整潔,整機重量也有所下降,所以,現(xiàn)在的LED驅動電源

關鍵字: LED 驅動電源 開關電源

LED驅動電源是把電源供應轉換為特定的電壓電流以驅動LED發(fā)光的電壓轉換器,通常情況下:LED驅動電源的輸入包括高壓工頻交流(即市電)、低壓直流、高壓直流、低壓高頻交流(如電子變壓器的輸出)等。

關鍵字: LED 隧道燈 驅動電源
關閉