UART and Timer conflict

RE: UART and Timer conflict

Edvin — Wed, 23 Jan 2019 10:11:54 GMT

Hello,

I would need a better description. I suggest you create a separate ticket describing your issue, if you haven't done this already.

RE: UART and Timer conflict

ps_anu — Wed, 23 Jan 2019 09:32:36 GMT

hi, edvin i am also having some issues while merging the uart ,twi and timer , please help me . i am using nrf52382 segger 15version . see my code

int main(void)


{
bool erase_bonds;



    // Initialize.
    uart_init();
    log_init();
    timers_init();
    buttons_leds_init(&erase_bonds);
    power_management_init();
    ble_stack_init();
    gap_params_init();
    gatt_init();
    services_init();
    advertising_init();
    conn_params_init();

  printf("\r\nUART started.\r\n");
    NRF_LOG_INFO("Debug logging for UART over RTT started.");
    advertising_start();


     

twi_init();
  LM75B_set_mode();
    

uint32_t time_ms = 50000; //Time(in miliseconds) between consecutive compare events.
    uint32_t time_ticks;
    uint32_t err_code = NRF_SUCCESS;

   
             

    //Configure all leds on board.
    bsp_board_init(BSP_INIT_LEDS);

    //Configure TIMER_LED for generating simple light effect - leds on board will invert his state one after the other.
    nrf_drv_timer_config_t timer_cfg = NRF_DRV_TIMER_DEFAULT_CONFIG;
   err_code = nrf_drv_timer_init(&TIMER_SENSOR, &timer_cfg, timer_sensor_event_handler);
    APP_ERROR_CHECK(err_code);

      nrf_drv_timer_extended_compare(
         &TIMER_SENSOR, NRF_TIMER_CC_CHANNEL0, time_ticks, NRF_TIMER_SHORT_COMPARE0_CLEAR_MASK, true);


    time_ticks = nrf_drv_timer_ms_to_ticks(&TIMER_SENSOR, time_ms);

     NRF_LOG_INFO("SUCCESS1"); 




 

    // Start execution.
    
    while (true)
    {
        nrf_delay_ms(6000);

       while (m_xfer_done == false);

         m_xfer_done = false;
                
		uint8_t reg[2] = {0x00U};
        err_code = nrf_drv_twi_tx(&m_twi,LM75B_ADDR, reg, sizeof(reg), true);
		APP_ERROR_CHECK(err_code);
		while (m_xfer_done == false);
		nrf_delay_ms(5);
		
	        m_xfer_done = false;
		ret_code_t err_code1 = nrf_drv_twi_rx(&m_twi,LM75B_ADDR, &m_sample, sizeof(m_sample));
		APP_ERROR_CHECK(err_code1);
                NRF_LOG_INFO("%d", m_sample);

}
   
 
               }

RE: UART and Timer conflict

Edvin — Wed, 16 May 2018 06:17:55 GMT

Hello,

Glad you found a solution that worked for you. You can alternatively try to set a prescaler != 0, which will slow the timer down, if you want to use the timer directly.

Best regards,

Edvin

RE: UART and Timer conflict

paul_tanner — Tue, 15 May 2018 16:23:55 GMT

Thx. I managed to get in working on 12.2 In the process I found that the max timer period was less that the 30 secs I needed. So I worked around that by counting a number of callbacks. I am aware that a better solution would be to use app_timer which is more flexible.

Thx for all the help Edvin

RE: UART and Timer conflict

Edvin — Fri, 04 May 2018 09:21:01 GMT

Oh sorry,

Yes, I misread that.

You can either port the example back to SDK.12.2, or port the rest of the application to SDK14. this example for SDK12.2.0 attached.

devzone.nordicsemi.com/.../uart_2B00_timer_5F00_12_5F00_2.zip

If you want to port the rest of your application to SDK14 instead, you must check the release notes for SDK13 and SDK14, as they handle the most significant changes between the major versions of the SDK.

Best regards,

Edvin

RE: UART and Timer conflict

paul_tanner — Fri, 04 May 2018 07:36:24 GMT

You might have missed my last reply. It *is* working on macos/screen now. I think I had a port problem before.

Anyway, as I need single-shot mode I'll have to do this with app_timer. That's my next step.

Then I need to bring all my code up to SDK14 if it wont work on 12_2.

Regards, Paul

RE: UART and Timer conflict

Edvin — Fri, 04 May 2018 07:28:51 GMT

