Incorrect MAC Address Read from Peripheral in Blinky Example

[Gopal Kumar]

Dear Nordic Devzone Team,

I hope this message finds you well. I am writing to report an issue I encountered while working with the Blinky peripheral and central examples using soft-devices S112 and S32 respectively. I am trying to read the peripheral's MAC address and found that the original address (81:E8:BF:90:D2:E6) is not being accurately retrieved by the central. The result I receive from p_ble_evt->evt.gap_evt.params.adv_report.peer_add is BF:90:D2:E6:02:18, which is incorrect.

The memory range from 0x20002F35 to 0x20002F3D appears as follows: "00 00 00 E8 BF 90 D2 E6 02 18 00 53". It is notable that the value "E8" is located just prior to the start address of the structure.

This is how I am trying to fetch the address.

log_ble_gap_addr_t(p_ble_evt->evt.gap_evt.params.adv_report.peer_addr);
            memcpy(&mac_address, &p_ble_evt->evt.gap_evt.params.adv_report.peer_addr, sizeof(ble_gap_addr_t));

I would greatly appreciate it if the team could help me resolve this issue. I am confident that with your expertise, we can resolve this matter and I can continue to work with the Blinky examples.

Thank you for your time and assistance in advance. I am looking forward to hearing from you soon.

Best regards,

Gopal Kumar

[Turbo J]

That is actually documented in the softdevice specs - it uses little endian byte order because that is how the MCU core is configured.

Easy to overlook, see for example the docs to "ble_gap_addr_t". LSB = Little endian byte order.

"Network byte order" would be MSB first normally, but softdevices does not use network byte order.

[Gopal Kumar]

But the 1st 2 byte ie 81 is not present in the memory and hence when i try to print gives wrong value