This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

UART API Explanation & FiFo

So I can see the "API Reference" documentation on the UART driver in the info centre, however this is all very low level and I am going to waste hours going through all this trying to decode it. Also the examples appear only to use a small subset of the available functionality.

So my question is where is the higher level explanation of the UART API functionality. For example is in the ble_app_uart example it seems a bit of a waste to allocate 256 byte read and write buffers and then to call uart_event_handle every time a byte arrives.

I frequently ask myself how much time, of Nordic employees (having to answer questions) and Nordic customer, is wasted by not providing some higher level functional descriptions of the API's?

Rant Over!

Parents
  • Hi Matt and thanks for your comments, no doubt I will end up following your suggestion. I suspect its a company cultural thing. The Nordic folks already understand how this stuff works inside and out consequently the pain of getting up to speed has passed for them, or is short lived as they can talk the creator of the API directly!

    The UART functionality seems comprehensive and I would like to architect my code efficiently, from the top down rather than hacking from the bottom up and getting very frustrated in the process. I need to create a parser on the data from the UART and I would like todo this optimally in terms of memory & cpu.

    It looks like there is no alternative; I will have to start the process of inefficient hacking and then start posting questions.

Reply
  • Hi Matt and thanks for your comments, no doubt I will end up following your suggestion. I suspect its a company cultural thing. The Nordic folks already understand how this stuff works inside and out consequently the pain of getting up to speed has passed for them, or is short lived as they can talk the creator of the API directly!

    The UART functionality seems comprehensive and I would like to architect my code efficiently, from the top down rather than hacking from the bottom up and getting very frustrated in the process. I need to create a parser on the data from the UART and I would like todo this optimally in terms of memory & cpu.

    It looks like there is no alternative; I will have to start the process of inefficient hacking and then start posting questions.

Children
No Data
Related