I am using the NRF2840 and WaveShare's 2.9 epaper display to make a cutdown tool, but I am facing some problems.

[leo li]

I have realized the cutdown function with the examples. But now I want to reflesh the number I have published, which means that I first publish a number, then I want to publish a new number. But now, the new number i published can't preemptive the old number. I want to know how to replace the old number. Thanks for all of your effort.

yours sincerely,

Leo Li.

[Edvin]

I don't know your setup Leo, but if the issue is that the numbers are stacked on top of each other, it sounds like you need to clear the screen first. How you do that, I don't know, but it is probably documented somewhere around the same place as you found out how to write to the epaper display.

[leo li]

Thank you for your reply. I am sorry that I don't describe my question very clearly. I have update my question in the previous answers by awneil. You can go to that answer to know further things. Thank you very much.

[leo li]

Yes, this is exactly what I mean. I want to abort the current countdown and start it with the new number. But I don't know how to realize this function. I just rewrite the nus_data_handler() function with a very easy logic. I changed the receive data into int, and let it decrease. The code is like this:

static void nus_data_handler(ble_nus_evt_t * p_evt)
{
     if (p_evt->type == BLE_NUS_EVT_RX_DATA)
    {
    
        int time_now_s;

        time_now_s=atoi((char*)p_evt->params.rx_data.p_data);
        ...
        ...
        ...
         while(time_now_s>0) 
		 {
            time_now_s--;
            ...
            ...
            ...

And the service_init() function is like this:

static void services_init(void)
{
    uint32_t           err_code;
    ble_nus_init_t     nus_init;
    nrf_ble_qwr_init_t qwr_init = {0};
	//	ble_nus_evt_t *pp_evt;

    // Initialize Queued Write Module.
    qwr_init.error_handler = nrf_qwr_error_handler;

    err_code = nrf_ble_qwr_init(&m_qwr, &qwr_init);
    APP_ERROR_CHECK(err_code);

    // Initialize NUS.
    memset(&nus_init, 0, sizeof(nus_init));
	
	
    nus_init.data_handler = nus_data_handler;
	
    err_code = ble_nus_init(&m_nus, &nus_init);
    APP_ERROR_CHECK(err_code);
}

I don't know whether these code will help you to understand my meanings or not.

Thank you for your continuous attention to my questions.

[leo li]

I have update some of my code in the reply to Edvin. Maybe that will help you to understand my thoughts. I just can't abort the countdown, maybe it's because of that the Nordic UART Service is FIFO?

Thank you for your continuous attention to my questions.

[awneil]

leo li said:

I just can't abort the countdown

Why not?

What's the problem?

leo li said:

maybe it's because of that the Nordic UART Service is FIFO

Why would that be a problem?

It's your code that does the countdown - so you should know how to abort it!

Can you get this working on its own - without the added complication of BLE?

It sounds like a problem with your system design ...

[Edvin]

Ok, I see.

The issue is that you are handling your entire countdown in the nus_data_handler(). Hence, when a new number enters, it is not able to handle that callback until you finish the handler that you are in now. They are two equal events with the same priority, so the new number is not called until the previous has returned.

I suggest you do something like this:

volatile uint32_t time_now_s = 0;       // remember to use volatile
volatile bool start_countdown = false;  // remember to use volatile
static void nus_data_handler(...)
{
    if (p_evt->type == BLE_NUS_EVT_RX_DATA)
    {
        time_now_s = atoi((char*)p_evt->params.rx_...;
        start_countdown = true;
    }
}

static void start_my_countdown()
{
    while(time_now_s > 0)
    {
        time_now_s--;
        ...
    }
}

main()
{
    ...
    for(;;)
    {
        if(start_countdown)
        {
            start_my_countdown();
            start_countdown = false;
        }
    }
}

But that is also not perfect. You should really use a timer that has a timeout of 1 second or whatever resolution you need, and use the timeout handler to decrement time_now_s and update the display. This way, you will allow the nRF to go to sleep to save some power while you are running the countdown as well.

[leo li]

That's exactly what I mean. I solved the problem with your help. Thank you very much for your kindly help these days.