Date   

Re: Zephyr development news, 4 Apr - 10 Apr 2018

Marti Bolivar
 

Fixing the mailing lists; sorry!

On Wed, Apr 11, 2018 at 12:02 PM, Marti Bolivar
<marti@opensourcefoundries.com> wrote:
Hello Zephyr community!

This is the first of a periodic (weekly-ish) newsletter tracking the latest
Zephyr development.

The goals are to give a human-readable summary of what's been merged
into master, breaking it down as follows:

- Highlights: important changes, new features, and bug fixes
- Individual changes: a complete list of patches, sorted chronologically
and sorted into separate areas (like "Architectures", "Kernel", "Drivers",
etc.)

The "important changes" will include things like API breaks and some
significant features. The focus is on changes in Zephyr that are
likely to require
changes in your Zephyr applications.

The new features and bug fixes sections aren't meant to be exhaustive; the
idea is to cover what happened from a high level. You can check the individual
changes section for a complete list of commits in areas you're interested in.

Any and all feedback on mistakes, significant omissions, etc., is welcome. We
will do our best to get things right, but we'll mess up sometimes :).

To start, I'm going to send these as plain text. Any comments on that or other
formatting and style feedback is also welcome.

Cheers,
Marti and Open Source Foundries

Highlights
==========

This newsletter covers changes in Zephyr between these two
commits:

