PCT2303 (ETC) PDF技术资料下载
PCT2303 供应信息 IC Datasheet 数据表 (1/1 页)
按型号查询：
PCT2303的AMR和MDC
[PCT2303 for AMR & MDC
&&PCT2303PDF文件：
PCT2303的AMR和MDC[PCT2303 for AMR & MDC
文件大小：&&60 KPDF页数：
&&1 页联系供应商：&& 品牌Logo:
&&&&未知厂家 [ ETC ]
!Codec/DAA Features??????????86dB dynamic range TX/RXpaths2-4 –wire hybridIntegrated ring detectorHigh Voltage Isolation of 2000V4000V InternationalSupport for “Caller ID”Compliant with FCC Part 68,CTR21, Net 4 and JATELow power standbyLow profile SOIC package( 2 ) SOIC 16 pins 10x3x1.55mmLow power consumption10mA @ 3.3V operation1mA @ 3.3V power downPCT2303 for AMR & MDCMotherboard integration of the modem subsystem has been problematic to date, in large part due to FCC andother international telecom certification processes that delay the introduction of a motherboard when themodem’s analog I/O (codec and DAA) circuitry was physically soldered to the board. Resolvinghomologation/certification issues for OEMs is one of the key objectives of the AMR specification.With an open, Industry-standard riser solution, a system manufacturer is free to implement audio and/or modemfunctions on the motherboard at a lower bill of materials (BOM) cost than would be possible by deploying thesefunctions in either industry-standard expansion slots or in a proprietary method.PC-TEL has streamlined the traditional modem into the Host Signal Processing (HSP) solution. Operatingwith the Pentium class processors, HSP becomes part of the host computer’s system software. It requires lesspower to operate and less physical space than standard modem solutions. PC-TEL’s HSP modem is an easilyintegrated, cost-effective communications solution that is flexible enough to carry you into the future.The 2303 chip set is an integrated direct access arrangement (DAA) and Codec that provides a programmableline interface to meet international telephone line requirements. The 2303 chip set is available in two 16-pinsmall outline packages (AC’97 interface on PCT303A and phone-line interface on PCT303W). The chip seteliminates the need for an AFE, an isolation transformer, relays, opto-isolators, and 2- to 4-wire hybrid. The2303 chip set dramatically reduces the number of discrete components and cost required to achieve compliancewith international regulatory requirements. The PCT303A complies with AC’97 Interface specification Rev. 2.1.The chip set is fully programmable to meet world-wide telephone line interface requirements including thosedescribed by CTR21, NET4, JATE, FCC, and various country-specific PTT specifications. The programmableparameters of the 2303 chip set include AC termination, DC termination, ringer impedance, and ringer threshold.The 2303 chip set has been designed to meet stringent world-wide requirements for out-of-band energy, billing-tone immunity, lightning surges, and safety requirements.Standard FeaturesData???ITU-T V.90 V.34, V.32bis, V.32,V.22bis, V.22, V.21, V.23,Bell 212A, Bell 103Data CompressionITU-T V.42bisMNP Class 5Error CorrectionITU-T V.42 LAPMMNP 2-4ITU-T V. 17, V.29, V.27ter, V.21Channel 2Group 3EIA Class IIntegrated DAA/Codec Chip SetAC ‘97 Digital ControllerAC ‘97 Audio CodecRJ11Integrated 2303 DAA/CodecRJ11AC ‘97 Audio CodecAMR 46-pin ConnectorAC ‘97 DigitalControllerFax?Modem Daughter CardMDC 30-pin ConnectorOperating Systems?Windows 98, NT 4.0, WindowsCE 2.0, and LinuxMicroModem Daughter Card(MD2)Modem Riser Card(MR2)68mmPTT ApprovedCountriesAustralia *AustriaBelgiumBulgaria *CanadaCyprus *DenmarkFinlandFranceGermanyGreece *Iceland *IrelandIsrael *ItalyJapanLuxembourg *MaltaNetherlandsNew Zealand *NorwayPortugalSingapore *South Africa *SpainSwedenSwitzerlandUnited KingdomUSAApproval pending in countriesmarked with *2303W Chip SetMDCI/F30-Pin27*45mm60mm2303W Chip SetIntel AMR I/FUS Office70 Rio RoblesSan Jose, CA 95134 USATel: 408-965-2100 Fax: 408-383-0455Japan OfficeYoshida Bldg. 5014-1-31, Kudankita, Chiyoda-ku, Tokyo 102Tel: +81-3- Fax: +81-3-Taiwan Office10F-2, 160, Sec 6, Minchuan E. Rd.,Taipei, Taiwan, R. O. C.Tel: +886-2- Fax: +886-2-Europe Office26 Rue Des Sources91530 Sermaise, FranceTel: +33-1- Fax: +33-1-扫二维码下载作业帮
拍照搜题，秒出答案，一键查看所有搜题记录
下载作业帮安装包
扫二维码下载作业帮
拍照搜题，秒出答案，一键查看所有搜题记录
关于专利中的 foreign application priority data美国专利 US ,PCT Filed: Sep.27,1999Date of Patent Jun, 1, 2004Foreign Application Priority Data： Sep.25,1998 (Great Britain)请问这个美国专利什么时候过期呢? 我是菜鸟,我认为要申请优先权的话也应该在一年内申请,这个申请超过了一年,所以优先权申请不成立.
窝窝西门2174
扫二维码下载作业帮
拍照搜题，秒出答案，一键查看所有搜题记录
美国专利第 号PCT国际申请日：公告日（专利日） 日国外优先权日 日/26是礼拜六礼拜天,延迟到9月27日,没有超过一年.专利期限从PCT申请日起算20年.
为您推荐：
其他类似问题
扫描下载二维码【原创】Android 系统稳定性 - ANR（二） - 美帝亡我之心不死，腐败终成抽心一烂。 - ITeye技术网站
博客分类：
文章都为原创，转载请注明出处，未经允许而盗用者追究法律责任。 很久之前写的了，留着有点浪费，共享之。编写者：李文栋P.S. OpenOffice粘贴过来后格式有些混乱。
//WindowManager所在的进程是system_server，进程号是127
I/WindowManager( 127): Input event dispatching timed out sending to com.example.anrdemo/com.example.anrdemo.ANRActivity
//system_server进程中的ActivityManagerService请求kernel向5033进程发送SIGNAL_QUIT请求
//你可以在shell中使用命令达到相同的目的：adb shell kill -3 5033
//和其他的Java虚拟机一样，SIGNAL_QUIT也是Dalvik内部支持的功能之一
I/Process ( 127): Sending signal. PID: 5033 SIG: 3
//5033进程的虚拟机实例接收到SIGNAL_QUIT信号后会将进程中各个线程的函数堆栈信息输出到traces.txt文件中
//发生ANR的进程正常情况下会第一个输出
I/dalvikvm( 5033): threadid=4: reacting to signal 3
I/dalvikvm( 5033): Wrote stack traces to '/data/anr/traces.txt'
... ...//另外还有其他一些进程
//随后会输出CPU使用情况
E/ActivityManager( 127): ANR in com.example.anrdemo (com.example.anrdemo/.ANRActivity)
//Reason表示导致ANR问题的直接原因
E/ActivityManager( 127): Reason: keyDispatchingTimedOut
E/ActivityManager( 127): Load: 3.85 / 3.41 / 3.16
//请注意ago，表示ANR发生之前的一段时间内的CPU使用率，并不是某一时刻的值
E/ActivityManager( 127): CPU usage from 26835ms to 3662ms ago with 99% awake:
E/ActivityManager( 127): 9.4% 98/mediaserver: 9.4% user + 0% kernel
E/ActivityManager( 127): 8.9% 127/system_server: 6.9% user + 2% kernel / faults: 1823 minor
E/ActivityManager( 127): +0% 5033/com.example.anrdemo: 0% user + 0% kernel
E/ActivityManager( 127): 39% TOTAL: 32% user + 6.1% kernel
//这里是later，表示ANR发生之后
E/ActivityManager( 127): CPU usage from 601ms to 1132ms later with 99% awake:
E/ActivityManager( 127): 10% 127/system_server: 1.7% user + 8.9% kernel / faults: 5 minor
E/ActivityManager( 127): 10% 163/InputDispatcher: 1.7% user + 8.9% kernel
E/ActivityManager( 127): 1.7% 127/system_server: 1.7% user + 0% kernel
E/ActivityManager( 127): 1.7% 135/SurfaceFlinger: 0% user + 1.7% kernel
E/ActivityManager( 127): 1.7% 2814/Binder Thread #: 1.7% user + 0% kernel
E/ActivityManager( 127): 37% TOTAL: 27% user + 9.2% kernel
final void appNotResponding(ProcessRecord app, ActivityRecord activity,
ActivityRecord parent, final String annotation) {
//firstPids和lastPids两个集合存放那些将会在traces中输出信息的进程的进程号
ArrayList&Integer& firstPids = new ArrayList&Integer&(5);
SparseArray&Boolean& lastPids = new SparseArray&Boolean&(20);
//mController是IActivityController接口的实例，是为Monkey测试程序预留的，默认为null
if (mController != null) {
long anrTime = SystemClock.uptimeMillis();
if (MONITOR_CPU_USAGE) {
updateCpuStatsNow(); //更新CPU使用率
synchronized (this) { //一些特定条件下会忽略ANR
if (mShuttingDown) {
Slog.i(TAG, "During shutdown skipping ANR: " + app + " " + annotation);
} else if (app.notResponding) {
Slog.i(TAG, "Skipping duplicate ANR: " + app + " " + annotation);
} else if (app.crashing) {
Slog.i(TAG, "Crashing app skipping ANR: " + app + " " + annotation);
//使用一个标志变量避免同一个应用在没有处理完时重复输出log
app.notResponding =
//①当前发生ANR的应用进程被第一个添加进firstPids集合中
firstPids.add(app.pid);
//②dumpStackTraces是输出traces文件的函数
File tracesFile = dumpStackTraces(true, firstPids, processStats, lastPids, null);
String cpuInfo =
if (MONITOR_CPU_USAGE) { //MONITOR_CPU_USAGE默认为true
updateCpuStatsNow(); //再次更新CPU信息
synchronized (mProcessStatsThread) {
//输出ANR发生前一段时间内的CPU使用率
cpuInfo = mProcessStats.printCurrentState(anrTime);
info.append(processStats.printCurrentLoad());
info.append(cpuInfo);
//输出ANR发生后一段时间内的CPU使用率
info.append(processStats.printCurrentState(anrTime));
//③将ANR信息同时输出到DropBox中
addErrorToDropBox("anr", app, app.processName, activity, parent, annotation,
cpuInfo, tracesFile, null);
//在Android4.0中可以设置是否不显示ANR提示对话框，如果设置的话就不会显示对话框，并且会杀掉ANR进程
boolean showBackground = Settings.Secure.getInt(mContext.getContentResolver(),
Settings.Secure.ANR_SHOW_BACKGROUND, 0) != 0;
synchronized (this) {
if (!showBackground && !app.isInterestingToUserLocked() && app.pid != MY_PID) {
Process.killProcessQuiet(app.pid);
// 显示ANR提示对话框
Message msg = Message.obtain();
HashMap map = new HashMap();
msg.what = SHOW_NOT_RESPONDING_MSG;
map.put("app", app);
if (activity != null) {
map.put("activity", activity);
mHandler.sendMessage(msg);
public static File dumpStackTraces(boolean clearTraces, ArrayList&Integer& firstPids,
ProcessStats processStats, SparseArray&Boolean& lastPids, String[] nativeProcs) {
//系统属性“dalvik.vm.stack-trace-file”用来配置trace信息输出文件
String tracesPath = SystemProperties.get("dalvik.vm.stack-trace-file", null);
if (tracesPath == null || tracesPath.length() == 0) {
File tracesFile = new File(tracesPath);
File tracesDir = tracesFile.getParentFile();
if (!tracesDir.exists()) tracesFile.mkdirs();
//FileUtils.setPermissions是个很有用的函数，设置文件属性时经常会用到
FileUtils.setPermissions(tracesDir.getPath(), 0775, -1, -1); // drwxrwxr-x
//clearTraces为true，会删除旧文件，创建新文件
if (clearTraces && tracesFile.exists()) tracesFile.delete();
tracesFile.createNewFile();
FileUtils.setPermissions(tracesFile.getPath(), 0666, -1, -1); // -rw-rw-rw-
} catch (IOException e) {
Slog.w(TAG, "Unable to prepare ANR traces file: " + tracesPath, e);
//一个重载函数
dumpStackTraces(tracesPath, firstPids, processStats, lastPids, nativeProcs);
return tracesF
getpropdalvik.vm.stack-trace-file
setprop dalvik.vm.stack-trace-file /tmp/stack-traces.txt
private static void dumpStackTraces(String tracesPath, ArrayList&Integer& firstPids,
ProcessStats processStats, SparseArray&Boolean& lastPids, String[] nativeProcs) {
//使用FileObserver监听应用进程是否已经完成写入traces文件的操作
//Android在判断桌面壁纸文件是否设置完成时也是用的FileObserver，很有用的类
FileObserver observer = new FileObserver(tracesPath, FileObserver.CLOSE_WRITE) {
public synchronized void onEvent(int event, String path) { notify(); }
//首先输出firstPids集合中指定的进程，这些也是对ANR问题来说最重要的进程
if (firstPids != null) {
int num = firstPids.size();
for (int i = 0; i & i++) {
synchronized (observer) {
//前面提到的SIGNAL_QUIT
Process.sendSignal(firstPids.get(i), Process.SIGNAL_QUIT);
observer.wait(200);
&!-- Watchdog写完后注意补充章节号 --&
Slog.i(TAG, "DropBox Service");
ServiceManager.addService(Context.DROPBOX_SERVICE, //服务名称为“dropbox”
new DropBoxManagerService(context, new File("/data/system/dropbox")));
public voidadd(DropBoxManager.Entryentry)
publicboolean isTagEnabled(String tag)
publicsynchronized DropBoxManager.Entry getNextEntry(String tag, long millis)
//文件中输出的第一个进程的trace信息，正是发生ANR的演示程序
//开头显示进程号、ANR发生的时间点和进程名称
----- pid 9183 at
22:20:42 -----
Cmd line: com.example.anrdemo
DALVIK THREADS: //以下是各个线程的函数堆栈信息
//mutexes表示虚拟机实例中各种线程相关对象锁的value值
(mutexes: tll=0 tsl=0 tscl=0 ghl=0 hwl=0 hwll=0)
//依次是：线程名、线程优先级、线程创建时的序号、①线程当前状态
"main" prio=5 tid=1 TIMED_WAIT
//依次是：线程组名称、suspendCount、debugSuspendCount、线程的Java对象地址、线程的Native对象地址
| group="main" sCount=1 dsCount=0 obj=0x self=0xce68
//sysTid是线程号，主线程的线程号和进程号相同
| sysTid=9183 nice=0 sched=0/0 cgrp=default handle=-
| schedstat=(
at java.lang.VMThread.sleep(Native Method)
at java.lang.Thread.sleep(Thread.java:1213)
at java.lang.Thread.sleep(Thread.java:1195)
at com.example.anrdemo.ANRActivity.makeANR(ANRActivity.java:44)
at com.example.anrdemo.ANRActivity.onClick(ANRActivity.java:38)
at android.view.View.performClick(View.java:2486)
at android.view.View$PerformClick.run(View.java:9130)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3703)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
at dalvik.system.NativeStart.main(Native Method)
//②Binder线程是进程的线程池中用来处理binder请求的线程
"Binder Thread #2" prio=5 tid=8 NATIVE
| group="main" sCount=1 dsCount=0 obj=0x40750b90 self=0x1440b8
| sysTid=9190 nice=0 sched=0/0 cgrp=default handle=1476256
| schedstat=( 63135 4 )
at dalvik.system.NativeStart.run(Native Method)
"Binder Thread #1" prio=5 tid=7 NATIVE
| group="main" sCount=1 dsCount=0 obj=0x self=0x78d40
| sysTid=9189 nice=0 sched=0/0 cgrp=default handle=1308088
| schedstat=( 43212 10 )
at dalvik.system.NativeStart.run(Native Method)
//线程名称后面标识有daemon，说明这是个守护线程
"Compiler" daemon prio=5 tid=6 VMWAIT
| group="system" sCount=1 dsCount=0 obj=0x self=0x141e78
| sysTid=9188 nice=0 sched=0/0 cgrp=default handle=1506000
| schedstat=(
at dalvik.system.NativeStart.run(Native Method)
//JDWP线程是支持虚拟机调试的线程，不需要关心
"JDWP" daemon prio=5 tid=5 VMWAIT
| group="system" sCount=1 dsCount=0 obj=0x self=0x16c958
| sysTid=9187 nice=0 sched=0/0 cgrp=default handle=1510224
| schedstat=( 7617 7 )
at dalvik.system.NativeStart.run(Native Method)
//“Signal Catcher”负责接收和处理kernel发送的各种信号，例如SIGNAL_QUIT、SIGNAL_USR1等就是被该线程
//接收到，这个文件的内容就是由该线程负责输出的，可以看到它的状态是RUNNABLE，不过此线程也不需要关心
"Signal Catcher" daemon prio=5 tid=4 RUNNABLE
| group="system" sCount=0 dsCount=0 obj=0x self=0x150008
| sysTid=9186 nice=0 sched=0/0 cgrp=default handle=1501664
| schedstat=( 6621 9 )
at dalvik.system.NativeStart.run(Native Method)
"GC" daemon prio=5 tid=3 VMWAIT
| group="system" sCount=1 dsCount=0 obj=0x self=0x168010
| sysTid=9185 nice=0 sched=0/0 cgrp=default handle=1503184
| schedstat=( 1778 2 )
at dalvik.system.NativeStart.run(Native Method)
"HeapWorker" daemon prio=5 tid=2 VMWAIT
| group="system" sCount=1 dsCount=0 obj=0x self=0x16a080
| sysTid=9184 nice=0 sched=0/0 cgrp=default handle=550856
| schedstat=( 36669 15 )
at dalvik.system.NativeStart.run(Native Method)
----- end 9183 -----
----- pid 127 at
22:20:42 -----
Cmd line: system_server
//省略其他进程的信息
Thread.java中定义的状态
Thread.cpp中定义的状态
TERMINATED
RUNNING/RUNNABLE
TIMED_WAITING
TIMED_WAIT
INITIALIZING
&!-- 线程的ThreadGroup最好也写进去 --&
E/ActivityManager( 127): ANR in com.example.anrdemo (com.example.anrdemo/.ANRActivity)
E/ActivityManager( 127): Reason: keyDispatchingTimedOut
E/ActivityManager( 127): Load: 3.85 / 3.41 / 3.16 //? CPU平均负载
//②ANR发生之前的一段时间内的CPU使用率
E/ActivityManager( 127): CPU usage from 26835ms to 3662ms ago with 99% awake://③
E/ActivityManager( 127): 9.4% 98/mediaserver: 9.4% user + 0% kernel
E/ActivityManager( 127): 8.9% 127/system_server: 6.9% user + 2% kernel / faults: 1823 minor //⑤ minor或者major的页错误次数
E/ActivityManager( 127)://⑥+0% 5033/com.example.anrdemo: 0% user + 0% kernel
E/ActivityManager( 127): 39% TOTAL: 32% user + 6.1% kernel
//⑦ANR发生之后的一段时间内的CPU使用率
E/ActivityManager( 127): CPU usage from 601ms to 1132ms later with 99% awake:
E/ActivityManager( 127): 10% 127/system_server: 1.7% user + 8.9% kernel / faults: 5 minor
E/ActivityManager( 127): 10% 163/InputDispatcher: 1.7% user + 8.9% kernel
E/ActivityManager( 127): 1.7% 127/system_server: 1.7% user + 0% kernel
E/ActivityManager( 127): 1.7% 135/SurfaceFlinger: 0% user + 1.7% kernel
E/ActivityManager( 127): 1.7% 2814/Binder Thread #: 1.7% user + 0% kernel
E/ActivityManager( 127): 37% TOTAL: 27% user + 9.2% kernel
CPU使用率= (T – I) / T
//第一次使用成员变量mProcessStats采样
if (MONITOR_CPU_USAGE) {
updateCpuStatsNow();
//声明了一个局部变量，参数true表示包括线程信息
final ProcessStats processStats = new ProcessStats(true);
//将processStats作为实参传入，在dumpStackTraces中相隔500毫秒两次调用其update函数进行采样
File tracesFile = dumpStackTraces(true, firstPids, processStats, lastPids);
String cpuInfo = null;
if (MONITOR_CPU_USAGE) {
//因为在第一次调用后，可能由于输出trace信息等操作，中间执行了较长的时间，所以有第二次使用成员变量
//mProcessStats采样，尽量使得采样时间点靠后。
//此函数中要求连续两次采样时间间隔不少于5秒，所以一般不会执行第二次采样。一旦执行，就会出现两个采样
//时间点一个在ANR发生之前，另一个在其之后，或者两个时间点都在ANR发生之后的情况。
updateCpuStatsNow();
synchronized (mProcessStatsThread) {
//mProcessStats是成员变量，创建对象时传入的参数是false，所以不包括线程信息
//此处先输出ANR发生之前一段时间内的CPU使用率
cpuInfo = mProcessStats.printCurrentState(anrTime);
info.append(processStats.printCurrentLoad());
info.append(cpuInfo);
//processStats对象是在ANR发生后创建并采样的，所以输出的是ANR发生之后一段时间内的CPU使用率
info.append(processStats.printCurrentState(anrTime));
。一个文件第一次被读写时会有很多的
&!-- 求证一下 --&
浏览 46562
浏览: 319795 次
来自: 北京
summertime2013 写道最后一句话，为什么继续超过1 ...
真心牛人啊
最后一句话，为什么继续超过10秒没返回，又会引起第2种ANR？ ...
楼主，求出书啊。求内容啊
读了您的几篇文章，找到了很多昨天上午向您请教问题的答案，受益匪 ...PCT14 数据表(PDF) - List of Unclassifed Manufacturers
数据搜索系统，热门电子元器件搜索
Selected language &
PCT14 数据表 (PDF) -
List of Unclassifed Manufacturers
部件型号 &PCT14
文件大小 &
396.51 Kbytes
页 & 11 Pages
制造商 &ETC1&[List of Unclassifed Manufacturers]
PCT14 数据表 (HTML) - List of Unclassifed Manufacturers&
相关电子零件
部件型号部件说明Hml View制造商
&&&&&Motorola, Inc&&&&&Toshiba Semiconductor&&&&&Sony Corporation&&&&&OKI electronic componets&&&&&NEC&&&&&Toshiba Semiconductor&&&&&ams AG&&&&&OKI electronic componets&&&&&Toshiba Semiconductor&&&&&Toshiba Semiconductor
ALLDATASHEET是否为您带来帮助?& &
& &|&&& &|&& & &|&& & &|&&
<a href="javascript:addbookmark()"书签& &|&&
All Rights Reserved(C)2003 - 2017&& &
Mirror SitesEnglish :
Japanese :
Portuguese :