Wrap Test: Change GROUP_ID/CHIP_ID to match the new proc numbering sc…

…heme

When we changed the fleetwood proc numbering to match cronus, we
didn't update the proc numbering for wrap mode. This lead to weird
behaviours, like proc0 was treated as alt master or booting off a
completely wrong proc (proc 3).

Change-Id: Ia91b10d6e52e6f2e7b36ee59e109133c72bd7372
CQ:SW439810
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/63488
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: ILYA SMIRNOV <ismirno@us.ibm.com>
Reviewed-by: Michael Baiocchi <mbaiocch@us.ibm.com>
Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com>
Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>

src/usr/targeting/common/processMrw.pl

@@ -1100,13 +1100,13 @@ sub processProcessor
 
         if    ($huid eq 0x50000)
         {
-            $grp_id  = 1;
-            $chip_id = 1;
+            $grp_id  = 0;
+            $chip_id = 0;
         }
         elsif ($huid eq 0x50001)
         {
             $grp_id  = 1;
-            $chip_id = 0;
+            $chip_id = 1;
         }
         elsif ($huid eq 0x50002)
         {
@@ -1115,7 +1115,7 @@ sub processProcessor
         }
         elsif ($huid eq 0x50003)
         {
-            $grp_id  = 0;
+            $grp_id  = 1;
             $chip_id = 0;
         }
         else