- 4291fb67a ("usb: Remove duplicated CDC_ECM_SUBCLASS
definition"), Apr 4 2018

- 9bde3c06e ("tests: build_all: Add LPS22HB and LSM6DSL sensors
build test"), Apr 10 2018

The most significant of these changes are due to a large re-work
of the SPI APIs, which affected both the peripheral drivers
themselves as well as their users.

Important Changes
-----------------

SPI API
~~~~~~~

The SPI API (in include/spi.h) has been re-worked and
finalized. All in-tree users were upgraded to the new API. The
old SPI API, and all of its implementations, have been
removed. Out of tree uses of the old SPI API will need updates. A
summary of the API changes follows.

The I/O APIs now use a new struct spi_buf_set, which contains a
pointer to a struct spi_buf array, and its length:

struct spi_buf_set {
const struct spi_buf *buffers;
size_t count;
};

This structure is used in the I/O APIs so that the TX and RX
arguments can be specified in two formal parameters, which allows
using registers instead of the stack in some API calls.

All SPI API calls also now take a pointer to the SPI device
itself as their first parameter, instead of storing that device
in struct spi_config. This makes the SPI API consistent with
other Zephyr device APIs.

The "EEPROM mode" support was removed from the master controller
operations bit mask. It was replaced with a new flag,
SPI_CS_ACTIVE_HIGH, which inverts the usual polarity of the chip
select pin.

The spi_config parameter passed to the SPI API is now constant,
allowing it to be stored in flash memory.

The asynchronous SPI API no longer uses CONFIG_POLL
directly. Instead, a layer of indirection through
CONFIG_SPI_ASYNC was introduced, which selects CONFIG_POLL.

In addition to these changes in the SPI master mode API,
experimental support for SPI slave implementations was added to
the new API.

Board Porting Guidelines
~~~~~~~~~~~~~~~~~~~~~~~~

Official board porting guidelines were merged, which have
consistent rules for how to structure a board's Kconfig. For
details, refer here:

http://docs.zephyrproject.org/porting/board_porting.html#default-board-configuration

Features
--------

VLAN support:

VLAN support was added for Ethernet network
interfaces. Initial support is provided for for mcux, native
POSIX, and Atmel E70. The SLIP driver also has VLAN support.

New net shell commands "net vlan", "net vlan add", and "net
vlan del" were added to query and manipulate the VLAN
configuration.

A new sample application, samples/net/vlan, was added, which
can be used to set VLAN tags for ethernet interfaces.

As part of these and other network changes, the ethernet
files now live in their own directory, net/ip/l2/ethernet.

Red/black trees:

A new red/black balanced binary tree implementation was
added; the API is available in include/misc/rb.h. Like the
linked list types, the structure is *intrusive*: red-black
tree nodes are meant to be embedded in another structure,
which contains the user data associated with that node. Code
size compared to a doubly linked list on most architectures
is approximately an additional 2-2.5 KB.

Completion of DTS support for I2C and SPI on STM32:

All STM32-based boards now use device tree for I2C and SPI
peripherals.

Bluetooth generalizations:

Continuing the effort to generalize the core Bluetooth
subsystem across SoCs, the Bluetooth "ticker" timing API now
includes a generic hal/ticker.h file, which abstracts out SoC
specific definitions.

Drivers:

Ethernet is now enabled by default on the sam_e70_xplained
board.

New driver support includes SPI on nRF52, an interrupt in
transfer callback on USB HID, USB CDC EEM support for
encapsulating Ethernet packets over a USB transport, and GPIO
triggering for the ST LSM6DSL accelerometer and IMU.

Boards:

New boards include the SiFive HiFive1 and Nordic nRF52
Thingy:52 (PCA20020).

Speeding up CI:

An effort is underway to reduce the amount of time spent in
CI. To that end, an additional CI build slave was added, some
duplicative test coverage on qemu_x86 and qemu_cortex_m32 was
eliminated, and other optimizations were performed.

Boot banner changes:

The boot banner now prints the git version (based on git
describe) and hash, but timestamps were removed from it by
default to increase the reproducibility of Zephyr builds.

User mode memory pools:

A new memory pool implementation which is compatible with use
from user mode threads was merged; the API is available in
include/misc/mempool.h. This implementation shares code with
the in-kernel k_mem_pool API, but avoids constraints that are
incompatible with user mode. Memory pools are defined at
compile time with SYS_MEM_POOL_DEFINE(), and initialized by
sys_mem_pool_init(). Memory may be allocated and freed from
an initialized memory pool with sys_mem_pool_alloc() and
sys_mem_pool_free(), respectively.

Network interface management:

Interface statistics collection is now per-interface.

The network shell command "net iface" can now enable or
disable network interfaces by index.

Initial support for ethernet interface configuration has been
merged. This includes a link speed capabilities query. An API
was also merged for changing hardware configuration; this
includes link speed, but is not limited to it.

Bug Fixes
---------

Support for enabling GPIO port H on STM32L0 was fixed.

Support accessing sub-region attributes on ARM MPUs was fixed.

A pair of Bluetooth mesh fixes were merged, including a null
dereference and an issue related to enabling node identity
advertising.

The behavior of the CONFIG_FP_SOFTABI option was fixed. It now
generates floating point instructions, rather than turning them
off, which it was doing previously.

The temperature sensor channel for the nRF TEMP IP block was
fixed; it is now SENSOR_CHAN_DIE_TEMP.

A fix was merged for k_thread_create(), which now properly checks
the provided stack size on systems which enforce power of two
sizes.

POSIX fixes for pthread_cancel and timer_gettime were merged.

Dozens of commits cleaning up and fixing the test cases were
merged.

Individual Changes
==================

Area summary (197 patches total):

Area Patches
---------------------- -------
Arches 10
Bluetooth 3
Boards 10
Build 3
Continuous Integration 6
Documentation 12
Drivers 60
External 2
Kernel 5
Libraries 5
Miscellaneous 3
Networking 18
Samples 10
Scripts 6
Testing 44

Arches (10):

- 6d870ae2 arch/quark_se: Switch to native SPI DW driver
- 4652f59d arch/quark_se_c1000_ss: Switch to SPI DW driver
- 1ac6f4bd arch/quark_d2000: Switch to SPI DW driver
- a8685613 arch/quark_se: Enable SPI port 2 as a slave only
- 2d926f35 native: doc eth TAP: can only be compiled in Unix
- 700e4bd2 ARM: -march compile option is not set
- 6dae38cb arch: riscv32: fe310: Always-On domain adress definition
- 77bbc42e arch: arm: soc: stm32l0: fix port H EXTI
- 54842182 arm_mpu: fix _get_region_attr()
- 6c2047fc arch/arm: stm32: All SoCs have dts for I2C and SPI

Bluetooth (3):

- b8042ea9 Bluetooth: Mesh: Fix possible NULL dereferences in client models
- d6a549ce Bluetooth: Mesh: Fix Node Identity advertising with PB-ADV
- 6c6d98bc Bluetooth: controller: Use hal/ticker.h to abstract SoC specifics

Boards (10):

- 1f0bfb85 boards/x86: Pinmux SPI port 2 relevantly on quark_se_c1000_devboard
- 3e54d391 boards: sam_e70_xplained: Enable L2 ethernet layer
- 938a9699 boards: SiFive HiFive1 board
- 9287a9bf boards/arm/olimexino_stm32: Don't enable I2C and SPI
- 439a63da boards: Add support for nRF52 Thingy:52 (PCA20020)
- a068f29d boards: arm: nrf52_pca20020: Add board documentation
- ea9a3451 boards: native_posix: mark netif as supported
- 2ee6dff7 boards: fix yaml syntax and reduce indentation
- 973ec4ea boards: reduce testing on the same platform with variations
- de8d755c boards: test networking only in one qemu type

Build (3):

- 7d301cbb cmake: qemu_x86: remove useless options
- 9be27f73 kconfig: Make CONIG_FP_SOFTABI generate floating point instructions
- daf7716d build: use git version and hash for boot banner

Continuous Integration (6):

- 0df7e1c1 ci: Increase number of build slaves to 5
- 424a3db7 sanitycheck: do not always dump footprint statistics
- 20f553fe sanitycheck: do not call cmake twice on run
- ab351f40 sanitycheck: do not create overlays for filtered platforms
- 5df8cff0 sanitycheck: simplify logic of build_only/enable_slow checking
- 75547e2b sanitycheck: add option to list all available tags

Documentation (12):

- 9782755a native doc: minor improvement in ethernet driver
- 51658761 doc: Add a comment describing the algorithm used by entropy_nrf5.c
- 6fd8a0b3 doc: dts: Add reference to mcuboot flash partitions
- 8a8d9818 doc: subsys: Add dfu and mgmt subsytem doc
- cd05a630 doc: getting_started: Modernize macOS instructions
- 4b782253 doc: usb: Update API doc
- 3314c367 doc: misspellings in public API doxygen comments
- e48b64d1 doc: fix doc misspellings in doc, boards, samples
- 9abc31e3 doc: clean up QEMU networking doc
- f1275a78 doc: subsystem: settings subsystem doc
- 361ef340 doc: subsys: Remove unnecessary subsystem from titles
- 97083720 doc: provide board porting guidelines

Drivers (60):

- 4291fb67 usb: Remove duplicated CDC_ECM_SUBCLASS definition
- efa3a137 usb: Remove duplicated ACM_SUBCLASS definition
- d89e8e6a drivers/spi: Cleanup the Kconfig files
- 32426542 api/spi: Disable legacy API by default
- f3f9fab2 api/spi: Make spi_config parameter constant
- ea2431f3 api/spi: Reduce parameter number on transceive function
- da42c007 api/spi: Add a dedicated Kconfig option for asynchronous
mode enablement
- 7b185831 api/spi: Removing eeprom mode in configuration
- 9b27f29c api/spi: Add octal MISO lines mode
- f44ba8e7 api/spi: Make cs attribute in struct spi_config constant
- d4065ae7 drivers/ieee802154: Switch CC2520 to new SPI API
- 16cb7ab8 drivers/flash: Switch W25QXXDV driver to new SPI API
- 244c2af1 drivers/sensors: Switch bme280 driver to new SPI API
- eb7af552 drivers/sensors: Switch bmi160 driver to new SPI API
- 94d7c9f2 drivers/sensors: Switch adxl362 driver to new SPI API
- 2f7e6b6d drivers/sensors: Switch lis2dh driver to new SPI API
- d620c16a drivers/adc: Switch ti_adc108s102 driver to new SPI API
- 595340ab drivers/bluetooth: Switch SPI based HCI driver to new SPI API
- 3219817d drivers/bluetooth: Get rid completely of legacy SPI API in SPI HCI
- 29a68cd7 drivers/spi: Adapt Kconfig and generic context to enable
slave support
- 659f0f2d api/spi: Add the possibility to request CS active high logic
- 2a14d289 drivers/ethernet: Switch enc28j60 to new SPI API
- 7f4378e2 api/spi: Precise a bit the documentation
- 57a1f7b4 drivers/spi: Add support for TX or RX only modes on DW driver
- 44d4de51 drivers/spi: Remove legacy DesignWare SPI driver
- 423f0095 drivers/spi: Specify options per-port on DW driver
- 29f8b23b drivers/clock_control: Enable ARC core support on quark_se driver
- a8634944 drivers/spi: Enable port 3 and 4 on DW driver
- dc49d0f3 drivers/spi: Fix typo on parameters type in DW arc regs definitions
- 0a43cac3 drivers/spi: Removing QMSI driver as it does not support new API
- 65f6c967 drivers/spi: Switch Intel driver to new SPI API
- ef5152ab spi: Implement new spi api in the mcux dspi driver
- b62b12ee drivers/ieee802154: Switch MCR20A driver to new SPI API
- 09dd5e9b drivers/spi: Remove legacy API support from mcux dspi driver
- 00397c65 drivers: spi: Add shim for nrfx SPI driver
- 841a4207 drivers/spi: Add slave mode support to the DesignWare driver
- 79308dd1 drivers/spi: Simplify how error is forwarded from ISR handler in DW
- 1086fdf1 drivers/spi: spi_context lock makes transceive function
reentrant in DW
- b702236d drivers/ethernet: No need of semaphore for spi in enc28j60
- d5e6874d drivers/ieee802154: No need of semaphore for spi in mcr20a
- 13dba12b drivers/spi: Remove legacy NRF5 master and slave drivers
- 3f4cffc3 spi: Remove SPI legacy API
- f1ae9402 api/spi: Slave transactions will return received frames on success
- bdd03f38 drivers: sensor: temp_nrf5: fix sensor type
- 42a96c56 drivers: clock_control: quark_se: Fix "make menuconfig"
- 011ad6f7 drivers/spi: Fix tmod update on DW driver
- aaa9cf2e drivers: entropy: nrf5: Clarify Kconfig options
- 7385e388 drivers: eth: mcux: Enabling VLAN
- 02ee3651 drivers: eth: gmac: Adding VLAN support to Atmel E70 board
- 73b43e00 drivers: eth: native_posix: Add VLAN support
- 2c343d2b drivers: net: slip: Add VLAN support
- ed923da4 drivers: net: mcux: Use VLAN priority to set RX packet priority
- 992e3284 usb: netusb: Rework netusb media connect/disconnect
- d80ae8ae usb: netusb: Add CDC EEM network usb function
- 0d04aef6 usb: hid: add a INT IN transfer complete callback.
- dbb22644 usb: hid: implement set_report()
- 8d2b22cd drivers: timer: expose RTC1 ISR handler function
- fbd3c2f4 sensors: ccs811: Deassert the reset pin with GPIO
- 8e1cf7b6 gpio: nrf5: Make the init priority configurable
- 6fb326ce drivers: sensor: lsm6dsl: add trigger support

External (2):

- ca1cb054 ext: lib: tinycbor: fix Zephyr specific settings
- 00f6fc96 ext: lib: tinycbor: fix half-FP feature compilation

Kernel (5):

- f762fdf4 kernel: posix: move sleep and usleep functions into c file.
- 95f14322 sys_mem_pool: add test case
- bf44bacd kernel: mutex: Copy assertions to assertions to syscall handler
- 18cb8326 kernel: Disable build timestamps by default for reproducibility
- ec7ecf79 kernel: restore stack size check

Libraries (5):

- aa6de29c lib: user mode compatible mempools
- f603e603 lib: posix: Move posix layer from 'kernel' to 'lib'
- 4226c6d8 lib: posix: Fix mutex locking in pthread_cancel
- fe46c75d lib: posix: Fix integer overflow in timer_gettime
- 193f4feb lib: Red/Black balanced tree data structure

Miscellaneous (3):

- 5f67a611 include: improve compatibility with C++ apps.
- 7383814d cpp: mark __dso_handle as weak.
- 2ef57f0a lib/rbtree: Add a rb_contains() predicate

Networking (18):

- de13e979 net: if: vlan: Add virtual lan support
- 487e8104 net: shell: Add VLAN support
- 6643bb08 net: l2: ethernet: Add priority to sent ethernet VLAN header
- ad5bbefd net: Add function to convert VLAN priority to packet priority
- 687c3339 net: if: Use DEVICE_NAME_GET() instead of fixed string
- b70b4bca net: shell: Add network interface up/down command
- ffd0a1f5 net: core: Check interface when receiving a packet
- 444dfa74 net: l2: Remove l2_data section start and end pointers
- e56a9f0e net: ethernet: Return correct non VLAN interface
- 85d65b20 net: stats: Fix the net_mgmt statistics collection
- 1443ff0f net: stats: Make statistics collection per network interface
- e996b37c net/ethernet: Add capabilities exposed by device drivers
- e9d77b60 net/ethernet: No need to expose vlan_setup if vlan is not enabled
- 4bf1a9bd net/ethernet: All types are prefixed with ethernet_
- af0c5869 net/ethernet: Moving ethernet code to dedicated directory
- f3d80126 net/ethernet: Add function driver API to change some hw configuration
- 8d558fb5 net/ethernet: Add a management interface
- 757c5d18 net/ethernet: Fix uninitialized attributes in ethernet mgmt
parameters

Samples (10):

- 308f4df9 samples/drivers: Switch Fujistu FRAM sample to new SPI API
- e7de85b5 samples/bluetooth: Move hci_spi to new SPI API
- a0df4f66 samples: net: Fix sanitycheck for sam_e70_xplained board
- 5fbd4807 samples: net: vlan: Simple app for setting virtual lan settings
- 81d211f3 samples: hci_uart: Add references to sections
- bd583ed9 samples: mgmt: Expand smp_svr sample documentation
- 7c5c222c samples: net: Add test cases for USB EEM
- 156091fb samples: sample.yaml cleanup
- 65600d47 samples: power_mgr: add harnesss configuration
- 15ccd9cc sample: net: stats: Example how to use net_mgmt for statistics

Scripts (6):

- 46a172ae kconfiglib: Update to 2259d353426f1
- db28a5d8 kconfiglib: Update to 981d24aff7654
- 8fc44f29 kconfiglib: Update to e8408a06c68d8
- e32ed180 jlink: fix flashing behavior on Windows
- ba2ce2e9 script/extract_dts_includes: factorize call to upper()
- 074c90c5 scripts: dts_extract_include: generate aliases defs

Testing (44):

- a5efadf2 tests/drivers: Removing old SPI test
- b4247fde tests/spi: Remove excluded boards
- 9116cc7a tests: spi_loopback: Add frdm_k64f configuration
- 18d354c4 tests: spi_loopback: Add configurations for a few nRF5 boards
- 92be4112 tests: drivers: build_all: add TEMP_NRF5 to sensor test
- d155e886 tests: stack_random: Add Ztest support
- fab8c278 tests: lifo: Add lifo test with scenario
- 14e356c7 tests: net: vlan: Add VLAN tests
- e3076a47 tests: add tag for memory pool tests
- 46931c9a tests: posix: Resolve header file dependencies
- 9e4bbcc9 tests: kernel: add Cortex-M33/M7 in list of MCUs
- 316ffff6 tests: kernel: fix irq_vector_table test for nRF52X platforms
- 4fc2ccbd test: mbox_usage: add legacy test case for mailbox
- bdda3695 tests: net: vlan: Fix VLAN disable test
- f8502690 tests: context: rename main test
- 88c16923 tests: context: use ztest macros
- 86bb19ac tests: mutex: rename main test function
- 5d569eac tests: rename test -> main.c
- e73a95bd tests: kernel: use a consistent test suite name
- 5c72f40c tests: tags should not be required
- f3e8cb7e tests: add missing harness support
- 016b21a4 tests: mbedtls_sslclient: fix filtering and default conf
- 1934d3bd tests: enhance test filtering for net tests
- 4f4f135b tests: mqtt: fix dependencies
- fca15b49 tests: xip: cleanup test
- 390a2c4c tests: classify tests
- 8e8d6de6 tests: posix: fix tags and sections
- 49bb8313 tests: classify periphera tests
- 9e9784fc qemu_xtensa: ignore net and bluetooth tests
- 848c1054 tests: classify net tests and cleanup
- 5c89a4ce tests: ipv6: cleanup tests
- 3e086c68 tests: base64: do not exclude newlib
- 31e201b5 tests: net: context: simplify filtering
- d7e7b08c tests: cleanup meta-data of various tests
- 55ce5510 tests: cleanup subsystem tests meta-data
- 835ee3ff tests: net: checksum_offload: exclude native [REVERTME]
- d2807576 ztest: define test_main in the header file.
- fe067eb3 tests: add a C++ compile test.
- b71d6bab tests/net: Add a test for Ethernet net mgmt interface
- 3c856028 tests: net: checksum_offload: Adjust number of interfaces
- e2924ab4 tests: add min_flash option for some tests
- c625ab85 tests: rbtree test
- d7b7f511 tests: rbtree: Fix test so its actually runs
- 9bde3c06 tests: build_all: Add LPS22HB and LSM6DSL sensors build test


Re: nrf51822 mesh example RAM constraints.

Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...>
 

But after adding support for LOW POWER feature got RAM overflow again…
Could you review the use of RADIO_LL_LENGTH_OCTETS_RX_MAX, just a suspicion that its incorrectly used on nRF51, if so, you could be saving few hundred bytes.

Do feel free to send a PR if you fix something.


-Vinayak



From: users@lists.zephyrproject.org [mailto:users@lists.zephyrproject.org] On Behalf Of Antonio
Sent: Tuesday, April 10, 2018 9:00 AM
To: users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] nrf51822 mesh example RAM constraints.


On Apr 9, 2018, at 23:08, Chettimada, Vinayak Kariappa <mailto:vinayak.kariappa.chettimada@nordicsemi.no> wrote:

Hi Antonio,

Please take a look at this mail chain: https://lists.zephyrproject.org/g/devel/topic/16760883#1960

a BBC micro:bit with nRF51822 256KB flash and 16 KB RAM can support BLE mesh. Yes, it is stretch on a 16 KB RAM variant, but you can take a look at the output of “make rom_report” to fine tune/reduce RAM usages in your application.

Regards,
Vinayak


Thank you Vinayak,
Got it working after deleting health and level server.

Memory region         Used Size  Region Size  %age Used
           FLASH:      100376 B       256 KB     38.29%
            SRAM:       16264 B        16 KB     99.27%
        IDT_LIST:         132 B         2 KB      6.45%


But after adding support for LOW POWER feature got RAM overflow again…

Memory region         Used Size  Region Size  %age Used
           FLASH:      104320 B       256 KB     39.79%
            SRAM:       16424 B        16 KB    100.24%
        IDT_LIST:         132 B         2 KB      6.45


Since GATT (GATT_PROXY,PB_GATT,Peripherial) support is so memory hungry, can we use PB_ADV instead and do something like
remote provisioning ?

https://infocenter.nordicsemi.com/index.jsp?topic=/com.nordic.infocenter.meshsdk.v0.9.1/group__PB__REMOTE.html
https://infocenter.nordicsemi.com/index.jsp?topic=/com.nordic.infocenter.meshsdk.v0.9.1/md_examples_pb_remote_client_README.html
https://infocenter.nordicsemi.com/index.jsp?topic=/com.nordic.infocenter.meshsdk.v0.9.1/md_examples_pb_remote_server_README.html

Is this feature supported ?
Trying to make something useful out of the NRF51, like a simple low power node mesh device.
But seems they are good only as a beacons for now ;(
Or perhaps someone can recommend the way to provision NRF51 node over the PB_ADV barrier ?


Re: nrf51822 mesh example RAM constraints.

Antonio <anvivaldi27@...>
 


On Apr 9, 2018, at 23:08, Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> wrote:

Hi Antonio,

Please take a look at this mail chain: https://lists.zephyrproject.org/g/devel/topic/16760883#1960

a BBC micro:bit with nRF51822 256KB flash and 16 KB RAM can support BLE mesh. Yes, it is stretch on a 16 KB RAM variant, but you can take a look at the output of “make rom_report” to fine tune/reduce RAM usages in your application.

Regards,
Vinayak


Thank you Vinayak,
Got it working after deleting health and level server.

Memory region         Used Size  Region Size  %age Used
           FLASH:      100376 B       256 KB     38.29%
            SRAM:       16264 B        16 KB     99.27%
        IDT_LIST:         132 B         2 KB      6.45%


But after adding support for LOW POWER feature got RAM overflow again…

Memory region         Used Size  Region Size  %age Used
           FLASH:      104320 B       256 KB     39.79%
            SRAM:       16424 B        16 KB    100.24%
        IDT_LIST:         132 B         2 KB      6.45

Since GATT (GATT_PROXY,PB_GATT,Peripherial) support is so memory hungry, can we use PB_ADV instead and do something like
remote provisioning ?


Is this feature supported ?
Trying to make something useful out of the NRF51, like a simple low power node mesh device.
But seems they are good only as a beacons for now ;(
Or perhaps someone can recommend the way to provision NRF51 node over the PB_ADV barrier ?


Re: nrf51822 mesh example RAM constraints.

Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...>
 

Hi Antonio,

Please take a look at this mail chain: https://lists.zephyrproject.org/g/devel/topic/16760883#1960

a BBC micro:bit with nRF51822 256KB flash and 16 KB RAM can support BLE mesh. Yes, it is stretch on a 16 KB RAM variant, but you can take a look at the output of “make rom_report” to fine tune/reduce RAM usages in your application.

Regards,
Vinayak

On 9 Apr 2018, at 21:27, Antonio <anvivaldi27@...> wrote:

Hi All,

I was able finally to run basic mesh example on NRF51 device.
But I have an issue with RAM limits.
To be able to work with meshctl (Bluez) provisioning 
GATT_PROXY and PB_GATT should be enabled.
(It was not clear at first)
This leads to 128 bytes RAM overflow.
(NRF51822 has 256k Flash and 16k RAM)
I was able to temporary fix the issue reducing ISR stack from 640 to 512 bytes.
Bu as soon as my node receiving message (OnOff in my case) I have a HARD FAULT.

***** BOOTING ZEPHYR OS v1.11.99 - BUILD: Apr  9 2018 18:58:45 *****
Ver 1.06 ... Initializing...
 PB_GATT enabled
Bluetooth initialized
Mesh initialized
 * Prov complete.
***** HARD FAULT *****
  Executing thread ID (thread): 0x20001660
  Faulting instruction address:  0x20002880
Fatal fault in ISR! Spinning…



So the main question is:
Is it possible to tune some other parameters on CONFIG or remove some features to fit basic MESH example to NRF51 device?
Or should I forget about BLE Mesh on NRF51822 ?
Another idea is to hardcode provisioning information and forget about provisioning procedure at all,
But it is not the best way for real production setup.

Thank you.




nrf51822 mesh example RAM constraints.

Antonio <anvivaldi27@...>
 

Hi All,

I was able finally to run basic mesh example on NRF51 device.
But I have an issue with RAM limits.
To be able to work with meshctl (Bluez) provisioning 
GATT_PROXY and PB_GATT should be enabled.
(It was not clear at first)
This leads to 128 bytes RAM overflow.
(NRF51822 has 256k Flash and 16k RAM)
I was able to temporary fix the issue reducing ISR stack from 640 to 512 bytes.
Bu as soon as my node receiving message (OnOff in my case) I have a HARD FAULT.

***** BOOTING ZEPHYR OS v1.11.99 - BUILD: Apr  9 2018 18:58:45 *****
Ver 1.06 ... Initializing...
 PB_GATT enabled
Bluetooth initialized
Mesh initialized
 * Prov complete.
***** HARD FAULT *****
  Executing thread ID (thread): 0x20001660
  Faulting instruction address:  0x20002880
Fatal fault in ISR! Spinning…



So the main question is:
Is it possible to tune some other parameters on CONFIG or remove some features to fit basic MESH example to NRF51 device?
Or should I forget about BLE Mesh on NRF51822 ?
Another idea is to hardcode provisioning information and forget about provisioning procedure at all,
But it is not the best way for real production setup.

Thank you.



Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

ashish shukla <ashish.shukla@...>
 

Hi Marti,

Thanks for pointing out the source of the problem, it's working for now.

Also, with help of detailed documentation, I was able to implement FOTA feature.
 

--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development


Please consider the environment before printing this e-mail or its attachments.

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi


Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

vikrant8051 <vikrant8051@...>
 

Hi,

I integrated my Nordic Blinky (which toggles LED1) into SMP_SVR example & flashed it along with mcuboot.

Then re-edit SMP_SVR to toggle LED4, & flashed this firmware using #FOTA feature.

So it is working for me !!

Thank to all !!

On Sun, Apr 8, 2018 at 12:27 AM, Marti Bolivar <marti@...> wrote:
Hi Carles, Ashish,

On Sat, Apr 7, 2018, 12:56 AM ashish shukla <ashish.shukla@...> wrote:
Hi Carles, 

Following the documentation provided : 

Step1 : Build MCUboot 
Step2: Flash MCUboot 

what I understand is these files reside in /zephyr/subsys/dfu, 

This is the problem.

Ashish, mcuboot is not part of Zephyr. It is an independent project. You need to build it using the instructions Carles gave you later in the thread.

The dfu subsystem contains zephyr-specific code for interfacing with mcuboot from the chain-loaded zephyr image. It is not a standalone application.

Marti



Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

Marti Bolivar
 

Hi Carles, Ashish,

On Sat, Apr 7, 2018, 12:56 AM ashish shukla <ashish.shukla@...> wrote:
Hi Carles, 

Following the documentation provided : 

Step1 : Build MCUboot 
Step2: Flash MCUboot 

what I understand is these files reside in /zephyr/subsys/dfu, 

This is the problem.

Ashish, mcuboot is not part of Zephyr. It is an independent project. You need to build it using the instructions Carles gave you later in the thread.

The dfu subsystem contains zephyr-specific code for interfacing with mcuboot from the chain-loaded zephyr image. It is not a standalone application.

Marti


Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

Carles Cufi
 

Hi Ashish,

 

If you are trying to build MCUboot then you need to go into the MCUboot folder, as per these instructions:

 

https://mcuboot.com/mcuboot/readme-zephyr.html

 

In essence the commands would be:

 

$ git clone git@...:runtimeco/mcuboot.git

$ cd mcuboot

$ cd boot/zephyr

$ mkdir build

$ cd build

$ cmake -GNinja -DBOARD=nrf52840_pca10056 ..

$ ninja

 

This works fine for me on Linux. I am really not sure why you are getting that error. Perhaps you could try joining our IRC channel (#zephyrproject on freenode.net) during weekdays CET working hours and I could try to help you there.

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 07 April 2018 06:56
To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi Carles,

Following the documentation provided :

Step1 : Build MCUboot

Step2: Flash MCUboot

what I understand is these files reside in /zephyr/subsys/dfu, I create a build directory in present directory and run

cmake -GNinja -DBOARD=nrf52840_pca10056 ..

This will lead into violation of policy CMP0002.  
Only after flashing the MCUboot, I can move to next step 
Step3: Build smp_svr 
For this I'm at /smp_svr/ directory, and run the following commands 
mkdir -p build/nrf52_pca10040 && cd build/nrf52_pca10040
cmake -GNinja -DBOARD=nrf52_pca10040 ../..
The latter one, produces same results. Also, for first time I'd replaced board name with nrf52840_pca10056, and in either case, I got same error. 
 
 
 
 

 

 


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 6:55 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Can you please paste here the full sequence of commands you are using please?

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 14:14


To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi,

Earlier I was building from /zephyr/subsys/dfu/build,

Even building from samples/subsys/mgmt/mcumgr/smp_svr/build , leads to same results


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 5:30 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Just to clarify, are you building from:

 

samples/subsys/mgmt/mcumgr/smp_svr/build ?

 

From the screenshot it seems you are trying to build from somewhere else?

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 13:58


To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi Carles,

. I'm working with CMake 3.8.2

.  I've sourced zephyr-env.sh in zephyr tree.

I'm attaching a snap of terminal for you to have a look, which iterates violation of policy CMP0002 again and again.


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 5:09 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Make sure of 2 things:

 

·         You are using CMake 3.4 or higher (cmake –version to check)

·         You have sourced zephyr-env.sh in the Zephyr tree before building MCUboot

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 13:36
To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi Carles,

Thanks a lot for pointing us to such a detailed documentation. However, while following through doc, I ran into an issue.  When I tried to build MCUboot in it's present form, after adding a prj.cnf file, and adding following line at the starting of CMakeLists.txt

include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
project(NONE)

policy CMP0002 of cmake is violated. How can this issue be resolved ?

 


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 2:22 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Here is the published documentation:

 

http://docs.zephyrproject.org/samples/subsys/mgmt/mcumgr/smp_svr/README.html

 

Regards,

 

Carles

 

 

From: zephyr-devel-bounces@... <zephyr-devel-bounces@...> On Behalf Of ashish.shukla@...
Sent: 21 March 2018 05:15
To: zephyr-devel@...; zephyr-users@...
Subject: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi all,

I've been waiting for FOTA and FCB support in zephyr and now when it is supported, I cannot see any samples available or proper documentation to use these features in my project.

Any help regarding the same would be of great help.

 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

 

 

 


Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

vikrant8051 <vikrant8051@...>
 

Hi,

After flashing $zephyr/samples/subsys/mgmt/mcumgr/smp_svr signed.hex on nRF52840
along with pre-flashed #mcuboot, I am able to execute following commands

#sudo mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='Zephyr' echo hello
o/p -> hello

#sudo mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='Zephyr' image list

o/p -> Images:
 slot=0
    version: 1.0.0
    bootable: true
    flags: active confirmed
    hash: 7c83263c9b0ebfbe192befd2e237c029ea3c7e56e7a30987cd20adb72897c34d
Split status: N/A (0)

#sudo mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='Zephyr' image upload signed.bin  // <--- signed.hex (Hello World example signed using imgtool.py)
o/p -> 44.49 KiB / 44.49 KiB [=================================================================================================]  99.99%
Done

#sudo mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='Zephyr' image list
o/p->
Images:
 slot=0
    version: 1.0.0
    bootable: true
    flags: active confirmed
    hash: 7c83263c9b0ebfbe192befd2e237c029ea3c7e56e7a30987cd20adb72897c34d
 slot=1
    version: 1.0.0
    bootable: true
    flags:
    hash: 65d9a1543f00b55e9cad4a56fb2a7d6934a6422320db4370f9ddfc0e2d663702
Split status: N/A (0)

#mcumgr --conntype ble --connstring 'peer_name=Zephyr' image test 65d9a1543f00b55e9cad4a56fb2a7d6934a6422320db4370f9ddfc0e2d663702
o/p->
Images:
 slot=0
    version: 1.0.0
    bootable: true
    flags: active confirmed
    hash: 7c83263c9b0ebfbe192befd2e237c029ea3c7e56e7a30987cd20adb72897c34d
 slot=1
    version: 1.0.0
    bootable: true
    flags: pending
    hash: 65d9a1543f00b55e9cad4a56fb2a7d6934a6422320db4370f9ddfc0e2d663702
Split status: N/A (0)


#sudo mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='Zephyr' reset
Done

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

But #nRF52840_PDK board does not print anything on its serial terminal.
And
#sudo mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='Zephyr' image confirm
O/P -> Error: 6

That means mcuboot, is not able to swap image from slot1 to slot0. 
Any solution or trick ?

Thanks,
vikrant8051









On Sat, Apr 7, 2018 at 11:33 AM, vikrant8051 <vikrant8051@...> wrote:
Hi David,

Your trick worked for me. Thank You !!

Using this i got version of cryptography

     pip freeze | grep "cryptography"
     cryptography==1.2.3

So I uninstalled i& reinstall it.

    pip uninstall cryptography
    pip install cryptography


I followed instructions on this link -> http://docs.zephyrproject.org/samples/subsys/mgmt/mcumgr/smp_svr/README.html

& flashed smp_server's signed.hex on #nRF52840_PDK board.

Now #nRFConnect is showing something like as per attached image ..

 Thank You !!

On Fri, Apr 6, 2018 at 9:45 PM, David Brown <david.brown@...> wrote:
Adding dev-mcuboot@...

On Fri, Apr 06, 2018 at 02:27:14PM +0000, Giuliano Franchetto wrote:

My bad, I think it was the cryptography python3 module we had to upgrade.

My version is cryptography==2.1.4

It'd be nice if we could figure out what minimum version of
cryptography we need, so we could put that in the requirements.txt
file.  Unfortunately, the stack trace isn't very help, which makes it
hard to even tell what API is missing/changed.

David






Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

vikrant8051 <vikrant8051@...>
 

Hi David,

Your trick worked for me. Thank You !!

Using this i got version of cryptography

     pip freeze | grep "cryptography"
     cryptography==1.2.3

So I uninstalled i& reinstall it.

    pip uninstall cryptography
    pip install cryptography


I followed instructions on this link -> http://docs.zephyrproject.org/samples/subsys/mgmt/mcumgr/smp_svr/README.html

& flashed smp_server's signed.hex on #nRF52840_PDK board.

Now #nRFConnect is showing something like as per attached image ..

 Thank You !!

On Fri, Apr 6, 2018 at 9:45 PM, David Brown <david.brown@...> wrote:
Adding dev-mcuboot@...

On Fri, Apr 06, 2018 at 02:27:14PM +0000, Giuliano Franchetto wrote:

My bad, I think it was the cryptography python3 module we had to upgrade.

My version is cryptography==2.1.4

It'd be nice if we could figure out what minimum version of
cryptography we need, so we could put that in the requirements.txt
file.  Unfortunately, the stack trace isn't very help, which makes it
hard to even tell what API is missing/changed.

David





Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

ashish shukla <ashish.shukla@...>
 

Hi Carles,

Following the documentation provided :

Step1 : Build MCUboot
Step2: Flash MCUboot

what I understand is these files reside in /zephyr/subsys/dfu, I create a build directory in present directory and run

cmake -GNinja -DBOARD=nrf52840_pca10056 ..
This will lead into violation of policy CMP0002.  

Only after flashing the MCUboot, I can move to next step 

Step3: Build smp_svr 

For this I'm at /smp_svr/ directory, and run the following commands 
mkdir -p build/nrf52_pca10040 && cd build/nrf52_pca10040
cmake -GNinja -DBOARD=nrf52_pca10040 ../..
The latter one, produces same results. Also, for first time I'd replaced board name with nrf52840_pca10056, and in either case, I got same error. 



 




--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development


Please consider the environment before printing this e-mail or its attachments.

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi


On Fri, Apr 6, 2018 at 6:55 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Can you please paste here the full sequence of commands you are using please?

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 14:14


To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi,

Earlier I was building from /zephyr/subsys/dfu/build,

Even building from samples/subsys/mgmt/mcumgr/smp_svr/build , leads to same results


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 5:30 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Just to clarify, are you building from:

 

samples/subsys/mgmt/mcumgr/smp_svr/build ?

 

From the screenshot it seems you are trying to build from somewhere else?

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 13:58


To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi Carles,

. I'm working with CMake 3.8.2

.  I've sourced zephyr-env.sh in zephyr tree.

I'm attaching a snap of terminal for you to have a look, which iterates violation of policy CMP0002 again and again.


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 5:09 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Make sure of 2 things:

 

·         You are using CMake 3.4 or higher (cmake –version to check)

·         You have sourced zephyr-env.sh in the Zephyr tree before building MCUboot

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 13:36
To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi Carles,

Thanks a lot for pointing us to such a detailed documentation. However, while following through doc, I ran into an issue.  When I tried to build MCUboot in it's present form, after adding a prj.cnf file, and adding following line at the starting of CMakeLists.txt

include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
project(NONE)

policy CMP0002 of cmake is violated. How can this issue be resolved ?

 


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 2:22 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Here is the published documentation:

 

http://docs.zephyrproject.org/samples/subsys/mgmt/mcumgr/smp_svr/README.html

 

Regards,

 

Carles

 

 

From: zephyr-devel-bounces@lists.zephyrproject.org <zephyr-devel-bounces@lists.zephyrproject.org> On Behalf Of ashish.shukla@...
Sent: 21 March 2018 05:15
To: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi all,

I've been waiting for FOTA and FCB support in zephyr and now when it is supported, I cannot see any samples available or proper documentation to use these features in my project.

Any help regarding the same would be of great help.

 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

 

 



Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

David Brown <david.brown@...>
 

Adding dev-mcuboot@lists.runtime.co

On Fri, Apr 06, 2018 at 02:27:14PM +0000, Giuliano Franchetto wrote:

My bad, I think it was the cryptography python3 module we had to upgrade.

My version is cryptography==2.1.4
It'd be nice if we could figure out what minimum version of
cryptography we need, so we could put that in the requirements.txt
file. Unfortunately, the stack trace isn't very help, which makes it
hard to even tell what API is missing/changed.

David


Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

Giuliano Franchetto
 

Hi Vikrant,

My bad, I think it was the cryptography python3 module we had to upgrade.

My version is cryptography==2.1.4

Regards

-----
De : users@lists.zephyrproject.org <users@lists.zephyrproject.org> De la part de vikrant8051
Envoyé : vendredi 6 avril 2018 16:24
À : users@lists.zephyrproject.org
Cc : users@lists.zephyrproject.org; devel@lists.zephyrproject.org
Objet : Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

Hi Giuliano,
To update openssl I execute -> apt-get install --only-upgrade openssl
But my system is already running latest version of it & hence return -> openssl is already the newest version (1.0.2g-1ubuntu4.11).
Thanks !!

On Fri, Apr 6, 2018 at 7:46 PM, Giuliano Franchetto <mailto:giuliano.franchetto@intellinium.com> wrote:
Hi Vikrant,

I already had this error. From what I remember, you need to upgrade the openssl library of your system.

Regards,
Giuliano

----
De : mailto:users@lists.zephyrproject.org <mailto:users@lists.zephyrproject.org> De la part de vikrant
Envoyé : vendredi 6 avril 2018 15:35
À : mailto:users@lists.zephyrproject.org
Objet : Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

Hi Carles,
After executing this command,
~/src/mcuboot/scripts/imgtool.py sign \
     --key ~/src/mcuboot/root-rsa-2048.pem \
     --header-size 0x200 \
     --align 8 \
     --version 1.0 \
     --included-header \
     <path-to-zephyr.(bin|hex)> signed.(bin|hex)
I got following error,

Traceback (most recent call last):
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 145, in <module>
    args()
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 142, in args
    subcmds[args.subcmd](args)
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 85, in do_sign
    img.sign(key)
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool/image.py", line 136, in sign
    sig = key.sign(bytes(self.payload))
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool/keys/rsa.py", line 92, in sign
Thanks !!


On Fri, Apr 6, 2018 at 6:55 PM, Cufi, Carles <mailto:mailto:carles.cufi@nordicsemi.no> wrote:
Hi Ashish,
 
Can you please paste here the full sequence of commands you are using please?
 
Thanks,
 
Carles
 
From: mailto:mailto:ashish.shukla@corvi.com <mailto:mailto:ashish.shukla@corvi.com>
Sent: 06 April 2018 14:14
To: Cufi, Carles <mailto:mailto:Carles.Cufi@nordicsemi.no>
Cc: mailto:mailto:users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0
 
Hi,
Earlier I was building from /zephyr/subsys/dfu/build,
Even building from samples/subsys/mgmt/mcumgr/smp_svr/build , leads to same results


 
--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development
http://www.corvi.com/
 

Please consider the environment before printing this e-mail or its attachments.
 
Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
 
 
On Fri, Apr 6, 2018 at 5:30 PM, Cufi, Carles <mailto:mailto:carles.cufi@nordicsemi.no> wrote:
Hi Ashish,
 
Just to clarify, are you building from:
 
samples/subsys/mgmt/mcumgr/smp_svr/build ?
 
From the screenshot it seems you are trying to build from somewhere else?
 
Thanks,
 
Carles
 
From: mailto:mailto:ashish.shukla@corvi.com <mailto:mailto:ashish.shukla@corvi.com>
Sent: 06 April 2018 13:58

To: Cufi, Carles <mailto:mailto:Carles.Cufi@nordicsemi.no>
Cc: mailto:mailto:users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0
 
Hi Carles,
. I'm working with CMake 3.8.2
.  I've sourced zephyr-env.sh in zephyr tree.
I'm attaching a snap of terminal for you to have a look, which iterates violation of policy CMP0002 again and again.


 
--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development
http://www.corvi.com/
 

Please consider the environment before printing this e-mail or its attachments.
 
Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
 
 
On Fri, Apr 6, 2018 at 5:09 PM, Cufi, Carles <mailto:mailto:carles.cufi@nordicsemi.no> wrote:
Hi Ashish,
 
Make sure of 2 things:
 
•         You are using CMake 3.4 or higher (cmake –version to check)
•         You have sourced zephyr-env.sh in the Zephyr tree before building MCUboot
 
Thanks,
 
Carles
 
From: mailto:mailto:ashish.shukla@corvi.com <mailto:mailto:ashish.shukla@corvi.com>
Sent: 06 April 2018 13:36
To: Cufi, Carles <mailto:mailto:Carles.Cufi@nordicsemi.no>
Cc: mailto:mailto:users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0
 
Hi Carles,
Thanks a lot for pointing us to such a detailed documentation. However, while following through doc, I ran into an issue.  When I tried to build MCUboot in it's present form, after adding a prj.cnf file, and adding following line at the starting of CMakeLists.txt

include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
project(NONE)

policy CMP0002 of cmake is violated. How can this issue be resolved ?
 


 
--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development
http://www.corvi.com/
 

Please consider the environment before printing this e-mail or its attachments.
 
Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
 
 
On Fri, Apr 6, 2018 at 2:22 PM, Cufi, Carles <mailto:mailto:carles.cufi@nordicsemi.no> wrote:
Hi Ashish,
 
Here is the published documentation:
 
http://docs.zephyrproject.org/samples/subsys/mgmt/mcumgr/smp_svr/README.html
 
Regards,
 
Carles
 
 
From: mailto:mailto:zephyr-devel-bounces@lists.zephyrproject.org <mailto:mailto:zephyr-devel-bounces@lists.zephyrproject.org> On Behalf Of mailto:mailto:ashish.shukla@corvi.com
Sent: 21 March 2018 05:15
To: mailto:mailto:zephyr-devel@lists.zephyrproject.org; mailto:mailto:zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0
 
Hi all,
I've been waiting for FOTA and FCB support in zephyr and now when it is supported, I cannot see any samples available or proper documentation to use these features in my project.
Any help regarding the same would be of great help.

 
--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development
http://www.corvi.com/
 

Please consider the environment before printing this e-mail or its attachments.
 
Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi


Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

vikrant8051 <vikrant8051@...>
 

Hi Giuliano,

To update openssl I execute -> apt-get install --only-upgrade openssl

But my system is already running latest version of it & hence return -> openssl is already the newest version (1.0.2g-1ubuntu4.11).

Thanks !!

On Fri, Apr 6, 2018 at 7:46 PM, Giuliano Franchetto <giuliano.franchetto@...> wrote:
Hi Vikrant,

I already had this error. From what I remember, you need to upgrade the openssl library of your system.

Regards,
Giuliano

----
De : users@... <users@...> De la part de vikrant
Envoyé : vendredi 6 avril 2018 15:35
À : users@...
Objet : Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

Hi Carles,
After executing this command,
~/src/mcuboot/scripts/imgtool.py sign \
     --key ~/src/mcuboot/root-rsa-2048.pem \
     --header-size 0x200 \
     --align 8 \
     --version 1.0 \
     --included-header \
     <path-to-zephyr.(bin|hex)> signed.(bin|hex)
I got following error,

Traceback (most recent call last):
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 145, in <module>
    args()
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 142, in args
    subcmds[args.subcmd](args)
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 85, in do_sign
    img.sign(key)
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool/image.py", line 136, in sign
    sig = key.sign(bytes(self.payload))
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool/keys/rsa.py", line 92, in sign
Thanks !!


On Fri, Apr 6, 2018 at 6:55 PM, Cufi, Carles <mailto:carles.cufi@nordicsemi.no> wrote:
Hi Ashish,
 
Can you please paste here the full sequence of commands you are using please?
 
Thanks,
 
Carles
 
From: mailto:ashish.shukla@... <mailto:ashish.shukla@corvi.com>
Sent: 06 April 2018 14:14
To: Cufi, Carles <mailto:Carles.Cufi@nordicsemi.no>
Cc: mailto:users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0
 
Hi,
Earlier I was building from /zephyr/subsys/dfu/build,
Even building from samples/subsys/mgmt/mcumgr/smp_svr/build , leads to same results


 
--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development
http://www.corvi.com/
 

Please consider the environment before printing this e-mail or its attachments.
 
Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
 
 
On Fri, Apr 6, 2018 at 5:30 PM, Cufi, Carles <mailto:carles.cufi@nordicsemi.no> wrote:
Hi Ashish,
 
Just to clarify, are you building from:
 
samples/subsys/mgmt/mcumgr/smp_svr/build ?
 
From the screenshot it seems you are trying to build from somewhere else?
 
Thanks,
 
Carles
 
From: mailto:ashish.shukla@... <mailto:ashish.shukla@corvi.com>
Sent: 06 April 2018 13:58

To: Cufi, Carles <mailto:Carles.Cufi@nordicsemi.no>
Cc: mailto:users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0
 
Hi Carles,
. I'm working with CMake 3.8.2
.  I've sourced zephyr-env.sh in zephyr tree.
I'm attaching a snap of terminal for you to have a look, which iterates violation of policy CMP0002 again and again.


 
--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development
http://www.corvi.com/
 

Please consider the environment before printing this e-mail or its attachments.
 
Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
 
 
On Fri, Apr 6, 2018 at 5:09 PM, Cufi, Carles <mailto:carles.cufi@nordicsemi.no> wrote:
Hi Ashish,
 
Make sure of 2 things:
 
•         You are using CMake 3.4 or higher (cmake –version to check)
•         You have sourced zephyr-env.sh in the Zephyr tree before building MCUboot
 
Thanks,
 
Carles
 
From: mailto:ashish.shukla@... <mailto:ashish.shukla@corvi.com>
Sent: 06 April 2018 13:36
To: Cufi, Carles <mailto:Carles.Cufi@nordicsemi.no>
Cc: mailto:users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0
 
Hi Carles,
Thanks a lot for pointing us to such a detailed documentation. However, while following through doc, I ran into an issue.  When I tried to build MCUboot in it's present form, after adding a prj.cnf file, and adding following line at the starting of CMakeLists.txt

include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
project(NONE)

policy CMP0002 of cmake is violated. How can this issue be resolved ?
 


 
--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development
http://www.corvi.com/
 

Please consider the environment before printing this e-mail or its attachments.
 
Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
 
 
On Fri, Apr 6, 2018 at 2:22 PM, Cufi, Carles <mailto:carles.cufi@nordicsemi.no> wrote:
Hi Ashish,
 
Here is the published documentation:
 
http://docs.zephyrproject.org/samples/subsys/mgmt/mcumgr/smp_svr/README.html
 
Regards,
 
Carles
 
 
From: mailto:zephyr-devel-bounces@lists.zephyrproject.org <mailto:zephyr-devel-bounces@lists.zephyrproject.org> On Behalf Of mailto:ashish.shukla@...
Sent: 21 March 2018 05:15
To: mailto:zephyr-devel@lists.zephyrproject.org; mailto:zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0
 
Hi all,
I've been waiting for FOTA and FCB support in zephyr and now when it is supported, I cannot see any samples available or proper documentation to use these features in my project.
Any help regarding the same would be of great help.

 
--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development
http://www.corvi.com/
 

Please consider the environment before printing this e-mail or its attachments.
 
Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
 
 
 
 







Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

Giuliano Franchetto
 

Hi Vikrant,

I already had this error. From what I remember, you need to upgrade the openssl library of your system.

Regards,
Giuliano

----
De : users@lists.zephyrproject.org <users@lists.zephyrproject.org> De la part de vikrant
Envoyé : vendredi 6 avril 2018 15:35
À : users@lists.zephyrproject.org
Objet : Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

Hi Carles,
After executing this command,
~/src/mcuboot/scripts/imgtool.py sign \
--key ~/src/mcuboot/root-rsa-2048.pem \
--header-size 0x200 \
--align 8 \
--version 1.0 \
--included-header \
<path-to-zephyr.(bin|hex)> signed.(bin|hex)
I got following error,

Traceback (most recent call last):
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 145, in <module>
    args()
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 142, in args
    subcmds[args.subcmd](args)
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 85, in do_sign
    img.sign(key)
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool/image.py", line 136, in sign
    sig = key.sign(bytes(self.payload))
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool/keys/rsa.py", line 92, in sign
Thanks !!

On Fri, Apr 6, 2018 at 6:55 PM, Cufi, Carles <mailto:carles.cufi@nordicsemi.no> wrote:
Hi Ashish,
 
Can you please paste here the full sequence of commands you are using please?
 
Thanks,
 
Carles
 
From: mailto:ashish.shukla@corvi.com <mailto:ashish.shukla@corvi.com>
Sent: 06 April 2018 14:14
To: Cufi, Carles <mailto:Carles.Cufi@nordicsemi.no>
Cc: mailto:users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0
 
Hi,
Earlier I was building from /zephyr/subsys/dfu/build,
Even building from samples/subsys/mgmt/mcumgr/smp_svr/build , leads to same results


 
--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development
http://www.corvi.com/
 

Please consider the environment before printing this e-mail or its attachments.
 
Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
 
 
On Fri, Apr 6, 2018 at 5:30 PM, Cufi, Carles <mailto:carles.cufi@nordicsemi.no> wrote:
Hi Ashish,
 
Just to clarify, are you building from:
 
samples/subsys/mgmt/mcumgr/smp_svr/build ?
 
From the screenshot it seems you are trying to build from somewhere else?
 
Thanks,
 
Carles
 
From: mailto:ashish.shukla@corvi.com <mailto:ashish.shukla@corvi.com>
Sent: 06 April 2018 13:58

To: Cufi, Carles <mailto:Carles.Cufi@nordicsemi.no>
Cc: mailto:users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0
 
Hi Carles,
. I'm working with CMake 3.8.2
.  I've sourced zephyr-env.sh in zephyr tree.
I'm attaching a snap of terminal for you to have a look, which iterates violation of policy CMP0002 again and again.


 
--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development
http://www.corvi.com/
 

Please consider the environment before printing this e-mail or its attachments.
 
Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
 
 
On Fri, Apr 6, 2018 at 5:09 PM, Cufi, Carles <mailto:carles.cufi@nordicsemi.no> wrote:
Hi Ashish,
 
Make sure of 2 things:
 
•         You are using CMake 3.4 or higher (cmake –version to check)
•         You have sourced zephyr-env.sh in the Zephyr tree before building MCUboot
 
Thanks,
 
Carles
 
From: mailto:ashish.shukla@corvi.com <mailto:ashish.shukla@corvi.com>
Sent: 06 April 2018 13:36
To: Cufi, Carles <mailto:Carles.Cufi@nordicsemi.no>
Cc: mailto:users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0
 
Hi Carles,
Thanks a lot for pointing us to such a detailed documentation. However, while following through doc, I ran into an issue.  When I tried to build MCUboot in it's present form, after adding a prj.cnf file, and adding following line at the starting of CMakeLists.txt

include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
project(NONE)

policy CMP0002 of cmake is violated. How can this issue be resolved ?
 


 
--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development
http://www.corvi.com/
 

Please consider the environment before printing this e-mail or its attachments.
 
Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi
 
 
On Fri, Apr 6, 2018 at 2:22 PM, Cufi, Carles <mailto:carles.cufi@nordicsemi.no> wrote:
Hi Ashish,
 
Here is the published documentation:
 
http://docs.zephyrproject.org/samples/subsys/mgmt/mcumgr/smp_svr/README.html
 
Regards,
 
Carles
 
 
From: mailto:zephyr-devel-bounces@lists.zephyrproject.org <mailto:zephyr-devel-bounces@lists.zephyrproject.org> On Behalf Of mailto:ashish.shukla@corvi.com
Sent: 21 March 2018 05:15
To: mailto:zephyr-devel@lists.zephyrproject.org; mailto:zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0
 
Hi all,
I've been waiting for FOTA and FCB support in zephyr and now when it is supported, I cannot see any samples available or proper documentation to use these features in my project.
Any help regarding the same would be of great help.

 
--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development
http://www.corvi.com/
 

Please consider the environment before printing this e-mail or its attachments.
 
Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi


Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

vikrant <vikrant8051@...>
 

Hi Carles,

After executing this command,
~/src/mcuboot/scripts/imgtool.py sign \
     --key ~/src/mcuboot/root-rsa-2048.pem \
     --header-size 0x200 \
     --align 8 \
     --version 1.0 \
     --included-header \
     <path-to-zephyr.(bin|hex)> signed.(bin|hex)
I got following error,

Traceback (most recent call last):
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 145, in <module>
    args()
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 142, in args
    subcmds[args.subcmd](args)
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 85, in do_sign
    img.sign(key)
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool/image.py", line 136, in sign
    sig = key.sign(bytes(self.payload))
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool/keys/rsa.py", line 92, in sign

Thanks !!


On Fri, Apr 6, 2018 at 6:55 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Can you please paste here the full sequence of commands you are using please?

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 14:14
To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi,

Earlier I was building from /zephyr/subsys/dfu/build,

Even building from samples/subsys/mgmt/mcumgr/smp_svr/build , leads to same results


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 5:30 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Just to clarify, are you building from:

 

samples/subsys/mgmt/mcumgr/smp_svr/build ?

 

From the screenshot it seems you are trying to build from somewhere else?

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 13:58


To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi Carles,

. I'm working with CMake 3.8.2

.  I've sourced zephyr-env.sh in zephyr tree.

I'm attaching a snap of terminal for you to have a look, which iterates violation of policy CMP0002 again and again.


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 5:09 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Make sure of 2 things:

 

·         You are using CMake 3.4 or higher (cmake –version to check)

·         You have sourced zephyr-env.sh in the Zephyr tree before building MCUboot

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 13:36
To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi Carles,

Thanks a lot for pointing us to such a detailed documentation. However, while following through doc, I ran into an issue.  When I tried to build MCUboot in it's present form, after adding a prj.cnf file, and adding following line at the starting of CMakeLists.txt

include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
project(NONE)

policy CMP0002 of cmake is violated. How can this issue be resolved ?

 


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 2:22 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Here is the published documentation:

 

http://docs.zephyrproject.org/samples/subsys/mgmt/mcumgr/smp_svr/README.html

 

Regards,

 

Carles

 

 

From: zephyr-devel-bounces@lists.zephyrproject.org <zephyr-devel-bounces@lists.zephyrproject.org> On Behalf Of ashish.shukla@...
Sent: 21 March 2018 05:15
To: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi all,

I've been waiting for FOTA and FCB support in zephyr and now when it is supported, I cannot see any samples available or proper documentation to use these features in my project.

Any help regarding the same would be of great help.

 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

 

 



Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

vikrant <vikrant8051@...>
 

Hi Carles,

After executing this command,
~/src/mcuboot/scripts/imgtool.py sign \
     --key ~/src/mcuboot/root-rsa-2048.pem \
     --header-size 0x200 \
     --align 8 \
     --version 1.0 \
     --included-header \
     <path-to-zephyr.(bin|hex)> signed.(bin|hex)
I got following error,

Traceback (most recent call last):
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 145, in <module>
    args()
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 142, in args
    subcmds[args.subcmd](args)
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool.py", line 85, in do_sign
    img.sign(key)
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool/image.py", line 136, in sign
    sig = key.sign(bytes(self.payload))
  File "/home/vikrant/projects/zephyr/mcuboot/scripts/imgtool/keys/rsa.py", line 92, in sign
    return self.key.sign(
AttributeError: '_RSAPrivateKey' object has no attribute 'sign'



On Fri, Apr 6, 2018 at 6:55 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Can you please paste here the full sequence of commands you are using please?

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 14:14
To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi,

Earlier I was building from /zephyr/subsys/dfu/build,

Even building from samples/subsys/mgmt/mcumgr/smp_svr/build , leads to same results


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 5:30 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Just to clarify, are you building from:

 

samples/subsys/mgmt/mcumgr/smp_svr/build ?

 

From the screenshot it seems you are trying to build from somewhere else?

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 13:58


To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi Carles,

. I'm working with CMake 3.8.2

.  I've sourced zephyr-env.sh in zephyr tree.

I'm attaching a snap of terminal for you to have a look, which iterates violation of policy CMP0002 again and again.


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 5:09 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Make sure of 2 things:

 

·         You are using CMake 3.4 or higher (cmake –version to check)

·         You have sourced zephyr-env.sh in the Zephyr tree before building MCUboot

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 13:36
To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi Carles,

Thanks a lot for pointing us to such a detailed documentation. However, while following through doc, I ran into an issue.  When I tried to build MCUboot in it's present form, after adding a prj.cnf file, and adding following line at the starting of CMakeLists.txt

include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
project(NONE)

policy CMP0002 of cmake is violated. How can this issue be resolved ?

 


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 2:22 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Here is the published documentation:

 

http://docs.zephyrproject.org/samples/subsys/mgmt/mcumgr/smp_svr/README.html

 

Regards,

 

Carles

 

 

From: zephyr-devel-bounces@lists.zephyrproject.org <zephyr-devel-bounces@lists.zephyrproject.org> On Behalf Of ashish.shukla@...
Sent: 21 March 2018 05:15
To: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi all,

I've been waiting for FOTA and FCB support in zephyr and now when it is supported, I cannot see any samples available or proper documentation to use these features in my project.

Any help regarding the same would be of great help.

 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

 

 



Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

Carles Cufi
 

Hi Ashish,

 

Can you please paste here the full sequence of commands you are using please?

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 14:14
To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi,

Earlier I was building from /zephyr/subsys/dfu/build,

Even building from samples/subsys/mgmt/mcumgr/smp_svr/build , leads to same results


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 5:30 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Just to clarify, are you building from:

 

samples/subsys/mgmt/mcumgr/smp_svr/build ?

 

From the screenshot it seems you are trying to build from somewhere else?

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 13:58


To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi Carles,

. I'm working with CMake 3.8.2

.  I've sourced zephyr-env.sh in zephyr tree.

I'm attaching a snap of terminal for you to have a look, which iterates violation of policy CMP0002 again and again.


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 5:09 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Make sure of 2 things:

 

·         You are using CMake 3.4 or higher (cmake –version to check)

·         You have sourced zephyr-env.sh in the Zephyr tree before building MCUboot

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 13:36
To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi Carles,

Thanks a lot for pointing us to such a detailed documentation. However, while following through doc, I ran into an issue.  When I tried to build MCUboot in it's present form, after adding a prj.cnf file, and adding following line at the starting of CMakeLists.txt

include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
project(NONE)

policy CMP0002 of cmake is violated. How can this issue be resolved ?

 


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 2:22 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Here is the published documentation:

 

http://docs.zephyrproject.org/samples/subsys/mgmt/mcumgr/smp_svr/README.html

 

Regards,

 

Carles

 

 

From: zephyr-devel-bounces@... <zephyr-devel-bounces@...> On Behalf Of ashish.shukla@...
Sent: 21 March 2018 05:15
To: zephyr-devel@...; zephyr-users@...
Subject: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi all,

I've been waiting for FOTA and FCB support in zephyr and now when it is supported, I cannot see any samples available or proper documentation to use these features in my project.

Any help regarding the same would be of great help.

 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

 

 


Re: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

ashish shukla <ashish.shukla@...>
 

Hey Rodrigo,

whenever I run a cmake, control is stuck in a loop. And for the very first time, running  "make pristine" produces

make: *** No rule to make target 'pristine'


--
Warm regards,
Ashish Shukla
Jr. Embedded Engineer
Research & Development


Please consider the environment before printing this e-mail or its attachments.

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi


On Fri, Apr 6, 2018 at 5:39 PM, Rodrigo Peixoto <rodrigopex@...> wrote:
Ashish, inside the build folder, try a "make pristine" and then run cmake again. It helps me a lot, mainly when I have changed the target or other major thing.

I hope it helps.

Best regards,
Rodrigo Peixoto
On Fri, 6 Apr 2018 at 09:00 Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Just to clarify, are you building from:

 

samples/subsys/mgmt/mcumgr/smp_svr/build ?

 

From the screenshot it seems you are trying to build from somewhere else?

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 13:58


To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi Carles,

. I'm working with CMake 3.8.2

.  I've sourced zephyr-env.sh in zephyr tree.

I'm attaching a snap of terminal for you to have a look, which iterates violation of policy CMP0002 again and again.


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 5:09 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Make sure of 2 things:

 

·         You are using CMake 3.4 or higher (cmake –version to check)

·         You have sourced zephyr-env.sh in the Zephyr tree before building MCUboot

 

Thanks,

 

Carles

 

From: ashish.shukla@... <ashish.shukla@...>
Sent: 06 April 2018 13:36
To: Cufi, Carles <Carles.Cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi Carles,

Thanks a lot for pointing us to such a detailed documentation. However, while following through doc, I ran into an issue.  When I tried to build MCUboot in it's present form, after adding a prj.cnf file, and adding following line at the starting of CMakeLists.txt

include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
project(NONE)

policy CMP0002 of cmake is violated. How can this issue be resolved ?

 


 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

On Fri, Apr 6, 2018 at 2:22 PM, Cufi, Carles <carles.cufi@...> wrote:

Hi Ashish,

 

Here is the published documentation:

 

http://docs.zephyrproject.org/samples/subsys/mgmt/mcumgr/smp_svr/README.html

 

Regards,

 

Carles

 

 

From: zephyr-devel-bounces@lists.zephyrproject.org <zephyr-devel-bounces@lists.zephyrproject.org> On Behalf Of ashish.shukla@...
Sent: 21 March 2018 05:15
To: zephyr-devel@lists.zephyrproject.org; zephyr-users@lists.zephyrproject.org
Subject: [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

 

Hi all,

I've been waiting for FOTA and FCB support in zephyr and now when it is supported, I cannot see any samples available or proper documentation to use these features in my project.

Any help regarding the same would be of great help.

 

--

Warm regards,
Ashish Shukla

Jr. Embedded Engineer

Research & Development

 

Please consider the environment before printing this e-mail or its attachments.

 

Disclaimer: The information contained herein (including any accompanying documents) is confidential and is intended solely for the addressee(s). If you have erroneously received this message, please immediately delete it and notify the sender. Also, if you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message or any accompanying document is strictly prohibited and is unlawful. The organization is not responsible for any damage caused by a virus or alteration of the e-mail by a third party or otherwise. The contents of this message may not necessarily represent the views or policies of Corvi

 

 

 


2021 - 2040 of 2727