Problem debugging bootloader using Ozone

RE: Problem debugging bootloader using Ozone

AntonHellbe — Fri, 06 Dec 2019 12:42:36 GMT

Hi,

Using the UICR registers as you suggested worked perfectly.

And as you said, after programming through Ozone and reading the MBR it shows 0xFF..FF.

RE: Problem debugging bootloader using Ozone

Vidar Berg — Fri, 06 Dec 2019 09:53:26 GMT

Thanks. So I got the same hardfault with GDB and turns out it's erasing the MBR section when setting the BL start and MBR param page address. Try to use the UICR registers instead:

When you have updated the registers in UICR, program the bootloader image first, and the Softdevice after.

Edit: you can 'nrfjprog memrd 0' after programming the bootloader in Ozone and see if it reads 0xFF..FF to determine if the MBR got erased.

RE: Problem debugging bootloader using Ozone

AntonHellbe — Fri, 06 Dec 2019 09:18:34 GMT

Here's the *.out file.

RE: Problem debugging bootloader using Ozone

Vidar Berg — Fri, 06 Dec 2019 09:16:53 GMT

The PC is 0xFF..FE so that explains the hardfault. It may even have lead to a lockup reset had you not been in debug mode. Unfortunately, I don't see any obvious reasons to how it could happen. Would it be possible to upload the bootloader .elf/.out so I can try it here?

RE: Problem debugging bootloader using Ozone

AntonHellbe — Fri, 06 Dec 2019 09:02:25 GMT

For some reason I have missed looking at the Call stack. Seems like we are stuck in a Hardfault handler.

Here are the screenshots:

Edit:

the CPU halting only occurs when using Ozone. If I upload the hex file using nrfjprog the bootloader start and I can start a DFU upgrade without any issues (logs printed aswell), however with Ozone no logs are printed and the bootloader doesn't react to I2C messages.

Modified the AfterTargetReset / Download:

void AfterTargetReset (void) {
/*
  unsigned int SP;                                                
  unsigned int PC;                                                
  unsigned int VectorTableAddr;                                   
                                                                  
  VectorTableAddr = Elf.GetBaseAddr();                            
                                                                  
  if (VectorTableAddr == 0xFFFFFFFF) {                            
    Util.Log("Project file error: failed to get program base"); 
  } else {                                                        
    SP = Target.ReadU32(0x0);                         
    Target.SetReg("SP", SP);                                    
                                                                  
    PC = Target.ReadU32(0x0 + 0x4);                     
    Target.SetReg("PC", PC);                                    
  }
*/
}

RE: Problem debugging bootloader using Ozone

Vidar Berg — Fri, 06 Dec 2019 08:44:29 GMT

Do you know that the CPU halting only occurs when debugging with Ozone? I've not been able to replicate this with the SDK bootloader. I just downloaded Ozone v2.70e and tested with and without AfterTargetReset() implemented. Can you post a screenshot of the CPU registers and call stack when it has halted?

RE: Problem debugging bootloader using Ozone

AntonHellbe — Fri, 06 Dec 2019 07:56:59 GMT

Hi Vidar,

I have tried that, the CPU still halts.

Here is the main function of the bootloader, I'm expecting it to run forever in the while loop as there is not valid application on the chip.

int main(void)
{
    ret_code_t ret;
    bootloader_callbacks_t bootloader_callbacks;

    bootloader_callbacks.start_application = start_application;
    bootloader_callbacks.send_i2c_message  = send_i2c_message;

    ret = nrf_drv_clock_init();
    APP_ERROR_CHECK(ret);
    nrf_drv_clock_lfclk_request(NULL);

    // Protect MBR and bootloader code from being overwritten.
    ret = nrf_bootloader_flash_protect(0, MBR_SIZE, false);
    APP_ERROR_CHECK(ret);
    ret = nrf_bootloader_flash_protect(BOOTLOADER_START_ADDR, BOOTLOADER_SIZE, false);
    APP_ERROR_CHECK(ret);

    APP_ERROR_CHECK(NRF_LOG_INIT(NULL));
    NRF_LOG_DEFAULT_BACKENDS_INIT();

    APP_ERROR_CHECK(app_timer_init());

    NRF_LOG_INFO("Inside main");

    bootloader_app_init(&bootloader_callbacks);
    
    if (dfu_enter())
    {
        twi_slave_init();
        send_fw_upgrade_response();
        NRF_LOG_DEBUG("DFU Enter requested. Waiting for FW");
        while(!new_fw_received)
        {
        }
    }
    else
    {
    }

    // Either there was no DFU functionality enabled in this project or the DFU module detected
    // no ongoing DFU operation and found a valid main application.
    // Boot the main application.
    //
    NRF_LOG_INFO("Starting application");
    nrf_bootloader_app_start();

    // Should never be reached.
    NRF_LOG_INFO("After main");
}

/ Anton

RE: Problem debugging bootloader using Ozone

Vidar Berg — Thu, 05 Dec 2019 13:33:15 GMT

Hi Anton,

Could you try comment out everything inside AfterTargetReset()? It should not be necessary to set SP and PC manually.