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

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

khosla — Wed, 21 Jun 2017 09:48:02 GMT

@Hung Bui okay, right now everything seems fine. But i will try to illustrate it better if need arises. Thanks!!!

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

Hung Bui — Mon, 19 Jun 2017 11:17:26 GMT

Hi Khosla,

Sorry but it's hard to fully understand what you plan to do. Could you maybe draw a figure explaining the mechanism ? The more detail the better. We wouldn't be able to look into your code or the article to check if everything works or not, we can only give you suggestion on what you should do.

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

khosla — Fri, 16 Jun 2017 07:00:31 GMT

Hi With regard to the same work, thers is another issue. I want that at the ready event timestamp to is captured and loaded into the packet. This is done using the interrupts itself as you can see in my mainc file attached at the top. Then after some time there is Start for the radio. So i am not using the Ready/Start shortcut here instead i am using the interrupts to load the packet initially at Ready just when ramping up of radio is about to be over. This is beacuse after packets will be on air i cant load the timesatamp onto the packet. And this is how the tiny sync algorithm work (referring to the link to the resarch papaer above-figure 1). Now i started the analyser by connecting to all the four pins 21,22,23,24 to see the behaviour of different events- Ready, Address and Payload and the time between ready and start. But it just shows some toogle on ready event which is inappropriate and nothing on the address and payload event. Can you look at the mainc file and verify if the interrupts are actually bound to work or not. I have an INTENSET in main and made a new function 'radio handler' just above main which is called on a radio interrupt. am also attaching my capture on the analyser at the top if you would like to view

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

khosla — Fri, 09 Jun 2017 13:45:55 GMT

it has been fixed. thanks!!!

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

Hung Bui — Fri, 09 Jun 2017 13:32:54 GMT

@khosla: the case is updated, could you check if it fixes the issue for you?

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

khosla — Fri, 09 Jun 2017 07:38:13 GMT

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

you can see the link

devzone.nordicsemi.com/.../ses-sdk1220-undefined-reference-to-sram_segment_end/

i have the same problem as this guy

please elaborate on this

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

khosla — Thu, 08 Jun 2017 13:33:23 GMT

you can see the link devzone.nordicsemi.com/.../ses-sdk1220-undefined-reference-to-sram_segment_end/ i have the same problem as this guy

please elaborate on this

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

Hung Bui — Thu, 08 Jun 2017 13:20:00 GMT

I would suggest you to create a new case for that issue, please describe how did you get into that.

Also could you add some more information how you fix the issue with the sniffer ?

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

khosla — Thu, 08 Jun 2017 12:56:49 GMT

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

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

khosla — Thu, 08 Jun 2017 12:52:23 GMT

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

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

Hung Bui — Wed, 07 Jun 2017 08:57:02 GMT

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"

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

khosla — Tue, 06 Jun 2017 13:12:54 GMT

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.

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

Hung Bui — Tue, 06 Jun 2017 13:05:42 GMT

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.

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

khosla — Tue, 06 Jun 2017 12:43:18 GMT

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.

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

Hung Bui — Tue, 06 Jun 2017 11:40:15 GMT

@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 ?

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

endnode — Mon, 05 Jun 2017 12:34:29 GMT

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.

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

khosla — Mon, 05 Jun 2017 12:27:34 GMT

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.

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

endnode — Mon, 05 Jun 2017 08:59:42 GMT

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).

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

khosla — Mon, 05 Jun 2017 08:54:41 GMT

Hi, I even tried to resolve this by setting a break point on "timer init". But when debugging while running in SES, and pausing, there is no call stack. This seems to be quite strange.

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

khosla — Sun, 04 Jun 2017 09:39:48 GMT

i am using radio with ppi functionality, since i am using harware timers to capture events and do need CPU intervention. i would be seeing the packet receive times in wireshark corresponding to my device. That would be advertising ind packets. Then i ought to see the toggle event times on the analyser. I am using the button functionality as u see in my code to distinguish between transmit and receive events.

I am just using wireshark and analyser for verification. Ofcourse i can't rely on their time samples, as i don't know which clocks they are using. But i would be using Segger RTT viewer to communicate with my board and then Pynrfjprg interface to transfer the data from the board to the PC. i AM USING THE STANDARD NRF Bluetooth smart sniffer from nrf51 downloads

Earlier the sniffer was running okay at the initial stages and my device showed up, but lately i had to modify the functionality to load the timestamp in the packet prior to it being sent as well as calling the function app button is pushed in the main function which represents a transmit event. So i think the address and the payload values i loaded in the mesh demo packet are same as earlier, but now after everything seems okay in the code, i can't see my device. If u could analyse the problem and get back to me.

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

endnode — Sun, 04 Jun 2017 09:00:38 GMT

OK, so you hope to do some kind of "time of flight" demo on nRF5x and for that you are (obviously) not using Soft Device but you need to command radio front-end directly. That looks correct. Have you used any SDK example as source? Why do you assume that you will see your packets in BLE sniffer? Are they even valid BLE packets? What sniffer are you using?

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

khosla — Sun, 04 Jun 2017 06:55:09 GMT

I have attached two files in my initial comment, one mainc and the other pdf of the research paper i am using. seeing fig 1 in that paper, u will know what i am doing.

to summarize, i am basically working on synchronizing time between two neighboring nodes as well as between distant nodes. so for that i am timestamping each of the send and receive events at the nodes. Considering two nodes, 1 and 2, the timestamp first being generated when the packet is sent from 1 to 2. then, when 2 receives it, another timestamp is generated. There is some delay, when 2 sends an acknowledgement back to1. so again now just when the ack is sent form 2, now 2 being the transmitter, another timestamp at node 2 and similarly when the ack is received at 1, then another timestamp collected. so total 4 timestamps being collected in each cycle. The packets being transmitted on radio carry the timestamp info generated by the hardware timers used at each node.

Fo that i need to see the time samples in wireshark and analyser. i am using sdk 12.2 and nrf51 board in segger studio. I need to basically capture the transmit and receive events.

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

endnode — Sat, 03 Jun 2017 20:38:11 GMT

Hi, your source code seems to be missing here. However from your description more items are unclear: what is your code based on? Was it ever working (meaning was it ever advertising)? The best approach is to start from some proven SDK example before writing bunch of code from scratch...