+ Reply to Thread
Results 141 to 160 of 2415
[project]Port android to meizu M8
This is a discussion on [project]Port android to meizu M8 within the Meizu M8 Android forums, part of the M8 Firmware category; Hi dark13, thanks for your help, it is a bit annoying cause myself i can only find 4/5/11 pins connectors, ...
-
07-31-2009 #141Valued Member
- Join Date
- Aug 2008
- Location
- Belgium
- Posts
- 2,434
- Thanks
- 127
Thanked 189 Times in 130 PostsHi dark13,
thanks for your help,
it is a bit annoying cause myself i can only find 4/5/11 pins connectors,
and if i find an 10 pins it is allways in high quantity
i also found this :

Hybrid Mini-USB-Jack Offers Various Mating Options
Where they notice that it is aBut i even then can not find a male version.Hybrid Mini-USB-Jack
I started wondering if i opened the m8 how difficult it would be to solder a wire, but it seems to tiny, have a look :
pictures in correct order for disassembling





















Last edited by evow04; 07-31-2009 at 08:34 AM.
-
07-31-2009 #142Valued Member
- Join Date
- Aug 2008
- Location
- Belgium
- Posts
- 2,434
- Thanks
- 127
Thanked 189 Times in 130 Posts




Like you notice , connecting a wire directly on will become difficult,
so i do hope someone could find a male plug that could be soldered.
Here is what we know for sure about the meizu connector,
The upper part is the connection used by the provided usb cable by meizu and this functions to charge or connect as usb storage disk.

This means that the known pinlayout is :
1 USB VCC +5v
2 USB Data -
3 USB Data +
4 N/A
5 USB GROUND
edit,
just started to think that i am going to see if i have some old spare cables to fabricate an own cable like this guy did :

fyi : http://www.mediafire.com/download.php?1c34vcwyfzd
a full repo for the uboot 1.1.6 with support for smdk 6410Last edited by evow04; 08-03-2009 at 06:44 PM.
-
08-09-2009 #143Valued Member
- Join Date
- Aug 2008
- Location
- Belgium
- Posts
- 2,434
- Thanks
- 127
Thanked 189 Times in 130 Posts*NEWSFLASH*

