Подробнее о пакете драйверов:Тип: драйвер Имя: Microsoft MTP Device Drivers Производитель: Standard MTP-compliant devices Версия драйвера (программы установщика): 5.2.5326.4762 Операционная система: Windows XP, Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows 10 Разрядность ОС: 32-bit (x86), 64-bit (x64) Размер файла: 8.8 mb Дата выхода: 2016-02-22 |
This driver package is designed to improve your USB workflow. This tool provides you with official USB drivers. Using Lenovo USB Driver, update relevant system files. Also it's compatible with the most popular Windows-based operating systems. After installing the driver on your computer, you can connect your Lenovo smartphone and tables with. Four sets of potential drivers or moderators of signal diversity are discussed. First, selective forces of an abiotic (environmental) nature for optimal electrolocation and communication.
Microsoft MTP Device Drivers. Характеристики драйвера
Драйверы MTP Device версии 5.2.5326.4762 для подключения смартфонов к ПК. Предназначен для ручной и автоматической установки для Microsoft Windows.
Внимание! Перед установкой драйвера Microsoft MTP Device Drivers рекомендутся удалить её старую версию. Удаление драйвера особенно необходимо - при замене оборудования или перед установкой новых версий драйверов для видеокарт. Узнать об этом подробнее можно в разделе FAQ.
Файлы для скачивания (информация)
MTP_Device_Drivers_v.5.2.5326.4762.zip - ручная установка (8.8 mb) v.5.2.5326.4762 от 22.02.2016
ISDevices_MTK.NT_1.1129.00.zip - автоматическая установка (8.5 mb) v.5.2.5326.4762 от 22.02.2006
Поддерживаемые устройства (ID оборудований):
USBVID_0bb4&PID_0003 | MediaTek Inc.AndroidUSBEthernet/RNDIS |
USBVID_0bb4&PID_0004 | AlcatelAndroidADBInterface |
USBVID_0bb4&PID_2010 | LenovoCompositeADBInterface |
USBVID_0bb4&PID_2011 | Google Inc.AndroidCompositeADBInterface |
USBVID_0bb4&PID_2028 | MediaTek Inc.AndroidCompositeUSBEthernet/RNDIS |
USBVID_0bb4&PID_202C | MediaTekAndroidCompositeUSBEthernet/RNDIS |
USBVid_0e8d&Pid_0003 | MediaTek Inc.MT6227phone |
USBVID_0E8D&PID_00A5 | MediaTek Inc.GSM modem[MedionSurfstickModel:S4222] |
USBVID_0E8D&PID_00A6 | MediaTekMobileBroadbandDevice |
USBVID_0E8D&PID_00AA | MediaTekMobileBroadbandDevice |
USBVid_0e8d&Pid_2000 | MediaTek Inc.MT65xxPreloader |
USBVid_0e8d&Pid_2001 | LenovoDA USBVCOM(Android),MediaTekDA USBVCOM Port |
USBVID_0E8D&PID_2003 | MediaTekAndroidCompositeADBInterface |
USBVID_0e8d&PID_2004 | MediaTekUSBEthernet-RNDIS |
USBVID_0e8d&PID_2005 | MediaTekAndroidUSBEthernet/RNDIS |
USBVID_0E8D&PID_2006 | GadgetCDC VCOMDriver |
USBVid_0e8d&Pid_2007 | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_2008 | Standard MTP-compliant devicesMTP Device |
USBVID_0E8D&PID_200A | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_200C | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_200D | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_200E | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_200F | MediaTekUSB VCOM(Android) |
USBVID_0e8d&PID_2010 | MediaTekAndroidCompositeADBInterface |
USBVID_0e8d&PID_2011 | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_2012 | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_2013 | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_2014 | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_2016 | Standard MTP-compliant devicesMTP Device |
USBVID_0E8D&PID_2017 | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_2018 | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_2019 | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_201A | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_201B | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_201C | MediaTekAndroidADBInterface |
USBVID_0E8D&PID_201D | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_2021 | Google Inc.AndroidCompositeADBInterface |
USBVID_0E8D&PID_2022 | Standard MTP-compliant devicesMTP Device |
USBVID_0E8D&PID_2024 | MediaTekAndroidBootloaderInterface |
USBVID_0E8D&PID_2025 | Google Inc.AndroidCompositeADBInterface |
USBVID_0E8D&PID_2026 | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_2027 | MediaTekELT Port |
USBVID_0e8d&PID_2028 | MediaTekAndroidCompositeUSBEthernet/RNDIS |
USBVID_0E8D&PID_2029 | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_202A | MediaTekELT Port |
USBVID_0E8D&PID_202B | MediaTekELT Port |
USBVID_0e8d&PID_202C | MediaTekELT Port |
USBVID_0E8D&PID_202D | MediaTekETS Port |
USBVID_0E8D&PID_202E | MediaTekELT Port |
USBVID_0E8D&PID_202F | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_2030 | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_2031 | MediaTekModem Port |
USBVID_0E8D&PID_2032 | MediaTekAT Port |
USBVID_0E8D&PID_2033 | MediaTekAT Port |
USBVID_0E8D&PID_2034 | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_2035 | MediaTekETS Port |
USBVID_0E8D&PID_2036 | MediaTekETS Port |
USBVID_0E8D&PID_2037 | MediaTekETS Port |
USBVID_0E8D&PID_2038 | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_2039 | MediaTekETS Port |
USBVID_0E8D&PID_2040 | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_2041 | MediaTekETS Port |
USBVID_0e8d&PID_2042 | MediaTekELT Port |
USBVID_0e8d&PID_2043 | MediaTekAndroidCompositeUSBEthernet/RNDIS |
USBVID_0E8D&PID_2044 | MediaTekELT Port |
USBVID_0e8d&PID_2045 | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_2047 | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_2048 | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_2049 | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_2050 | MediaTekModem Port |
USBVID_0E8D&PID_2051 | MediaTekModem Port |
USBVID_0E8D&PID_2052 | MediaTekModem Port |
USBVID_0E8D&PID_2053 | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_2054 | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_2055 | MediaTekUSB VCOM(Android) |
USBVID_0E8D&PID_2056 | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_2057 | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_2058 | MediaTekETS Port |
USBVID_0E8D&PID_2059 | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_205A | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_205B | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_205C | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_205D | MediaTekELT Port |
USBVID_0E8D&PID_205E | MediaTekETS Port |
USBVID_0E8D&PID_205F | MediaTekAndroidCompositeADBInterface |
USBVID_0e8d&PID_2061 | MediaTekELT Port |
USBVID_0e8d&PID_2062 | MediaTekAndroidCompositeADBInterface |
USBVID_0E8D&PID_2063 | MediaTekETS Port |
USBVID_0e8d&PID_2064 | MediaTekAndroidCompositeUSBEthernet/RNDIS |
USBVID_0E8D&PID_7106 | MediaTekUSB DebugPort |
USBMS_COMP_MTP | |
SBUSVID_0E8D&PID_00A5 | MediaTek Inc.GSM modem[MedionSurfstickModel:S4222] |
SBUSVID_0E8D&PID_00A6 | MediaTekMobileBroadbandDevice |
SBUSVID_0E8D&PID_00AA | MediaTekMobileBroadbandDevice |
SBUSVID_0E8D&PID_7106 | MediaTekUSB DebugPort |
Другие драйверы от Microsoft
White or black boxes given away with a BT (British Telecom) broadband subscription in UK. The first noticeable difference between V1 and the V1.5 is the shape and size. Under the cover they are identical apart from a slight pcb revision, addition of 5 extra red led's and two extra buttons on the V1.5.
There are other routers based on the same board as the Home Hub V1. Known are: Speedtouch 7g and Aolbox although there may be more.
The Home Hub includes ADSL2+, 802.11b/g wireless, host and slave USB ports, 2 wired ethernet ports, DECT, FXS & FXO ports and VOIP functionality.
All members of the BT Home Hub OpenWrt community are now encouraged to join in ongoing development efforts on later models at http://openwrt.ebilan.co.uk.
Supported Versions
Not supported yet. However you can install OpenWrt (no ADSL) using a custom CFE.
Bootloader (CFE), OpenWrt prebuilt firmware, and patches to build your own firmware: HomeHubV1-openwrt_12.09_wl-CFE.zip |
Hardware Highlights
SoC | Ram | Flash | Ethernet | USB | Wireless | Serial | JTag | VOIP | FXS |
---|---|---|---|---|---|---|---|---|---|
Broadcom BCM96348 | 32MB | 8MB | 2 | Yes | yes | Yes | Yes | yes | yes |
OEM Flash Layout
Based on FIrmware 6.2.2.6
0x00000000-0x0003FFFF | Space allocated for bootloader - includes board parameters (serial number, Board type, MAC address, etc) |
0x00040000-0x000FFFFF | JFFS2 User partition |
0x00100000-0x0010000F | Firmware version magic |
0x00100010-0x001AFFFF | Linux Kernel |
0x001B0000-0x007FFFFF | Squashfs root fs |
It is somewhat different from the usual Broadcom layout. Probably due to the fact that this board does not use the CFE bootloader but uses a proprietory loader instead who's origins are unknown.This supplied bootloader is useless. I went through Tens of bootloaders before i come across a redboot loader from the inventel livebox and modified it to work with the Home Hub. Now i have recently discovered that this very same bootloader from the livebox is used in the Aolbox wich has a board identical to the Home Hub but uses different RAM memory thus the Aolbox/livebox and Home Hub bootloaders are not directly interchangeable.
Flash Details
You can access the flash via jtag at 1f400000 provided the Home Hub bootloader is running. If the loader is not running ie, bad flash you can access bootloader at 1fc00000+. The The flash chip is actually mapped at 1f800000-1fffffff while the mips boot address is 1fc00000 (half way through the physical flash address). The hub bootloader actally remaps the 4MB at 1fc00000 back before the physical start of the flash. Eg, actual 1f800000-1fffffff # copy 1fc00000-1fffffff to 1f400000 # now the flash lives at 1f400000-1fbfffff.
Installation
Flash Layout
Please check out the article flash.layout. It contains an example and a couple of explanations.
CFE easy installation
This section deals with how you install OpenWrt once the OEM bootloader is replaced by a new CFE.
- Press the button labeled as reset, don't release it yet!
- Wait 10 seconds
- Browse to http://192.168.1.1
- Upgrade the image
- Telnet to 192.168.1.1 and set a root password, or browse to http://192.168.1.1 if LuCI is installed. or browse to http://192.168.1.1 if LuCI is installed.
OEM installation using the TFTP method
Upgrading OpenWrt
→ generic.sysupgrade
If you have already installed OpenWrt and like to reflash for e.g. upgrading to a new OpenWrt version you can upgrade using the mtd command line tool. It is important that you put the firmware image into the ramdisk (/tmp) before you start flashing.
LuCI Web Upgrade Process
- Browse to http://192.168.1.1/cgi-bin/luci/mini/system/upgrade/ LuCI Upgrade URL
- Wait for reboot
Terminal Upgrade Process
- Use the following commands to upgrade.
- If sysupgrade does not support this router, use the following commands.
Basic configuration
→ Basic configuration After flashing, proceed with this.
Set up your Internet connection, configure wireless, configure USB port, etc.
Specific Configuration
Interfaces
The default network configuration is:
Interface Name | Description | Default configuration |
---|---|---|
br-lan | LAN & WiFi | 192.168.1.1/24 |
eth0 | WAN | dhcp |
eth1 | LAN | bridged |
wlan0 | WiFi | disabled |
Failsafe mode
Buttons
→ hardware.button on howto use and configure the hardware button(s).
The Home Hub 1 has only 1 button
Hardware
Info
Instruction set | MIPS |
---|---|
Vendor | Broadcom |
bootloader | Unknown (custom Thomson) Can be replaced by cfe |
System-On-Chip | BCM6348 |
CPU/Speed | BMIPS3300 V0.7 / 256 MHz |
Flash-Chip | Spansion S29GL064A11TFIR4, 64Mbit, 8MByte, Pointless bottom boot blocks |
Flash size | 8 MiB |
RAM-Chip | Qimonda HYB39SC256160FE-7, 8Mbitx16bit, 32MByte, 133MHz |
RAM size | 32 MiB |
Wireless | BCM4318 802.11b/g (onboard), using seperate radio amplifier and diversity switch via pci |
Ethernet | 1x internal PHY + 1x external PHY (Altima AC101 MII PHY) |
Internet | ADSL2+, not supported in OpenWrt |
USB | Yes |
DECT | Philips/NXP PCD80705 Baseband DECT processor via spi |
Slic | Silicon Labs si3230 ProSLIC |
Serial | Yes |
JTAG | Yes |
Photos
Technogym spa driver download. There are plenty of pictures of the Home Hub on the internet so i wont fill this space with its cover on.
V1.0
V2.0
Board:
HomeHub V1.0 | HomeHub V1.5 |
---|---|
Top view | Top view |
This one has had its led wiring changed to suit the Speedtouch 7G firmware | Note the extra 2 buttons and their position and the shape of the board. The led's are now on the other side too. |
Bottom view | Bottom view |
Note changes to the led type. They are now tri colour (green+red=orange). I have fitted it with a crude jtag connector. |
GPIOs
V1.0
LEDS | |||
---|---|---|---|
label | color | GPIO | active |
Lan Activity | green | 0 | high |
Upgrade | green | 1 | high |
Broadband (ADSL) | green | 2 | high |
WiFi | green | 3 | high |
Phone (icon) | green | 4 | high |
V1.5
Softdsp Driver Download Torrent
LEDS | |||
---|---|---|---|
label | color | GPIO | active |
green | 0 | ||
green | 1 | ||
green | 2 | ||
green | 3 | ||
green | 4 | ||
red | 5 | ||
red | 22 | ||
red | 7 | ||
red | 29 | ||
red | 30 |
Serial
→ port.serial general information about the serial port, serial port cable, etc.
How to connect to the Serial Port of this specific device:
- Solder a 4 pin header - Use a TTL serial cable
Photo of PCB with markings
Settings:
- Data bits: 8
- Stop bits: 1
JTAG
→ port.jtag general information about the JTAG port, JTAG cable, etc.
How to connect to the JTAG Port of this specific device:
Softdsp Driver Download Windows 10
Photo of PCB with markings
For reading/writing to the flash you can use UrJTAG (latest svn). UrJTAG is able to operate in DMA mode with bcm63xx boards, then it's faster than hairydairymaid. |
Backup whole flash
- Connect your JTAG cable from your computer to your board
- Power on the board
Restore whole flash
- Connect your JTAG cable from your computer to your board
- Power on the board
Flashing a bootloader
- Connect your JTAG cable from your computer to your board
- Power on the board
Debricking
→ generic.debrick
Bootlogs
OEM bootlog
Decompressing Bootloader................. Speedtouch initialization sequence started.BOOTING THE THOMSON LINUX KERNELStarting the kernel @ 0x801bc018 serial initializedLinux version 2.6.8.1 (debusb@cplx82.edegem.eu.thmulti.com) (gcc version 3.4.2) #1 Mon Nov 12 09:53:50 CET 2007CPU revision is: 00029107bcm63xx : initiazation of mpi bus ........Determined physical RAM map: memory: 01f7d000 @ 00002000 (usable)On node 0 totalpages: 8063 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 3967 pages, LIFO batch:1 HighMem zone: 0 pages, LIFO batch:1Built 1 zonelistsKernel command line: root=/dev/mtdblock1 rootfstype=squashfsbrcm mips: enabling icache and dcache..Primary instruction cache 16kB, physically tagged, 2-way, linesize 16 bytes.Primary data cache 8kB 2-way, linesize 16 bytes.PID hash table entries: 128 (order 7: 1024 bytes)Using 128.000 MHz high precision timer.Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)Memory: 29968k/32244k available (1450k kernel code, 2232k reserved, 258k data, 68k init, 0k highmem)Calibrating delay loop.. 251.39 BogoMIPSMount-cache hash table entries: 512 (order: 0, 4096 bytes)Checking for 'wait' instruction.. available.NET: Registered protocol family 16usbcore: registered new driver usbfsusbcore: registered new driver hubBluetooth: Core ver 2.6NET: Registered protocol family 31Bluetooth: HCI device and connection manager initializedBluetooth: HCI socket layer initializedsquashfs: version 3.2-r2 (2007/01/15) Phillip Loughersquashfs: LZMA suppport for slax.org by jroJFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.bcm963xx_serial driver v2.0Inotify sysfs create file = 0Inotify sysfs create file = 0Inotify sysfs create file = 0inotify device minor=63Using noop io schedulerThomson BCM963xx flash mapping for BTHubflash: Found 1 x16 devices at 0x0 in 16-bit bank Amd/Fujitsu Extended Query Table at 0x0040number of CFI chips: 1cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.flash mapping initializedCreating 3 MTD partitions on 'flash':0x00040000-0x00100000 : 'user'0x001b0000-0x00800000 : 'rootfs'0x00100010-0x001b0000 : 'kernel'mtd: partition 'kernel' doesn't start on an erase block boundary -- force read-onlyBluetooth: HCI UART driver ver 2.1Bluetooth: HCI H4 protocol initializedBluetooth: HCI BCSP protocol initializedbrcmboard: brcm_board_init entryERROR - Invalid number of MAC addresses (1007714320) is configured.NET: Registered protocol family 2IP: routing cache hash table of 512 buckets, 4KbytesTCP: Hash tables configured (established 2048 bind 4096)NET: Registered protocol family 1NET: Registered protocol family 17NET: Registered protocol family 15VFS: Mounted root (squashfs filesystem) readonly.Freeing unused kernel memory: 68k freedinit started: BusyBox v1.00 (2007.11.12-09:05+0000) multi-call binaryinit started: BusyBox v1.00 (2007.11.12-09:05+0000) multi-call binaryStarting pid 36, console /dev/ttyS0: '/etc/init.d/rcS'Algorithmics/MIPS FPU Emulator v1.5Using /nmon/nmon.konmon: module license 'unspecified' taints kernel.Button: Character device registered successfully. *** OH G997Init: txIdle set to TRUEpSdramPHY=0xA1FFFFF8, 0x2FE05 0xDEADBEEF[BCM ADSL] Firmware load : 446280 446280 LMEM=(0xFFF00000, 54108) SDRAM=(0xA1FA0000, 392164)AdslCoreHwReset: AdslOemDataAddr = 0xA1FFE458ADSL PHY version is A2pBT009a2.d18b6w_initmpi: device 0x4318 found in PCI slot 1, function 0wl: srom not detected, using main memory mapped srom info (wombo board)IPSecControl Character device registered successfully.NET: Registered protocol family 3NET: Registered protocol family 9NET: Registered protocol family 4NET: Registered protocol family 5NET: Registered protocol family 18NET: Registered protocol family 25SIOCSIFADDR: No such devicekillall: smbd: no process killedkillall: nmbd: no process killedlevel: 24ls: /var/usbmount: No such file or directoryUsing /lib/modules/2.6.8.1/kernel/drivers/usb/host/ohci-hcd.koohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)ohci_hcd: block sizes: ed 64 td 64PCI: Enabling device 0000:00:09.0 (0000 -> 0002)ohci_hcd 0000:00:09.0: OHCI Host ControllerPCI: Setting latency timer of device 0000:00:09.0 to 64ohci_hcd 0000:00:09.0: irq 20, pci mem c0155b00ohci_hcd 0000:00:09.0: new USB bus registered, assigned bus number 1hub 1-0:1.0: USB hub foundhub 1-0:1.0: 2 ports detectedUsing /lib/modules/2.6.8.1/kernel/drivers/usb/class/usblp.kousblp: falsely claims to have parameter proto_biasusbcore: registered new driver usblpdrivers/usb/class/usblp.c: v0.13: USB Printer Device Class driverStarting print_servermodprobe: module printer.o not found.modprobe: failed to load module printer.ostarting lpdsrvMounting deviceUsing /lib/modules/2.6.8.1/kernel/drivers/scsi/scsi_mod.koSCSI subsystem initializedUsing /lib/modules/2.6.8.1/kernel/drivers/scsi/sd_mod.koUsing /lib/modules/2.6.8.1/kernel/drivers/usb/storage/usb-storage.koInitializing USB Mass Storage driver..usbcore: registered new driver usb-storageUSB Mass Storage support registered.Using /lib/modules/2.6.8.1/kernel/fs/fat/fat.koUsing /lib/modules/2.6.8.1/kernel/fs/vfat/vfat.koUsing /lib/modules/2.6.8.1/kernel/fs/nls/nls_cp437.koUsing /lib/modules/2.6.8.1/kernel/fs/nls/nls_iso8859-1.kousbmgr[280]: start 0.4.8usbmgr[280]: sleep time -1 micro secName: /etc/usbmgr/usbmgr.confLoad_from_file: /etc/usbmgr/preload.confkillall: hciattach: no process killedUsing /lib/modules/krtp.kokrtp ver 2.8 softdsp-vad-multiline-wb (Nov 12 2007 10:10:08)Copyright (C) 2004 Inventel SystemesWritten 2004 by David Libault <david.libault@inventel.fr>Written 2004 by Bruce Forgues <bruce.forgues@inventel.fr>Written 2004 by Eric Humbert <eric.humbert@inventel.fr>usbmgr[282]: buffer line: remove Tusbmgr[282]: class:0x9 subclass:0x0 protocol:0x0usbmgr[282]: try /etc/usbmgr/class/09/00/00/moduleusbmgr[282]: try /etc/usbmgr/class/09/00/moduleusbmgr[282]: try /etc/usbmgr/class/09/moduleusbmgr[282]: try /etc/usbmgr/class/moduleUsing /lib/modules/bt_reset.kousbmgr[282]: USB device isn't matched the configurationUsing /lib/modules/tty_spi.koConsole is free againMDG on CS0MDG version: 1192-1, expect 1192-1MDG Current Eeprom version : 51, expect 51LOADER: Register timer for first checkLOADER: Register SIGUSR1 - rescueLOADER: Register SIGUSR2 - broadcast alertLOADER: Register SIGHUP - test serial link with handset trough chargerLOADER: Register HCI sniffer for Handset update request notificationsUsing /lib/modules/2.6.8.1/kernel/net/bluetooth/l2cap.koBluetooth: L2CAP ver 2.3Bluetooth: L2CAP socket layer initializedStarting pid 333, console /dev/ttyS0: '/nmon/linux_appl.exe'************* ERROR RECORD *************000000:00:00.000000Application NMON started after POWERON.****************** END *****************appl_init: BUILD VERIFIED with the boardname WL firmwarecode (9-5-B0G0_9-6)WARNING: Unknown Parameter Type ipintf[adsl] trace = 5 0[CWMP] NoIpTimeout must be minimum 120 s.Invalid option => Username :