libuarte init with ANT softdevice ?

RE: libuarte init with ANT softdevice ?

Einar Thorsrud — Mon, 22 Feb 2021 14:29:28 GMT

Hi,

I don't know, really. I need to see all to get an overview. There is one thing we can try first, though. Referring to:

[quote user="RixtronixLAB"]

and the app gives me :

rror> app: Fatal error

arning> app: System reset

[/quote]

If you define DEBUG and DEBUG_NRF in your project settings (if you use a SES SDK project it should be enough to just select the "Debug" target), then you will get much more information in the error message. You should see where the fatal error comes from, and why. With that it should be much easier to pin-point the problem.

RE: libuarte init with ANT softdevice ?

RixtronixLAB — Mon, 22 Feb 2021 14:29:17 GMT

I used timer3 and it's now giving me a proper response,

NRF_LIBUARTE_ASYNC_DEFINE(libuarte1, 1, 3, 2, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 255, 3); //timer0 id =2, rtc1 id =2..

Thanks for helping, I'll keep posting and share the progress....thanks again..

RE: libuarte init with ANT softdevice ?

RixtronixLAB — Mon, 22 Feb 2021 14:23:42 GMT

is my "create_timers();" crashed with libuarte1 timer ?

RE: libuarte init with ANT softdevice ?

RixtronixLAB — Mon, 22 Feb 2021 14:21:25 GMT

Which part of code do you want to see ?

I make a copy of main function, hang on...