So what i have done and what this means...
I found an old usb cable and usb ttl convertor.
Stripped the usb cable, tested the pins i had found after stripping.
Hooked on my multimeter, found the following voltages:
0 volt ==== ground
0,2 volt === VCC
3 volt ==== RX (on ttl side, on usb side it is TX)
0 volt ==== TX (on ttl side, on usb side it is RX)
Hooked up my 3 volt ttl convertor and connected wires,
Started with teraterm, but did not get a conenction, used DNW (comes with SMDK6410 BSP) and voila there it spits some info on my terminal.
Things ive got to do now:
*crack an other usb cable for power supply cause connecting to serial port means that the display lids up whole the time so it is draining my battery.
*find out the correct settings for the terminal.
So finally someone did really hack the m8, now we need to continu.
Who is willing to help? ;-)
edit: just found out that the correct baudrate is 115200bps,
now it gives in DNW some readable info:-)Last edited by evow04; 08-09-2009 at 08:00 PM.
-
08-09-2009 #144Valued Member
- Join Date
- Aug 2008
- Location
- Belgium
- Posts
- 2,434
- Thanks
- 127
Thanked 189 Times in 130 PostsI will make a new post, some debug output:
Code:[TSP] Pen Up ¢ ³j¢ ³j¢ ³j2òñì'Ô2jU}àU}F³ÃªÿaePÅÈõ2â§”(ó2ò1Y³È}Ý}«ºûUè걫úûóÈ8»È0ºÈ[û[ûÓÛÑ[TSP] Pen Up [TSP] Pen Up [TSP] Pen Up RilDrv: Sending cmd: AT+COPS=3,2;+COPS?;+XREG?;+CSQ<cr> 710MUX: Dispatcher::Send: -> wake up TE RilDrv: Accumulated response: <cr><lf>+CME ERROR: 11<cr><lf> RilDrv: Sending cmd: AT+COPS=3,2;+COPS?;+XREG?;+CSQ<cr> 710MUX: Dispatcher::Send: -> wake up TE RilDrv: Accumulated response: <cr><lf>+CME ERROR: 11<cr><lf> [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up [TSP] Pen Up RilDrv: Sending cmd: AT+COPS=3,2;+COPS?;+XREG?;+CSQ<cr> 710MUX: Dispatcher::Send: -> wake up TE RilDrv: Accumulated response: <cr><lf>+CME ERROR: 11<cr><lf> [TSP] Pen Up ###### Shell ######: ERROR_TYPE<Warning>: Ready Power OFF! [TSP] Pen Up Check netcard is existing or not Check netcard is existing or not ###### Shell ######: ERROR_TYPE<Warning>: Reset Email Before Shut Down! IOCTL_POWER_SET++++++++++D4++SHUT DOWN+++++++ 710MUX: CChanel - Terminate COM9: 710MUX: Chnl COM9:: -> send DISC 710MUX: Dispatcher::Send: -> wake up TE 710MUX: Chnl Ctrl: -> ParseUIH--CurCmd.bType=0xe3 710MUX: Chnl COM9:: -> modem status 0x6 710MUX: Chnl COM9:: -> rec UA/DM (0x73) 710MUX: CChanel - Terminate COM7: 710MUX: Chnl COM7:: -> send DISC 710MUX: Chnl Ctrl: -> ParseUIH--CurCmd.bType=0xe3 710MUX: Chnl Ctrl: ->MSC--1---dwCallStatus=0,g_dwRingAlertCount=2 710MUX: Chnl COM7:: -> modem status 0x6 710MUX: Chnl COM7:: -> rec UA/DM (0x73) 710MUX: CChanel - Terminate Ctrl 710MUX: Chnl Ctrl: -> send DISC 710MUX: Chnl Ctrl: -> rec UA/DM (0x73) 710MUX: Dispatcher: -> SwitchRadioOff++++m_isOk=0 710MUX: Dispatcher: -> SwitchRadioOff++++ 710MUX: Dispatcher::SwitchRadioOff.....bRet=1+++++ 710MUX: Dispatcher: ->timeout--2 710MUX: Dispatcher: -> CPOF cmd OK IOCTL_POWER_SET++++++++++D4++SHUT DOWN+++++++ 710MUX: Dispatcher: -> SwitchRadioOff++++m_isOk=0 ###### Shell ######: ERROR_TYPE<Warning>: End Close GSM OK! [MFC IOCTL_POWER_SET] newdx = 4 [OEM] ++OEMSWReset()++ ONBL2 : main ++ ++ ONBL2 : main : BML_Init ok++ [ONLD : MSG] nDev = 00 [ONLD : MSG] nMID = 0x00ec [ONLD : MSG] nDID = 0x0040 [ONLD : MSG] nVID = 0x0121 [ONLD:MSG] nNumOfBlks = 2048 [ONLD:MSG] nNumOfPlanes = 1 [ONLD:MSG] nBlksInRsv = 40 [ONLD:MSG] nBadPos = 0 [ONLD:MSG] nLsnPos = 2 [ONLD:MSG] nECCPos = 8 [ONLD:MSG] nBWidth = 1 [ONLD:MSG] nMEFlag = 1 [ONLD:MSG] nLKFlag = 0 [BBM: ] << DevNO:0 MAPPING INFORMATION >> [BBM: ] Bad Mark Information [BBM: ] - Bad Mark (0x22) by write error [BBM: ] - Bad Mark (0x11) by erase error [BBM: ] pstDev->n1stSbnOfULArea = 0 [BBM: ] 000: Sbn[ 33] ==> Rbn[2006] / UnLocked / BadMark:0x00 [BBM: ] 001: Sbn[ 241] ==> Rbn[2007] / UnLocked / BadMark:0x00 [BBM: ] 002: Sbn[1152] ==> Rbn[2008] / UnLocked / BadMark:0x00 [BBM: ] 003: Sbn[1528] ==> Rbn[2009] / UnLocked / BadMark:0x00 [BBM: ] << Total : 4 BAD-MAPPING INFORMATION >> ++ ONBL2 : main : BML_Open ok++ Press [SPACE] to enter EBOOT within 2 sec. ++ Shadow Eboot ++ _ReadImage, nStartVsn=256, nNumOfScts=1024, nSrcAddr=80030000 -- Shadow Eboot -- LaunchAddr=0x80030000 PhysicalJump=0x50030000 Microsoft Windows CE Bootloader Common Library Version 1.4 Built Mar 21 2009 11:06:07 Microsoft Windows CE Bootloader for the Samsung SMDK6410 Version 2.4 Built Mar 21 2009 [EBOOT: IN] ++PocketStoreInitialize() [EBOOT: ] BML_Init success [EBOOT: IN] ++_SetXSRPI POCKETSTORE15 [ONLD : MSG] nDev = 00 [ONLD : MSG] nMID = 0x00ec [ONLD : MSG] nDID = 0x0040 [ONLD : MSG] nVID = 0x0121 [ONLD:MSG] nNumOfBlks = 2048 [ONLD:MSG] nNumOfPlanes = 1 [ONLD:MSG] nBlksInRsv = 40 [ONLD:MSG] nBadPos = 0 [ONLD:MSG] nLsnPos = 2 [ONLD:MSG] nECCPos = 8 [ONLD:MSG] nBWidth = 1 [ONLD:MSG] nMEFlag = 1 [ONLD:MSG] nLKFlag = 0 [BBM: ] << DevNO:0 MAPPING INFORMATION >> [BBM: ] Bad Mark Information [BBM: ] - Bad Mark (0x22) by write error [BBM: ] - Bad Mark (0x11) by erase error [BBM: ] pstDev->n1stSbnOfULArea = 0 [BBM: ] 000: Sbn[ 33] ==> Rbn[2006] / UnLocked / BadMark:0x00 [BBM: ] 001: Sbn[ 241] ==> Rbn[2007] / UnLocked / BadMark:0x00 [BBM: ] 002: Sbn[1152] ==> Rbn[2008] / UnLocked / BadMark:0x00 [BBM: ] 003: Sbn[1528] ==> Rbn[2009] / UnLocked / BadMark:0x00 [BBM: ] << Total : 4 BAD-MAPPING INFORMATION >> [EBOOT: ] Vol 0 is Opened [EBOOT: ] PocketStoreInitialize success +OALArgsInit() Arguments area has some values -OALArgsInit() [Eboot] ++InitializeDisplay() [Eboot] --InitializeDisplay() INFO: (unsigned)C_IsrHandler : 0x80049260 INFO: (unsigned)ASM_IsrHandler : 0x80049C00 INFO: (unsigned)pISR : 0xEA0126F8 BP_Init BP_Init++ BP_Init] pMemory=0xa00c0000 BP_Init] g_pbMBRSector=0xa00c0000 BP_Init] g_pbBlock=0xa00c0200 BP_Init] g_pSectorInfoBuf=0xa00e0200 BP_Init-- wNUM_BLOCKS : 1152(0x480) .Press [ENTER] to download image stored on boot media, or [SPACE] to enter boot monitor. Initiating image download in 2 seconds. Starting auto-download ... ++ShadowNK() Windows CE Kernel for ARM (Thumb Enabled) Built on Jan 21 2009 at 18:02:34 [OAL] ++OEMInit() [OAL] HCLK : 133000000 [OAL] PCLK : 33250000 [OAL] CE:6.0 miniOne:0.9.1.10 M8:1.0.0.0 [OAL] InitializeGPIO() [OAL] InitializeCLKSource() [OAL] InitializeCLKGating() [OAL] InitializeBlockPower() DCache: 128 sets, 4 ways, 32 line size, 16384 size ICache: 128 sets, 4 ways, 32 line size, 16384 size +OALArgsInit() Arguments area has some values -OALArgsInit() +OALTimerInit( 1, 16624, 0 ) -OALIntrRequestSysIntr(irq = 38, sysIntr = 16) [OAL] --OEMInit() [OEMIO:INF] + IOCTL_HAL_POSTINIT [OEMIO:INF] - IOCTL_HAL_POSTINIT OEMSetRealTime(2009/8/9 22:1:22.000) [HALWP:INF] nCtrlCode = PS_HAL_BML_INIT [HALWP:INF] nCtrlCode = PS_HAL_BML_OPEN [HALWP:INF] nVol = 0 [ONLD : MSG] nDev = 00 [ONLD : MSG] nMID = 0x00ec [ONLD : MSG] nDID = 0x0040 [ONLD : MSG] nVID = 0x0121 [ONLD:MSG] nNumOfBlks = 2048 [ONLD:MSG] nNumOfPlanes = 1 [ONLD:MSG] nBlksInRsv = 40 [ONLD:MSG] nBadPos = 0 [ONLD:MSG] nLsnPos = 2 [ONLD:MSG] nECCPos = 8 [ONLD:MSG] nBWidth = 1 [ONLD:MSG] nMEFlag = 1 [ONLD:MSG] nLKFlag = 0 [BBM: ] << DevNO:0 MAPPING INFORMATION >> [BBM: ] Bad Mark Information [BBM: ] - Bad Mark (0x22) by write error [BBM: ] - Bad Mark (0x11) by erase error [BBM: ] pstDev->n1stSbnOfULArea = 0 [BBM: ] 000: Sbn[ 33] ==> Rbn[2006] / UnLocked / BadMark:0x00 [BBM: ] 001: Sbn[ 241] ==> Rbn[2007] / UnLocked / BadMark:0x00 [BBM: ] 002: Sbn[1152] ==> Rbn[2008] / UnLocked / BadMark:0x00 [BBM: ] 003: Sbn[1528] ==> Rbn[2009] / UnLocked / BadMark:0x00 [BBM: ] << Total : 4 BAD-MAPPING INFORMATION >> BIBDRV_PS:GetProfileName - Profile = SMFlash, length = 16 [HALWP:INF] nCtrlCode = PS_HAL_BML_INIT [BIF:WRN] BML_Init is already called [OND:MSG] GetBmlId - BmlPartitionId = 8 [OND:MSG] GetBmlId - BmlVolumeId = 0 [HALWP:INF] nCtrlCode = PS_HAL_BML_OPEN [HALWP:INF] nVol = 0 [OND:INF] otp uid(0~7) 0xec, 0x0, 0xe4, 0x90, 0x26, 0xe9, 0x32, 0x37 [OND:INF] otp uid(8~15) 0x33, 0x30, 0x31, 0x37, 0x18, 0x18, 0xb, 0x8 [OAL] Not Clear Storage [OAL] Not Clear System Hive [OAL] Not Clear User Hive [OAL] Not Clear System Hive -OALIntrRequestSysIntr(irq = 43, sysIntr = 18) DEBUG: CreateSerialObject 0 -OALIntrRequestSysIntr(irq = 61, sysIntr = 19) WARN: OALIoCtlHalGetHWEntropy: Buffer too small -OALIntrRequestSysIntr(irq = 1, sysIntr = 20) -OALIntrRequestSysIntr(irq = 2, sysIntr = 21) -OALIntrRequestSysIntr(irq = 3, sysIntr = 22) -OALIntrRequestSysIntr(irq = 4, sysIntr = 23) -OALIntrRequestSysIntr(irq = 5, sysIntr = 24) -OALIntrRequestSysIntr(irq = 7, sysIntr = 25) -OALIntrRequestSysIntr(irq = 9, sysIntr = 26) -OALIntrRequestSysIntr(irq = 40, sysIntr = 27) -OALIntrRequestSysIntr(irq = 19, sysIntr = 28) -OALIntrRequestSysIntr(irq = 23, sysIntr = 29) -OALIntrRequestSysIntr(irq = 20, sysIntr = 30) ...........Mux07_10 Driver Attach+++++++++++++++ 710MUX: Chnl COM7:: -> Init 710MUX: CDispatcher - Init 710MUX: CDispatcher - Init open underlying COM port 710MUX: Dispatcher: ->m_hComPort = CreateFile-m_hComPort=-1- 710MUX: Dispatcher: ->m_GetCommState--- 710MUX: Dispatcher: ->SGOLD_RIL_DRIVER--- 710MUX: Dispatcher: -> Switch radio on--- 710MUX: Dispatcher: -> SwitchRadioOn 710MUX: Dispatcher: -> SwitchRadioOn 710MUX: Dispatcher: -> AT+IPR=230400--- 710MUX: Dispatcher: -> AT+XPOW=4,2000,0--- 710MUX: Dispatcher::Init -> SLEEP(xxx) -> TO BE DELETED WHEN SABM BUG WILL BE FIXED 710MUX: CDispatcher - Init open underlying COM port OK 710MUX: Chnl Ctrl: -> Init 710MUX: CDispatcher::Register: chanel Ctrl, dlci 0 710MUX: Chnl Ctrl: -> send SABM 710MUX: Chnl Ctrl: -> rec UA/DM (0x73) 710MUX: Chnl Ctrl: -> Init OK 710MUX: CDispatcher::Register: chanel COM7:, dlci 1 710MUX: Chnl COM7:: -> send SABM 710MUX: Chnl COM7:: -> rec UA/DM (0x73) 710MUX: Chnl Ctrl: -> ParseUIH--CurCmd.bType=0xe3 710MUX: Chnl Ctrl: ->MSC--1 710MUX: Chnl Ctrl: ->MSC--1---dwCallStatus=0,g_dwRingAlertCount=1 710MUX: Chnl COM7:: -> modem status 0xc 710MUX: Chnl COM7:: -> Init OK 710MUX: Chnl COM7:: -> sending modem status 0x8c 710MUX: DLCI 1: -> Send modem status 0x8c 710MUX: Chnl Ctrl: -> TE answer 0xe0 710MUX: Chnl Ctrl: -> got modem status rsp
-
08-09-2009 #145Valued Member
- Join Date
- Aug 2008
- Location
- Belgium
- Posts
- 2,434
- Thanks
- 127
Thanked 189 Times in 130 PostsCode:710MUX: Chnl COM9:: -> Init 710MUX: CDispatcher::Register: chanel COM9:, dlci 2 710MUX: Chnl COM9:: -> send SABM 710MUX: Chnl Ctrl: -> ParseUIH--CurCmd.bType=0xe3 710MUX: Chnl COM9:: -> modem status 0xc 710MUX: Chnl COM9:: -> rec UA/DM (0x73) 710MUX: Chnl COM9:: -> Init OK 710MUX: Chnl COM9:: -> sending modem status 0x8c 710MUX: DLCI 2: -> Send modem status 0x8c 710MUX: Chnl Ctrl: -> TE answer 0xe0 710MUX: Chnl Ctrl: -> got modem status rsp 710MUX: Chnl COM7:: -> sending modem status 0x8c 710MUX: DLCI 1: -> Send modem status 0x8c 710MUX: Chnl Ctrl: -> TE answer 0xe0 710MUX: Chnl Ctrl: -> got modem status rsp 710MUX: Chnl COM7:: -> sending modem status 0x8c 710MUX: DLCI 1: -> Send modem status 0x8c 710MUX: Chnl Ctrl: -> TE answer 0xe0 710MUX: Chnl Ctrl: -> got modem status rsp -OALIntrRequestSysIntr(irq = 88, sysIntr = 31) -OALIntrRequestSysIntr(irq = 15, sysIntr = 32) RilDrv: Sending cmd: ATZS0=0E0Q0V1X4&C1&D1<cr> RilDrv: Accumulated response: ATZS0=0E0Q0V1X4&C1&D1<cr> RilDrv: Accumulated response: ATZS0=0E0Q0V1X4&C1&D1<cr><cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CFUN?<cr> RilDrv: Accumulated response: <cr><lf>+CFUN: 1,0<cr><lf> RilDrv: Accumulated response: <cr><lf>+CFUN: 1,0<cr><lf><cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CGACT?<cr> RilDrv: Accumulated response: <cr><lf>ERROR<cr><lf> RilDrv: Sending cmd: AT+CLCC<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CFUN=4<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> [WAV:MSG] HeadPhoneStatusChange() 0 [WAV:ERR] Initialize() : HeadPhoneStatus Event Already Exist -OALIntrRequestSysIntr(irq = 73, sysIntr = 33) -OALIntrRequestSysIntr(irq = 74, sysIntr = 34) -OALIntrRequestSysIntr(irq = 42, sysIntr = 35) [HSMMC1] Initializing the HSMMC Host Controller -OALIntrRequestSysIntr(irq = 95, sysIntr = 36) [HSMMC1] Turn ON the F/B delay control. [HSMMC1] Card is Inserted! [HSMMC1] SetVotage ++ [HSMMC1] SetVotage 11 [HSMMC1] SetVotage 22 [HSMMC1] SetVotage 33 [HSMMC1] SetVotage -- [HSMMC1] Turn ON the F/B delay control. [HSMMC1] Setting for 1 bit mode , Clock Rate = 100000 Hz [HSMMC1] Turn ON the F/B delay control. ERR CMD:5 : CMD Timeout Error... ERR CMD:8 : CMD Timeout Error... [HSMMC1] SetVotage ++ [HSMMC1] SetVotage 11 [HSMMC1] SetVotage 22 [HSMMC1] SetVotage 33 [HSMMC1] SetVotage -- ERR CMD:8 : CMD Timeout Error... [MARVELL-WIFI]:INIT - Enter DriverEntry [MARVELL-WIFI]:*** Driver [SDBUS] MMC Spec Version : 4.0/4.1/4.2 version 50.p10 *** [MARVELL-WIFI]:*** Built on Jul 23 2009 14:10:11 *** [SDBUS] HSMMC card in HSMMC slot [SDBUS] This HSMMC card supports up to 52Mhz [HSMMC1] Setting for 8 bit mode , Clock Rate = 52000000 Hz [HSMMC1] Turn ON the F/B delay control. [SDBUS] This MMC Card must be Normal MMCPlus. [SDBUS] MMC Spec Version : >=4.2 [SDMEM] This MMC card is on SPEC42. [UFNPDD] USB MSF Function Class Enabled MMC : 3, SD : 3, SDHC : 3, FLASH : 3 [UFNPDD] SD or SDHC or MMC is mass storage device [USB] dii.dwIrq = 96 -OALIntrRequestSysIntr(irq = 96, sysIntr = 37) [UFNPDD] SetEvent: PlugEvent_ Cable not Connected [OTG:ERR] Initialize() : m_hUSBDetectInterrupt Event Already Exist 0x045F0003 Current Client "Mass_Storage_Class" [UFNPDD] USB MSF Function Class Enabled tag 2008-09-03... [A2DP] HardwareContext::Init..... [A2DP] GetInterruptThreadPriority 97 [A2DP] Open key successfully. We got dwPrio 97 [A2DP] GetInterruptThreadPriority return 97 [A2dp] Set audio rendering thread pri successully [A2DP] GetInterruptThreadPriority 97 [A2DP] Open key successfully. We got dwPrio 97 [A2DP] GetInterruptThreadPriority return 97 [A2dp] Set audio writing thread pri successully [A2DP] SetToLocalDefaultValuesConfiguration...................... A2DP :: PrintCodecCaps() : printing raw codec capabilities A2DP :: Byte 0 : [0x22] A2DP :: Byte 1 : [0x15] A2DP :: Byte 2 : [0x50] A2DP :: Byte 3 : [0x50] A2DP :: PrintCodecCaps() : translated codec capabilities A2DP :: PrintCodecCaps() : supports STEREO A2DP :: PrintCodecCaps() : supports Sampling Frequency 44.1kHz A2DP :: PrintCodecCaps() : supports Alocation Method Loudness A2DP :: PrintCodecCaps() : supports # Subbands [8] A2DP :: PrintCodecCaps() : supports # BlockLen [16] A2DP :: PrintCodecCaps() : min bitpool value [80] A2DP :: PrintCodecCaps() : max bitpool value [80] [A2DP] SetToLocalDefaultValuesConfiguration...................... A2DP :: PrintCodecCaps() : printing raw codec capabilities A2DP :: Byte 0 : [0x22] A2DP :: Byte 1 : [0x15] A2DP :: Byte 2 : [0x50] A2DP :: Byte 3 : [0x50] A2DP :: PrintCodecCaps() : translated codec capabilities A2DP :: PrintCodecCaps() : supports STEREO A2DP :: PrintCodecCaps() : supports Sampling Frequency 44.1kHz A2DP :: PrintCodecCaps() : supports Alocation Method Loudness A2DP :: PrintCodecCaps() : supports # Subbands [8] A2DP :: PrintCodecCaps() : supports # BlockLen [16] A2DP :: PrintCodecCaps() : min bitpool value [80] A2DP :: PrintCodecCaps() : max bitpool value [80] [A2DP] HardwareContext::Init return.... DEBUG: CreateSerialObject 1 -OALIntrRequestSysIntr(irq = 62, sysIntr = 38) -OALIntrRequestSysIntr(irq = 13, sysIntr = 39) -OALIntrRequestSysIntr(irq = 14, sysIntr = 40) [MFC POWER] Power is up. [MFC POWER] Power is down-OALIntrRequestSysIntr(irq = 26, sysIntr = 41) MFC Interrupt has been initialized. [MFC IOCTL_POWER_CAPABILITIES] [MFC IOCTL_POWER_CAPABILITIES] leaving... [MFC POWER] Power is up. [MFC POWER] Power is down[Acc driver] ACC DLL_PROCESS_ATTACH.... [Acc driver] ACC_Init++.... [Acc driver] ACC init successfully.... +TCH_Init [FIMGDRV] InitDriver [FIMGDRV] Alloc Block Num = 8 Alloc Block Size = 0x200000 [FIMGDRV] alloc physmem = 159707136 / 180318208 [FIMGDRV] alloc virtmem = 1073676288/1073741824 [FIMGDRV] alloc physmem = 142909440 / 180318208 [FIMGDRV] alloc virtmem = 1073676288/1073741824 [FIMGDRV] Allocated Pool 0xd3a40000 0x52b25000 0x0 [FIMGDRV] Allocated Pool 0xd3c40000 0x52d25000 0x0 [FIMGDRV] Allocated Pool 0xd3e40000 0x52f26000 0x0 [FIMGDRV] Allocated Pool 0xd4040000 0x53126000 0x0 [FIMGDRV] Allocated Pool 0xd4240000 0x53327000 0x0 [FIMGDRV] Allocated Pool 0xd4440000 0x53527000 0x0 [FIMGDRV] Allocated Pool 0xd4640000 0x53728000 0x0 [FIMGDRV] Allocated Pool 0xd4840000 0x53928000 0x0 -OALIntrRequestSysIntr(irq = 18, sysIntr = 42) [FIMGDRV:0xffff0000] driver is closed *** FIMG VERSION : 0x1050000 *** [FIMGDRV:0xd3047b00] driver is opened [FIMGDRV:0xd3047b00] driver is closed [FIMGDRV:0xd3047b00] Garbage Collect -OALIntrRequestSysIntr(irq = 21, sysIntr = 43) [TSP:] Manufacture - Snaptics_TM1195 -OALIntrRequestSysIntr(irq = 45, sysIntr = 44) [TSP:INF] DdsiTouchPanelEnable() : gIntrTouch = 44 [TSP:INF] DdsiTouchPanelEnable() : gIntrTouchChanged = 0 [TSP:INF] TSP_PowerOn() : Exit Deep Sleep Mode. [TSP:INF] TSP_PowerOn() : S/W Reset TSP ... [TSP:INF] TSP_PowerOn() : Enable TSP Interrupt ... [TSP] Pen Up CreateFile ::\windows\CellCore.dll CreateFile ::\windows\CellCore.dll CreateFile ::\windows\CellCore.dll [UFNPDD] PostUsbNotifyMsg : No Window Message Registered!!! ("BTAGSVC: Initializing Audio Gateway Service.\n")("BTAGSVC: Starting Audio Gateway Service.\n")BTAGSVC: AG Engine is being initialized. RilDrv: Sending cmd: AT+CFUN?<cr> 710MUX: Dispatcher::Send: -> wake up TE RilDrv: Accumulated response: <cr><lf>+CFUN: 4,0<cr><lf> RilDrv: Accumulated response: <cr><lf>+CFUN: 4,0<cr><lf><cr><lf>OK<cr><lf> BTAGSVC: OnServiceCallback: 1 ("BTAGSVC: Audio Gateway Service started successfully.\n")("BTAGSVC: ++ListenThread_Int\n")("BTAGSVC: Successfully added SDP record.\n")("BTAGSVC: Successfully added SDP record.\n")("BTAGSVC: Setting SO_BTH_AUTHENTICATE on server socket.\n")("BTAGSVC: ++SCOListenThread_Int\n")[BTSVC] Service thread start...... RilDrv: Sending cmd: AT+CPIN RilDrv: Accumulated response: <cr><lf>+CPIN: SIM PIN<cr><lf> RilDrv: Accumulated response: <cr><lf>+CPIN: SIM PIN<cr><lf><cr><lf>OK<cr><lf> Load_Ril_Func+++++++++ CallInterface::Dial_Init().....Ril_Initialize successfully......... RilDrv: Sending cmd: AT+CFUN?<cr> RilDrv: Accumulated response: <cr><lf>+CFUN: 4,0<cr><lf> RilDrv: Accumulated response: <cr><lf>+CFUN: 4,0<cr><lf><cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CPIN RilDrv: Accumulated response: <cr><lf>+CPIN: SIM PIN<cr><lf> RilDrv: Accumulated response: <cr><lf>+CPIN: SIM PIN<cr><lf><cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CFUN?<cr> RilDrv: Accumulated response: <cr><lf>+CFUN: 4,0<cr><lf> RilDrv: Accumulated response: <cr><lf>+CFUN: 4,0<cr><lf><cr><lf>OK<cr><lf> Load_Ril_Func+++++++++ CallInterface::Dial_Init().....Ril_Initialize successfully......... CTapiConnection::AddRequest .....pReq=220d00,dwRequestID=11,functype=0
-
08-09-2009 #146Valued Member
- Join Date
- Aug 2008
- Location
- Belgium
- Posts
- 2,434
- Thanks
- 127
Thanked 189 Times in 130 PostsSo thats the whole boot debug message,Code:RilDrv: Sending cmd: AT+XPINCNT<cr> RilDrv: Accumulated response: <cr><lf>+XPINCNT: 3,3,10,10<cr><lf> RilDrv: Accumulated response: <cr><lf>+XPINCNT: 3,3,10,10<cr><lf><cr><lf>OK<cr><lf> CallInterface:ResultCallBack .........dwCode = 0x1,hrCmdID=0xb.. CallInterface:ResultCallBack ..end... CallInterface::GetResult exit&&&&&&&&&&&&&&&&&&&&&&& CTapiConnection::DeleteRequests .....pReq=220d00,dwRequestID=11,funcType=23 CConnectManagerApp........ Load_Ril_Func+++++++++ CallInterface::Dial_Init().....Ril_Initialize successfully......... RilDrv: Sending cmd: AT+CPIN RilDrv: Accumulated response: <cr><lf>+CPIN: SIM PIN<cr><lf> RilDrv: Accumulated response: <cr><lf>+CPIN: SIM PIN<cr><lf><cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CFUN?<cr> RilDrv: Accumulated response: <cr><lf>+CFUN: 4,0<cr><lf> RilDrv: Accumulated response: <cr><lf>+CFUN: 4,0<cr><lf><cr><lf>OK<cr><lf> CTapiConnection::AddRequest .....pReq=220220,dwRequestID=15,functype=0 RilDrv: Sending cmd: AT+CFUN=1<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: ATZS0=0E0Q0V1X4&C1&D1<cr> CallInterface:ResultCallBack .........dwCode = 0x1,hrCmdID=0xf.RilDrv: Accumulated response: <cr><lf>OK<cr><lf> . CallInterface:ResultCallBack ..end... CallInterface::RIL_NOTIFY_RADIOEQUIPMENTSTATCallInterface::GetResult exit&&&&&&&&&&&&&&&&&&&&&&& CTapiConnection::DeleteRequests .....pReq=220220,dwRequestID=15,funcType=9 ECHANGED******************** CallInterface::RIL_NOTIFY_RADIOEQUIPMENTSTATECHANGED******************** CallInterface::RIL_NOTIFY_RADIOEQUIPMENTSTATECHANGED*****dwEqState=2****** RilDrv: Sending cmd: AT+CMEE=1;+CRC=1;+CR=1;+CMOD=0<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CREG=1<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CMGF=0<cr> RilDrv: Accumulated response: <cr><lf>+CME ERROR: 11<cr><lf> RilDrv: Sending cmd: AT+CSMS=1<cr> RilDrv: Accumulated response: <cr><lf>+CME ERROR: 11<cr><lf> RilDrv: Sending cmd: AT+XMER=0<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CMER=1,1,0,2,1<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Accumulated response: <cr><lf>+CIEV: 1,3<cr><lf> RILDrv : i : ParseIndicatorEvent : Unhandled indicator event 1 RilDrv: Sending cmd: AT+XCALLSTAT=1<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+FCLASS=0<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CSSN=1,1<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CMUT=0<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CLVL=40<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CGEREP=2,1<cr> RilDrv: Accumulated response: <cr><lf>+CME ERROR: 11<cr><lf> RilDrv: Sending cmd: AT+XSIMSTATE=1<cr> RilDrv: Accumulated response: <cr><lf>+XSIM: 1<cr><lf> RilDrv: Accumulated response: <cr><lf>+XLOCK: <cr><lf><cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+TRACE=0<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+XPROGRESS=1<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CSCS="HEX"<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CLIP=1<cr> RilDrv: Accumulated response: <cr><lf>+CME ERROR: 11<cr><lf> RilDrv: Sending cmd: AT+CLIR=0<cr> RilDrv: Accumulated response: <cr><lf>+CME ERROR: 11<cr><lf> RilDrv: Sending cmd: AT<cr> RilDrv: Accumulated response: <cr><lf>OK<cr><lf> RilDrv: Sending cmd: AT+CPIN CallInterface::RIL_NOTIFY_RADIOEQUIPMENTSTATECHANGRilDrv: Accumulated response: <cr><lf>+CPIN: SIM PIN<cr><lf> RilDrv: Accumulated response: <cr><lf>+CPIN: SIM PIN<cr><lf><cr><lf>OK<cr><lf> ED******************** RilDrv: Sending cmd: AT+CFUN?<cr> CallInterface::RIL_NOTIFY_RADIOEQUIPMENTSTATECRilDrv: Accumulated response: <cr><lf>+CFUN: 1,0<cr><lf> RilDrv: Accumulated response: <cr><lf>+CFUN: 1,0<cr><lf><cr><lf>OK<cr><lf> HANGED******************** RilDrv: Sending cmd: AT+COPS=3,2;+COPS?;+XREG?;+CSQ<cr> RilDrv: Accumulated response: <cr><lf>+CME ERROR: 11<cr><lf> RilDrv: Sending cmd: AT+COPS=3,2;+COPS?;+XREG?;+CSQ<cr> 710MUX: Dispatcher::Send: -> wake up TE RilDrv: Accumulated response: <cr><lf>+CME ERROR: 11<cr><lf> RilDrv: Sending cmd: AT+COPS=3,2;+COPS?;+XREG?;+CSQ<cr> 710MUX: Dispatcher::Send: -> wake up TE RilDrv: Accumulated response: <cr><lf>+CME ERROR: 11<cr><lf> RilDrv: Sending cmd: AT+COPS=3,2;+COPS?;+XREG?;+CSQ<cr> 710MUX: Dispatcher::Send: -> wake up TE RilDrv: Accumulated response: <cr><lf>+CME ERROR: 11<cr><lf>
as you will notice while reading we can actually enter eboot to flash the whole device..
SO I NEED SOME HELP OF YOU GUYS
-
08-09-2009 #147Administrator
- Join Date
- Mar 2007
- Location
- Budapest, Hungary
- Posts
- 4,601
- Thanks
- 245
Thanked 1,049 Times in 391 PostsSeems that you're going in the right direction! I'd love to be able to help out, but this is like chinese for me
-
08-10-2009 #148Dutch Moderator
- Join Date
- Jan 2009
- Location
- The Netherlands
- Posts
- 1,589
- Thanks
- 117
Thanked 173 Times in 72 PostsMe to N2KU!

