MC75A0 - BB/DL device lockup BSP41

// Expert user has replied.
R Reginald Corpuz 3 years 5 months ago
1 1 0

1) Time/Date - 3/11/2013, 2:44 PM

2) Response time - 4 hours

3) Product - MC75A0

4) OS Version - BSP41

5) Clarify Case # CASE#2794849 Need help in reviewing the eMscripts attached for a customer issue raised by Siemens.
This site is having an issue unlike any of our other sites.   They have a high level of device locking.  They have 13 devices and all their device lockup constantly. 
I would go through and reset the all the devices.   My process would be to first soft reset, then try a clean boot, then reimage.  some of these device would start the reset and get to the motorola splash screen and the status circle would just keep spinning and never clear.  most would eventually take the image but it would take 5 or 6 tries, some won't reset at all, The ones that did reset some of those would fail again before I was finished  resetting and setting up the last device. 

I brought one of my device(2.37) from my office to the site and I wasn't having any of these issues with my device while running at the site for 2 days. They are currently running the 2.37 image, but I updated half of these device with the new 3.41 image and the problem still exist.  When I was able to get them all up and running I would come back in a few hours and half would be locked up again and we would start the process over again    
Devices locked up on the following screens, Multiple pik screens, Motorola splash screen, hibernation screen(screen off) or just sitting at windows screen like a clean boot was done

Attached are the eMscript folders from some of the failures PIK 9, 2, 13(all running 3.41).  PIK13 just needed a soft reset. PIK2 and PIK9 needed to reimaged   
here is a list of all the serial numbers
12054522501639 12054522501580 12054522501623 12054522501586 12054522501652 12054522501858 12054522501612 12054522501604 12054522501606 12054522501577 12054522501870 12054522501631 12054522501584

Please Register or Login to post a reply

1 Replies

R Reginald Corpuz

I've reviewed the logs and provided this feedback to the customer:  looking for feedback
Pik13 – the one that needed a soft reset. All I see here prior to the reboot is that the WLAN connectivity is lost when the device was cradled and PtldChk.exe was running.  PtldChk.exe was giving out a message of Error retrieving name.  After a reboot and WLAN connection the message was gone.

 

Pik2 - need to be reimaged In this the only thing I noticed is TCP/IP Address errors, not sure if this is related but maybe installing the new Fusion and netlog might help us more in this.

 

Pik9 - need to be reimaged There is no WLAN connectivity (most likely because the device is cradled)

 

In any case, I would still suggest to install the Fusion patch and the USB/Ethernet patch and let me know if there is some improvement on this.

CONTACT
Can’t find what you’re looking for?