Bootloader hardfault

RE: Bootloader hardfault

bjorn-spockeli — Fri, 05 Feb 2016 07:29:53 GMT

Happy to help :)

RE: Bootloader hardfault

Sergy — Fri, 05 Feb 2016 05:08:03 GMT

Yup, I confirm that everything works. Thanks so much for helping me out on this!!!

RE: Bootloader hardfault

bjorn-spockeli — Tue, 02 Feb 2016 12:34:59 GMT

As far as I know, that is normal.

RE: Bootloader hardfault

Sergy — Tue, 02 Feb 2016 12:18:56 GMT

What I meant to say - is it normal that it doesn't occupy the whole page, but is trimmed to exactly number of bytes it takes?

RE: Bootloader hardfault

bjorn-spockeli — Tue, 02 Feb 2016 12:08:19 GMT

Well, its no wonder that the image is smalle, but yes, I would expect it to be around 0x6000. I do not have an explenation for this, but as long as its below the DFU_BL_IMAGE_MAX_SIZE I guess its O.K.

RE: Bootloader hardfault

Sergy — Tue, 02 Feb 2016 10:32:57 GMT

ah thats interesting, I have a "const" in front, not sure why:

const uint8_t  m_boot_settings[CODE_PAGE_SIZE] __attribute__((at(BOOTLOADER_SETTINGS_ADDRESS))) __attribute__((used));

If I remove "const" I generate BIN file from HEX and the size of bin is 18832 (0x4990). A bit weird, no?

RE: Bootloader hardfault

bjorn-spockeli — Tue, 02 Feb 2016 10:26:01 GMT

I checked your "Bootloader Hex without BANK_VALID_APP" and the entire flash page from 0x3FC00 to 0x40000 is initialized to 0x00. How are you reserving the bootloader flash page? Line 18 in bootloader_settings.c should be the following:

uint8_t  m_boot_settings[CODE_PAGE_SIZE] __attribute__((at(BOOTLOADER_SETTINGS_ADDRESS))) __attribute__((used));

RE: Bootloader hardfault

bjorn-spockeli — Tue, 02 Feb 2016 10:06:15 GMT

The bootloader settings flash page should start at 0x3FC00. DFU_BL_IMAGE_MAX_SIZE is defined as (BOOTLOADER_SETTINGS_ADDRESS - BOOTLOADER_REGION_START) so in your case it will be 0x3FC00-0x39C00 = 6000. Have you written anything to flash above 0x3FC00 ?

RE: Bootloader hardfault

Sergy — Tue, 02 Feb 2016 09:30:00 GMT

Yes I did remove it, but my bootloader start address is before bootloader settings, so may be there is some problem with that?

RE: Bootloader hardfault

bjorn-spockeli — Tue, 02 Feb 2016 09:18:54 GMT

Did you remove the code that set the BANK_APP_VALID flag on the bootloader settings page? The bootloader settings flash page is 1kB and will be included in the image if something is written to it.

RE: Bootloader hardfault

Sergy — Thu, 28 Jan 2016 15:59:33 GMT

ok I compiled it and was able to run debugger. Funny thing I used size 0x6000 and now it complains that image size is 0x6400. For some reason it keeps adding 1kb to the real size of the debugger?

Also if I generate update package bin file inside its is 0x6400 size. Why does it create it 1kb bigger than in settings?

IROM: 0x39C00 0x6000

Program Size: Code=17200 RO-data=4108 RW-data=212 ZI-data=3992

RE: Bootloader hardfault

Sergy — Thu, 28 Jan 2016 15:22:54 GMT

I tried, but i get stopped out here:

    __STATIC_INLINE void nrf_gpio_cfg_output(uint32_t pin_number)
{
    nrf_gpio_cfg(
            pin_number,
            NRF_GPIO_PIN_DIR_OUTPUT,
            NRF_GPIO_PIN_INPUT_DISCONNECT,
            NRF_GPIO_PIN_NOPULL,
            NRF_GPIO_PIN_S0S1,
            NRF_GPIO_PIN_NOSENSE);
}

without setting any breakpoint in this code.

RE: Bootloader hardfault

bjorn-spockeli — Thu, 28 Jan 2016 15:18:48 GMT

You're not able to set breakpoints at the locations when using Level 3 or 2?

RE: Bootloader hardfault

Sergy — Thu, 28 Jan 2016 15:05:37 GMT

I cant even compile it with Level 0 optimisation, I get this error: ._build\nrf51422_xxac.axf: Error: L6985E: Unable to automatically place AT section bootloader_settings.o(.ARM.__AT_0x0003FC00) with required base address 0x0003fc00. Please manually place in the scatter file using the --no_autoat option.

