Fix sfdp_find_addr_region algorithm

sfdp_find_addr_region() was causing issues with SPI
flashes with sector table parsed from SFDP (in
particular SST26VF016B).

In particular, it was returning -1 when address 0 is
passed (probably also if the address in the first
region). I do not know why the search algorithm is
written to search from the higher to lower regions,
but it was obvious that it would fail for the first
region. Also it was harder to read due to the index
manipulation.

Author: boraozgen

drivers/include/drivers/internal/SFDP.h

@@ -121,7 +121,7 @@ int sfdp_detect_erase_types_inst_and_size(uint8_t *bptbl_ptr, sfdp_hdr_info &sfd
  *
  * @return Region number
  */
-int sfdp_find_addr_region(bd_size_t offset, const sfdp_hdr_info &sfdp_info);
+int sfdp_find_addr_region(bd_addr_t offset, const sfdp_hdr_info &sfdp_info);
 
 /** Finds the largest Erase Type of the Region to which the offset belongs to
  *

drivers/source/SFDP.cpp

@@ -377,20 +377,20 @@ int sfdp_detect_erase_types_inst_and_size(uint8_t *bptbl_ptr, sfdp_hdr_info &sfd
     return 0;
 }
 
-int sfdp_find_addr_region(bd_size_t offset, const sfdp_hdr_info &sfdp_info)
+int sfdp_find_addr_region(bd_addr_t offset, const sfdp_hdr_info &sfdp_info)
 {
-    if ((offset > sfdp_info.bptbl.device_size_bytes) || (sfdp_info.smptbl.region_cnt == 0)) {
+    if ((offset >= sfdp_info.bptbl.device_size_bytes) || (sfdp_info.smptbl.region_cnt == 0)) {
         return -1;
     }
 
     if (sfdp_info.smptbl.region_cnt == 1) {
         return 0;
     }
 
-    for (int idx = sfdp_info.smptbl.region_cnt - 2; idx >= 0; idx--) {
+    for (int idx = 0; idx < sfdp_info.smptbl.region_cnt; idx++) {
 
-        if (offset > sfdp_info.smptbl.region_high_boundary[idx]) {
-            return (idx + 1);
+        if (offset <= sfdp_info.smptbl.region_high_boundary[idx]) {
+            return idx;
         }
     }
     return -1;