int main(void)
{
	ret_code_t err_code;
	float convert;
	
	 // This function contains workaround for PAN_028 rev2.0A anomalies 28, 29,30 and 31.
    
   uint32_t tick;			
		
	  
    log_init();
    utils_setup();
    softdevice_setup();
	    //**Init I2C and EEPROM before ant started, in order toclear EEPROM before sensor start TEST**
	    ssd1306_init_i2c(SSD1306_CONFIG_SCL_PIN, SSD1306_CONFIG_SDA_PIN);
			eeprom_cmd_clear_distance(); 
	    //initialize time for distance saving
			m_speed_calc_data.acc_evt_time=0; 
	
    profile_setup();
	
	  create_timers();
	 
	  /* Init systick driver */
    nrf_drv_systick_init();
	 
	 app_timer_start(m_repeated_timer_id, APP_TIMER_TICKS(1000), NULL);
	   //SSD1306 Code
	    // ssd1306_init_i2c(SSD1306_CONFIG_SCL_PIN, SSD1306_CONFIG_SDA_PIN);
	   ssd1306_begin(SSD1306_SWITCHCAPVCC, SSD1306_I2C_ADDRESS, false);
	   ssd1306_clear_display(); //Rixtronix LAB
		    //nrf_delay_ms(1000);
        ssd1306_display();
	      nrf_delay_ms(500);
	      NRF_LOG_INFO("--- testdrawline ---");
        //
        ssd1306_draw_circle(SSD1306_LCDWIDTH / 2, SSD1306_LCDHEIGHT / 2, 30, WHITE);
	       nrf_delay_ms(1000);
        ssd1306_display();
	        nrf_delay_ms(1000);
           //convert int32_t to float
         ieee_float();	
     				nrf_delay_ms(1000); 
			
			 /**********init from libuarte*****/
			 //err_code=nrf_drv_clock_init();
			 //APP_ERROR_CHECK(err_code);
			// NRF_LOG_INFO("Err_code nrf_drv_clk %u",err_code);
			 
			 //nrf_drv_clock_lfclk_request(NULL);
				
				nrf_libuarte_async_config_t nrf_libuarte_async_config1 = {
            .tx_pin     = SER_APP_TX_PIN,
            .rx_pin     = SER_APP_RX_PIN,
            .baudrate   = NRF_UARTE_BAUDRATE_9600,
            .parity     = NRF_UARTE_PARITY_EXCLUDED,
            .hwfc       = NRF_UARTE_HWFC_DISABLED,
            .timeout_us = 1000,
            .int_prio   = APP_IRQ_PRIORITY_LOW
			      
    };
		err_code=nrf_libuarte_async_init(&libuarte1, &nrf_libuarte_async_config1, uart_event_handler1, (void *)&libuarte1);
			APP_ERROR_CHECK(err_code);
		NRF_LOG_INFO("Err_code libuarte_init libuarte1 %u",err_code);
  	nrf_libuarte_async_enable(&libuarte1);

    GPS_Init();		
		/**********init from libuarte*****/

RE: libuarte init with ANT softdevice ?

Einar Thorsrud — Mon, 22 Feb 2021 14:17:45 GMT

I see. There should be no difference at all. You just need to ensure that you do not try to use peripherals that are used by the SoftDevice or other libraries. If you still struggle, perhaps you can share your code so that I can see?

RE: libuarte init with ANT softdevice ?

RixtronixLAB — Mon, 22 Feb 2021 14:17:16 GMT

which part of application do you want to see ?

RE: libuarte init with ANT softdevice ?

RixtronixLAB — Mon, 22 Feb 2021 14:16:49 GMT

rror> hardfault: HARD FAULT at 0x00017FB8

<error> hardfault: R0: 0x20001064 R1: 0x39000000 R2: 0x00000010 R3: 0x0

0000F

rror> hardfault: R12: 0x20000E08 LR: 0x0001E39F PSR: 0x21000029

<error> hardfault: Cause: Data bus error (PC value stacked for the exception ret

n points to the instruction that caused the fault).

rror> hardfault: Bus Fault Address: 0x39000000

RE: libuarte init with ANT softdevice ?

RixtronixLAB — Mon, 22 Feb 2021 14:15:57 GMT

I'm using libuarte for UART1 only now,

NRF_LIBUARTE_ASYNC_DEFINE(libuarte1, 1, 2, 2, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 255, 3); //timer0 id =2, rtc1 id =2

and the app gives me :

rror> app: Fatal error

arning> app: System reset

RE: libuarte init with ANT softdevice ?

RixtronixLAB — Mon, 22 Feb 2021 14:12:34 GMT

it works well when I implement from the libuarte example, but when I merge with ANT and softdevice, it's stop working....

RE: libuarte init with ANT softdevice ?

Einar Thorsrud — Mon, 22 Feb 2021 14:07:23 GMT

Hi,

It is not clear to me how your application looks, so it is difficult to suggest much.

I noticed this though:

[quote user=""]

I commented out

//err_code=nrf_drv_clock_init();

//nrf_drv_clock_lfclk_request(NULL);

//nrf_libuarte_async_enable(&libuarte1);

to stabilize the application,

[/quote]

The first two is not directly related to the libuarte, and if you use a SoftDevice the LFCKL is allready started, so it does not matter if you use it or not. However, you need to call nrf_libuarte_async_enable() before using it. To be honest it is not so reassuring if you comment out blindly in order to attempt to stabilize the application. May I suggest you refer to the libuarte example in the SDK? That shows you how to use it.

Once you understand the example you can copy it to your application and make necessary adjustments, where we come to this:

[quote user=""]

Is
NRF_LIBUARTE_ASYNC_DEFINE(libuarte, 0, 0, 0, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 255, 3);

conflicting with my current UART setting for NRF_LOG in softdevice ? it's using the same port UART0

[/quote]

Yes, you cannot use the same peripheral for two things (at the same time). The libuarte is quite resource intensive, and needs a UARTE instance two timers and and RTC, as you can see from the API doc of NRF_LIBUARTE_ASYNC_DEFINE. You need to ensure that there are no overlaps. When doing so, keep in mind that the SoftDevice use TIMER0 and RTC0. So that cannot be used. The app_timer use RTC1, which you typically want to use, so that should also be avoided.

RE: libuarte init with ANT softdevice ?

RixtronixLAB — Mon, 22 Feb 2021 14:00:48 GMT

Video shot :

nRF52840 HARD FAULT Softdevice libuarte ANT

RE: libuarte init with ANT softdevice ?

RixtronixLAB — Mon, 22 Feb 2021 13:48:20 GMT

SDK config

RE: libuarte init with ANT softdevice ?

RixtronixLAB — Mon, 22 Feb 2021 13:47:32 GMT

RE: libuarte init with ANT softdevice ?

RixtronixLAB — Mon, 22 Feb 2021 13:46:06 GMT

//NRF_LIBUARTE_ASYNC_DEFINE(libuarte, 0, 0, 0, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 255, 3);
NRF_LIBUARTE_ASYNC_DEFINE(libuarte1, 1, 2, 2, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 255, 3); //timer0 id =2, rtc1 id =2
.
.
.

				nrf_libuarte_async_config_t nrf_libuarte_async_config1 = {
            .tx_pin     = SER_APP_TX_PIN,
            .rx_pin     = SER_APP_RX_PIN,
            .baudrate   = NRF_UARTE_BAUDRATE_9600,
            .parity     = NRF_UARTE_PARITY_EXCLUDED,
            .hwfc       = NRF_UARTE_HWFC_DISABLED,
            .timeout_us = 1000,
            .int_prio   = APP_IRQ_PRIORITY_LOW
			      
    };
		err_code=nrf_libuarte_async_init(&libuarte1, &nrf_libuarte_async_config1, uart_event_handler1, (void *)&libuarte1);
			APP_ERROR_CHECK(err_code);
		NRF_LOG_INFO("Err_code libuarte_init libuarte1 %u",err_code);
  	nrf_libuarte_async_enable(&libuarte1);

    GPS_Init();

RE: libuarte init with ANT softdevice ?

RixtronixLAB — Sat, 20 Feb 2021 23:42:01 GMT

I get :

nfo> app: Err_code libuarte_init libuarte1 = 0