Date   

List configuration test

David Brown
 

Sorry for the noise. I'm trying to figure out what happens when a
message is sent to both the Zephyr devel mailing list, and the mcuboot
mailing list.

Thanks,
David


Zephyr list configuration

David Brown
 

I guess I hadn't been paying attention, but it seems at some point,
the zephyr mailing list software has started doing a lot of header
rewriting of the messages. Perhaps some of this has to do with
anti-spam measures.

However, it is now impossible to cross-post messages to the zephyr
list and any other mailing list. Because of the header rewrite (and
how it removes all other recipients from To or CC), it means that the
message thread is essentially forked. There will be one chain of
messages exclusive to the Zephyr list, and another on the other lists.
It also means that if you do "CC" someone, they will get two separate
messages, and have to make sure they reply to the right one (or
construct a correct reply, adding the "CC" recipients back in).

At this point, we've kind of broken much of the functionality that
gives mailing lists an advantage, and should possibly consider moving
our discussions over to a forum (disqus.com being the most popular).
We could also fix our list software so that it is a better citizen.
Right now, it could be described as "selfish", because it will steal
any conversation from any other cross-posted lists.

This has specifically been affecting me, as I do work on projects that
affect more than one project. For example, many posts to the MCUboot
mailing list should also be cross posted to the Zephyr devel list.
Right now, however, these messages get split, and many people only see
parts of the conversation.

Thanks,
David


Re: Some flash drivers don't use DTS write-block-size setting (even though it's set)

David Brown
 

On Fri, Apr 06, 2018 at 04:43:53PM -0700, Michael Scott wrote:

I noticed today that many of the flash drivers don't make use of the DTS
"write-block-size" setting (STM being the exception):
I wouldn't really expect the driver to make use of the
write-block-size. This value isn't exactly a "setting", but is a
description of the constraints of the hardware. It is perfectly
reasonable that this value is also hardcoded into a driver in some
other manner (e.g., k64f writes in blocks on 8 bytes).

The value in the DTS is needed by clients of the device, to know what
their restrictions are. Writing smaller than this value, or not
aligned to this value is undefined (perhaps this needs to be
documented better). Some drivers will do invalid things (such as
writing a whole block), other will try to read/write parts of the
data, which in general is a terrible thing to have in the driver, as
it generally breaks any attempts by the client code to be robust
against power downs. Sometimes the constraint isn't even visible in
the driver, but writing smaller values can result in excessive wear of
the underlying flash.

David


Re: [Zephyr-users] [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-users] [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





Some flash drivers don't use DTS write-block-size setting (even though it's set)

Michael Scott
 

Hello Zephyr-devel list,

I noticed today that many of the flash drivers don't make use of the DTS
"write-block-size" setting (STM being the exception):

$ fgrep -nr "write_block_size" drivers/flash
drivers/flash/flash_handlers.c:32:_SYSCALL_HANDLER1_SIMPLE(flash_get_write_block_size,
K_OBJ_DRIVER_FLASH,
drivers/flash/soc_flash_nrf.c:215:    .write_block_size = 1,
drivers/flash/soc_flash_mcux.c:139:    .write_block_size =
FSL_FEATURE_FLASH_PFLASH_BLOCK_WRITE_UNIT_SIZE,
drivers/flash/flash_sam0.c:369:    .write_block_size = FLASH_PAGE_SIZE,
drivers/flash/flash_stm32.c:228:    .write_block_size =
FLASH_WRITE_BLOCK_SIZE,
drivers/flash/flash_stm32f3x.c:132:    .write_block_size = 2,
drivers/flash/spi_flash_w25qxxdv.c:352:    .write_block_size = 1,
drivers/flash/soc_flash_nios2_qspi.c:435:    .write_block_size =
NIOS2_WRITE_BLOCK_SIZE,
drivers/flash/soc_flash_qmsi.c:261:    .write_block_size = 4,

I know many boards don't have setting in their DTS, but the NXP, nRF and
STM32 and 1 of the Atmel boards have it:

$ fgrep -nr "write-block-size" dts/
dts/bindings/mtd/soc-nv-flash.yaml:29:    write-block-size:
dts/arm/st/stm32f4.dtsi:46:                write-block-size = <1>;
dts/arm/st/stm32l0.dtsi:46:                write-block-size = <4>;
dts/arm/st/stm32f0.dtsi:46:                write-block-size = <2>;
dts/arm/st/stm32l4.dtsi:47:                write-block-size = <8>;
dts/arm/nxp/nxp_kw40z.dtsi:66:                write-block-size = <4>;
dts/arm/nxp/nxp_kw2xd.dtsi:74:                write-block-size = <4>;
dts/arm/nxp/nxp_kl25z.dtsi:38:                write-block-size = <4>;
dts/arm/nxp/nxp_kw41z.dtsi:66:                write-block-size = <4>;
dts/arm/nxp/nxp_k6x.dtsi:82:                write-block-size = <8>;
dts/arm/atmel/samd21.dtsi:41:                write-block-size = <64>;
dts/arm/nordic/nrf52840.dtsi:30:                write-block-size = <4>;
dts/arm/nordic/nrf52832.dtsi:30:                write-block-size = <4>;
dts/arm/nordic/nrf51822.dtsi:30:                write-block-size = <4>;

We have a few areas in the source that use FLASH_WRITE_BLOCK_SIZE (DTS
generated) directly:
(specifically: subsys/dfu/img_util/flash_img.c and
subsys/dfu/boot/mcuboot.c require it to be set):

$ fgrep -nr "FLASH_WRITE_BLOCK_SIZE" .
./drivers/flash/flash_stm32.c:227:#ifdef FLASH_WRITE_BLOCK_SIZE
./drivers/flash/flash_stm32.c:228:    .write_block_size =
FLASH_WRITE_BLOCK_SIZE,
./samples/drivers/flash_shell/src/main.c:239:#if defined
FLASH_WRITE_BLOCK_SIZE
./samples/drivers/flash_shell/src/main.c:240:    printk("%d\n",
FLASH_WRITE_BLOCK_SIZE);
./doc/release-notes-1.11.rst:337:* :github:`5305` - flash: use generated
FLASH_WRITE_BLOCK_SIZE in flash_stm32_api
./subsys/dfu/img_util/flash_img.c:21:BUILD_ASSERT_MSG((CONFIG_IMG_BLOCK_BUF_SIZE
% FLASH_WRITE_BLOCK_SIZE == 0),
./subsys/dfu/img_util/flash_img.c:23:  "FLASH_WRITE_BLOCK_SIZE");
./subsys/dfu/boot/mcuboot.c:70:#define FLASH_MIN_WRITE_SIZE
FLASH_WRITE_BLOCK_SIZE

Worse .. when taking a close look, I see we have 2 *different* settings
for the nRF boards at the moment, since the driver sets a value of 1 and
the DTS all say 4.   Not sure which is correct.

Seems like this could be prone to getting out of sync.

- Mike


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

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-users] [Zephyr-devel] Firmware over the air (FOTA) and FCB support in 1.11.0

