pca10028 disconnects immediately when trying to connect using ble_app_uart

[softorchestra]

Can anyone tell me if there is a specific problem on the nFR 51 using the 12.3 DK, where a disconnect is seen when it connects? I'm using Android Lolipop 5.0 on a BLU device. I see the disconnect immediately after selecting the nordic device in the selection dropdown, so it does see the device.

I have read that the 51 had problems, and it wasn't clear if the 52 also has the same problem, or if this is similar with a timeout not being set at the start?

The project I'm working on will use the 52 and I'm thinking of just buying one, but before I do I wanted to find out if this is a common problem with 51 and 52 devices? Isolated to 51? Neither, an error in the ble_app_uart example?

I'm going to get the sniffer setup tonight and see what I see, but I'm using Linux so it requires some jumping through a couple hoops to get the nRF sniffer going...:(

Any help would be appreciated. Eventually I need to get a 52 board, but was trying to use this until the firmware iscomplete, that will be based around your 52 chipset. I'm not doing that portion, I'm on the software side.

The firmware engineer is on vacation, so I'm trying to get going in the meantime. AFAIK, I have the example built and flashed properly to the pca10028 device I'm using.

I'm attempting to use the UART profile with 32 bytes of data.

Compiler:
arm-none-eabi-gcc (GNU Tools for Arm Embedded Processors 7-2018-q2-update) 7.3.1 20180622 (release) [ARM/embedded-7-branch revision 261907]

flash:
[aland@eagle armgcc]$ pwd
/home/aland/src/nRF5_12.3.0/examples/ble_peripheral/ble_app_uart/pca10028/s130/armgcc
[aland@eagle armgcc]$ make flash
Flashing: _build/nrf51422_xxac.hex
nrfjprog --program _build/nrf51422_xxac.hex -f nrf51 --sectorerase
Parsing hex file.
Erasing page at address 0x1B000.
Erasing page at address 0x1B400.
Erasing page at address 0x1B800.
Erasing page at address 0x1BC00.
Erasing page at address 0x1C000.
Erasing page at address 0x1C400.
Erasing page at address 0x1C800.
Erasing page at address 0x1CC00.
Erasing page at address 0x1D000.
Erasing page at address 0x1D400.
Erasing page at address 0x1D800.
Erasing page at address 0x1DC00.
Erasing page at address 0x1E000.
Erasing page at address 0x1E400.
Erasing page at address 0x1E800.
Erasing page at address 0x1EC00.
Erasing page at address 0x1F000.
Erasing page at address 0x1F400.
Erasing page at address 0x1F800.
Erasing page at address 0x1FC00.
Erasing page at address 0x20000.
Erasing page at address 0x20400.
Erasing page at address 0x20800.
Applying system reset.
Checking that the area to write is not protected.
Programming device.
nrfjprog --reset -f nrf51
Applying system reset.
Run.

OS:
Ubuntu 18.04 (bionic beaver)

Alan

[Edvin]

Do you know what chip is on the nRF52DK that you have? It should say on the chip. either N52832 or N52840.

If you have the nRF52832 you should use the S132 softdevice. If you have the nRF52840 you should use the S140 softdevice.

You should also use the correct projects for your board.

the nRF52832 DK is PCA10040, and the nRF52840 DK is PCA10056 (It says on the white sticker on the programming chip on your DK).

The project folder PCA10056 has a subfolder called s140, not s132. 

You should be able to find the correct device using nRF Connect. You can see the RSSI, which is a negative number indicating the signal strength. The higher the number (closer to 0), the closer the device is. So if it is reasonably close, you should see only one device with RSSI  >-30.

 

Some phones tend to store the device name of BLE devices. If they do, they may display an old name (from another project), so the displayed name might reflect a previous application on the chip. Other than that, it shouldn't cause any problems.

 

I suggest that if you want to get things up and running, try the following example:

if nRF52832:

SDK15.0.0\examples\ble_peripheral\ble_app_uart\pca10040\s132\...

if nRF52840:

SDK15.0.0\examples\ble_peripheral\ble_app_uart\pca10056\s140\...

 

Also remember to program the softdevice first, located in:

SDK15.0.0\components\softdevice\s1[32/40]\hex

 

Best regards,

Edvin

[softorchestra]

Ok, I have the SDK 15.0.0, but my directory is different and I only have an s140, but I built that and flashed the device.

I don't seem to see the device in nRF Connect, shouldn't I?

I see my Apple iPhone and I see the Google device on the Blu Studio C phone.

Not sure if I lost a reply or not. I had the 12.3 SDK loaded as you mentioned this was fixed in SD 130, and there was SD 132 on the 12.3 SDK in the ble_app_uart directory uder armgcc. Possibly you're using a different compiler.

I upgraded to the 15.0.0 SDK and only have the s140 inside:

examples/ble_peripheral/ble_app_uart/pca10056/s140/armgcc

I don't see any other s140 in any of the other directories under the ble_app_uart other than pca10056, and that is the device I have.

Do I need something other than nRF Connect to see and connect to the 52840?

Cheers,

Alan

[softorchestra]

Edvin,

I'm trying this one also:

nRF5-15/examples/connectivity/ble_connectivity/pca10056/ser_s140_uart/armgcc

Shouldn't I see the device in nRF Connect?

Alan

[softorchestra]

I think it's time to get the sniffer setup...

[softorchestra]

Edvin,

I should also add, I flashed the ble_app_blinky to the 52840 and nRF Blinky doesn't see the device either. Is there some setting on the device I need to change?

Alan