I am more a hardware guy.....
Ben je Nederlands?
Dan kan je ook gewoon in de Nederlandse sectie reageren en vragen: http://www.meizume.com/dutch
-
08-10-2009 #149
it seems that your error comes when this command is sent:
What this means i have no idea, but in my mind it could possibly be a incorrect value being sent.Code:RilDrv: Sending cmd: AT+CLIP=1<cr>
-
08-10-2009 #150Valued Member
- Join Date
- Aug 2008
- Location
- Belgium
- Posts
- 2,434
- Thanks
- 127
Thanked 189 Times in 130 PostsHi there guys,
Beeing honest i can get allmost everything done on hardware level,
the same for software if i know it ofcourse otherwise it could take some time.
And from here on, i do have no experiences so i guess we are on the same level.
The fact we can communicate with m8 on debug level means that full custom rom and bootloader for wince can be implemented.
Aswell as custom build bootloaders for android.
So best thing we can do from here is having a look on the uboot,
for example how they created dualboot fo smartq 5.
Implementing this would be very nice cause then an android kernel is not much more work.
So if you are willing to help you can try and help researching on how to develop uboot for m8:-)
An other thing you can help me is by testing what happens if you overwrite the original bootloader with qsmartq 5 bootloader i previuosly mentioned.
Are you guys interested in an how to with pictures on the serial port connection?
btw, this serial port has 1 downside: i still do not know where tv out is located
thanks for reply
-
08-10-2009 #151Member
- Join Date
- Nov 2008
- Location
- Germany
- Posts
- 152
- Thanks
- 8
Thanked 12 Times in 8 Postsbut i think there is a big risk to play with the bootloader, or not?
-
08-10-2009 #152Valued Member
- Join Date
- Aug 2008
- Location
- Belgium
- Posts
- 2,434
- Thanks
- 127
Thanked 189 Times in 130 PostsHow do you mean with my error?
raangu,
not sure, did not test it and have no experiences on to this stuff..
But i most say that i am thinking that an extra m8 for such test purposes could be very usefull, but i am not willing to buy one completly on my own expenses so i was thinking maybe we could create a donation for such developer device, or we should be able to find some cheap broken devices?
On the other hand, if i got some time i will see in the eboot menu if i can backup the original one first then there is no risk cause like mentioned in the debug log, meizu uses the original eboot that is been delivered with the smdk6410 bsp. (or some one else could have a look)
I also would like to mention that the tools and manuals i launched in the wince bsp topic, are 100 pct accurate, so following the howto pdf can inform us on how to proceed.
I will make some time this evening to shoot some pictures on how to make the cable.
shall i create just 1 new topic for serial connection, or do i post here? cause it belongs to android aswell to windows ce development.
-
08-10-2009 #153Member
- Join Date
- Nov 2008
- Location
- Germany
- Posts
- 152
- Thanks
- 8
Thanked 12 Times in 8 Postsi think a new thread would be good
-
08-10-2009 #154Valued Member
- Join Date
- Aug 2008
- Location
- Belgium
- Posts
- 2,434
- Thanks
- 127
Thanked 189 Times in 130 Postsok,
like you noticed, i created a seperated topic on this debugging :
[How-To] Serial debug connection
So for the connection cable we can continu there.
This to let us been able to focus here on android.
So what we need here:
*a backup of original eboot bootloader by meizu
*an uboot version (bootloader)
*an android kernel (we can use that one from smartq5 , booting with haret provided the least errors so i guess it will pretty much work)
Who is willing to help on the uboot part, by helping developping or testing?
(even if you do not have experiences on this , it does not matther, cause on my own it willtake ages)
-
08-10-2009 #155
I want to help/test
-
08-11-2009 #156Valued Member
- Join Date
- Aug 2008
- Location
- Belgium
- Posts
- 2,434
- Thanks
- 127
Thanked 189 Times in 130 Posts
-
08-11-2009 #157Valued Member
- Join Date
- Aug 2008
- Location
- Belgium
- Posts
- 2,434
- Thanks
- 127
Thanked 189 Times in 130 Postscrap i got stuck

