GPIO interrupt stopped working after adding bootloader

RE: GPIO interrupt stopped working after adding bootloader

sne_333 — Thu, 09 Nov 2023 03:48:26 GMT

Anyways I have solved the issue. Same pin was being accessed in bootloader as well as application fw which caused the issue. Thanks for your reply.

RE: GPIO interrupt stopped working after adding bootloader

Hung Bui — Wed, 08 Nov 2023 13:27:47 GMT

Hi Snehal,

What change you are talking about ?
I don't see why you point to these code.

RE: GPIO interrupt stopped working after adding bootloader

sne_333 — Wed, 08 Nov 2023 05:49:43 GMT

Hi Hung,

The changes you mentioned:-

There are for bootloader xml right?

RE: GPIO interrupt stopped working after adding bootloader

Hung Bui — Tue, 07 Nov 2023 15:25:40 GMT

Hi Snehal,
I'm not so sure what could be wrong here, but please try to simplify the application down so we can narrow down the root cause.
One thing to be careful about the bootloader is that the bootloader expect the application to clear any register before use. Meaning the bootloader doesn't reset all the registers before it jumps to the application.

But I don't see the reason why the bootloader would affect the USB MSC or the GPIO. But you need to pay extra attention to reconfigure the register, interrupt in the application as it might be modified by the bootloader.

RE: GPIO interrupt stopped working after adding bootloader

sne_333 — Tue, 07 Nov 2023 13:57:03 GMT

Does other functionality of the application still work and only the GPIO interrupt stops ?

>>> yes other functionality works.. only GPIO interrupt not working.

I assume you also generate bootloader setting when you test with merged hex ? I would suggest to test doing DFU with flashing SD + BL first and then update the application instead of merge them .

>>> Yes I also generate settings.hex when I merge the files. I have tried both options, with merged and without merged files. With both same is happening.

Also one more thing I am also using USB MSC code. So in my main file I had to initialize USB drivers first.

int main(void)
{
        bool erase_bonds;
    ret_code_t err_code;
    // Initialize modules.
    log_init();
    timers_init();


    //err_code = nrf_drv_power_init(NULL);
    //APP_ERROR_CHECK(err_code);

    err_code = nrf_drv_power_init(NULL);
    if ((err_code != NRF_SUCCESS) && (err_code != NRF_ERROR_MODULE_ALREADY_INITIALIZED))
    {
        /* This should never happen */
        APP_ERROR_HANDLER(err_code);
    }

    clock_init();
    nrf_drv_clock_lfclk_request(NULL);

    while(!nrf_drv_clock_lfclk_is_running())
    {
        /* Just waiting */
    }
    
  usbd_config_init(); 
  spi_init_flash();
  usb_msc_init();


    // Initialize the async SVCI interface to bootloader before any interrupts are enabled.
    // We don't check for error in case bootloader not in place
    ble_dfu_buttonless_async_svci_init();

    err_code = nrf_drv_gpiote_init();
    APP_ERROR_CHECK(err_code);

     // Do not start any interrupt that uses system functions before system initialisation.
    // The best solution is to start the OS before any other initalisation.

#if NRF_LOG_ENABLED
    // Start execution.
    m_logger_thread = xTaskCreateStatic(logger_thread, "LOGGER", sizeof(xLoggerStack) / sizeof(xLoggerStack[0]), NULL, LOGGER_TASK_PRIORITY, xLoggerStack, &xLoggerTaskBuffer);
    if (m_logger_thread == NULL) {
        APP_ERROR_HANDLER(NRF_ERROR_NO_MEM);
    }
#endif

NRF_LOG_INFO("TESTING NEW FIRMWARE");
    
      //init_device_storage();

    // Activate deep sleep mode.
    SCB->SCR |= SCB_SCR_SLEEPDEEP_Msk;

    device_storage_init();
    clinitraq_load_settings();
  

    memset(app_fw_version, 0, sizeof(app_fw_version));
    app_version_str(app_fw_version, sizeof(app_fw_version));

    mem_init();

 /* Enable interrupt for FPU so we can clear it */
    NVIC_SetPriority(FPU_IRQn, APP_IRQ_PRIORITY_LOW);
    NVIC_EnableIRQ(FPU_IRQn);

    // Configure and initialize the BLE stack.
    ble_stack_init();
    gap_params_init();
    gatt_init();
    services_init();
    advertising_init();
    conn_params_init();
    peer_manager_init();

    // Initialize modules.
    
 
    
    
    application_timers_start();

 /* Set TX Output Power to +4dBm */
    err_code = sd_ble_gap_tx_power_set(BLE_GAP_TX_POWER_ROLE_ADV, m_advertising.adv_handle, 4); 
    APP_ERROR_CHECK(err_code);

    // Create a FreeRTOS task for the BLE stack.
    // The task will run advertising_start() before entering its loop.
    nrf_sdh_freertos_init(advertising_start, &erase_bonds);

    
    init_usb_msc_task();
    init_led_button_task();
    init_system_task();


    
     // Start FreeRTOS scheduler.
    vTaskStartScheduler();

    for (;;) {
        APP_ERROR_HANDLER(NRF_ERROR_FORBIDDEN);
    }
}


