DOUBT ABOUT FLASH MEMORY IN NRF52832 QFABB0

RE: DOUBT ABOUT FLASH MEMORY IN NRF52832 QFABB0

Kenneth — Mon, 02 Sep 2019 13:22:03 GMT

I don't need the dump.hex anymore, I think the below explain what you are experiencing.

[quote user="kme"]What may be the case here is that during early production of a new variant it may share silicon with a larger variant for a short period of time, for instance to meet production schedule. However, this will only occur for a short period of time, and the RAM and Flash above the specified size is not tested or guaranteed to work in any way. So if you have created firmware that exceed the size of a variant, then you need to use a larger variant.[/quote]

RE: DOUBT ABOUT FLASH MEMORY IN NRF52832 QFABB0

NANDHU — Mon, 02 Sep 2019 13:13:24 GMT

[quote user="kme"]Have you tried to readback the code for instance by using: nrfjprog --readcode dump.hex[/quote]

I tried these look the screen short below a dump.hex file was generated but i didn't got any information regarding the memory from it.

RE: DOUBT ABOUT FLASH MEMORY IN NRF52832 QFABB0

Kenneth — Thu, 29 Aug 2019 08:57:49 GMT

Yes, though build code B (rev 1) I believe is no longer in production. So I assume it will be QFAAE0 (rev 2), ref:
https://infocenter.nordicsemi.com/topic/comp_matrix_nrf52832/COMP/nrf52832/ic_revision_overview.html?cp=3_1_2_0

RE: DOUBT ABOUT FLASH MEMORY IN NRF52832 QFABB0

NANDHU — Thu, 29 Aug 2019 08:15:14 GMT

So you are saying i want to use NRF52832 QFAAB0

RE: DOUBT ABOUT FLASH MEMORY IN NRF52832 QFABB0

Kenneth — Wed, 28 Aug 2019 09:57:38 GMT

What may be the case here is that during early production of a new variant it may share silicon with a larger variant for a short period of time, for instance to meet production schedule. However, this will only occur for a short period of time, and the RAM and Flash above the specified size is not tested or guaranteed to work in any way. So if you have created firmware that exceed the size of a variant, then you need to use a larger variant.

Best regards,
Kenneth

RE: DOUBT ABOUT FLASH MEMORY IN NRF52832 QFABB0

NANDHU — Wed, 28 Aug 2019 05:01:38 GMT

[quote user="kme"]Have you tried program using nRFgo Studio, close nRFgo Studio, open nRF Connect and Programmer plug-in and hit the Read button?[/quote]

I did these look the below screen short .

LOOK THERE IS ONLY SOFTDEVICE AND APPLICATION SECTION IN THE MEMORY LAYOUT NO BOOLTODER SECTION. IN WHICH MEMORY THE BOOTLOADER IS STORING?

[quote user="kme"]Can you try? [/quote]

I don't known to do these. can you help me?

RE: DOUBT ABOUT FLASH MEMORY IN NRF52832 QFABB0

Kenneth — Tue, 27 Aug 2019 11:17:33 GMT

Have you tried program using nRFgo Studio, close nRFgo Studio, open nRF Connect and Programmer plug-in and hit the Read button?

[quote user="NANDHU NAKULAN"][/quote]

Have you tried to readback the code for instance by using: nrfjprog --readcode dump.hex

NO.

Can you try?

RE: DOUBT ABOUT FLASH MEMORY IN NRF52832 QFABB0

NANDHU — Tue, 27 Aug 2019 08:55:50 GMT

[quote user="kme"]Have you tried to readback the code for instance by using: nrfjprog --readcode dump.hex[/quote]

NO.

[quote user="kme"]If you download nRF Connect for Desktop and use the Programmer plug-in there you can see the memory layout of the chip after programming.[/quote]

I tried to flash the softdevice ,bootloder,application hex files by using nRF Connect ,softdevice hex is flashed successfully but when i tryed to flash the bootloader hex its showing some error please look the screen short.

NOTE:- when i flashed the softdevice ,bootloder and application hex file with " nRFgo Studio " there is no error is showing and also the flashing is taking place successfully and the application working fine too.

Why that error is showing on nRF_ Connect?

LOGGINGS SCREEN SHORT ARE PLACED BELOW

RE: DOUBT ABOUT FLASH MEMORY IN NRF52832 QFABB0

Kenneth — Tue, 27 Aug 2019 07:50:34 GMT

Hi,

Have you tried to readback the code for instance by using: nrfjprog --readcode dump.hex

I think they case may be that you are mixing the size of the hex file in windows file system (contains for instance overhead due to the hex file format) and the actual memory footprint in flash. If you download nRF Connect for Desktop and use the Programmer plug-in there you can see the memory layout of the chip after programming.

Best regards,
Kenneth