If I use 24Kb or 25Kb, same error.

RE: Bootloader hardfault

bjorn-spockeli — Thu, 28 Jan 2016 13:46:07 GMT

NRF_ERROR_DATA_SIZE is returned at line 334, 339, and 415 in dfu_single_bank.c . Start a Debug Session in the bootloader project, set a breakpoint at each of these locations and perform a firmware update.

When I performed a DFU, I got caught at the breakpoint at line 334:

 if (m_start_packet.bl_image_size > DFU_BL_IMAGE_MAX_SIZE)
    {
        return NRF_ERROR_DATA_SIZE;
    }

RE: Bootloader hardfault

Sergy — Thu, 28 Jan 2016 06:43:52 GMT

ive added a screenshot of NRF Studio where it shows that start address of bootloader is 0x3A000, so if the image size would be 0x6000 it wouldnt fit and we would get a programming error, correct? Then the question is why you think image size is 0x6000, but NRF Studio programs it as 0x5C00 without errors and BL also works.

Nevertheless I did what you suggested - Increased BL memory by another 1K, but the result is still the same - getting Exceeded Data Size error. Do you have some other suggestions?

RE: Bootloader hardfault

bjorn-spockeli — Wed, 27 Jan 2016 10:18:46 GMT

When you flash it using a programmer, you will update the bootloader start address that is written to a UICR register. This is not done when performing a OTA DFU, then you only replace the bootloader, but the bootloader start adress will remain the same as the old bootloader.

RE: Bootloader hardfault

Sergy — Wed, 27 Jan 2016 10:13:33 GMT

Hm this is a bit weird. How do I flash it with a cable then and it works? There is no size check?

RE: Bootloader hardfault

bjorn-spockeli — Wed, 27 Jan 2016 10:08:33 GMT

I found the issue. The image size was 0x6000 bytes and the size reserved for the bootloader was 0x5C00, i.e. 0x400 (1kB) too large.

Change the ROM/RAM settings to the following

IROM1 start: 0x39C00 size:6000

and set BOOTLOADER_REGION_START to 0x00039C00 in dfu_types.h.

RE: Bootloader hardfault

Sergy — Wed, 27 Jan 2016 04:17:58 GMT

I removed BANK_VALID_APP, but still having the same problem: Data Size Exceeds Limit. Just for the sake of clarity I tried two things: 1)first flashed SD+APP+BL with set BANK_VALID_APP. Then I tried OTA DFU and sent a BL without BANK_VALID_APP.

I loaded SD+BL without BANK_VALID_APP and tried to do OTA DFU. Got the same error. Im attaching both new package and hex file to the main thread. Please have a look.

RE: Bootloader hardfault

bjorn-spockeli — Mon, 25 Jan 2016 10:12:21 GMT

The size issue turned out to be error with the script I used to create a hexdump of the hexfile you sent me.

In the bootloader hex you have set the BANK_VALID_APP flag on the bootloader settings flash page. If you are using a single bank bootloader, the application will be erased and the new bootloader is saved to the application flash space. When the bootloader is swapped with the old one, it will check the bootloader settings to see if the BANK_VALID_APP flag is set. If it is set, the bootloader will branch to what it thinks is a valid application, but in reality is just an empty flash area.

Do not set the BANK_VALID_APP in bootlaoder images when performing OTA DFU. Only set it if you're flashing BL+APP+SD using a programmer.

RE: Bootloader hardfault

Sergy — Mon, 25 Jan 2016 09:23:51 GMT

Attached to main thread. I think O3 was enabled last time as well. File sizes seem identical.

RE: Bootloader hardfault

bjorn-spockeli — Mon, 25 Jan 2016 07:56:16 GMT

Ok, I am not sure why the hexfile is to big. Could you try compiling the bootloader again with optimization level 3 turned on?

RE: Bootloader hardfault

Sergy — Sat, 23 Jan 2016 12:03:28 GMT

I'm actually planning to make bootloader support UART update as well, so I need to have some space reserved for it, can't make it smaller. What makes hex file so big? Can we fix the root cause?

RE: Bootloader hardfault

bjorn-spockeli — Fri, 22 Jan 2016 14:29:21 GMT

My suggestion would be to revert to the default memory settings, i.e.

IROM1 Start: 0x3C000 Size:0x3C00

and turn on compiler optimization to level 3(-O3). Then you have 144 bytes left of application flash space and you can use the Dual Bank Bootloader ( if your application is not going to be bigger thatn 72kB). If 72kB is not enough then you can use Single Bank.