void usbd_config_init(void)
{
   ret_code_t ret;

   static const app_usbd_config_t usbd_config = {
        .ev_isr_handler = usb_new_event_isr_handler,
        .ev_state_proc = usbd_user_ev_handler
    };

    ret = app_usbd_init(&usbd_config);
    APP_ERROR_CHECK(ret);

    app_usbd_class_inst_t const * class_inst_msc = app_usbd_msc_class_inst_get(&m_app_msc);
    ret = app_usbd_class_append(class_inst_msc);
    APP_ERROR_CHECK(ret);

}


void spi_init_flash(void)
{

     nrf_gpio_cfg_output(SPI_WP);
     nrf_gpio_cfg_output(SPI_HOLD);
     nrf_gpio_cfg_output(SPI_SS);
     
     nrf_gpio_pin_clear(SPI_SS);//enable all slaves
     nrf_gpio_pin_clear(SPI_WP);

     nrf_gpio_pin_set(SPI_HOLD);
     nrf_gpio_pin_set(SPI_SS_USB);
     nrf_drv_spi_uninit(&m_spi);
}


void usb_msc_init(void)
{

    ret_code_t ret;

    

    if (fatfs_init())
    {
          //fatfs_mkfs();
          fatfs_ls();
    }




    NRF_LOG_INFO("USBD MSC example started.");

    nrf_qspi_cinstr_conf_t cinstr_cfg = {
        .opcode    = 0x9F,
        .length    = 4,
        .io2_level = true,
        .io3_level = true,
        .wipwait   = true,
        .wren      = true
    };

    uint8_t rdid_buf[3] = {0, 0, 0};
    ret = nrf_drv_qspi_cinstr_xfer(&cinstr_cfg, NULL, rdid_buf);
    if (ret != NRF_SUCCESS)
    {
        NRF_LOG_INFO("read eror.");
        //NRF_LOG_INST_ERROR(p_qspi_dev->p_log, "QSPI get 3 byte id error: %"PRIu32"", ret);
        //return ret;
    }
    NRF_LOG_INFO("rdid_buf [%02x %02x %02x]", rdid_buf[0], rdid_buf[1], rdid_buf[2]);
    

    get_memory_space(&total,&free1);
    NRF_LOG_INFO("total %d,free %d",total,free1);

    if(file_found_on_sdcard == 0)
    {
    fatfs_file_create();
    write_header();
    }

    //write_data_in_file(15,0.1234);

    //write_data_in_file(16,0.0001);
    get_memory_space(&total,&free1);

    if(MAX_ID_DETECTED == 0)
    {
      if (USBD_POWER_DETECTION)
      {
          ret = app_usbd_power_events_enable();
          APP_ERROR_CHECK(ret);
      }
      else
      {
          NRF_LOG_INFO("No USB power detection enabled\r\nStarting USB now");

          app_usbd_enable();
          app_usbd_start();
          m_usb_connected = true;
      }
    }
}

