sjanc commented on issue #1947: URL: https://github.com/apache/mynewt-nimble/issues/1947#issuecomment-3630909264
Hi, NPL_LOG is just generalization of what logging is on Mynewt, where logging is done via 'modules' and is controlled (and generated) by Mynewt build system. So ports need to do some sort of wrapping for modules used.. This particular case you mentioned is EATT module so required macros to implement by port are (this is from nimble_npl_log.h in nuttx port) ``` #define BLE_EATT_LOG_DEBUG(msg, ...) nimble_info(msg, ##__VA_ARGS__) #define BLE_EATT_LOG_INFO(msg, ...) nimble_info(msg, ##__VA_ARGS__) #define BLE_EATT_LOG_WARN(msg, ...) nimble_warn(msg, ##__VA_ARGS__) #define BLE_EATT_LOG_ERROR(msg, ...) nimble_err(msg, ##__VA_ARGS__) #define BLE_EATT_LOG_CRITICAL(msg, ...) nimble_err(msg, ##__VA_ARGS__) ``` If you want to fine tune those this is the place. However, I'm not sure why this log yuu mentioned is error log to begin with... (I think it should probably be info or just debug) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
