• State Not Answered
  • Replies 14 replies
  • Subscribers 63 subscribers
  • Views 5472 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 128781
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Nrf52832 app_uart problem

Kerem

Hello, although i have included every library and c file that is needed. i still get a declaration error. I'm almost sure that i enabled everything in sdk_config . I'm kinda stuck here and would appreciate any help.

nrf_drv_uart.h:88:30: error: 'NRF_UARTE1' undeclared here (not in a function)
Parents
  • 0

    But there is no UART1 on nRF52832, that is applicable only to nRF52840. Normally you should never reach such point in SDK files if you define global things (such as NRF52 and S132 etc.) properly in your project. What SDK do you use? What example you started from? What IDE/compilation chain do you use?

  • 0 in reply to endnode

    Normal people (unless they are 100% sure about what they are doing) do small steps and verify each of them that the thing compiles and also that it loads to the dev board and works as expected. if you did too many changes and now you don't know where is problem you will need to go back and start more or less from scratch but with smaller steps. Like start from perfectly working example and do just little change, remove small things here and there, recompile, test, then add few of your custom functions, again compile and test... etc. then you cannot end up in situation where you have new error in build log and you don't know what change lead to the error. So simple life can be.

Reply
  • 0 in reply to endnode

    Normal people (unless they are 100% sure about what they are doing) do small steps and verify each of them that the thing compiles and also that it loads to the dev board and works as expected. if you did too many changes and now you don't know where is problem you will need to go back and start more or less from scratch but with smaller steps. Like start from perfectly working example and do just little change, remove small things here and there, recompile, test, then add few of your custom functions, again compile and test... etc. then you cannot end up in situation where you have new error in build log and you don't know what change lead to the error. So simple life can be.

Children
No Data
Related