I am not sure if it is a problem with a too long coperwire to connect my ttl with usb or my ttl convertor itself,
but booting m8 it gives :
andCode:Press [SPACE] to enter EBOOT within 2 sec
when i push space in terminal or dnw it does not respond on the commandCode:Press [ENTER] to download image stored on boot media, or [SPACE] to enter boot monitor

So i got stuck and i can not check wether i could download the bootloader flash or play some more with it.
I see a led flashing on my ttl that i Tx files to m8 when providing commands but nothing seems to reach it ,
so i do hope someone played around aswell with a custom build debug cable just to know if the m8 receives commands.
Could anyone confirm this (i really do hope i am not the only one playing around)
If no one confirms i will try in a few days to downgrade to older firmware to make sure it is not a security setting in m8 firmware or so, or i will rebuild my debug cable.
serial debuging is not something i have a lot of knowledge on :s so i hope i will get past this issue soon, cause receiving debug messagges from m8 goes fluid and without any issues.
thanks
-
08-12-2009 #158
I dont think a too long wire would be the problem, the voltage lost is minimal, unless your using a 200meter long wire.
I would rather use a multimeter to tjek for a broken connection.
-
08-12-2009 #159Valued Member
- Join Date
- Aug 2008
- Location
- Belgium
- Posts
- 2,434
- Thanks
- 127
Thanked 189 Times in 130 Posts
how stupid of me that i did not check it

