FAtal error, i have combined the i2c and usb code. am able to collect the sensor data from i2c and send it to usb. now am combined uart Central code to it.i want to collect the data from ble and send it to uart simultnsly . pls help.
thanks in advance ,
am using this ble module as central, whenever its connects to the peripheral its shows fatal error, without connecting to peripheral device, its working fine
I'm seeing the following error when a connection is made:
<error> app: ERROR 18 [NRF_ERROR_CONN_COUNT] at C:\testing SDK\nRF5_SDK_17.1.0_ddde560\examples\peripheral\usbd_ble_uart\main.c:182
PC at: 0x0003D6E1
<error> app: End of error report
This seems to occur because you have set the central link count to 0:
// <o> NRF_SDH_BLE_CENTRAL_LINK_COUNT - Maximum number of central links.
#ifndef NRF_SDH_BLE_CENTRAL_LINK_COUNT
#define NRF_SDH_BLE_CENTRAL_LINK_COUNT 0
#endif
Increasing this to 1 seems to resolve this error, but you need to increase the RAM start address to make room for the additional softdevice RAM usage:
<warning> nrf_sdh_ble: Change the RAM start location from 0x20002AE8 to 0x20003170.
<warning> nrf_sdh_ble: Maximum RAM size for application is 0x1CE90.
With this resolved, I got another error:
<error> app: ERROR 3735928559 [Unknown error code] at C:\testing SDK\nRF5_SDK_17.1.0_ddde560\components\libraries\timer\app_timer2.c:619
This seems to occur because you have included the source/header files for ble_conn_params.c library in your application, but you have not initialized it to create the required timers. If you want to use this library, please see how to initialize it in conn_params_init() in ble_app_uart example.
app: ERROR 3735928559 [Unknown error code] at C:\testing SDK\nRF5_SDK_17.1.0_ddde560\components\libraries\usbd\app_usbd.c:817
You should move the call to nrf_drv_clock_init() before your call to app_usbd_init(). I'm not sure if this is causing the issue you are seeing, but I'm not seeing any other issues when running your code. I don't have the TWI device connected, so the code is stuck at waiting for m_xfer_done, not sure if your issues occur after this point?
