nRF Connect Programmer tool shows a wrong address range for the nRF52811 evaluation board.

[Felipe1]

Hi, I have a question about nRF Connect Programmer tool.

[Description]

The device memory layout shows the address range as "0x00000000 - 0x00100000 (size 1048576  bytes), even though nRF52811 flash size is 0x30000 or 192kByte.  It should be "0x00000000 - 0x00030000 (size 192kByte)".  Could you please let us know why?

[Environment]

Windows 10, nRF Connect v3.7.1, Programmer 1.4.11

nRF52811 evaluation board

J-Link Lite

 

[Steps to repro]

1. Launch nRF Connect Programmer.
2. Drag and drop a HEX file (e.g. s112_nrf52_7.2.0_softdevice.hex (any file is fine)) to the right pane (File memory layout).
3. Mouseover the right box (File memory layout).  Then a balloon pops up and goes "Address range : 0x00000000 - 0x00100000".
4. Click "Read" in the right pane.
5. Mouseover the top green box in the left box (nRF52811).  Then a balloon pops up and goes "Address range : 0x00030000 - 0x000FFFFF".

 

[Expected behavior]

In step 3, the address range should be 0x00000000 - 0x00030000.

In step 5, the address range of the left box should be 0x00000000 - 0x00030000.

 

[Details]

In case of nRF52 DK, the left box indicates nRF52832, and the upper address is 0x00080000 correctly.  Accordingly the right box indicates the upper address as 0x00080000.

The FICR shows the correct values of CODEPAGESIZE, CODESIZE, and INFO.FLASH in both of nRF52811 and nRF52DK, as written below.

 

• nRF52 DK

c:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin>nrfjprog --memrd 0x10000010 --n 0x10

0x10000010: 00001000 00000080 FFFFFFFE FFFFFFFF   |................|

Code pagesize = 0x80

Code size = 0x1000

Total code space = 0x80000

 

c:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin>nrfjprog --memrd 0x1000010C --n 0x10

0x1000010C: 00000040 00000200 FFFFFFFF FFFFFFFF   |@...............|

INFO.FLASH = 0x200 (512 kByte FLASH)

 

• nRF52811

c:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin>nrfjprog --memrd 0x10000000 --n 0x18

0x10000000: 55AA55AA 55AA55AA FFFFFFFF FFFFFFFF   |.U.U.U.U........|

0x10000010: 00001000 00000030                     |....0...|

Code pagesize = 0x30

Code size = 0x1000

Total code space = 0x30000

 

c:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin>nrfjprog --memrd 0x1000010C --n 0x10

0x1000010C: 00000018 000000C0 FFFFFFFF FFFFFFFF   |................|

INFO.FLASH = 0xC0 (192 kByte flash)

 

Any comments would be greatly appreciated.

[Vidar Berg]

Hi,

Thanks for reporting this.  I can confirm that I get the same result here now when I try to read the memory content from a nRF52811. Not sure if it's something that has been  introduced in a recent release, I will check with the team who is responsible for this app.

Best regards,

Vidar

[Felipe1]

Hi Vidar,

Thank you for your confirmation.  I can double check the fixed module if necessary.

Regards,

Toru (Felipe1)

[Vidar Berg]

Hi Toru,

Turns out this is a known issue that we're planning to address in a future release. Fixing this bug has not been given immediate priority because it only affects the UI. Sorry for the inconvenience.

Regards,

Vidar

[Felipe1]

Hi Vidar,

Thank you so much for your confirmation.  I will wait for the future release.  Does this problem happen on nRF52811 only or any other models as well?

[Vidar Berg]

Hi,

It has not been confirmed, but I would expect to at least see the same problem with 52810 and 52805 as they have the same memory configuration.

[Felipe1]

Hi Vidar,

Thank you for your Info.  I was told that nRF52810 works fine, so please double check it when the fix becomes available.  Thank you again for your support.

[Vidar Berg]

No problem. I will update this thread once I know more.