I will test it and notify if it solves my issue.
I would expect that, but the voltage levels are pretty low (0.1-3 voltage)
so if one of my connections is not working properly it could screw everything up
But before i can improve my cabling/ttl i will need time to get a now soldering iron, cables etc.
it could take lots of time cause the clossest shop quited selling those stuff due crisis
and i will need to find a new one who hopely can get his hands on a 10 pins usb connector too;-)
-
08-12-2009 #160Member
- Join Date
- Nov 2008
- Location
- Germany
- Posts
- 152
- Thanks
- 8
Thanked 12 Times in 8 Postsi'm not sure, but i think in one firmware release, an eboot was in there...
yesterday i read the tutorial to create a wince rom... i think it's not that difficult, the only thing you need is the wince installer / license for windows to create the rom with visual studio... via msdnaa i only get "wince 4.2 .net" or something like this... 6cds... i will look around these days and if i get all the stuff i need, i will try to do it
edit: maybe i can provide the wince rom if i am able to compile it
Similar Threads
-
PROJECT: Meizu M8 Nederlandse taal
By MaikelRunia in forum DutchReplies: 47Last Post: 09-02-2009, 10:11 AM -
Port Meizu OS to Samsung Omnia i900
By natedogg20050 in forum Modding & DevelopmentReplies: 8Last Post: 08-17-2009, 12:09 PM -
What does the Meizu Rockbox project need?
By Err0r in forum RockboxReplies: 21Last Post: 05-17-2008, 12:12 PM -
Meizu M8 Project On Temporary Hold
By Err0r in forum Meizu M8 NewsReplies: 68Last Post: 04-20-2008, 04:02 AM -
The USB port
By vipert in forum TechnicalReplies: 3Last Post: 05-03-2007, 04:03 PM



Reply With Quote

