NRf51822 qfaa bootloader settings not working

RE: NRf51822 qfaa bootloader settings not working

Dhaval Dalvadi — Mon, 27 Jan 2020 17:14:37 GMT

I tried SDK11 its working perfect

I also tried SDK12.1.0,12.2.0 and 12.3.0 all have same problem with nrf51DK.

I didnt modify any example code

I have app based on s130_nrf51_2.0.1_softdevice. So I have to use DFU example based on sdk12.

I doubt on toolchain version or something

I am using eclipse IDE

RE: NRf51822 qfaa bootloader settings not working

Dhaval Dalvadi — Mon, 27 Jan 2020 12:31:34 GMT

RE: NRf51822 qfaa bootloader settings not working

Dhaval Dalvadi — Mon, 27 Jan 2020 12:29:26 GMT

I put delay

void app_error_fault_handler(uint32_t id, uint32_t pc, uint32_t info)
{
    NRF_LOG_ERROR("received a fault! id: 0x%08x, pc: 0x&08x\r\n", id, pc);
    nrf_delay_ms(2000);
    NVIC_SystemReset();
}

void app_error_handler_bare(uint32_t error_code)
{
    (void)error_code;
    NRF_LOG_ERROR("received an error: 0x%08x!\r\n", error_code);
    nrf_delay_ms(2000);
    NVIC_SystemReset();
}

but not printed anything

RE: NRf51822 qfaa bootloader settings not working

bjorn-spockeli — Mon, 27 Jan 2020 12:29:15 GMT

Just changing the public key should not affect the ability to connect to the device. Please place breakpoints at the locations I stated below. Do you enter one of the handlers?

RE: NRf51822 qfaa bootloader settings not working

Dhaval Dalvadi — Mon, 27 Jan 2020 12:21:39 GMT

testing with nrf51DK
nRF5_SDK_12.3.0_d7731ad\examples\dfu\bootloader_secure\pca10028_debug\hex\secure_dfu_secure_dfu_ble_s130_pca10028_debug.hex

With this hex file I am able to connect discover all service and characteristics and allows DFU

nRF5_SDK_12.3.0_d7731ad\examples\dfu\bootloader_secure\pca10028_debug
I have compiled same example which preexist with sdk just changed public key file and its not able to find services

RE: NRf51822 qfaa bootloader settings not working

bjorn-spockeli — Mon, 27 Jan 2020 12:11:18 GMT

Ok, can you place breakpoints in app_error_handler_bare() and app_error_fault_handler() in main.c and then try to connect? Do you end up in one of these handlers? If so, please look at the call stack and see which function that caused the error.

Best regards

Bjørn

RE: NRf51822 qfaa bootloader settings not working

Dhaval Dalvadi — Mon, 27 Jan 2020 11:11:00 GMT

Its advertising as DFUTARG

RE: NRf51822 qfaa bootloader settings not working

bjorn-spockeli — Mon, 27 Jan 2020 10:31:11 GMT

Ok, so the nrf51822 is advertising as Nordic_Buttonless, when you try to connect, then you're not able to connect with the application?

Best regards

bjørn

RE: NRf51822 qfaa bootloader settings not working

Dhaval Dalvadi — Mon, 27 Jan 2020 09:54:13 GMT

INFO:Inside main
0> :INFO:In nrf_bootloader_init
0> :INFO:In real nrf_dfu_init
0> :INFO:running nrf_dfu_settings_init
0> :INFO:Enter nrf_dfu_continue
0> :INFO:Valid App
0> :INFO:Application sent bootloader request
0> :INFO:In nrf_dfu_transports_init
0> :INFO:num transports: 1
0> :INFO:vector table: 0x00035c00
0> :INFO:After nrf_dfu_transports_init
0> :INFO:------- nrf_dfu_flash_init-------
0> :INFO:Waiting for events

this is getting on dfu start via RTT

Here is log from nrf connect app

nRF Connect, 2020-01-27
DfuTarg (CA:1A:F2:51:65:B7)
V	15:21:15.600	Connecting to CA:1A:F2:51:65:B7...
D	15:21:15.600	gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D	15:21:15.970	[Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I	15:21:15.970	Connected to CA:1A:F2:51:65:B7
D	15:21:15.973	[Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
V	15:21:16.009	Discovering services...
D	15:21:16.012	gatt.discoverServices()
I	15:21:16.413	Connection parameters updated (interval: 7.5ms, latency: 0, timeout: 5000ms)
D	15:21:46.373	[Callback] Connection state changed with status: 22 and new state: DISCONNECTED (0)
E	15:21:46.373	Error 22 (0x16): GATT CONN TERMINATE LOCAL HOST
I	15:21:46.373	Disconnected
D	15:21:46.411	[Broadcast] Action received: android.bluetooth.device.action.ACL_DISCONNECTED

RE: NRf51822 qfaa bootloader settings not working

bjorn-spockeli — Mon, 27 Jan 2020 09:41:30 GMT

Please use the nRF Connect app instead of the nRF Toolbox and provide the log files from the nRF Connect app.

RE: NRf51822 qfaa bootloader settings not working

Dhaval Dalvadi — Mon, 27 Jan 2020 09:12:14 GMT

It worked with my module when I changed ram as below

FLASH (rx) : ORIGIN = 0x35C00, LENGTH = 0xA000

/** RAM Region for bootloader. This setting is suitable when used with s110, s120, s130, s310. */
RAM (rwx) : ORIGIN = 0x200025e0, LENGTH = 0x1a02

/** Location of non initialized RAM. Non initialized RAM is used for exchanging bond information
* from application to bootloader when using buttonluss DFU OTA.
*/
NOINIT (rwx) : ORIGIN = 0x20003fe2, LENGTH = 0x80

/** Location of bootloader setting in at the last flash page. */
BOOTLOADER_SETTINGS (rw) : ORIGIN = 0x0003FC00, LENGTH = 0x0400

/** Location in UICR where bootloader start address is stored. */
UICR_BOOTLOADER (r) : ORIGIN = 0x10001014, LENGTH = 0x04

but on OTA inrf toolbox giving me error upload failed gatt error

I have generated package using application hex and private key using following command

nrfutil pkg generate --hw-version 51 --application-version 1 --application testFirmware\mainApp.hex --sd-req 0x87 --key-file keys\private.pem OTATest.zip

RE: NRf51822 qfaa bootloader settings not working

bjorn-spockeli — Mon, 27 Jan 2020 08:07:43 GMT

HI Dhaval,

does the nRF51822 module have an external 32kHz crystal? If not, then you need to change the LFCLK configuration to use the internal RC Oscillator, i.e.

#define NRF_CLOCK_LFCLKSRC      {.source        = NRF_CLOCK_LF_SRC_RC,            \
                                 .rc_ctiv       = 16,                                \
                                 .rc_temp_ctiv  = 2,                                \
                                 .xtal_accuracy = NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM}
Best regards
Bjørn