Address Discrepances between Debugging and nrfjprog memrd

Address Discrepances between Debugging and nrfjprog memrdhttps://devzone.nordicsemi.com/f/nordic-q-a/33432/address-discrepances-between-debugging-and-nrfjprog-memrdIntroduction I use fStorage to write some data to flash and I read the data by following procedure: uint32_t Read32(uint32_t address) { return *(mpFlashConfig->p_start_addr + address); } All seamed working correctly. But then I tried to read someen-USTelligent Community 13Mon, 16 Apr 2018 14:37:55 GMTRE: Address Discrepances between Debugging and nrfjprog memrdhttps://devzone.nordicsemi.com/thread/128507?ContentTypeID=1Mon, 16 Apr 2018 14:37:55 GMT137ad170-7792-4731-bb38-c0d22fbe4515:90638822-253b-4cbf-a937-4e75e4acdf87Roman<p>This is simple<strong> pointer arithmetics</strong>:</p> <p>p_start_addr is uint32_t const pointer, but addresses are byte-wise organized.</p> <p>(p_start_addr++ would increment the p_start_addr by four)</p> <p></p> <p>Adding some address value means the address is multiplied by four and added to the pointer.</p> <p></p><div style="clear:both;"></div>