Custom services not showing when code is uploaded on custom board.

[xproto]

I disabled the DIS.

With nRF52DK the custom services characteristics are shown but if I upload the code to the ebyte e73-tbb, the custom service and characteristics are not shown. The same shows with nrf connect app in PC via the nrf52840_dongle. The build and code are the same. The ebyte e73-tbb has already predefined template for build in Zephyr. Im using the nrfconnect plugin in vscode. Do I need to adjust something? I have used this module multiple times and code should have same result. This is the first time I encountered it. TIA

[Sigurd]

Hi!

Click on the 3 dots in the upper right corner, and click "Refresh services", are you able to discover the services?

[xproto]

Hello! and thanks for reply. I have tried that. It still says empty list.

[Sigurd]

That's strange. Do you have any log output(e.g. from the UART) from the device? Any warnings or errors in the log?

[xproto]

Yeah very strange. Now there is none currently.  Based on my searches it shows it might be lack of RAM, or need to adjust address because of the additional characteristic? but those searches all shows from old SDK, not zephyr.

Before I turned off DIS and other parameters like CCC, CUD cause I suspect the characteristic might be too many for slow phones, this one shows.

failed to allocate new mpu region 255

EDIT:

I don't know if this will help, here is the diff output of two build config.

$diff build/zephyr/.config build_1/zephyr/.config

< CONFIG_BOARD="nrf52dk_nrf52832"
---
> CONFIG_BOARD="ebyte_e73_tbb_nrf52832"
57,58d56
< CONFIG_DT_HAS_ARDUINO_UNO_ADC_ENABLED=y
< CONFIG_DT_HAS_ARDUINO_HEADER_R3_ENABLED=y
84d81
< CONFIG_DT_HAS_NORDIC_NRF_SPI_ENABLED=y
87d83
< CONFIG_DT_HAS_NORDIC_NRF_TWI_ENABLED=y
536d531
< # CONFIG_MPSL_PIN_DEBUG is not set
1087,1088c1082,1083
< # CONFIG_NRFX_TWI0 is not set
< # CONFIG_NRFX_TWI1 is not set
---
> # CONFIG_NRFX_TWIM0 is not set
> # CONFIG_NRFX_TWIM1 is not set
1298c1293
< CONFIG_BOARD_NRF52DK_NRF52832=y
---
> CONFIG_BOARD_EBYTE_E73_TBB_NRF52832=y
1303d1297
< CONFIG_BOARD_ENABLE_DCDC=y
1465,1466d1458
< CONFIG_HAS_HW_NRF_SPI1=y
< CONFIG_HAS_HW_NRF_SPI2=y
1474d1465
< CONFIG_HAS_HW_NRF_TWI0=y
1489d1479
< CONFIG_SOC_DCDC_NRF52X=y

[Sigurd]

Hi!

Try programming with this command:

west flash --recover

[xproto]

It did not worked then I reflashed recover it 3 times then worked for 2-3 times then not working again. I wonder whats with this behaviour.

What is even more confusing is that when it works with the M2101K6G on first connect. The second phone [phone]UY only shows the custom characteristics when M2101k6g phone connected first. Is like M2101K6G needs to discover the services first before 22011119UY can see it. 

And then yeah back to the major problem why it doesnt show the services again. No error logs on hardware.

[Sigurd]

Maybe you can catch a sniffer trace of what's happening on-air.

https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE

[xproto]

I attached the two files. The one working is the nrf52dk log.

ebyte.pcapng

nrf52dk.pcapng

EDIT: I created a new build instead and added this option. So both build for dev board and custom board are from same config.

CONFIG_BOARD_ENABLE_DCDC=n

With the nRF52dk it works as usual. With the custom board I get flooded with 

<err> mpu: Failed to allocate new MPU region 255

[Sigurd]

Looking at the sniffer log,

it seems like the slave device rebooted. The BLE connection suddenly stops, and then we see the device start advertising again after a few seconds.

xproto said:

With the custom board I get flooded with 

Do you have more of this log? Could you try setting CONFIG_DEBUG=y , and then post the full log output ?