Signing update rejected

RE: Signing update rejected

bjorn-spockeli — Tue, 12 Jul 2016 09:35:35 GMT

Yes, as you pointed out , the SecuritySVCHandler is not defined for __GNUC. You'll have to port it and modify SVC_Handler to branch to the Security_SVC_Handler if the SVC number is equal to 8.

RE: Signing update rejected

Fabien Comte — Fri, 08 Jul 2016 13:13:19 GMT

Hello, are you using normal mapping ? Did you fixed it ?

RE: Signing update rejected

Fabien Comte — Sun, 03 Jul 2016 08:31:58 GMT

Security_SVC_Handler is not defined for GCC, so how it knows nrf_sec position ? Is GCC supported ?

RE: Signing update rejected

Fabien Comte — Fri, 01 Jul 2016 14:11:07 GMT

Hello, I reserved a bigger size for bootloader (i have another device to init). I guess that your ld is for bootloader. Can I make my mapping compatible with sec ? if yes how please ?

RE: Signing update rejected

bjorn-spockeli — Thu, 30 Jun 2016 13:09:12 GMT

facotl(Fabien Comte): Why aren't you using the linker settings in the dfu_gcc_nrf52.ld linker script?

FLASH (rx) : ORIGIN = 0x7A000, LENGTH = 0x4000

  /** RAM Region for bootloader. This setting is suitable when used with s132. */
  RAM (rwx) :  ORIGIN = 0x20002C00, LENGTH = 0x5380

  /** 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 = 0x20007F80, LENGTH = 0x80

  /** Location of bootloader setting in flash. */
  BOOTLOADER_SETTINGS (rw) : ORIGIN = 0x0007F000, LENGTH = 0x1000

  /** Location in UICR where bootloader start address is stored. */
  UICR_BOOTLOADER (r) : ORIGIN = 0x10001014, LENGTH = 0x04
  
  /** Location of mbr params page in flash. */
  MBR_PARAMS_PAGE (rw) : ORIGIN = 0x0007E000, LENGTH = 0x1000
  
  /** Location in UICR where mbr params page address is stored. */
  UICR_MBR_PARAM_PAGE(r) : ORIGIN = 0x10001018, LENGTH = 0x04
}

RE: Signing update rejected

Fabien Comte — Fri, 24 Jun 2016 12:00:50 GMT

Did you set somewhere in code the address of nrf_sec ?

RE: Signing update rejected

Fabien Comte — Fri, 24 Jun 2016 11:57:14 GMT

I have already modified theses ones in dfu_types.h

#define BOOTLOADER_REGION_START             0x00075800                  
#define BOOTLOADER_SETTINGS_ADDRESS         0x0007C800                 
#define BOOTLOADER_MBR_PARAMS_PAGE_ADDRESS  0x0007B800

RE: Signing update rejected

Fabien Comte — Fri, 24 Jun 2016 11:49:13 GMT

Hello, I try to re open this question :-)

I just thinked, NRFSEC_SETTINGS and NRFSEC_MODULE are specifics. Is there somewhere to set them in code ?

