case about nRF52820 uart dfu

Hi,

1.Please help me complete example pca10100e_uart

2.I am testing the nRF52820 UART DFU example

3.The example is named pca10100e_uart based on example pca10040_uart

4.The following problems occurred in the test:

5.I suspect my memory address is set incorrectly:

6.Please give me the correct nRF52820 memory address, As shown in the figure below

https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/lib_bootloader.html

sdk nRF5_SDK_17.1.0_ddde560

code:

Thank you for all your assistance.
Kind regards,
Peter.Min

Parents
  • Hello,

    It seems I never tried to build a bootloader for the nRF52820 (at least with Keil), because I was not able to compile your project. Do you happen to know where to get the file that it claims to be missing (It is evening, and I am sitting at home. I can reach out to some colleagues tomorrow if I don't find it). I assume that you have what you need to compile, other than the 

    However, I see that the array that you refer to is missing the nRF52820. However, the nRF52820 has different flash and RAM sizes from the other devices. As you can see here, it has 256 kB flash and 32kB RAM. This means that the flash is on the address:

    0x0000 0000 -> 0x0004 0000

    And the RAM is on the address:

    0x2000 0000 -> 0x2000 8000

    So an appropriate set of the bootloader's memory segments should be somthing like:

    Bootloader settings: 0x0003 F000 -> 0x0004 0000

    MBT parameter storage: 0x0003 E000 -> 0x0003 F000

    Bootloader: 0x0003 8000 -> 0x0003 E000

    Application area (depending on the softdevice that you use, but if you are using only MBR) : 0x0001 0000 -> however large you need, but less than 0x0003 F000. You don't need to specify the top.

    Master Boot Record (MBR) 0x0000 0000 -> 0x0000 1000

    SoftDevice -

    If you intend to have a softdevice, your softdevice will replace the MBR, and the application will start after the softdevice. E.g. if you use the S112 from SDK17.1.0:

    Softdevice: (which includes MBR) 0x0000 0000 -> 0x0002 8000

    This leaves this flash for the application: 0x0002 8000 -> 0x0003 8000 (NB: Only 64kB).

    I hope this clears things up a bit. Let me know if anything was unclear.

    BR,

    Edvin

  • Hi  Edvin,

    1. I make sure I set up the correct addresses

    2. During the debug process, it is found that the program does not run to the main entrance of the bootloader

    3. I used nRF52820 module for testing

    4. Is there anything else that needs to be changed?

    5. Other s112 + MBR = 100 KB

    6.Calculate the application available space

    settings = 4kb

    mbr data = 4kb

    bootloader =24kb

    application = ?

    softdevice = 96kb

    mbr = 4kb

    Application free space: 256-4-4-24-96-4= 124KB

    7.The address before the error was reported is as follows:

    Thank you for all your assistance.
    Kind regards,
    Peter.Min

Reply
  • Hi  Edvin,

    1. I make sure I set up the correct addresses

    2. During the debug process, it is found that the program does not run to the main entrance of the bootloader

    3. I used nRF52820 module for testing

    4. Is there anything else that needs to be changed?

    5. Other s112 + MBR = 100 KB

    6.Calculate the application available space

    settings = 4kb

    mbr data = 4kb

    bootloader =24kb

    application = ?

    softdevice = 96kb

    mbr = 4kb

    Application free space: 256-4-4-24-96-4= 124KB

    7.The address before the error was reported is as follows:

    Thank you for all your assistance.
    Kind regards,
    Peter.Min

Children
No Data
Related