Single bank DFU failed over Meizu phone and 360phone

RE: Single bank DFU failed over Meizu phone and 360phone

bjorn-spockeli — Thu, 20 Apr 2017 09:41:03 GMT

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

#define SCHED_QUEUE_SIZE                30

RE: Single bank DFU failed over Meizu phone and 360phone

bjorn-spockeli — Tue, 15 Nov 2016 14:43:38 GMT

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

RE: Single bank DFU failed over Meizu phone and 360phone

Milk — Tue, 15 Nov 2016 12:14:47 GMT

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?

RE: Single bank DFU failed over Meizu phone and 360phone

bjorn-spockeli — Tue, 15 Nov 2016 10:13:07 GMT

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?