My question is pertaining to running of sniffer to show my device name

[khosla]

50 MHz, 500 M Samples [16].logicdatamainc.txt(/attachment/98d67704ad9c5affad8d5bce2ef93315)(/attachment/f20245cb8f1c01edb4b17875b6eedc4b)01200555.pdfI am using the radio with ppi to transmit as well as receive packets through the same code. I need to record the time events.I have enabled a special button functionality to distinguish between the transmit and receive events.

I am attaching the mainc file under. I have thoroughly checked the address, and other values that i put in the packet. If you could let me know what could be the problem behind my device named "Raghav" not being showed on sniffer, even though the code is built and run properly. I even try to set break point at timer init and commented out 'app button is pushed' function but no change occurs.

I am attaching my mainc file .

[Hung Bui]

Note that the "time" inside the chip are relative. We are talking about the counter of the timer on the chip. And our task is to calculate the difference between the counter on different chips to sync them, or better to set them to the same number. It's not related to the actual "real life" time when the sniffer catch the packet or when the packet is sent from the chip.

Again, have you verified the packet you sent match with BLE spec ? Do you follow the spec when you write your code, please verify using a phone or using nRFConnect app on PC, before you test with the sniffer.

[khosla]

ya the packet contents are as per the specification. and you are right that those times are just estimates, there can be delay when the timestamp is loaded as soon as the radio starts and then when it is actually sent from node 1. Thats what also has to be taken into consideration. But let me test it on my phone and see. because initially i tried debugging and running in SES by setting a breakpoint on timer init, but still there is no call stack seen in the debugger window.

[Hung Bui]

I'm not talking about estimated or anything, my point is the time stamp on the chip (which sent over the radio packet) has nothing to do with the actual time on the computer and on wireshark, unless you somehow managed to update the actual time on PC down to the chip.

Let me know if you can see the advertising packet. Note that if you don't start advertising on address 37, you need to configure the sniffer to match with the channel sequence you use. Check "h - Define new adv hop sequence"

[khosla]

Hi

I am facing this error on running my code:

In function `SystemInit':

1> C:/Users/Raghav Khosla/Downloads/nRF5_SDK_12.2.SES/nRF5_SDK_12.2.SES/examples/peripheral/ppi/pca10028/blank/arm5_no_packs/../../../../../../components/toolchain/embedded_studio/ses_nrf51_startup.s:108: undefined reference to `__SRAM_segment_end__'

would appreciate your comment on this

[khosla]

@hung bui i am seeing my packet now on the sniffer.