BPM Updates: Extend the reset device wait to 15 seconds from 10

There was an issue where the BPM reset wait was set to 10 seconds which
would sometimes lead to SCAP timeouts. By setting it to 15 seconds, the
issue goes away by giving the BPM more time to come back online after a
reset command is sent.

Change-Id: I3c20657ef976f13fb6636b280c7cc95195a24d53
RTC:215466
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/83482
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Reviewed-by: TSUNG K YEUNG <tyeung@us.ibm.com>
Reviewed-by: Daniel M Crowell <dcrowell@us.ibm.com>

src/usr/isteps/nvdimm/bpm_update.C

@@ -1863,10 +1863,12 @@ errlHndl_t Bpm::resetDevice()
                 break;
             }
 
+            // If we wait less than 15 seconds for the reset to occur it is
+            // possible that BPM won't be ready for more commands via the NVDIMM
             TRACFCOMP(g_trac_bpm, "Bpm::resetDevice(): "
-                      "Resetting BPM for NVDIMM 0x%.8X, sleep for 10 seconds.",
+                      "Resetting BPM for NVDIMM 0x%.8X, sleep for 15 seconds.",
                       TARGETING::get_huid(iv_nvdimm));
-            longSleep(10);
+            longSleep(15);
         }
         else
         {