DFU app update over BLE with non-BLE app.

RE: DFU app update over BLE with non-BLE app.

SL06 — Wed, 05 Feb 2020 17:24:39 GMT

This is the link that I was using for the RAM and FLASH position:https://devzone.nordicsemi.com/nordic/short-range-guides/b/getting-started/posts/adjustment-of-ram-and-flash-memory

For my s132 softdevice v7.0.0 the Ram start at 0x20001668 and Flash start at 0x26000 work just fine with my apps without the softdevice. I had also to decrease the HEAP size to solve an error.

I played also with the app version with the softdevice but did no solved completely the error mention above:

ASSERTION FAILED at ../../../../../../integration/nrfx/nrfx_glue.h:107

A work around was to remove the line SOFTDEVICE_PRESENT in the preprocessor. I used the RAM and flash setting above. The ESB was not working until I change .radio_irq_priority = 1, to 2 in the nerf_esb.h header file.

I don't need the softdevice version since the first app is now working properly , so I won't pursue that route. Your help was greatly appreciate.

RE: DFU app update over BLE with non-BLE app.

Edvin — Tue, 04 Feb 2020 08:14:54 GMT

[quote user="SL06"]I am not sure what is the problem. Is there a priority not define, a conflict, or something else.[/quote]

That sounds like a conflict, yes.

I suspect this is already what you are doing, but you need your application to be able to run while having the softdevice, so for now you don't need to worry about the bootloader.

The INTERRUPT_PRIORITY_IS_VALID() define comes from nrfx_glue.h:

#ifdef NRF51
#ifdef SOFTDEVICE_PRESENT
#define INTERRUPT_PRIORITY_IS_VALID(pri) (((pri) == 1) || ((pri) == 3))
#else
#define INTERRUPT_PRIORITY_IS_VALID(pri) ((pri) < 4)
#endif //SOFTDEVICE_PRESENT
#else
#ifdef SOFTDEVICE_PRESENT
#define INTERRUPT_PRIORITY_IS_VALID(pri) ((((pri) > 1) && ((pri) < 4)) || \
                                          (((pri) > 4) && ((pri) < 8)))
#else
#define INTERRUPT_PRIORITY_IS_VALID(pri) ((pri) < 8)
#endif //SOFTDEVICE_PRESENT
#endif //NRF52

In your case, SOFTDEVICE_PRESENT should be true, and NRF51 should be false, hence, this line is what will be checked:

#define INTERRUPT_PRIORITY_IS_VALID(pri) ((((pri) > 1) && ((pri) < 4)) || \

(((pri) > 4) && ((pri) < 8)))

So your priority needs to be either 2, 3, 5, 6, or 7 when you are working on an nRF52, and you are using the softdevice. The reason for this is that the interrupt priority levels 0, 1, and 4 is reserved by the softdevice:

https://infocenter.nordicsemi.com/topic/sds_s132/SDS/s1xx/processor_avail_interrupt_latency/exception_mgmt_sd.html

Not sure if the link you provided is the one you intended to provide, but when you start your application, the log should tell you if you should adjust your ram and flash settings.

Best regards,

Edvin

RE: DFU app update over BLE with non-BLE app.

SL06 — Mon, 03 Feb 2020 22:45:21 GMT

Hi, I have fiddle around with my project changing FLASH and RAM address without success and decide finally to use blinky_S132 as a template and transpose my program in it.

It took several hours. I had to set the start addresses for RAM and FLASH according to those recommandation https://devzone.nordicsemi.com/f/nordic-q-a/33077/sdk15-nrfx-error-numbering

I had also to reduce the heap size by half to 4096. I read in ticket that it could be set to 0 if I use the s132 softdevice. I have not tried.

I am at the point now that my program compile without error, start te setup part but stop after a few line , where I am trying to init the twi driver with the following routine:

uint32_t nrf_drv_mpu_init(void)
{
    uint32_t err_code;
    
    const nrfx_twi_config_t twi_mpu_config = {
       .scl                = MPU_TWI_SCL_PIN,
       .sda                = MPU_TWI_SDA_PIN,
       .frequency          = NRF_TWI_FREQ_400K,
     //  .interrupt_priority = APP_IRQ_PRIORITY_HIGHEST,
       //.clear_bus_init     = false
    };
    
    err_code = nrfx_twi_init(&m_twi_instance, &twi_mpu_config, nrfx_mpu_twi_event_handler, NULL);
    if(err_code != NRF_SUCCESS)
	{
		return err_code;
	}
    
    nrfx_twi_enable(&m_twi_instance);
	
	return NRF_SUCCESS;
}

The error on the Segger RTT terminal is :

00> <error> app: ASSERTION FAILED at ../../../../../../integration/nrfx/nrfx_glue.h:107

Line 107 in nrfx_glue.h is : ASSERT(INTERRUPT_PRIORITY_IS_VALID(priority));

static inline void _NRFX_IRQ_PRIORITY_SET(IRQn_Type irq_number,
                                          uint8_t   priority)
{
    ASSERT(INTERRUPT_PRIORITY_IS_VALID(priority));
    NVIC_SetPriority(irq_number, priority);
}

I am not sure what is the problem. Is there a priority not define, a conflict, or something else.

Thanks for helping.

RE: DFU app update over BLE with non-BLE app.

Edvin — Mon, 03 Feb 2020 14:16:01 GMT

Hello,

If you use a BLE bootloader, remember that the bootloader itself use the softdevice, so it is not deleted. If you look in the SDK\examples\peripheral\blinky\pca10040 folder, you see that there are three project files. One blank, one mbr and one for the softdevice. The differences are mostly linking and RAM placement, but if possible, I suggest you use a project file that already has the softdevice included. You don't need to actively use the softdevice in your application, but since the bootloader requires it, you can't save space by deleting it either way.

The other approach is to fiddle around with the project settings, so that it will run with a softdevice in the bottom of flash and ram.

RE: DFU app update over BLE with non-BLE app.

SL06 — Sun, 02 Feb 2020 18:55:49 GMT

I have tried the nrtutil settings generate command, since I did not had problem with the ble_app_hrs test, and was not shure of the purpose. Should I lookout this ?

RE: DFU app update over BLE with non-BLE app.

SL06 — Sun, 02 Feb 2020 18:16:27 GMT

I have forgot to mention. I am using SDK v16.