boards: rename nrf9160_innblue22ns

config BOARD_NRF9160_INNBLUE22

	bool "nRF9160 innblue v2.2"

config BOARD_NRF9160_INNBLUE22NS

config BOARD_NRF9160_INNBLUE22_NS

	bool "nRF9160 innblue V2.2 non-secure"

endif # SOC_NRF9160_SICA

# Copyright (c) 2020 InnBlue

# SPDX-License-Identifier: Apache-2.0

if BOARD_NRF9160_INNBLUE22 || BOARD_NRF9160_INNBLUE22NS

if BOARD_NRF9160_INNBLUE22 || BOARD_NRF9160_INNBLUE22_NS

config BOARD

	default "nrf9160_innblue22"

endif # BOARD_NRF9160_INNBLUE22 && TRUSTED_EXECUTION_SECURE

if BOARD_NRF9160_INNBLUE22NS

if BOARD_NRF9160_INNBLUE22_NS

config FLASH_LOAD_OFFSET

	default $(dt_chosen_reg_addr_hex,$(DT_CHOSEN_Z_CODE_PARTITION))

config FLASH_LOAD_SIZE

	default $(dt_chosen_reg_size_hex,$(DT_CHOSEN_Z_CODE_PARTITION))

endif # BOARD_NRF9160_INNBLUE22NS

endif # BOARD_NRF9160_INNBLUE22_NS

config BT_HCI_VS

	default y if BT

endif # BOARD_NRF9160_INNBLUE22 || BOARD_NRF9160_INNBLUE22NS

endif # BOARD_NRF9160_INNBLUE22 || BOARD_NRF9160_INNBLUE22_NS

1. Build the Secure Zephyr application using ``-DBOARD=nrf9160_innblue22`` and

   ``CONFIG_TRUSTED_EXECUTION_SECURE=y`` in the the application project configuration file.

2. Build the Non-Secure Zephyr application using ``-DBOARD=nrf9160_innblue22ns``.

2. Build the Non-Secure Zephyr application using ``-DBOARD=nrf9160_innblue22_ns``.

3. Merge the two binaries together.

When building a Secure/Non-Secure application, the Secure application will

identifier: nrf9160_innblue22ns

identifier: nrf9160_innblue22_ns

name: nRF9160-INNBLUE22-Non-Secure

type: mcu

arch: arm