Central mode get wrong device mac address.

RE: Central mode get wrong device mac address.

frogofmagic — Thu, 03 Apr 2025 08:49:22 GMT

Hi,

Yes~ I change adv_report to connected and get the correct mac addr now!

Thank you~ really appreciate it 😃

RE: Central mode get wrong device mac address.

Einar Thorsrud — Thu, 03 Apr 2025 08:36:15 GMT

Hi,

I think I spotted the error now. Unions are a bit tricky as the member in the union is decided runtime, so you will not get a build error when using the wrong union member. And here you are using the adv_report in the handling of the BLE_GAP_EVT_CONNECTED event, which is incorrect. You need to use the connected union member. So it should be something like this:

            NRF_LOG_INFO("MAC %02X:%02X:%02X:%02X:%02X:%02X \r\n",
                    p_gap_evt->params.connected.peer_addr.addr[0],
                    p_gap_evt->params.connected.peer_addr.addr[1],
                    p_gap_evt->params.connected.peer_addr.addr[2],
                    p_gap_evt->params.connected.peer_addr.addr[3],
                    p_gap_evt->params.connected.peer_addr.addr[4],
                    p_gap_evt->params.connected.peer_addr.addr[5]);

RE: Central mode get wrong device mac address.

frogofmagic — Wed, 02 Apr 2025 10:25:03 GMT

Hi,

I tried SES V5.42a, and got same result as keil.

I only change

m_target_periph_name
Add NRF_LOG_INFO("MAC %02X:%02X:%02X:%02X:%02X:%02X \r\n", p_gap_evt->params.adv_report.peer_addr.addr[0], at case BLE_GAP_EVT_CONNECTED:

I also tested nRF5_SDK_16.0.0_98a08e2 with s140_nrf52_7.0.1_softdevice.hex, still the same.

Any idea? or anything want to try?

RE: Central mode get wrong device mac address.

frogofmagic — Wed, 02 Apr 2025 09:59:26 GMT

Hi,

Stack_Size EQU 16384 add to 32768 doesn't help. Still get wrong mac.

I will come back after try Segger Embedded Studio version 5.42a.

RE: Central mode get wrong device mac address.

Einar Thorsrud — Wed, 02 Apr 2025 09:13:16 GMT

Hi,

I see. In Keil projects, the easiest way to adjust the stack size is to modify modules/nrfx/mdk/arm_startup_nrf52840.s and where you have a line starting with "Stack_Size EQU", modify the number to a higher value. Alternatively, it should work to go to Options for Target -> C/C++ -> Preprocessor Symbols and define __STACK_SIZE to the value you want. (The stack size may not be the issue here, but it is worth increasing it to check).

RE: Central mode get wrong device mac address.

frogofmagic — Wed, 02 Apr 2025 09:05:53 GMT

Hi,

Which version of Keil are you using?
- uVision 5.28
Do you only see this with optimization level 0?
- debug mode only work well with level 0. I tried level 3 and print mac to usb, still got wrong mac as level 0.
Can you build the project with Segger Embedded Studio version 5.42a (this is the version used with the nRF5 SDK 17.1.0 release test) to see if you can reproduce the issue there?
- This need take some time to get everything work, will try it next few days.
I assume you are using an external debugger as the nRF52840 dongle does not have an onboard debugger, or are you testing on a different board (the DK for instance)?
- I connect PCA10059 with PCA10028 as picture.
The backtround for these questions is that it the address type as well as the address are invalid, so I wonder if there could be a stack overflow or similar corrupting the memory. Can you try to increase the stack size and see if that helps?
- How to increase stack size?
- Now my IRAM1: 0x200043A8 0x3BC58, I tried 0x20010000 0x30000 doesn't help.

RE: Central mode get wrong device mac address.

Einar Thorsrud — Wed, 02 Apr 2025 07:58:38 GMT

Hi,

I don't see any issues in the code here or your changes. I notice you are using Keil which I have not been able to test, but I have some questions:

Which version of Keil are you using?
Do you only see this with optimization level 0?
Can you build the project with Segger Embedded Studio version 5.42a (this is the version used with the nRF5 SDK 17.1.0 release test) to see if you can reproduce the issue there?
I assume you are using an external debugger as the nRF52840 dongle does not have an onboard debugger, or are you testing on a different board (the DK for instance)?

The backtround for these questions is that it the address type as well as the address are invalid, so I wonder if there could be a stack overflow or similar corrupting the memory. Can you try to increase the stack size and see if that helps?

RE: Central mode get wrong device mac address.

frogofmagic — Wed, 02 Apr 2025 02:49:26 GMT

Hi, thanks for reply. I did combine USB and LED fuction.

So I download and unzip nRF5_SDK_17.1.0_ddde560.zip make sure all clean. And open ble_app_multilink_central as attached file.

Here's my change:

Set Optimization to Level 0
Change define BOARD_PCA10056 to BOARD_PCA10059
Change m_target_periph_name[] to my device name.
Add NRF_LOG_INFO("MAC %02X:%02X:%02X:%02X:%02X:%02X \r\n", p_gap_evt->params.adv_report.peer_addr.addr[0], at case BLE_GAP_EVT_CONNECTED:

Than I test 2 different devices, 1 is made with ST bluenrg-lp and the other is Nordic 52832.

And still can't get the correct mac address :(

Any idea?

devzone.nordicsemi.com/.../8688.ble_5F00_app_5F00_multilink_5F00_central.zip

RE: Central mode get wrong device mac address.

Einar Thorsrud — Tue, 01 Apr 2025 12:23:00 GMT

Hi,

I assum the peripheral is using a static address so that you know what to expect? I notice that the addr_type value is invalid as well, so I wonder if something has corrupted this data somehow. Have you made any changes to the ble_app_multilink_central example? Can you explain what those changes are? Are you ablet o reproduce this issue without your changes (if any)?