52832，SDK15.3，APP_ERROR_CHECK(), PWM

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

yzfy_12345 — Wed, 18 Oct 2023 01:03:12 GMT

Thank you very much!

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

Vidar Berg — Fri, 13 Oct 2023 11:57:10 GMT

Hi,

I see. I don't think the UART is directly related to the issue, but it may affect the timing. Please add more logging to your code. For example, "Start playing sound" when My_PWM_Start() is called, and "Stop playing sound" when PWM_Stop() is called, then upload your log here.

Thanks,

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

yzfy_12345 — Fri, 13 Oct 2023 01:02:17 GMT

Hi：

My program is based on

...\nRF5_SDK_15.3.0_59ac345\examples\ble_peripheral\ble_app_uart\pca10040\s132\arm5_no_packs

to develop.

Yes, When I Open the UART，It seems that mistakes are more likely to occur。

My project is Open UART as needed. The UART is normally turned off to save power.

as follow:

When UART is needed: uart_init() -> UART Tx/Rx Data -> my_app_uart_close()

When Data Tx/Rx finish, will colse the UART.

void uart_init(void)
{
    uint32_t                     err_code;
    app_uart_comm_params_t const comm_params =
    {
        .rx_pin_no    = RX_PIN_NUMBER,
        .tx_pin_no    = TX_PIN_NUMBER,
        .rts_pin_no   = RTS_PIN_NUMBER,
        .cts_pin_no   = CTS_PIN_NUMBER,
        .flow_control = APP_UART_FLOW_CONTROL_DISABLED,
        .use_parity   = false,
#if defined (UART_PRESENT)
        .baud_rate    = NRF_UART_BAUDRATE_115200
#else
        .baud_rate    = NRF_UARTE_BAUDRATE_115200
#endif
    };

    APP_UART_FIFO_INIT(&comm_params,
                       UART_RX_BUF_SIZE,
                       UART_TX_BUF_SIZE,
                       uart_event_handle,
                       APP_IRQ_PRIORITY_LOWEST,
                       err_code);
		
    APP_ERROR_CHECK(err_code);
}

void my_app_uart_close(void)
{
		uint32_t err_code;
	
		if(bMy_UART_Enable_Fg == false)			// 如果当前UART没有打开，则不需要重复关闭
		{		return;		}
		bMy_UART_Enable_Fg = false;
		
		nrf_uart_task_trigger(NRF_UART0, NRF_UART_TASK_STOPRX);		// 触发串口停止接收事件
		nrf_uart_event_clear(NRF_UART0, NRF_UART_EVENT_RXDRDY);		// 清空串口接收标志
	
		err_code = app_uart_close();						// 关闭串口 
		APP_ERROR_CHECK(err_code);
}

Thanks!

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

Vidar Berg — Wed, 11 Oct 2023 13:16:46 GMT

Hi,

Thanks for confirming. I asked because I wanted to know if there were errors elsewhere, for example, from the UART callback.

[quote userid="76678" url="~/f/nordic-q-a/104506/52832-sdk15-3-app_error_check-pwm/449746"]when I used the UART, also Frequent switch.[/quote]

Could you clarify what you mean? Is it that the error seems to occur more frequently when using UART?

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

yzfy_12345 — Wed, 11 Oct 2023 12:56:27 GMT

Hi:

Yes, I enable Debug, and the error raised in My_PWM_Start() -> APP_ERROR_CHECK(err_code);

the error code is 8.

Thanks!

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

Vidar Berg — Wed, 11 Oct 2023 11:52:08 GMT

Hi,

Have you enabled debug logging so you can see where the error(s) are raised?

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

yzfy_12345 — Wed, 11 Oct 2023 09:28:26 GMT

Hi:

My PWM use to control the Buzzer.

I dont't find what happen, when ignore the NRF_ERROR_INVALID_STATE error.

I find that, when ignore the error, The number of restarts will be reduced, and didn't find affect.

Does it have anything to do with UART? uart and pwm

when I used the UART, also Frequent switch.

UART_RX_PIN = P0.07; UART_TX_PIN = P0.05;

void uart_init(void)
{
    uint32_t                     err_code;
    app_uart_comm_params_t const comm_params =
    {
        .rx_pin_no    = RX_PIN_NUMBER,
        .tx_pin_no    = TX_PIN_NUMBER,
        .rts_pin_no   = RTS_PIN_NUMBER,
        .cts_pin_no   = CTS_PIN_NUMBER,
        .flow_control = APP_UART_FLOW_CONTROL_DISABLED,
        .use_parity   = false,
#if defined (UART_PRESENT)
        .baud_rate    = NRF_UART_BAUDRATE_115200
#else
        .baud_rate    = NRF_UARTE_BAUDRATE_115200
#endif
    };
		
		bMy_UART_Enable_Fg = true;		// true = 串口已打开，只在这个地方置真

    APP_UART_FIFO_INIT(&comm_params,
                       UART_RX_BUF_SIZE,
                       UART_TX_BUF_SIZE,
                       uart_event_handle,
                       APP_IRQ_PRIORITY_LOWEST,
                       err_code);
		
    APP_ERROR_CHECK(err_code);		// 屏蔽这里还有 PWM Initial 里面的，感觉重启的机率就很小了，或不出现
		
}

Thanks!

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

Vidar Berg — Wed, 11 Oct 2023 06:26:36 GMT

Hi,

Calling My_PWM_Start() when the PWM is already running might affect the PWM output. However, I wouldn't expect it to impact other parts of your application – but keep in mind that I don't know what role the PWM has in your app.