Can you please try the application with another UART terminal? Maybe if you have access to a windows computer, can you try to use the Termite terminal? I also see some weird behavior on Putty, but I am not familiar with the settings in this terminal.

The project is working. If you want confirmation, you can try to connect the UART to something else, like another DK, (pin P0.06 and P0.08),

BR,

Edvin

RE: UART and Timer conflict

paul_tanner — Thu, 03 May 2018 16:46:47 GMT

OK that works so output to the terminal is OK.
... and strangely input is now working too. I must have been mistaken when I first tried this or the port got stuck somehow.

So we're almost there. I just need to port this back or, better, my main body of code forward from SDK 12_2.

What's the best way to review what changes are going to be necessary?

Many thx.

Regards, Paul

RE: UART and Timer conflict

Edvin — Thu, 03 May 2018 13:35:40 GMT

do you have any settings on your terminal?

In my UART terminal, I have:

115200 Baudrate,

8 data bits,

1 stop bit,

parity none,

flow control none

Append LF (this one shouldn't matter)

If you try to change the timeout handler to this, will you see the '1's printed on the terminal then?

        case NRF_TIMER_EVENT_COMPARE0:
            NRF_TIMER4->EVENTS_COMPARE[0] = 0;
            nrf_gpio_pin_toggle(US_TSET_PIN);
			uint8_t cr = '1';
			while (app_uart_put(cr) != NRF_SUCCESS);
            break;

BR,

Edvin

RE: UART and Timer conflict

paul_tanner — Thu, 03 May 2018 12:48:09 GMT

Thx Edvin,

(I did include the path to nrf_drv_timer.h but never mind)

I am now using your latest setup.

It compiles OK and the timer is working

However, for some reason the terminal is not echoing. I'm using macos screen at 115200.

(I have wondered in the past whether this a reasonable way to work with the pca10040 uart?)

So I commented out timer_int() and then the terminal works.

This is telling me that the timer/uart conflict remains

Regards, Paul

RE: UART and Timer conflict

Edvin — Thu, 03 May 2018 12:00:42 GMT

Did you include the path to the nrf_drv_timer.h file? Also, did you enable the timer in sdk_config.h?

There are many things that are changed between SDK12 and SDK14, so I don't think you will be able to run the main.c code here in SDK14. I changed some parts (removed the SPI) and changed sdk_config.h, which decides what peripherals that are activated.

devzone.nordicsemi.com/.../uart_2B00_timer.zip

Try to unzip the attached project so that you get the path:

SDK14.0.0\examples\peripheral\timer+uart\pca10040\armgcc\makefile

Then run cmd from the armgcc folder, and run:

"make clean && make -j3 && nrfjprog -e && nrfjprog --program _build\nrf52832_xxaa.hex --verify && nrfjprog --reset"

When the DK is connected. You should see that LED1 starts blinking, and it should echo everything it receives on UART (using the USB and a UART terminal).

RE: UART and Timer conflict

paul_tanner — Thu, 03 May 2018 10:45:26 GMT

Thx @Edvin and sorry for my delay in replying.

OK. Finally got some time to look into this but having issues with compilation.

I put your code in a copy of examples/uart.

Using SDK14 for pca10040.

I took the config from examples/uart
+ added to Makefile: $(SDK_ROOT)/components/drivers_nrf/timer/nrf_drv_timer.c \

I get...

In file included from ../../../../../../components/libraries/util/app_error.h:58:0,
from ../../../main.c:26:
../../../../../../components/libraries/experimental_log/src/nrf_log_internal.h:105:38: error: pasting "m_nrf_log_" and ""APP"" does not give a valid preprocessing token
#define NRF_LOG_MODULE_DATA CONCAT_3(m_nrf_log_,NRF_LOG_MODULE_NAME,_logs_data)
^
../../../../../../components/libraries/util/nordic_common.h:133:31: note: in definition of macro 'CONCAT_3_'
#define CONCAT_3_(p1, p2, p3) p1##p2##p3

Presumably there are other things i need to do to my config?

May I have a copy of the config file you are using pls and anything else I need to change.

RE: UART and Timer conflict

Edvin — Wed, 25 Apr 2018 07:48:31 GMT

paul_tanner:

Could you please check the file I added for masloooo?

If not, could you specify the issue?

BR,

Edvin

RE: UART and Timer conflict

Edvin — Wed, 25 Apr 2018 07:11:14 GMT

masloooo

There were a few things. First, your timer config was not set, which uses the default TIMER4 values from nrf_drv_config.h. On timer 4, this was set to a 16bit timer, so you would not get the 10µs that you intended. Or actually, you would, but if you want to be able to see it, you will need a larger bit width. Changed it to 32. Change back if you feel like it.

Also, I changed the pin you toggled, to be able to see the toggling (P0.17 = LED_0). Change back if you please.

Then there was a while loop in your timer_init() function, which meant it never reached the end of this function. Not a problem in itself, but if you want to add something after timer_init(), this should be moved to the end of main().

If you want to see a string repeated on the uart (more than a character) you need to have the while(app_uart_get/put) in a while loop. Please see the attached main.c file, and try to replace the main.c in your project with this one.

If you want a more dynamic uart, you should look into how it is done in the ble_app_uart example, which uses an event handler for the uart as well.

Also, if you are in the early development stage, I would recommend to move to a newer SDK (14 or 15).

devzone.nordicsemi.com/.../main.c

Best regards,

Edvin

RE: UART and Timer conflict

paul_tanner — Tue, 24 Apr 2018 17:46:38 GMT

I get the problem when I have no blocking code. Maybe I'll have to do a reduced version after all.

RE: UART and Timer conflict

paul_tanner — Tue, 24 Apr 2018 14:45:27 GMT

I have the same on SDK 12.2 with armgcc. My board is non-standard but the issue seems to be exactly the same.

RE: UART and Timer conflict

masloooo — Tue, 24 Apr 2018 14:23:37 GMT

The problem is: when I init the timer, I assume it's a endless loop as its _WFI() functions.

Then I try to comment this part, then I init the UART to get exact strings I send.

The UART test code should be:

while(app_uart_get(&cr)!=NRF_SUCCESS);

while(app_uart_put(cr)!=NRF_SUCCESS);

I made some changes before I upload the code...And it seems I mistakenly deleted the following line.

RE: UART and Timer conflict

Edvin — Tue, 24 Apr 2018 14:14:04 GMT

Ok,

So the problem is not that nothing is working when you enable the uart. The problem is that when you enable the uart (I assume that you mean the part between the comments:

// uart test

...

// uart test done

The call:

while(app_uart_get(&cr) != NRF_SUCCESS);

is a blocking call. When you include this, then nothing will happen before you get a character on the uart. You can test this by sending a character on the uart. Disable the flow control in uart_init() first, as many UART terminals for computers are not too god at handling flow control.

Best regards,

Edvin

RE: UART and Timer conflict

masloooo — Tue, 24 Apr 2018 12:34:56 GMT

sorry for the wrong info.. the version I'm using is SDK 11

RE: UART and Timer conflict

masloooo — Tue, 24 Apr 2018 11:05:12 GMT

downloading...

BTW r u using the code in arm4(within my code path)?

RE: UART and Timer conflict

Edvin — Tue, 24 Apr 2018 10:35:46 GMT

Ok. Still missing quite a few variables.

Are you able to compile your project in an unmodified version of the sdk? Try to download it from here, and extract your project into it, and see what files you are missing. I need them to be able to compile the project.

Best regards,

Edvin

RE: UART and Timer conflict

paul_tanner — Tue, 24 Apr 2018 07:57:28 GMT

sorry for the delay in replying. I was away from the lab. back now but I need to make a much simpler example which does not use special hardware. Thx to masloooo for his which seems to be showing up the same issue. I will check again to see if anything gets logged.

RE: UART and Timer conflict

masloooo — Tue, 24 Apr 2018 07:44:17 GMT

My settings are included in the nrf_drv_config.h

RE: UART and Timer conflict

Edvin — Tue, 24 Apr 2018 07:06:23 GMT

I can't find the sdk_config.h file for your project. Is it included? Also, can you check your APP_ERROR_CHECK(...)s? Do any of them receive an input that is not NRF_SUCCESS?

You can check this by enabling DEBUG in your preprocessor defines, and then set a breakpoint on line 48 in app_error.c. Check if the breakpoint is hit sometime during debug.

Best regards,

Edvin

RE: UART and Timer conflict

masloooo — Mon, 23 Apr 2018 15:34:01 GMT

hi, Edvin.

I'm using SDK 12.1.0 and code in PCA10040. I attach the project heredevzone.nordicsemi.com/.../timer_2B00_uart.rar.

I haven't check the handler... I just noticed that if I init the timer(0-4) before UART, then UART won't function.

Same thing happens when I init UART(then timer won't work.)