1*042d53a7SEvalZeroNimBLE Host 2*042d53a7SEvalZero----------- 3*042d53a7SEvalZero 4*042d53a7SEvalZeroIntroduction 5*042d53a7SEvalZero~~~~~~~~~~~~ 6*042d53a7SEvalZero 7*042d53a7SEvalZeroAt a high level, the NimBLE stack is divided into two components: 8*042d53a7SEvalZero 9*042d53a7SEvalZero- Host 10*042d53a7SEvalZero- Controller 11*042d53a7SEvalZero 12*042d53a7SEvalZeroThis document is an API reference for the host component. If you are 13*042d53a7SEvalZerointerested in the general structure of the NimBLE stack and its non-host 14*042d53a7SEvalZerocomponents, you might want to read the :doc:`../index`. 15*042d53a7SEvalZero 16*042d53a7SEvalZeroThe host sits directly below the application, and it serves as the 17*042d53a7SEvalZerointerface to the application for all BLE operations. 18*042d53a7SEvalZero 19*042d53a7SEvalZero.. toctree:: 20*042d53a7SEvalZero :titlesonly: 21*042d53a7SEvalZero 22*042d53a7SEvalZero Return Codes <ble_hs_return_codes> 23*042d53a7SEvalZero GAP <ble_gap> 24*042d53a7SEvalZero GATT Client <ble_gattc> 25*042d53a7SEvalZero GATT Server <ble_gatts> 26*042d53a7SEvalZero Identity <ble_hs_id> 27*042d53a7SEvalZero ATT <ble_att> 28