CONNECT_REQ PDU can not receive

RE: CONNECT_REQ PDU can not receive

zcmm — Fri, 14 Apr 2017 02:40:10 GMT

thank you Hung Bui

RE: CONNECT_REQ PDU can not receive

Hung Bui — Wed, 12 Apr 2017 13:50:23 GMT

You can try to add system variable PATH to that folder. But I would suggest to try to install nrfcommand line tool again.

RE: CONNECT_REQ PDU can not receive

zcmm — Wed, 12 Apr 2017 10:54:48 GMT

JLinkARM.dll inside one of the folder inside C:\Program Files\SEGGER,i need intall JLINK to Program Files (x86)?

RE: CONNECT_REQ PDU can not receive

Hung Bui — Wed, 12 Apr 2017 10:27:59 GMT

Please check if you have JLinkARM.dll inside one of the folder inside C:\Program Files (x86)\SEGGER You can try to copy nrfjprog inside that folder and run from there. Just in case the System PATH to that folder is not set correctly.

RE: CONNECT_REQ PDU can not receive

endnode — Wed, 12 Apr 2017 09:26:59 GMT

QS1 (do you want to know "why you don't see CONNECT_REQ?" Well that's easy, most likely there was no CONNECT_REQ issued, can also be because sniffer missed it.)

QS2: If you expect your phone to connect to BLE Peripheral then yes, it should come from the phone.

QS3: "how long send CONNECT_REQ PDU" what??? You want to know how long is CONENCT_REQ PDU or at what time it should be sent after any ADV_xxx packet?

QS4: Data on all 3 advertising channels 37/38/39 seems to be OK. If you believe that signal strength is not quasi-equal across whole BLE frequency range then you simply have wrong antenna performance and tuning matching.

QS5: What do you mean by "accuracy is very bad" and what do you expect from 2$ IC? Atomic clock?

RE: CONNECT_REQ PDU can not receive

zcmm — Wed, 12 Apr 2017 09:20:19 GMT

which? this " JLinkARM.dll could not be located after the installation info in the registry or in the current folder"?

RE: CONNECT_REQ PDU can not receive

endnode — Wed, 12 Apr 2017 09:18:08 GMT

Almost none of your questions make any sense, sorry.

RE: CONNECT_REQ PDU can not receive

zcmm — Wed, 12 Apr 2017 09:01:25 GMT

sorry ,it can not work.

RE: CONNECT_REQ PDU can not receive

Hung Bui — Wed, 12 Apr 2017 07:57:37 GMT

You may want to uninstall Segger Jlink and install it again. Also please take a screenshot when you see the error.

RE: CONNECT_REQ PDU can not receive

zcmm — Wed, 12 Apr 2017 06:07:05 GMT

thanks,but it note: JLinkARM.dll could not be located after the installation info in the registry or in the current folder.Please reinstall JlinkARM software. The nrfgostudio and mdk is normally work.

RE: CONNECT_REQ PDU can not receive

endnode — Thu, 06 Apr 2017 11:58:49 GMT

Open command like ("cmd") and run "nrfjprog" from that...

RE: CONNECT_REQ PDU can not receive

zcmm — Thu, 06 Apr 2017 10:48:23 GMT

thanks,i can open nrfjprog.exe,but the windows is quit(use win+R open nrfjprog),how to solve it?

RE: CONNECT_REQ PDU can not receive

Hung Bui — Thu, 06 Apr 2017 08:04:04 GMT

We set the start address at 0x20002C00 so that it would work on different Softdevice including the S130 and S310 which may requires upto 0x2C00 byte.

The size is 0x1380 if you use 16kB RAM variant.

RE: CONNECT_REQ PDU can not receive

zcmm — Thu, 06 Apr 2017 02:59:40 GMT

for 50,i have no question.sometimes is 100 times,maybe 60,it is random. i have another question,the sdk8.1.0,the dfu bootlooder,the iram1 is 0x20002C00 SIZE 0X1380,Why is not 0x20002000,size is 8K-0x80?

RE: CONNECT_REQ PDU can not receive

Hung Bui — Wed, 05 Apr 2017 08:17:24 GMT

What do you mean exactly by "50 is not connect device" ? 50 on how many trial ? Which phone did you use ? Have you tried with other phones and how was the result ?

RE: CONNECT_REQ PDU can not receive

zcmm — Wed, 05 Apr 2017 01:42:43 GMT

NO,the 50 is not connect device. the advertising rate is 500ms,it is still not correct.But it is still missing RF packet,i think it is not usual.

RE: CONNECT_REQ PDU can not receive

Hung Bui — Mon, 03 Apr 2017 10:44:44 GMT

@zcmm: You mean it may happens once in 50 trial ? What about interference ? I would say it's not very unusual that an RF packet is missing because of that.

Have you tried to increase the advertising rate ?

For question #5, when you have 250ppm, you should expect the tolerance of 250 parts per 1.000.000. In 24 hours you have 86400 seconds, this means you can have up to 22 seconds in the tolerance.

RE: CONNECT_REQ PDU can not receive

endnode — Sat, 01 Apr 2017 11:51:14 GMT

There is no reason why FW should cause malfunctioning on particular radio channel, this is all managed by the stack (Soft Device). I'm not HW engineer to advice on HW debugging but I guess that's pretty impossible to do over internet... If you have any doubts about FW then you should get some trusted HW (like DK or some 3rd party module) and verify it there.

RE: CONNECT_REQ PDU can not receive

zcmm — Sat, 01 Apr 2017 10:55:24 GMT

yes,it is my board.No,I have not test the DK,beacause i change my board Crystals matching capacitance from 30pf to 12pf,it is normal.This is very strange. Do you know QS5 ?

RE: CONNECT_REQ PDU can not receive

endnode — Sat, 01 Apr 2017 10:42:56 GMT

Is this your custom board? Have you verified all that with some proven HW like nRF52 DK?

RE: CONNECT_REQ PDU can not receive

zcmm — Sat, 01 Apr 2017 07:10:31 GMT

Different mobile phone is different.May be 50 times once.I have another question,pls see pictures

RE: CONNECT_REQ PDU can not receive

Hung Bui — Thu, 30 Mar 2017 14:26:43 GMT

Is there any chance that CONNECT_REQ PDU was never sent from the phone when the phone can't connect ? Then it's easy to understand why both the scanner and the device doesn't receive that packet.

How often do you see the phone can't connect ? Have you tried to increase the advertising interval to make it faster. The CONNECT_REQ PDU is sent when the phone receives the advertising packet.