case 2810925 Date 03/29/2013 12:00 pm customer UPS Device MC65 with Custom RS507 cab file and CRD5501 Ethernet Cradle OS 2.41.400 issue is device not waking from suspend reproduction steps below Nick Ford captured logs , need assistance analyzing them issue needs to be resolved before 4/12/13. as per TA
We did some further testing at UPS today.
When putting the MC65 into the CRD5501 cradle it does get a IP address.
10.246.215.149
255.255.255.0 is subnet mask.
The Ethernet cable is plugged into Port2 on the rear of the CRD5501-4000ER. This is the port that shows the light on the front.
FYI – Testing a clean unit set up to our instructions, we have not been able to reproduce the issue without the Ethernet cable connected. So the Ethernet needs to be attached.
UPS is planning to test with cable plugged into Port1 and will update us.
In our testing today we have reproduced the issue 3 times and have eMscript logs for the failures.
We took removed the eMscript logs after each cold boot following the failure. We then cold booted the device again after file transfer in USB cradle prior to starting the test again.
Device Time of failure
Number of tries to reproduce
eMscript logs
6:17
15
eMscript_917
6:30
2
eMscript_930
6:38
6
eMscript_938
The above logs are continuous, so look toward the end of each of the logs for the last suspend and resume prior to the incident and cold boot.
This is the reproduction steps. All duplication has been done at customer site so far. I have not been able to duplicate here.
Re-flash MC65 w/BSP41 02.41.0400 Turn phone radio off
Install RS507 CAB file (MC65_RS507_Support_Beeping_RC3.cab )in the application folder
Run CAB file – Installed to device
Perform cold boot - 1-9-power
Connect Power and Ethernet to the CRD5501-4000ER cradle.
No other MC65s are in the cradle.
With the MC65 on the home screen, insert the MC65 into the cradle. Wait 5 seconds (tried range from 5 to 10 seconds)
Remove the MC65 from the cradle.
Wait at least 2 seconds. (tried range from 2 to 10 seconds)
Press the power button to suspend the MC65
Wait at least 2 seconds. (tried range from 2 to 10 seconds)
Press the power button to wake up the MC65.
If device wakes up, repeat steps 8 – 15.
If device does not wake up, it will require a cold boot (1-9-pwr)
2 Replies
this is the last entries in the RTLog if this helps... 15016, 2013-03-29, 04:30:03, 6cbedcfah, 6cbb02eah, CertVerify: USBModem.dll trust = 2 15017, 2013-03-29, 04:30:03, 6cbedcfah, 6cbb02eah, CertVerify: SCardDriver.dll trust = 2 15018, 2013-03-29, 04:30:03, 6cbb030eh, 6cbb02eah, SCardDriver: SCR_Init 15019, 2013-03-29, 04:30:03, 6cbb030eh, 809f1fbah, MMGSDIEventCb, event 1 15020, 2013-03-29, 04:30:03, 6cbb030eh, 809f1fbah, MMGSDI_CARD_ERROR_EVT 15021, 2013-03-29, 04:30:03, 6cbb030eh, 6cbb02eah, DC::RI CompareNetworkSelection:SetReg DWORD for m_bFirstTimeBoot=1 15022, 2013-03-29, 04:30:03, 6cbb030eh, 6cbb02eah, [Memory] hThread in RIL init Close 15023, 2013-03-29, 04:30:03, 6cbb030eh, a0785fa6h, AutoReboot Registry not present. So set NV Item 905 as 1. Enable AutoReboot 15024, 2013-03-29, 04:30:04, 6cbb030eh, 809f1fbah, CRC::FPA Did not find provisioning app 15025, 2013-03-29, 04:30:04, 6cbb030eh, 809f1fbah, ABC::TMCETR MMGSDI_CARD_ERR_XXX=2->RIL error=-2130705911 15026, 2013-03-29, 04:30:04, 6cbb030eh, 809f1fbah, SetEvent("RIL_GW_ONLY_4SIM_INSERTED") 15027, 2013-03-29, 04:30:04, 6cbb030eh, 6cbb02eah, -OALPAtoVA(va = 0x8cbff000) 15028, 2013-03-29, 04:30:04, 6cbb030eh, 6cbb02eah, -OALPAtoVA(va = 0x8cbff000) 15029, 2013-03-29, 04:30:04, 6cbedcfah, 6cbb02eah, CertVerify: wce_vdec_driver.dll trust = 2 15030, 2013-03-29, 04:30:04, 6cbb030eh, 6cbb02eah, WinCE VDEC Driver :DllMain dwReason == DLL_PROCESS_ATTACH 15031, 2013-03-29, 04:30:04, 6cbb030eh, 6cbb02eah, Diag_LSM: Diag_LSM_Init: Failed to open handle to windiag driver, error = 55 15032, 2013-03-29, 04:30:04, 6cbb030eh, 6cbb02eah, Diag_LSM: RegisterForMaskChange: DeviceIOControl failed. 15033, 2013-03-29, 04:30:04, 6cbb030eh, 6cbb02eah, WinCE VDEC Driver :DllMain Diag_LSM_Init failed 15034, 2013-03-29, 04:30:04, 6cbb030eh, 6cbb02eah, WCE_VDEC : INIT :WCEVDEC_INITIALIZE := dwValue 0 15035, 2013-03-29, 04:30:04, 6cbb030eh, 6cbb02eah, No registry key value found for vdec thread priority 15036, 2013-03-29, 04:30:04, 6cbb030eh, 6cb9efdah, WinCE VDEC Driver : WVT_Open 15037, 2013-03-29, 04:30:04, 6cbb030eh, 6cb9efdah, WCE_VDEC: Received IOCTL_POWER_CAPABILITIES 15038, 2013-03-29, 04:30:04, 6cbb030eh, 6cb9efdah, WinCE VDEC Driver : WVT_Open 15039, 2013-03-29, 04:30:04, 6cbedcfah, 6cbb02eah, CertVerify: regmerge.dll trust = 2
additional information
To answer your previous question, yes this CAB file is required to reproduce the issue. No RS507 needs to be used or connected in this test. Also the issue does not occur when testing with the old CRD5500-4000ER cradle.
There are two version CAB files that UPS has for the RS507. The issue was tested with both CAB files, and the issue occurs with either CAB file.
MC65_RS507_Support_Beeping_RC3.cab - This is the CAB file that they are running in their production units
65XXw65HenCB760802.cab – This is a new CAB file provided to UPS for updating enhanced RS507 BT pairing.
These CAB file were supplied by MIL team. Reference CPR 8258. summary: MC65_RS507_Support_Beeping_RC3.cab CRD5501-4000ER with Ethernet connection is required for duplication