sd130 and sdk12.1.0 ble bootloader problem

RE: sd130 and sdk12.1.0 ble bootloader problem

air — Tue, 13 Dec 2016 01:12:20 GMT

I saw the application run when 1st power on after sd130/application/bootloader flashing.

I made a mistake in making settings file.

I close this issue.

I greatly appreciate you.

RE: sd130 and sdk12.1.0 ble bootloader problem

bjorn-spockeli — Mon, 12 Dec 2016 10:19:02 GMT

Yes, you have to provide the application hex file, not the bootloader.hex file when generating the settings page. nrfutil will calculate the CRC of the application image and store that in bootloader settings. On startup the bootloader will compare the CRC of the application in flash and the CRC that is stored in the bootloader settings page. If they match then the application will start otherwise the device will stay in bootloader mode.

RE: sd130 and sdk12.1.0 ble bootloader problem

air — Mon, 12 Dec 2016 10:12:12 GMT

Sure, I did that. I'll explain what I did.

application.hex package make
bootloader.hex make
bootloader settings.hex make

nrfutil settings generate --family NRF51 --application bootloader.hex --application-version 3 --bootloader-version 2 --bl-settings-version 1 settings.hex

mergehex -m bootloader.hex settings.hex -o boot_set.hex
I flash SD130 / application.hex / boot_set.hex.
After repower on I can see DfuTarg scanned in the nrf toolbox.

Application doesn't any BLE operation. It just waits Key input to enter bootloader.

Is there anything wrong?

RE: sd130 and sdk12.1.0 ble bootloader problem

bjorn-spockeli — Mon, 12 Dec 2016 09:39:44 GMT

Hi Air, you have to create a bootloader settings page with nrfutil to set the valid app flag using the follwing command

nrfutil settings generate --family NRF52 --application <name of application hex file>.hex --application-version 1 --bootloader-version 1 --bl-settings-version 1 bootloader_settings.hex

After creating the bootloader_settings.hex file you have to merge it with the combined bootoader, application and softdevice hex file, and then flash it to your device.

RE: sd130 and sdk12.1.0 ble bootloader problem

air — Mon, 12 Dec 2016 06:49:28 GMT

Thank you very much!

Now, it's possible to enter bootloader mode and DFU using my custom key.

But,there's one thing to be solved.

I want to run the application(not bootloader) when the 1st power on after SD / application / bootloader programmed into the board.

I'm trying to modify this.

If you know this would you give me a tip?

Always thanks.

RE: sd130 and sdk12.1.0 ble bootloader problem

bjorn-spockeli — Fri, 09 Dec 2016 14:36:35 GMT

Hi air, there is a bug in the buttonless examples so if you have tried to write to the DFU control, but the device is not jumping to bootloader mode then you have add the write permission to the control point characteristic as described in this answer.

If you want to switch to bootloader with a button press then you have to call the enter_bootloader() function in ble_dfu.c once you get an interrupt from the button pin. Or you can simply do

s_dfu_settings.enter_buttonless_dfu = true;

(void)nrf_dfu_settings_write(flash_callback);

sd_nvic_SystemReset();

RE: sd130 and sdk12.1.0 ble bootloader problem

air — Fri, 09 Dec 2016 08:01:31 GMT

Hello, I tried some

In the bootloader_secure project I removed the init_softdevice check in ble_stack_init().

//if (init_softdevice)

//{

err_code = sd_mbr_command(&com);
APP_ERROR_CHECK(err_code);

//}

In the buttonless_dfu project I inserted code related with jump to bootloader.

int main(void)

{

uint32_t err_code;
bool     erase_bonds;

NRF_POWER->GPREGRET = 0xb1;		// BOOTLOADER_DFU_START;
NVIC_SystemReset();

. .

}

And

SD130/bootloader programming into PCA10028 board
Buttoness_dfu f/w package file upload in android phone

In this procedure -2, I guess buttoness_dfu runs(jump to bootloader again) after upload done.

So, I think I can upload the new F/W again.

Sure, I saw 1st upload.

But, bootloader doesn’t run after 1st upload.

These are related with what I want to realize as I explained in the above comments.

If it’s wrong How can I realize?

RE: sd130 and sdk12.1.0 ble bootloader problem

air — Fri, 09 Dec 2016 04:53:48 GMT

Thanks, I saw the DFU works after doing as you mentioned(set the --hw-version to 51 and not 1).

Now, How should I modify buttonless_dfu projecs If I want to do as below?

my application run when power on
bootloader enter(using buttonless_dfu projecs , Already I merged with my application.) after some key input (This key is in my custom board.)

int main(void)

{

uint32_t err_code;

UART_TX_HIGH;

lfclk_config();								// clock init
nrf_delay_ms(5);

twi_master_init();							// eeprom init
TWI_400K;									// twi frequency

// dfu check
if(checkDfu())								// check eeprom and enter into DFU mode
	goto DFU;
	.
	.
	.
// ******* main loop start ******* //
while (1)
{
	.
	.
	.
}

DFU:

startDfu();

}

// It's the same as buttonless_dfu main function

void startDfu(void)

{

uint32_t err_code;
bool erase_bonds;

// Initialize.
err_code = NRF_LOG_INIT(NULL);
APP_ERROR_CHECK(err_code);

timers_init();
buttons_leds_init(&erase_bonds);
ble_stack_init();

peer_manager_init(erase_bonds);
if (erase_bonds == true)
{
	NRF_LOG_DEBUG("Bonds erased!\r\n");
}

gap_params_init();
advertising_init();

services_init();
NRF_LOG_DEBUG("Services are initialized\r\n");

conn_params_init();
NRF_LOG_DEBUG("conn params are initialized\r\n");

// Start execution.
application_timers_start();
NRF_LOG_DEBUG("app timers are started\r\n");

err_code = ble_advertising_start(BLE_ADV_MODE_FAST);
APP_ERROR_CHECK(err_code);
NRF_LOG_DEBUG("advertising is started\r\n");

// loop
for( ; ; )
{
	if(NRF_LOG_PROCESS() == false)
	{
		power_manage();
	}
}

}

upload my new F/W using bootloader_secure in android phone.
my new application run again after DFU done.

To do this, I tried to modify DFU control point. But, it didn't work. I am trying to solve this problem. I'm sorry but it's better to have your help.