This is my linker configuration (in ld file)

      FLASH (rx) : ORIGIN = 0x00075800, LENGTH = 0x6000 /* 24 Ko bootloader */
	/* modify BOOTLOADER_REGION_START in dfu_types.h to use the previous origin*/
	
	SOFT_DEVICE (rw) : ORIGIN = 0x00000000, LENGTH = 0x1C000
	
   /** slot 1 */
	SLOT_1 (rw) : ORIGIN = 0x0001C000, LENGTH = 0x2C400
	
  /** slot 2 */
	SLOT_2 (rw) : ORIGIN = 0x00048400, LENGTH = 0x2C400
	
  	/** Location of application data */
	APPLICATION_DATA (rw) : ORIGIN = 0x00074800, LENGTH = 0x1000
  
  /** Flash start address for the bootloader. This setting will also be stored in UICR to allow the
   *  MBR to init the bootloader when starting the system. This value must correspond to 
   *  BOOTLOADER_REGION_START found in dfu_types.h. The system is prevented from starting up if 
   *  those values do not match. The check is performed in main.c, see
   *  APP_ERROR_CHECK_BOOL(*((uint32_t *)NRF_UICR_BOOT_START_ADDRESS) == BOOTLOADER_REGION_START);
   */
  BOOTLOADER (rx) : ORIGIN = 0x00075800, LENGTH = 0x6000 /* 24 Ko bootloader */
	/* modify BOOTLOADER_REGION_START in dfu_types.h to use the previous origin*/
	
	/** Location of mbr params page in flash. */
  MBR_PARAMS_PAGE (rw) : ORIGIN = 0x0007B800, LENGTH = 0x1000
  
  /** Location of bootloader setting in flash. */
  BOOTLOADER_SETTINGS (rw) : ORIGIN = 0x0007C800, LENGTH = 0x1000
  
  /** Update signing module */
  NRFSEC_SETTINGS (rw) : ORIGIN = 0x0007D800, LENGTH = 0x400
  NRFSEC_MODULE (rw) : ORIGIN = 0x0007DC00, LENGTH = 0x2400

  /** RAM Region for bootloader. This setting is suitable when used with s132. */ /* see in app_ram_base.h APP_RAM_BASE_CENTRAL_LINKS_3_PERIPH_LINKS_1_SEC_COUNT_3_MID_BW */
  RAM (rwx) :  ORIGIN = 0x20002F50, LENGTH = 0xD030

  /** 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 = 0x2000FF80, LENGTH = 0x80

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

RE: Signing update rejected

Fibar_TeamA — Tue, 07 Jun 2016 10:18:00 GMT

Hi Bjørn,

I have a problem with this example. When I try send a DFU package (ble_app_hrs_s132_with_dfu_signed.zip) from MCP 3.10.0.14 every time I catch BLE_ERROR_INVALID_CONN_HANDLE on dfu_transport_ble.c

       case BLE_DFU_BYTES_RECEIVED_SEND:
        err_code = ble_dfu_bytes_rcvd_report(p_dfu, m_num_of_firmware_bytes_rcvd);
        APP_ERROR_CHECK(err_code);

It's looks like SD can't Notify application but i have no idea why. Conn_handle isn't empty.

Name : conn_handle
Hex:0x70d0

The same problem with update from android nrf MCP.

Chip: nrf52832-QFAAB0

SD: s132_nrf52_2.0.0_softdevice.exe

GCC: 4.9 2015q3

RE: Signing update rejected

bjorn-spockeli — Mon, 09 May 2016 07:26:19 GMT

Are you able to identify where the reset, i.e. the device enters app_error_fault_handler?

RE: Signing update rejected

Fabien Comte — Thu, 05 May 2016 19:27:36 GMT

Hello, i finally found time to test and it was not a success. nRF52 reset few seconds after the DFU started...

RE: Signing update rejected

bjorn-spockeli — Fri, 29 Apr 2016 07:37:30 GMT

No problem. Keep me posted if you run into any problems.

RE: Signing update rejected

Fabien Comte — Fri, 29 Apr 2016 07:27:25 GMT

Thank you for your response, i will try asap

RE: Signing update rejected

bjorn-spockeli — Mon, 11 Apr 2016 06:00:32 GMT

Yes, it is based in SDK v11.0.0. I suggest you read the Experimental DFU Signing pdf, found in examples/dfu/experimental. Just extract the zip as a regular SDK release and you should be able to compile and flash the example.

RE: Signing update rejected

Fabien Comte — Sun, 10 Apr 2016 13:59:33 GMT

Hello, how can i use it ? There is a lot of files Inside, is that 11 final based ?

RE: Signing update rejected

Fabien Comte — Sun, 10 Apr 2016 13:55:08 GMT

Thank you, i will try asap

RE: Signing update rejected

bjorn-spockeli — Wed, 30 Mar 2016 09:04:24 GMT

Hi Fabien,

I have attached a modified version of the nRF5 SDK v11.0.0, where I have ported the DFU with signing example from nRF52 SDK v0.9.2.

-Bjørn

Attachments:

nRF5_SDK_v11_0_0_nrf52_dfu_signing_290316.zip (DFU with signing example)

RE: Signing update rejected

Fabien Comte — Tue, 09 Feb 2016 13:20:22 GMT

Hello, It's on nRF52.

RE: Signing update rejected

bjorn-spockeli — Wed, 27 Jan 2016 12:02:49 GMT

There is no experimental folder under examples/dfu containing bootloader_signing and the nrf_sec_module as far as I know in SDK v11. Are you trying to port it from SDK v10? Are you using it on the nRF51 or nRF52?

RE: Signing update rejected

Fabien Comte — Wed, 27 Jan 2016 11:43:44 GMT

But bootloader with signing is available in SDK 11...

RE: Signing update rejected

bjorn-spockeli — Wed, 27 Jan 2016 08:04:08 GMT

DFU with signing is experimental and is currently only released as a part of SDK v10 for nRF51.

RE: Signing update rejected

Fabien Comte — Tue, 26 Jan 2016 19:45:43 GMT

I posted here for nrf_sec devzone.nordicsemi.com/.../ Thank you for your help.

RE: Signing update rejected

Wojtek — Tue, 26 Jan 2016 19:39:29 GMT

No. It is still possible to dump your rom (unless you set readback protect). There is no encryption of the updated app. Signing only secures your device against somebody who could connect to it with mobile MCP and upload blinky or some hello world app :) Somewhere near that nrf_sec should be some nice PDF document describing whole signing process and advantages it gives.

Did you also check ZIP version?

RE: Signing update rejected

Fabien Comte — Tue, 26 Jan 2016 19:39:02 GMT

Not found in SDK 11 last alpha

RE: Signing update rejected

Fabien Comte — Tue, 26 Jan 2016 19:37:16 GMT

Do you know if signing DFU also protect (encryption) against unsollicited hacker copie ?