0% found this document useful (0 votes)
59 views2 pages

How To Update Module Firmware With FORScan - Page 3

Uploaded by

Shabaan Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
59 views2 pages

How To Update Module Firmware With FORScan - Page 3

Uploaded by

Shabaan Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

FORScan forum

Software scanner for Ford, Mazda, Lincoln, Mercury vehicles Search…  

 Quick links  FAQ  Notifications  Private messages aloneraja 

 Board index ‹ English & International forums ‹ Beta testing

How to update module firmware with FORScan


Locked    Search this topic…   21 posts  1 2 3

4.4. Troubleshooting: Recovery 


FORScan
Site Admin
mode
Posts: 2922
 by FORScan » Mon Sep 06, 2021 3:38 am Joined: Fri Jun 13, 2014 5:21 am

Recovery mode is a special mode of work that may be required only in some
very rare cases when module "freezes".

Normally, even if FMFU process has failed, the module remains online and
available for programming. This is possible because PBL is located in ROM and
cannot be rewritten or damaged during FMFU. So, even if the programming
equipment has erased flash, PBL remains working and implements minimal
functionality that is enough to restart the programming process and recover
the module. Thus in 98% of cases module remains easily recoverable. But it
works only if PBL has detected that primary application is missing, damaged or
incompatible and doesn't run it. If PBL hasn't detected it properly and launched
damaged application, the module may get "frozen" and thus becomes not
available for programming. Recovery Mode in FORScan was created specially
for this case.

The idea of the Recovery Mode is that PBL usually has a special, very small
(usually about 20ms) delay between the moment of start and running primary
application. If it receives programming command during this interval, it will
start programming session instead of loading the damaged application and can
be recovered this way. So user needs to cycle the power (disconnect module
from the power supply, then connect it back), to initiate PBL restart, and
programming equipment needs to send commands fast enough to catch the
moment right after restart. This is what Recovery mode in FORScan does: it ask
user to de-energize the module, starts sending programming requests in cycle
and then asks user to connect the power. Figure 4d illustrates how it looks like:
Picture 4d. Recovery mode in FORScan

Back to contents

Locked      21 posts  1 2 3

 Return to “Beta testing” Jump to 

WHO IS ONLINE
Users browsing this forum: aloneraja and 0 guests

 Board index  The team  Members  Delete cookies All times are UTC+03:00

Powered by phpBB® Forum Software © phpBB Limited


Privacy | Terms

You might also like