These 3 functions:-

usbd_config_init();
spi_init_flash();
usb_msc_init();

were first called inside init_usb_msc_task() ->usb_msc_task

But I had to call it inside main.c before BLE stack init as it was causing issues in advertising and code used to hang,

I am doubting USB MSC drivers might be causing the GPIO issue.

RE: GPIO interrupt stopped working after adding bootloader

Hung Bui — Tue, 07 Nov 2023 12:04:36 GMT

Hi,

Does other functionality of the application still work and only the GPIO interrupt stops ?

Please try a quick test by making a very simple application that handle GPIO input in P1.15 (make sure it run with the softdevice).

Then test it with the unmodified bootloader.

I assume you also generate bootloader setting when you test with merged hex ? I would suggest to test doing DFU with flashing SD + BL first and then update the application instead of merge them .

As far as I know the bootloader doesn't touch P1.15 . There is no reason it should affect the application.

RE: GPIO interrupt stopped working after adding bootloader

sne_333 — Tue, 07 Nov 2023 11:50:02 GMT

I am able to do OTA and the bootloader jumps to the application without any issue. I can see it in the logs. The application I2C,SPI runs properly. Only GPIO interrupts are not working.

RE: GPIO interrupt stopped working after adding bootloader

snoopy20 — Tue, 07 Nov 2023 11:38:39 GMT

Also have you blocked off the memory for the bootloader within segger in the same way that you must for softdevice, so that when the app is compiled it doesn't use the memory registers?

You should have something like this in flash_placement.xml...

<ProgramSection keep="Yes" load="No" name=".bootLoader" start="$(FLASH_BOOTLOADER_START)" size="$(FLASH_BOOTLOADER_END)-$(FLASH_BOOTLOADER_START)" />
<ProgramSection keep="Yes" load="No" name=".mbrSettings" start="$(FLASH_MBRSETTINGS_START)" size="$(FLASH_MBRSETTINGS_END)-$(FLASH_MBRSETTINGS_START)" />
<ProgramSection keep="Yes" load="No" name=".bootLoaderSettings" start="$(FLASH_BOOTLOADERSETTINGS_START)" size="$(FLASH_BOOTLOADERSETTINGS_END)-$(FLASH_BOOTLOADERSETTINGS_START)" />
</MemorySegment>

RE: GPIO interrupt stopped working after adding bootloader

snoopy20 — Tue, 07 Nov 2023 11:34:12 GMT

Debugging?

I don't know your application, but I'd take a step back - is anything working, i.e has the bootloader passed over to the app?

One thing I have found in the past which sounds similar is when using all three and testing the bootloader for the first time, with a OTA flash, it writes a CRC value (enabled by default) into flash. If you then update the App manually say over Segger the CRC code fails and it's stuck in bootloader mode, which may not be as obvious as it appears 'nothing works'.

RE: GPIO interrupt stopped working after adding bootloader

sne_333 — Tue, 07 Nov 2023 11:12:39 GMT

How do I check that if its looping inside handler or if interrupt handler is not fired?

RE: GPIO interrupt stopped working after adding bootloader

snoopy20 — Tue, 07 Nov 2023 11:10:56 GMT

I guess you mean GPIOTE interrupt as GPIO doesn't have such a feature. Anyhow, there's nothing in SD and bootloader that controls or takes over the output pins or usage of the GPIOTE interrupt handler, so my guess is the interrupt handler is firing but isn't being serviced maybe due to code looping inside an interrupt handler at a higher priority level, something like that.