Custom bootloader: Can't reach interrupt handler

RE: Custom bootloader: Can't reach interrupt handler

Tim — Tue, 09 Apr 2019 06:56:09 GMT

Hi Bjørn,

Thanks, then this is what I thought. .I suspect we have another issue then, I will continue searching for it, but it's probably not linked to ISRs in general because it seems the SPI handler is called correctly. I can't share the code, but your answer is enough for me.

Best regards and thanks for your time,

Tim

RE: Custom bootloader: Can't reach interrupt handler

bjorn-spockeli — Tue, 26 Mar 2019 15:15:05 GMT

HI Timothée,

the MBR should already have set the IRQ forwarding address to the bootloader's vectortable address prior to passing execution to the bootloader. If you look at our Secure Bootloader we only call nrf_dfu_mbr_irq_forward_address_set( which in turn calls sd_mbr_command with SD_MBR_COMMAND_IRQ_FORWARD_ADDRESS_SET as a parameter) when we jump to the application.

Would it be possible for you to share the project so that I could try running this on a NRF52840 DK ?

Best regards
Bjørn

RE: Custom bootloader: Can't reach interrupt handler

Tim — Tue, 26 Mar 2019 13:10:52 GMT

Hi Bjørn, no problem, this is not a blocking point for us.

We actually found a way to fix this, but I'm really curious to know if this is just a workaround or if this is the correct way to do it. What we do now is that at the beginning of our bootloader's main, we perform a MBR command (SD_MBR_COMMAND_IRQ_FORWARD_ADDRESS_SET) to forward IRQ to the bootloader. After we do this, we correctly enter the GPIOTE handler when toggling our GPIO.

What makes me think it could not be the correct way is that the s140 SDS states this:

Else if a bootloader is present:
Forward interrupts to the bootloader.
Run Bootloader Reset Handler (defined in bootloader Vector Table at BOOTLOADERADDR).

So I was thinking we wouldn't need to tell the MBR to forward interrupts to the bootloader since it's already part of the procedure. Also, the MBR already knows the address of the bootloader ISR vector since it's where it jumps to at the beginning.

Best regards,

Timothée

RE: Custom bootloader: Can't reach interrupt handler

bjorn-spockeli — Tue, 26 Mar 2019 10:22:00 GMT

Hi Timothée,

I sincerly apologize for the late reply. I have been travelling since I meet you at Embedded World and I am not back in the office after 4 weeks on the road.

If you're using the PORT event and not the IN event, then you are completly correct, IN0 does not need to be set, only the GPIOTE.INTENSET.PORT should be set.

Best regards

Bjørn

RE: Custom bootloader: Can't reach interrupt handler

Tim — Mon, 25 Feb 2019 14:48:09 GMT

Hi Bjørn, thanks for your reply !
skip_gpio_setup is used in the SDK 15.1 in nrfx_gpiote.c line 529. As for INTENSET.IN0 I will check ASAP, but are you sure it is needed ? Here I only want to use PORT events.

Best regards,
Timothée

RE: Custom bootloader: Can't reach interrupt handler

bjorn-spockeli — Wed, 20 Feb 2019 15:53:36 GMT

HI Timothee,

I assume that hte .skip_gpio_setup = true option is a customization you have added as this option is not present in my clean release of SDK v15.1.0. May I ask what it does?

Also can you verify that the INTENSET.IN0 is set to 1 ?

Best regards

Bjørn