NRF52840 Donlge - JLink Programming

RE: NRF52840 Donlge - JLink Programming

Jørgen Holmefjord — Mon, 26 Oct 2020 10:28:14 GMT

Hi,

Sorry for the slow response. I compared the hex-files to the dummy.hex file. It looks like the eclipse read-back is identical in the relevant areas, while the nrfconnect readback has a lot of single bits set in addition in most lines. This is not what I see when I readback the flash of a nRF52840 device after writing a hex-file with nRF Connect Programmer application, it is reading back the same hex-file as I programmed.

Did you test this on the same dongle, or on two different dongles? It sounds strange that the one programmed with nRF Connect is working, while the one programmed from JFlash is not working, if the one flashed with nRF Connect does not contain the same hex-file that you flashed.

Could it be that you have somehow erased/overwritten the bootloader, which is causing the application to not run on the Dongle flashed using JFlash?

RE: NRF52840 Donlge - JLink Programming

jibba — Tue, 20 Oct 2020 13:54:59 GMT

Hi Jorgen

Is this ticket still in process or do you need more information ?

Thank you

RE: NRF52840 Donlge - JLink Programming

jibba — Mon, 12 Oct 2020 11:34:44 GMT

Ok. Here is the hexfile i flashed (https://we.tl/t-VuXnDaqxy8)

#include "mbed.h"

int main()
{
    DigitalOut led1(P0_6,  1);
    DigitalOut led2(P0_8,  1);
    DigitalOut led3(P1_9,  1);
    DigitalOut led4(P0_12, 1);

    while (true)
    {
        led1.write(0);
        ThisThread::sleep_for(10);
        led1.write(1);
        ThisThread::sleep_for(10);

        led2.write(0);
        ThisThread::sleep_for(10);
        led2.write(1);
        ThisThread::sleep_for(10);

        led3.write(0);
        ThisThread::sleep_for(10);
        led3.write(1);
        ThisThread::sleep_for(10);

        led4.write(0);
        ThisThread::sleep_for(10);
        led4.write(1);
        ThisThread::sleep_for(10);
    }
}

#define MBED_APP_START 0x1000
#define MBED_APP_SIZE 0xDB000
#define MBED_RAM_START 0x20000008
#define MBED_RAM_SIZE 0x3FFF8
#define MBED_BOOT_STACK_SIZE 0x800
#define MBED_RAM0_START MBED_RAM_START
#define MBED_RAM0_SIZE  0x100

#define MBED_CRASH_REPORT_RAM_START (MBED_RAM0_START + MBED_RAM0_SIZE)
#define MBED_CRASH_REPORT_RAM_SIZE  0x100

#define MBED_RAM1_START (MBED_CRASH_REPORT_RAM_START + MBED_CRASH_REPORT_RAM_SIZE)
#define MBED_RAM1_SIZE  (MBED_RAM_SIZE - (MBED_RAM0_SIZE + MBED_CRASH_REPORT_RAM_SIZE))

MEMORY
{
  FLASH (rx)     : ORIGIN = MBED_APP_START, LENGTH = MBED_APP_SIZE
  RAM_NVIC (rwx) : ORIGIN = MBED_RAM0_START, LENGTH = MBED_RAM0_SIZE
  RAM_CRASH_DATA (rwx) : ORIGIN = MBED_CRASH_REPORT_RAM_START, LENGTH = MBED_CRASH_REPORT_RAM_SIZE
  RAM (rwx)      : ORIGIN = MBED_RAM1_START, LENGTH = MBED_RAM1_SIZE
}

RE: NRF52840 Donlge - JLink Programming

Jørgen Holmefjord — Mon, 12 Oct 2020 11:15:07 GMT

Hi,

nRF Connect Programmer should not program anything else than the content of the provided hex-files. It looks like the difference is located right above the MBR, which is the softdevice region if a softdevice is used by the application. If the programmed hex-file was programmed with only a sectorerase and the dongles contained different softdevice version, this could explain the difference in the readback.

Can you post the hex-file you flashed? It should indicate the start address of the data that will be written to flash during programming.

Best regards,
Jørgen