This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Bootloader hardfault

Hi,

Im trying to use BLE DFU Bootloader from examples. I loaded SD8 and then bootloader via nrfStudio (dont have a valid app flashed), but I cant see the device from Android app. I decided to do some debugging via Keil. I recompiled Bootloader with no optimisation and moved bootloader address to 0x3A000.

If I try to debug in Keil it doesnt stop at main, but if i manually press stop it gets into hardfault: image description

Memory settings: image description

Compilation settings: image description

Im using Revision 3 chip. What do I do wrong?

app.zip

hex

Bootloader

Bootloader hex O3

bootloader package without BANK_VALID_APP

Bootloader HEX without BANK_VALID_APP

Memory map according to NRF Studio: Memory map

Bootloader optimisation Level 2 gets stuck on run: image description

Image size > 0x6400

Parents
  • No, didnt change anything else. But now I get sometimes GATT error and sometimes not, so at least something. Im using Huawei P8Lite, Android version 5.0.1. I do understand lowering interval gives better calibration:) what about negative effects?

    Meanwhile I tried to upload my own application which is 47K and from MCP I get the following error: Data Size Exceeds Limit. Im trying to upload application only, so even with dual bank it should work. Any idea why it says exceeding size? (in first tests I was using attached HRM hex and zip files). Here is manifest of my update pckg:

    {
        "manifest": {
            "application": {
                "bin_file": "blinky_arm.bin",
                "dat_file": "blinky_arm.dat",
                "init_packet_data": {
                    "application_version": 65535,
                    "device_revision": 65535,
                    "device_type": 65535,
                    "firmware_crc16": 47807,
                    "softdevice_req": [
                        100
                    ]
                }
            },
            "dfu_version": 0.5
        }
    }
    

    Thanks!

Reply
  • No, didnt change anything else. But now I get sometimes GATT error and sometimes not, so at least something. Im using Huawei P8Lite, Android version 5.0.1. I do understand lowering interval gives better calibration:) what about negative effects?

    Meanwhile I tried to upload my own application which is 47K and from MCP I get the following error: Data Size Exceeds Limit. Im trying to upload application only, so even with dual bank it should work. Any idea why it says exceeding size? (in first tests I was using attached HRM hex and zip files). Here is manifest of my update pckg:

    {
        "manifest": {
            "application": {
                "bin_file": "blinky_arm.bin",
                "dat_file": "blinky_arm.dat",
                "init_packet_data": {
                    "application_version": 65535,
                    "device_revision": 65535,
                    "device_type": 65535,
                    "firmware_crc16": 47807,
                    "softdevice_req": [
                        100
                    ]
                }
            },
            "dfu_version": 0.5
        }
    }
    

    Thanks!

Children
No Data
Related