Have you tried to see what happens if you simply ignore the NRF_ERROR_INVALID_STATE error?

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

yzfy_12345 — Wed, 11 Oct 2023 01:43:30 GMT

Hi:

I want to sure that if I Mask this error, as follow:

//APP_ERROR_CHECK(err_code); // didn't process this sentence, With what effect?

If this statement is not executed, Will affect the whole program??

thank you very much!

Because this error is not very often appear, and Must appear when working with my equipment.

So I think you might have a hard time getting it out.

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

Vidar Berg — Tue, 10 Oct 2023 14:06:32 GMT

I'm not sure why you're receiving the NRF_ERROR_INVALID_STATE from My_PWM_Start() if the program always follows the sequence you described: My_PWM_Start(); -> My_PWM_Stop(); -> My_PWM_Start(); and so on. Could you provide a minimal example for me to debug here?

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

yzfy_12345 — Tue, 10 Oct 2023 12:10:32 GMT

error position：

void My_PWM_Start(void)

{

......

APP_ERROR_CHECK(err_code); // error position

......

}

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

yzfy_12345 — Tue, 10 Oct 2023 12:08:05 GMT

Hi:
Another problem.
When I frequency switch PWM, it will An error occurred, as follow:
APP_ERROR_CHECK(err_code); err_code = 8 = NRF_ERROR_INVALID_STATE

Why does this error occur?
1、Can I ignore this error?？？？？

2、have any Other solutions?？？？？

My Call example:
My_PWM_Start(); continue 1 second; My_PWM_Stop();
after a few minutes:
My_PWM_Start(); continue 1 second; My_PWM_Stop();
......

my pwm program as follow:

//===================================================
void My_PWM_Start(void)
{	
	uint32_t err_code;
	
    nrf_drv_pwm_config_t const config0 =
    {
        .output_pins =
        {
            //PN_BUZZER | NRF_DRV_PWM_PIN_INVERTED, 			// channel 0, High Level
						PN_BUZZER, 																		// channel 0, Low Level
            PN_NC1 | NRF_DRV_PWM_PIN_NOT_USED, 						// channel 1
            PN_NC2 | NRF_DRV_PWM_PIN_NOT_USED, 						// channel 2
            PN_NC3 | NRF_DRV_PWM_PIN_NOT_USED  						// channel 3
        },
        .irq_priority = APP_IRQ_PRIORITY_LOWEST,
        .base_clock   = NRF_PWM_CLK_500kHz,
        .count_mode   = NRF_PWM_MODE_UP,
        .top_value    = 125,										
        .load_mode    = NRF_PWM_LOAD_INDIVIDUAL,
        .step_mode    = NRF_PWM_STEP_AUTO
    };
		
    err_code = nrf_drv_pwm_init(&m_pwm0, &config0, NULL);	
	APP_ERROR_CHECK(err_code);																// error position
	
	static nrf_pwm_values_individual_t seq_values[] = 
	{
			{63,0,0,0},																
	};
		
	nrf_pwm_sequence_t const seq =
	{
		.values.p_individual = seq_values,
	    .length = NRF_PWM_VALUES_LENGTH(seq_values),
		.repeats = 0,
		.end_delay = 0
	};
	
    (void)nrf_drv_pwm_simple_playback(&m_pwm0, &seq, 1, NRF_DRV_PWM_FLAG_LOOP);
}

//==================================================
void My_PWM_Stop(void)
{
		nrf_drv_pwm_stop(&m_pwm0, false);
	
		nrf_drv_pwm_uninit(&m_pwm0);
	
		IO_BUZZER_OFF;
}

Thanks!

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

yzfy_12345 — Tue, 10 Oct 2023 07:39:25 GMT

thank you very much!

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

Vidar Berg — Tue, 10 Oct 2023 07:01:45 GMT

Hi,

Sorry, I noticed that you were using the NRF_DRV_PWM_PIN_INVERTED flag, and what I meant to suggest was that you remove it, but there was a typo in my sentence (edited now)

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

yzfy_12345 — Tue, 10 Oct 2023 06:58:43 GMT

Hi:

I Have been configuration PIN as "NRF_DRV_PWM_PIN_INVERTED", as follow: I only use one pin for buzzer.

.output_pins =
{
PN_BUZZER | NRF_DRV_PWM_PIN_INVERTED, // channel 0
PN_NC1 | NRF_DRV_PWM_PIN_NOT_USED, // channel 1
PN_NC2 | NRF_DRV_PWM_PIN_NOT_USED, // channel 2
PN_NC3 | NRF_DRV_PWM_PIN_NOT_USED // channel 3
},

when I stop the PWM, I test the result is the PIN (PN_BUZZER) output high level,

when I stop the PWM, I want the pin (PN_BUZZER) output low level.

I wish output Low level , when PWM idle

How to config?

thanks!

RE: 52832，SDK15.3，APP_ERROR_CHECK(), PWM

Vidar Berg — Tue, 10 Oct 2023 05:53:53 GMT

Hello,

The easiest way to debug issues like this is to enable debug logging and examine the crash log when the program enters the error handler (Error module). If you use the 'Debug' build configuration in Segger Embedded Studio, the crash log will include the file name and line number where the error occurred.

Are you invoking the error handler on APP_UART_COMMUNICATION_ERROR events as below? If so, consider commenting out APP_ERROR_HANDLER() to ignore UART errors and then check if you still experience resets.

2. Try to remove NRF_DRV_PWM_PIN_INVERTED flag from your PWM pin configuration.

Best regards,

Vidar