Hi everyone,
I'm using ses IDE to debug via J-link on nRF52840 DK.
I'm debbuging CDC ACM example (I haven't changed it) but when I debug: ret = app_usbd_cdc_acm_write(&m_app_cdc_acm, m_tx_buffer, size) I have that ret is not NRF_SUCCESS,
Why?
BR
Hi everyone,
I'm using ses IDE to debug via J-link on nRF52840 DK.
I'm debbuging CDC ACM example (I haven't changed it) but when I debug: ret = app_usbd_cdc_acm_write(&m_app_cdc_acm, m_tx_buffer, size) I have that ret is not NRF_SUCCESS,
Why?
BR
Hello,
I'm debbuging CDC ACM example (I haven't changed it) but when I debug: ret = app_usbd_cdc_acm_write(&m_app_cdc_acm, m_tx_buffer, size) I have that ret is not NRF_SUCCESS,
Could you make sure that you have DEBUG defined in your preprocessor defines, like shown in the included image?
This will make a more complete error message be printed to your logger output when an APP_ERROR_CHECK is passed a non-NRF_SUCCESS argument.
Please do this, and let me know what is outputted to your log when the error occurs.
Best regards,
Karl
Hello,
I'm debbuging CDC ACM example (I haven't changed it) but when I debug: ret = app_usbd_cdc_acm_write(&m_app_cdc_acm, m_tx_buffer, size) I have that ret is not NRF_SUCCESS,
Could you make sure that you have DEBUG defined in your preprocessor defines, like shown in the included image?
This will make a more complete error message be printed to your logger output when an APP_ERROR_CHECK is passed a non-NRF_SUCCESS argument.
Please do this, and let me know what is outputted to your log when the error occurs.
Best regards,
Karl