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 .

[endnode]

Well I'm afraid debugger doesn't need to work as you expect on these systems, I would rather go with some old fashion tracing through UART or RTT or similar. First seeing "trace" through the program on working FW and then see difference on modified one. I guess you will find the discrepancy pretty quickly (especially if you will keep development "steps" small enough so there will never be too much new code in the project since last stable version).

[khosla]

I don't get u exactly but as i told u i need to first just get an overview of the samples obtained using sniffer and wireshark.I would be relying on the RTT viewer and Pynrfjprog for accurate results. But even after flashing the firmware again, sniffer doesnt show my device. or maybe i am missing some hint of yours. Also i tried to include the "int printf(const char *fmt,...);" statement (this is to be included in the file segger rtt.h) at the top of mainc file and just a random text hello as "printf("Hello\n");" just at the start of the main function in my code. This was to see if hello text actually gets printed when i run the debugger but nothing happens as of now.

[endnode]

Unfortunately my only advice is: if you had some FW version which was working well (meaning that radio packets were visible by Sniffer as you require) then roll back to that version and by doing small modifications (e.g. put some "dummy" static time-stamp into the packet and run the test again, if still visible on Sniffer then add timer initialization and run it again, if still visible on the Sniffer only then add actual timing information into the packet on the place of "dummy" time stamp) debug your app. I guess this is standard way of doing things.

[Hung Bui]

@Khosla: I don't really understand why you need the sniffer here. Why would the timestamp on the sniffer important here ? You can use the sniffer to read the content of the packet I agree, but to use the timestamp on the sniffer I don't understand.

In addition, have you made sure you are sending a proper Advertising packet , following BLE spec ?

Do you see your device advertising with a phone ?

[khosla]

I just to need to use sniffer to see the time samples on wireshark and similarly i would verify using the analyser. As i told u earlier i am just using these tools to see what time samples are recorded. Actual measurements will be done using the Segger RTT viewer. But if u could follow up this blog post and get back to me. i am not able to see my device on sniffer. i have included my mainc file at the top.