Giuliano Franchetto <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-users] [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-users] [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: mimxrt1050_EVK sdram support

Maureen Helm
 

Hi Lukasz,

Yes there is definitely interest in adding support for the SDRAM. I posted a PR yesterday that adds the dts nodes for the external memories, including the SDRAM, but I haven’t yet configured the IVT and DCD. I have some local WIP for the IVT but it doesn’t actually work yet, and I got sidetracked trying to figure out if/how the debugging tools (DAPLink, JLink) were doing it.

 

https://github.com/zephyrproject-rtos/zephyr/pull/6951

 

The PR should help with the scenario we talked about on the NXP community, where you develop/debug with JLink in SRAM, then switch to DAPLink to program the Hyperflash. It’s still not ideal unfortunately. As an alternative, I’m thinking about trying to hook up the LinkServer from MCUXpresso IDE into the Zephyr runner infrastructure.

 

Maureen

 

From: devel@... [mailto:devel@...] On Behalf Of Lukasz Grzymkowski
Sent: Thursday, April 5, 2018 3:45 AM
To: devel@...
Subject: [Zephyr-devel] mimxrt1050_EVK sdram support

 

Hello,

 

I’m working on a project that uses Zephyr on mimxrt1050_evk with GUI on the LCD display. To allocate framebuffers I obviously need more memory than SRAM provides, and so I’ve added support for the external SDRAM.

 

I’m wondering if there is actually any on-going work to add SDRAM support for this board, so I don’t necessarily reinvent the wheel, or if there is actually any interest in adding support for it to Zephyr?

 

Best regards,

Lukasz

 


Re: Firmware over the air (FOTA) and FCB support in 1.11.0

Carles Cufi
 

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

 


QEMU and bridged networking

David Brown
 

When I use qemu with Linux, one of the network configurations I can
use is bridged, which makes the emulated platform appear as its own
device on my network. This allows things such dhcpc to work as it
would on a standalone device on my network.

With Zephyr, since we're doing the networking through a slip interface
over a simulated uart, the automated qemu bridge networking doesn't
work.

Has anyone successfully enabled qemu_x86 with a network configuration
that bridged the device to the hosts network interface.

What I've tried so far is:

- Changed my systemd network configuration to create br0 as a bridge
interface.

- Set my ethernet devices to master to br0

- Run dhcp on br0 instead of the ethernet device (maybe this is an
error).

- After starting up loop-slip-tap.sh, set tap0 to master to br0.

Running the dhcpv4_client app doesn't ever find an address. I can
next try to hard-code an IP address and see if TCP will get through.

Thanks,
David


LLVM Support (Pre 1.12 PR)

jshafer4@...
 

All,

I am interested in analyzing Zephyr symbolically using KLEE, which requires LLVM bitcode.

Prior to the 1.12 PR, is this possible via undocumented support for LLVM/Clang in 1.11 PR, or some development branch?

Thanks.


Re: OpenThread support on Zephyr

Carles Cufi
 

Hi Marcio,

 

I recommend you start by building the echo_client and echo_server projects for the nrf52840_pca10056 board using prj_nrf52840_ot.conf.

That will get you an echo client and server that communicate over Thread.

 

The code for OpenThread will be pulled by CMake when you trigger the build.

 

Regards,

 

Carles

 

From: devel@... <devel@...> On Behalf Of Marcio Montenegro
Sent: 05 April 2018 14:42
To: devel@...
Subject: [Zephyr-devel] OpenThread support on Zephyr

 

Hi all,
Please share technical details about this topic.
Thanks in advance

https://www.zephyrproject.org/zephyr-project-announces-openthread-first-thread-protocol-implementation-integrate-zephyr-rtos/


OpenThread support on Zephyr

Marcio Montenegro
 

Hi all,
Please share technical details about this topic.
Thanks in advance

https://www.zephyrproject.org/zephyr-project-announces-openthread-first-thread-protocol-implementation-integrate-zephyr-rtos/


mimxrt1050_EVK sdram support

Lukasz Grzymkowski
 

Hello,

 

I’m working on a project that uses Zephyr on mimxrt1050_evk with GUI on the LCD display. To allocate framebuffers I obviously need more memory than SRAM provides, and so I’ve added support for the external SDRAM.

 

I’m wondering if there is actually any on-going work to add SDRAM support for this board, so I don’t necessarily reinvent the wheel, or if there is actually any interest in adding support for it to Zephyr?

 

Best regards,

Lukasz

 


Re: Implement SPI on a STM32f7

Tomasz Bursztyka
 

Hi Clemence,

SPI is supported on stm32f4 SoCs, the doc is probably not up to date.

Maybe it's just not enabled on the board's dts file.
But on SoC level it is, see dts/arm/st/stm32f407.dtsi which includes
dts/arm/st/stm32f405.dtsi including itself: dts/arm/st/stm32f401.dtsi

Tomasz

Hello,

I am trying to implement SPI on the STM32f4 discovery (STM32f407).

On the doc of Zephyr, it is written the list of the hardware
features
supported by the board STM32f4 discovery (NVIC, UART, PINMUX, GPIO
aand
PWM) and SPI is not in this list.

I have already changed some files to add the SPI:

- $ENV{ZEPHYR_BASE}/boards/arm/pinmux.c

- $ENV{ZEPHYR_BASE}/boards/arm/stm32f4_disco.dts

- $ENV{ZEPHYR_BASE}/boards/arm/stm32f4_disco.yaml

- $ENV{ZEPHYR_BASE}/boards/arm/Kconfig.defconfig

- $ENV{ZEPHYR_BASE}/dts/arm/st/stm32f4-pinctrl.dtsi

- $ENV{ZEPHYR_BASE}/arch/arm/soc/st_stm32/stm32f4/soc.h

- prj.conf


I would like to know what I need to modify or add to implement SPI
for
the STM32f4 discovery please ?


Thanks,

Clemence


_______________________________________________
Zephyr-devel mailing list
Zephyr-devel@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-devel


Re: NRF54280 coded phy

Carles Cufi
 

Hi there,

 

You can use coded phy today in connections, but not really during advertising and scanning because that requires Advertising Extensions to be implemented.

We are currently making architectural changes to the BLE Controller to, among other things, pave the way for Advertising Extensions. Those changes should come very soon to master, and later on we will consider implementing AE, but we can’t give you a fixed timeline for that. Once the architectural changes are merged you are more than welcome to contribute AE features.

 

Regards,

 

Carles

 

From: zephyr-devel-bounces@... <zephyr-devel-bounces@...> On Behalf Of deadpool code
Sent: 04 April 2018 05:20
To: zephyr-devel@...
Subject: [Zephyr-devel] NRF54280 coded phy

 

Hello

 

I would like to use coded phy both in sending the data and in broadcasting 

 

when is it expected to be supported?

 

thank you 


Implement SPI on a STM32f7

clemence
 

Hello,

I am trying to implement SPI on the STM32f4 discovery (STM32f407).

On the doc of Zephyr, it is written the list of the hardware features supported by the board STM32f4 discovery (NVIC, UART, PINMUX, GPIO aand PWM) and SPI is not in this list.

I have already changed some files to add the SPI:

- $ENV{ZEPHYR_BASE}/boards/arm/pinmux.c

- $ENV{ZEPHYR_BASE}/boards/arm/stm32f4_disco.dts

- $ENV{ZEPHYR_BASE}/boards/arm/stm32f4_disco.yaml

- $ENV{ZEPHYR_BASE}/boards/arm/Kconfig.defconfig

- $ENV{ZEPHYR_BASE}/dts/arm/st/stm32f4-pinctrl.dtsi

- $ENV{ZEPHYR_BASE}/arch/arm/soc/st_stm32/stm32f4/soc.h

- prj.conf


I would like to know what I need to modify or add to implement SPI for the STM32f4 discovery please ?


Thanks,

Clemence

3641 - 3660 of 8033