Single bank DFU failed over Meizu phone and 360phone

[Milk]

First,the meizu phone can dfu successfully in the dual bank mode, So do the 360 phone. But in single bank DFU,this two kinds of phone failed, So I make the programm enter the debug mode, It stopped at the file app_scheduler.c about the line 133 in the bootloader project of SDK9.0. It generated the error_code = NRF_ERROR_NO_MEM, I found the variable event_index is equal to 0xFFFF,it means that the function APP_SCHED_QUEUE_FULL() is equal to true.So I comment the function APP_SCHED_QUEUE_FULL(), then DFU retry again,at last,dfu successed.

I have a question,would commenting the APP_SCHED_QUEUE_FULL() make some other problems? The details over the OTA app on RedMi3 as follows：

[bjorn-spockeli]

I do not think that commenting out the

 if (!APP_SCHED_QUEUE_FULL())
        {
            event_index       = m_queue_end_index;
            m_queue_end_index = next_index(m_queue_end_index);
        }

check is a good idea, the check is there for a reason. There is no single bank OTA bootloader in SDK v9.0.0, so I am assuming that you have modified the dual bank example. If that is the case, how have you modified it?

[Milk]

The file single_bank_serial_s110 is not single bank example in SDK v9.0.0? I admit I modified the dual bank example to become so-called single bank OTA by myself. The check code as above shows,what is the reason for it's existing? Is there some ways to make the OTA successfully changing the app code(like the Master Control Panel code) instead of changing the bootloader code?

[bjorn-spockeli]

As the name implies, its a serial bootloader using a wired serial interface, not an Over-the-Air Bluetooth Low energy bootloader.

[bjorn-spockeli]

Could you try increasing the SCHED_QUEUE_SIZE define in main.c to a higher value, e.g. 30

#define SCHED_QUEUE_SIZE                30