Add retry of EXP_FW_STATUS when status is FW_BUSY

Change-Id: If0d48114122246c2d221fb197274a6f31598f118
Original-Change-Id: Ic6b962fd4afdcce617ebb893b307ad5cc95086b8
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/77203
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Reviewed-by: Glenn Miles <milesg@ibm.com>
Tested-by: PPE CI <ppe-ci+hostboot@us.ibm.com>
Tested-by: Hostboot CI <hostboot-ci+hostboot@us.ibm.com>
Reviewed-by: Mark Pizzutillo <mark.pizzutillo@ibm.com>
Reviewed-by: STEPHEN GLANCY <sglancy@us.ibm.com>
Reviewed-by: Thi N. Tran <thi@us.ibm.com>

src/import/chips/ocmb/explorer/procedures/hwp/memory/lib/i2c/exp_i2c.H

@@ -59,15 +59,27 @@ namespace check
 /// @param[in] i_target the OCMB target
 /// @param[in] i_cmd_id the command ID
 /// @param[in] i_data data to check from EXP_FW_STATUS
+/// @param[out] o_busy true if explorer returns FW_BUSY status, false otherwise
 ///
 inline fapi2::ReturnCode status_code( const fapi2::Target<fapi2::TARGET_TYPE_OCMB_CHIP>& i_target,
                                       const uint8_t i_cmd_id,
-                                      const std::vector<uint8_t>& i_data )
+                                      const std::vector<uint8_t>& i_data,
+                                      bool& o_busy )
 {
+    // Set o_busy to false just in case we don't make it to where we check it
+    o_busy = false;
+
     // Set to a high number to make sure check for SUCCESS (== 0) isn't a fluke
     uint8_t l_status = ~(0);
     FAPI_TRY( status::get_status_code(i_target, i_data, l_status) );
 
+    // We need to try again if we get a FW_BUSY status, so set the flag
+    if (l_status == status_codes::FW_BUSY)
+    {
+        o_busy = true;
+        return fapi2::FAPI2_RC_SUCCESS;
+    }
+
     // Technically many cmds have their own status code decoding..but SUCCESS is always 0.
     // If it's anything else we can just look up the status code
     FAPI_ASSERT( l_status == status_codes::SUCCESS,
@@ -127,11 +139,37 @@ fapi_try_exit:
 ///
 inline fapi2::ReturnCode fw_status(const fapi2::Target<fapi2::TARGET_TYPE_OCMB_CHIP>& i_target)
 {
-    std::vector<uint8_t> l_data;
-
-    // Get data and check for errors
-    FAPI_TRY(get_fw_status(i_target, l_data));
-    FAPI_TRY( check::status_code(i_target, FW_STATUS, l_data) );
+    constexpr uint64_t NUM_LOOPS = 50;
+    // So, why aren't we using the memory team's polling API?
+    // This is a base function that will be utilized by the platform code
+    // As such, we don't want to pull in more libraries than we need to: it would cause extra dependencies
+    // So, we're decomposing the polling library below
+    bool l_busy = true;
+    uint64_t l_loop = 0;
+
+    // Loop until we max our our loop count or get a doorbell response
+    for(; l_loop < NUM_LOOPS && l_busy; ++l_loop)
+    {
+        std::vector<uint8_t> l_data;
+        FAPI_TRY(get_fw_status(i_target, l_data));
+        FAPI_TRY( check::status_code(i_target, FW_STATUS, l_data, l_busy) );
+
+        if (l_busy)
+        {
+            FAPI_INF( "%s reutrned FW_BUSY status. Retrying...", mss::c_str(i_target) );
+            FAPI_TRY( fapi2::delay( DELAY_100NS, 200) );
+        }
+    }
+
+    FAPI_DBG("%s stopped on loop%u/%u. %s",
+             mss::c_str(i_target), l_loop, NUM_LOOPS, (l_busy ? "FW_BUSY" : "SUCCESS"));
+
+    // Check that Explorer is not still in FW_BUSY state
+    FAPI_ASSERT( !l_busy,
+                 fapi2::MSS_EXP_I2C_FW_STATUS_BUSY().
+                 set_TARGET(i_target),
+                 "Polling timeout on FW_STATUS command (still FW_BUSY) for %s",
+                 mss::c_str(i_target) );
 
 fapi_try_exit:
     return fapi2::current_err;

src/import/chips/ocmb/explorer/procedures/hwp/memory/lib/shared/exp_consts.H

@@ -217,6 +217,7 @@ enum status_codes
     SUCCESS              = 0x00,
     ADDRESS_OUT_OF_RANGE = 0x01,
     ADDRESS_PROHIBITED   = 0x02,
+    FW_BUSY              = 0xFE,
 };
 
 ///

src/import/chips/ocmb/explorer/procedures/xml/error_info/mss_exp_errors.xml

@@ -117,6 +117,26 @@
     </deconfigure>
   </hwpError>
 
+  <hwpError>
+    <rc>RC_MSS_EXP_I2C_FW_STATUS_BUSY</rc>
+    <description>
+      Received FW_BUSY status after polling timeout for
+      command ID EXP_FW_STATUS
+    </description>
+    <ffdc>STATUS_CODE</ffdc>
+    <callout>
+      <procedure>CODE</procedure>
+      <priority>MEDIUM</priority>
+    </callout>
+    <callout>
+      <target>TARGET</target>
+      <priority>HIGH</priority>
+    </callout>
+    <deconfigure>
+      <target>TARGET</target>
+    </deconfigure>
+  </hwpError>
+
   <hwpError>
     <rc>RC_MSS_EXP_I2C_POLLING_TIMEOUT</rc>
     <description>