Re: BLE_HS_ENOMEM when trying to connect to a second peripheral

I hate when this happens... Will, that was exactly it. \-- **Marco Ferreira** Founder / CTO ma...@altitude.co [www.altitude.co](https://link.nylas.com/link/d8alirm8yqo9t58fef8uienha/local-

Re: BLE_HS_ENOMEM when trying to connect to a second peripheral

Isnt it “NIMBLE_OPT_MAX_CONNECTIONS”. I see you have NIMBLE_OPT_MAX_CONNECTION (not plural). > On Jul 23, 2016, at 4:05 PM, Marco Ferreira wrote: > > My target pkg.yml: > > > > pkg.cflags: > \- "-DNIMBLE_OPT_MAX_CONNECTION=8" > > > > > > Yes, ble_gap_connect()

Re: BLE_HS_ENOMEM when trying to connect to a second peripheral

My target pkg.yml: pkg.cflags: \- "-DNIMBLE_OPT_MAX_CONNECTION=8" Yes, ble_gap_connect() is returning the BLE_HS_ENOMEM. \-- **Marco Ferreira** Founder / CTO ma...@altitude.co [www.altitude.co](https://link.nylas.com/link/d8alirm8yqo9t58fef8uienha/local-

Re: BLE_HS_ENOMEM when trying to connect to a second peripheral

On Sat, Jul 23, 2016 at 09:32:59PM +, Marco Ferreira wrote: > Here's the complete config in my code: > > > > /* Configure the host. */ >cfg = ble_hs_cfg_dflt; >cfg.max_hci_bufs = 16; >// cfg.max_connections = MAX_CONNECTIONS*3; >// cfg.max_gattc_procs = 5; >

Re: BLE_HS_ENOMEM when trying to connect to a second peripheral

I agree with the suggested improvements. It is indeed not trivial to configure all this settings. Based on the value set for NIMBLE_OPT_MAX_CONNECTIONS, the default config should be set accordingly. Back to my issue, I'm still getting the same error. Here's the complete config in my