Device hang in libuarte function when no debugger run

RE: Device hang in libuarte function when no debugger run

Karl Ylvisaker — Wed, 24 Feb 2021 14:02:40 GMT

[quote user="Jacob Lee"]Thanks for the reply.[/quote]

No problem at all, I am happy to help!

[quote user="Jacob Lee"]I think I found the root cause.[/quote]

I am glad to hear that you have found the root cause of the issue.

[quote user="Jacob Lee"]

I comment the all fprintf to solve this issue.

So, the fprintf will make device hang if it's not in the debug mode.

[/quote]

Do you have RETARGET defined to 1 in your sdk_config?

Did you also do as I recommended in my previous comment, and add error code checks to the returned error codes, and defined DEBUG in preprocessor defines?
These two things will be very helpful during future development.

If you issue is resolved, we may close this ticket. If so, please do not hesitate to open a new ticket if you should encounter any issues or question in the future! :)

Best regards,
Karl

RE: Device hang in libuarte function when no debugger run

Jacob Lee — Wed, 24 Feb 2021 02:39:11 GMT

Hi Karl,

Thanks for the reply.

I think I found the root cause.

I imported a library in out project and it use the fprintf(stdout..) to show message.

I comment the all fprintf to solve this issue.

So, the fprintf will make device hang if it's not in the debug mode.

Maybe this issue can be related to this:

devzone.nordicsemi.com/.../133776

RE: Device hang in libuarte function when no debugger run

Karl Ylvisaker — Tue, 23 Feb 2021 10:14:14 GMT

Hello Jacob Lee,

[quote user=""]But if running without debugging, device will hang after uart start to tranxfer data.
(I create a timer to print log(RTT) periodically to check if device alive or not)[/quote]

Could you make sure that you have DEBUG defined in your preprocessor defines, like shown in the included image?

I also notice that you do not check the returned error codes in your code, such as in your rs485_byte_send function.
You should always pass the returned error codes to an APP_ERROR_CHECK to see if the function call was successful. These checks are your only way of knowing whether a function call has failed (for whatever reason), or if your program can proceed as usual.
If you have defined DEBUG as mentioned, any non NRF_SUCCESS returned error code will generate a detailed error message printed by your logger.

Please add checks to all returned error codes and add the DEBUG define to preprocessor defines, and let me know if any error message is printed when you run the device without debugging.

Looking forward to resolve this issue together!

Best regards,
Karl

RE: Device hang in libuarte function when no debugger run

Jacob Lee — Mon, 22 Feb 2021 09:19:49 GMT

The SDK version is 16.0.0