Date   

Store DTLS credentials independent to the binary #networking #flash #dtls #nrf52480

Nikos Karamolegkos
 

Hello everybody, I would like to ask you if it is safe to use these functions in order to store and get DTLS credentials on the device? I would like to make over the air update so I would like the transmitted binary to be independent of the DTLS credentials. An other idea may be to create a different partition for the credentials. What are your thoughts?

Thank you


Nordic 52840 as client Exchange MTU Request Not Supported

Eric Cooper <ericcooper2005@...>
 

Hi Zephyr Team, I am relative newby to BLE and Zephyr so forgive me if I am missing something obvious.

I have a 52840 with the Zephyr firmware acting a client communicating with a Nordic device.

If the device sends an Exchange MTU (for 247) a btmon trace shows a response of Request Not Supported (and could this be a bluez issue?). In the same setup if the client then sends an Exchange MTU Request it appears to be successfully acknowledged but going forward the data is sent from the device in 23 byte MTUs as opposed to the preferred 247.

If the device does not send an Exchange MTU request and the client side sends the Exchange MTU request the device does properly use the larger MTU.

So two issues:
. the client does not support Exchange MTU request (Zephyr or bluez issue?)
. given a rejected Exchange MTU request from the device (server) and an accepted MTU from the client to the device the full MTU size is not utilized. And as I think about it this could be an issue on the device.

A trace is at the end of this email.

Thanks in advance and please let know if there is more information I can provide.

Eric


@ RAW Open: gatttool version 2.22                                                                                                                                        {0x0003} 506.381902
@ RAW Close: gatttool                                                                                                                                                    {0x0003} 506.381912
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7                                                                                                             #19 [hci0] 506.381948
        Type: Passive (0x00)
        Interval: 60.000 msec (0x0060)
        Window: 30.000 msec (0x0030)
        Own address type: Random (0x01)
        Filter policy: Ignore not in white list (0x01)
> HCI Event: Command Complete (0x0e) plen 4                                                                                                                            #20 [hci0] 506.382783
      LE Set Scan Parameters (0x08|0x000b) ncmd 1
        Status: Success (0x00)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2                                                                                                                 #21 [hci0] 506.382794
        Scanning: Enabled (0x01)
        Filter duplicates: Enabled (0x01)
> HCI Event: Command Complete (0x0e) plen 4                                                                                                                            #22 [hci0] 506.383779
      LE Set Scan Enable (0x08|0x000c) ncmd 1
        Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 42                                                                                                                              #23 [hci0] 506.808920
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Connectable undirected - ADV_IND (0x00)
        Address type: Random (0x01)
        Address: E0:8E:4B:E4:9D:3E (Static)
        Data length: 30
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        128-bit Service UUIDs (complete): 1 entry
          Vendor specific (00001523-1212-efde-1523-785feabcd123)
        Name (complete): B8_1777
        RSSI: -41 dBm (0xd7)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2                                                                                                                 #24 [hci0] 506.808935
        Scanning: Disabled (0x00)
        Filter duplicates: Disabled (0x00)
> HCI Event: Command Complete (0x0e) plen 4                                                                                                                            #25 [hci0] 506.809779
      LE Set Scan Enable (0x08|0x000c) ncmd 1
        Status: Success (0x00)
< HCI Command: LE Create Connection (0x08|0x000d) plen 25                                                                                                              #26 [hci0] 506.809785
        Scan interval: 60.000 msec (0x0060)
        Scan window: 60.000 msec (0x0060)
        Filter policy: White list is not used (0x00)
        Peer address type: Random (0x01)
        Peer address: E0:8E:4B:E4:9D:3E (Static)
        Own address type: Random (0x01)
        Min connection interval: 30.00 msec (0x0018)
        Max connection interval: 50.00 msec (0x0028)
        Connection latency: 0 (0x0000)
        Supervision timeout: 420 msec (0x002a)
        Min connection length: 0.000 msec (0x0000)
        Max connection length: 0.000 msec (0x0000)
> HCI Event: Command Status (0x0f) plen 4                                                                                                                              #27 [hci0] 506.811778
      LE Create Connection (0x08|0x000d) ncmd 1
        Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 19                                                                                                                              #28 [hci0] 506.997999
      LE Connection Complete (0x01)
        Status: Success (0x00)
        Handle: 0
        Role: Master (0x00)
        Peer address type: Random (0x01)
        Peer address: E0:8E:4B:E4:9D:3E (Static)
        Connection interval: 50.00 msec (0x0028)
        Connection latency: 0 (0x0000)
        Supervision timeout: 420 msec (0x002a)
        Master clock accuracy: 0x07
@ MGMT Event: Device Connected (0x000b) plen 43                                                                                                                   {0x0002} [hci0] 506.998012
        LE Address: E0:8E:4B:E4:9D:3E (Static)
        Flags: 0x00000000
        Data length: 30
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        128-bit Service UUIDs (complete): 1 entry
          Vendor specific (00001523-1212-efde-1523-785feabcd123)
        Name (complete): B8_1777
@ MGMT Event: Device Connected (0x000b) plen 43                                                                                                                   {0x0001} [hci0] 506.998012
        LE Address: E0:8E:4B:E4:9D:3E (Static)
        Flags: 0x00000000
        Data length: 30
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        128-bit Service UUIDs (complete): 1 entry
          Vendor specific (00001523-1212-efde-1523-785feabcd123)
        Name (complete): B8_1777
< HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2                                                                                                       #29 [hci0] 506.998070
        Handle: 0
> HCI Event: LE Meta Event (0x3e) plen 4                                                                                                                               #30 [hci0] 506.998125
      LE Channel Selection Algorithm (0x14)
        Handle: 0
        Algorithm: #2 (0x01)
> HCI Event: Command Status (0x0f) plen 4                                                                                                                              #31 [hci0] 506.998800
      LE Read Remote Used Features (0x08|0x0016) ncmd 1
        Status: Success (0x00)



> ACL Data RX: Handle 0 flags 0x02 dlen 7                                                                                                                              #32 [hci0] 506.999954
      ATT: Exchange MTU Request (0x02) len 2
        Client RX MTU: 247
> HCI Event: LE Meta Event (0x3e) plen 11                                                                                                                              #33 [hci0] 507.098804
      LE Data Length Change (0x07)
        Handle: 0
        Max TX octets: 251
        Max TX time: 2120
        Max RX octets: 251
        Max RX time: 2120
> HCI Event: LE Meta Event (0x3e) plen 12                                                                                                                              #34 [hci0] 507.150804
      LE Read Remote Used Features (0x04)
        Status: Success (0x00)
        Handle: 0
        Features: 0x25 0x41 0x00 0x00 0x00 0x00 0x00 0x00
          LE Encryption
          Extended Reject Indication
          LE Data Packet Length Extension
          LE 2M PHY
          Channel Selection Algorithm #2
< ACL Data TX: Handle 0 flags 0x00 dlen 9                                                                                                                              #35 [hci0] 507.150967
      ATT: Error Response (0x01) len 4
        Exchange MTU Request (0x02)
        Handle: 0x0000
        Error: Request Not Supported (0x06)
> HCI Event: Number of Completed Packets (0x13) plen 5                                                                                                                 #36 [hci0] 507.199876
        Num handles: 1
        Handle: 0
        Count: 1



< ACL Data TX: Handle 0 flags 0x00 dlen 7                                                                                                                              #37 [hci0] 507.202314
      ATT: Exchange MTU Request (0x02) len 2
        Client RX MTU: 512
> HCI Event: Number of Completed Packets (0x13) plen 5                                                                                                                 #38 [hci0] 507.249913
        Num handles: 1
        Handle: 0
        Count: 1
> ACL Data RX: Handle 0 flags 0x02 dlen 7                                                                                                                              #39 [hci0] 507.300798
      ATT: Exchange MTU Response (0x03) len 2
        Server RX MTU: 247
< ACL Data TX: Handle 0 flags 0x00 dlen 11                                                                                                                             



#40 [hci0] 507.351938
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x0001-0xffff
        Attribute type: Characteristic (0x2803)
> HCI Event: Number of Completed Packets (0x13) plen 5                                                                                                                 #41 [hci0] 507.399916
        Num handles: 1
        Handle: 0
        Count: 1
> ACL Data RX: Handle 0 flags 0x02 dlen 27                                                                                                                             #42 [hci0] 507.450802
      ATT: Read By Type Response (0x09) len 22
        Attribute data length: 7
        Attribute data list: 3 entries
        Handle: 0x0002
        Value: 0a0300002a
        Handle: 0x0004
        Value: 020500012a
        Handle: 0x0006
        Value: 020700042a
< ACL Data TX: Handle 0 flags 0x00 dlen 11                                                                                                                             #43 [hci0] 507.450883
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x0007-0xffff
        Attribute type: Characteristic (0x2803)
> HCI Event: Number of Completed Packets (0x13) plen 5                                                                                                                 #44 [hci0] 507.499912
        Num handles: 1
        Handle: 0
        Count: 1
> ACL Data RX: Handle 0 flags 0x02 dlen 13                                                                                                                             #45 [hci0] 507.550832
      ATT: Read By Type Response (0x09) len 8
        Attribute data length: 7
        Attribute data list: 1 entry
        Handle: 0x0008
        Value: 020900a62a
< ACL Data TX: Handle 0 flags 0x00 dlen 11                                                                                                                             #46 [hci0] 507.550914
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x0009-0xffff
        Attribute type: Characteristic (0x2803)
> HCI Event: Number of Completed Packets (0x13) plen 5                                                                                                                 #47 [hci0] 507.599915
        Num handles: 1
        Handle: 0
        Count: 1
> ACL Data RX: Handle 0 flags 0x02 dlen 27                                                                                                                             #48 [hci0] 507.650831
      ATT: Read By Type Response (0x09) len 22
        Attribute data length: 21
        Attribute data list: 1 entry
        Handle: 0x000c
        Value: 180d0023d1bcea5f782315deef121224150000
< ACL Data TX: Handle 0 flags 0x00 dlen 11                                                                                                                             #49 [hci0] 507.650913
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x000d-0xffff
        Attribute type: Characteristic (0x2803)
> HCI Event: Number of Completed Packets (0x13) plen 5                                                                                                                 #50 [hci0] 507.749874
        Num handles: 1
        Handle: 0
        Count: 1
> ACL Data RX: Handle 0 flags 0x02 dlen 27                                                                                                                             #51 [hci0] 507.750989
      ATT: Read By Type Response (0x09) len 22
        Attribute data length: 21
        Attribute data list: 1 entry
        Handle: 0x000f
        Value: 38100023d1bcea5f782315deef121225150000
< ACL Data TX: Handle 0 flags 0x00 dlen 11                                                                                                                             #52 [hci0] 507.751051
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x0010-0xffff
        Attribute type: Characteristic (0x2803)
> HCI Event: Number of Completed Packets (0x13) plen 5                                                                                                                 #53 [hci0] 507.799910
        Num handles: 1
        Handle: 0
        Count: 1
> ACL Data RX: Handle 0 flags 0x02 dlen 27      


ESP32 Dual core - getting started

Lawrence King
 

Dear All:

 

I have started a new project based on ESP32.

 

To start I wrote boards files for the ESP32-CAM board  and defined a single LED as a peripheral. I was able to compile the blinky sample, flash it to the board and have it start up at board power on. Great!  I should mention that the ESP32-CAM board is a single core ESP32, and download is over the serial UART.

 

Now moving on to bigger and better things, I received a ESP32-WROVER-KIT board. This board has UART and JTAG debug on board and a dual-core CPU. I created a boards file(s) for this board (similar to the ESP32-CAM dts). I managed to get the esp variant of openOCD setup, it seems to download code to the board over JTAG correctly. Unfortunately when I reset the board it doesn’t run my Blinky code, it runs whatever was programmed in the board when I got it.

 

I think I have two issues, 1) which core is zephyr supposed to run on (cpu0 or cpu1), and 2) what address should the code be loaded to so that it will start at boot time?.

 

Here is the output of “west -v flash”:

 

-- west flash: using runner openocd

runners.openocd: /usr/local/bin/openocd -f board/esp32-wrover-kit-3.3v.cfg -c init -c targets -c 'reset halt' -c 'load_image /home/lawrence/workspace/cradle/build/zephyr/zephyr.elf' -c 'resume 0x00000000400807b4' -c shutdown

Open On-Chip Debugger  v0.10.0-esp32-20200526-33-gadc5c3ff-dirty (2020-10-09-17:36)

Licensed under GNU GPL v2

For bug reports, read

      http://openocd.org/doc/doxygen/bugs.html

Info : FreeRTOS creation

Info : FreeRTOS creation

Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi_tdo_sample_edge falling"

Info : clock speed 20000 kHz

Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)

Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)

Info : esp32.cpu0: Debug controller was reset.

Info : esp32.cpu0: Core was reset.

Info : esp32.cpu1: Debug controller was reset.

Info : esp32.cpu1: Core was reset.

Info : Listening on port 3333 for gdb connections

    TargetName         Type       Endian TapName            State      

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

0  esp32.cpu0         esp32      little esp32.cpu0         running

1* esp32.cpu1         esp32      little esp32.cpu1         running

 

Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)

Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)

Info : esp32.cpu0: Target halted, PC=0x400D5614, debug_reason=00000000

Info : Set GDB target to 'esp32.cpu0'

Info : esp32.cpu1: Target halted, PC=0x400D1AA6, debug_reason=00000000

Info : esp32.cpu0: Debug controller was reset.

Info : esp32.cpu0: Core was reset.

Info : esp32.cpu0: Target halted, PC=0x500000CF, debug_reason=00000000

Info : esp32.cpu0: Core was reset.

Info : esp32.cpu0: Target halted, PC=0x40000400, debug_reason=00000000

Info : esp32.cpu1: Debug controller was reset.

Info : esp32.cpu1: Core was reset.

Info : esp32.cpu1: Target halted, PC=0x40000400, debug_reason=00000000

14854 bytes written at address 0x40080000

920 bytes written at address 0x3ffb0000

downloaded 15774 bytes in 0.096819s (159.104 KiB/s)

 

shutdown command invoked

 

It looks like it wrote Zephyr to the chip (at address 0x40080000), and scribbled something at 0x3ffb0000. But when I restart the board the blinky code doesn’t run.

 

The serial terminal output shows it startes something else:

 

rst:0x1 (POWERON_RESET),boot:0x1e (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0xee

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00

mode:DIO, clock div:2

load:0x3fff0018,len:4

load:0x3fff001c,len:5984

ho 0 tail 12 room 4

load:0x40078000,len:0

load:0x40078000,len:15720

entry 0x4007901c

I (30) boot: ESP-IDF v3.1-dev-789-g0c58f11 2nd stage bootloader

I (30) boot: compile time 20:13:08

I (31) boot: Enabling RNG early entropy source...

I (36) qio_mode: Enabling default flash chip QIO

I (41) boot: SPI Speed      : 40MHz

I (45) boot: SPI Mode       : QIO

I (49) boot: SPI Flash Size : 2MB

I (54) boot: Partition Table:

I (57) boot: ## Label            Usage          Type ST Offset   Length

I (64) boot:  0 nvs              WiFi data        01 02 00009000 00006000

I (72) boot:  1 phy_init         RF data          01 01 0000f000 00001000

I (79) boot:  2 factory          factory app      00 00 00010000 00100000

I (87) boot: End of partition table

I (91) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x1d36c (119660) map

I (135) esp_image: segment 1: paddr=0x0002d394 vaddr=0x3ffb0000 size=0x025c0 (  9664) load

I (139) esp_image: segment 2: paddr=0x0002f95c vaddr=0x40080000 size=0x00400 (  1024) load

I (143) esp_image: segment 3: paddr=0x0002fd64 vaddr=0x40080400 size=0x002ac (   684) load

I (151) esp_image: segment 4: paddr=0x00030018 vaddr=0x400d0018 size=0x1a354 (107348) map

I (192) esp_image: segment 5: paddr=0x0004a374 vaddr=0x400806ac size=0x0d73c ( 55100) load

I (212) esp_image: segment 6: paddr=0x00057ab8 vaddr=0x400c0000 size=0x00000 (     0) load

I (221) boot: Loaded app from partition at offset 0x10000

I (221) boot: Disabling RNG early entropy source...

I (223) spiram: SPI RAM mode: flash 40m sram 40m

I (227) spiram: PSRAM initialized, cache is in low/high (2-core) mode.

I (234) cpu_start: Pro cpu up.

I (238) cpu_start: Starting app cpu, entry point is 0x4008111c

I (0) cpu_start: App cpu up.

I (1136) spiram: SPI SRAM memory test OK

I (1136) heap_init: Initializing. RAM available for dynamic allocation:

I (1137) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM

I (1143) heap_init: At 3FFB3368 len 0002CC98 (179 KiB): DRAM

I (1149) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM

I (1156) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM

I (1162) heap_init: At 4008DDE8 len 00012218 (72 KiB): IRAM

I (1168) cpu_start: Pro cpu start user code

I (1173) spiram: Adding pool of 4096K of external SPI memory to heap allocator

I (1181) spiram: Reserving pool of 32K of internal memory for DMA/internal allocations

I (196) cpu_start: Starting scheduler on PRO CPU.

I (0) cpu_start: Starting scheduler on APP CPU.

I (0) gpio: GPIO[0]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0

I (0) gpio: GPIO[2]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0

I (10) gpio: GPIO[4]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0

light init

LCD ID: 00000000

ILI9341 detected.

LCD ILI9341 initialization.

 

I suspect I set something up incorrectly, but what?

 

Lawrence King

Principal Developer

Connected Transport Market Unit

https://www.Irdeto.com

+1(416)627-7302

 

1  2 - linkedin  3 - instagram  4 - youtube  6 - facebook  7

            

CONFIDENTIAL: This e-mail and any attachments are confidential and intended solely for the use of the individual(s) to whom it is addressed. It can contain proprietary confidential information and be subject to legal privilege and/or subject to a non-disclosure Agreement. Unauthorized use, disclosure or copying is strictly prohibited. If you are not the/an addressee and are in possession of this e-mail, please delete the message and notify us immediately. Please consider the environment before printing this e-mail. Thank you.

 

 

 


API meeting: agenda

Carles Cufi
 


How do I get the radio frequency in ble sample #ble

mfinmuch@...
 

I'm trying the sample of bluetooth 
I use central and peripheral(use gatt) code load in two boards
I want to Implement frequency hopping to send the data
but I don't know how to start 
 what api should I call , so that I can know the frequency channel which is using and change the frequency channel  ?
I also found " bt_le_set_chan_map " can set the channel map ,but how to use this api?

thanks,
Poyi


windows-curses 2.2.0a1: call for testing and maintainers

Bolivar, Marti
 

Hi,

I've uploaded a 2.2.0a1 release of the windows-curses package to PyPI.

This is a dependency on Windows for the 'menuconfig' build system
target. (POSIX platforms have curses and thus 'menuconfig' support
without this package.)

Python versions 3.6 through 3.9 are supported. Previous windows-curses
releases only supported up to 3.8, since 3.9 was just released.

Call for testing
================

Please test by installing like this (again, Windows only):

pip3 install windows-curses==2.2.0a1

Then running 'west build -t menuconfig' on your favorite Zephyr
application and configuring away.

Please report any issues that don't also reproduce on windows-curses
version 2.1.0.

I've given this some basic testing on all the supported Python versions
listed above (both 32- and 64-bit versions), but I don't use Windows
every day and I may have missed something.

Call for maintainers
====================

After we conclude the 2.2.0 windows-curses release, the package will
become unmaintained.

In practice, this means that 'menuconfig' will be unavailable on Windows
starting with Python 3.10, which is expected to come out in late 2021.

After this time, only the 'guiconfig' target will be officially
supported by upstream Zephyr for viewing and editing application Kconfig
trees on Windows. (Don't worry: the 'menuconfig' target will continue to
be available on POSIX operating systems.)

If you would like to take over maintainership of this package, please
let the Zephyr TSC know:

https://github.com/zephyrproject-rtos/windows-curses

Thanks!
Martí


IPSP with global IPv6 addresses #coap #ipsp #nrf52480

Stefan Hristozov
 

Hi,

I have a set up consing of an nrf52840, a Raspberry pi and a Linux workstation,
which communicate over IPSP following the IPSP sample.
The nrf52840 is a UDP/CoAP client, the Raspberry pi is a border router and the workstation is a UDP/CoAP server. The Raspberry pi and the Linunx workstation are both in my LAN, see the diagram below showing the set up with all IPv6 addresses.

            BLE                                                            
nrf5x --------------------  RPI Border router      ---------- ISP router --------- Linux WS
2001:db8::1     (bt0)2001:db8::2 (eth0)2001:db9::1                           2001:db9::2


This works all fine. Now I want to replace the Linux workstation with a remote Linux server. The Linux server has a global IPv6 address. I can ping this address and send UDP packets to it form the Raspberry. However, the UDP packets which the nrf52840 send does not arrive at it. I can see with tcpdump that the packets are sent out from the Raspberry but I think my ISP router does not forward them on the internet. My ISP router has IPv6 support.

I think the  nrf52840 needs also a global IPv6 address. How to create/get a global IPv6 address for the nrf52840?


Re: run-time non-volatile overwrite

Bolivar, Marti
 

Hi,

It's not clear what you are asking. By 'Zephyr requires the ability',
what part of Zephyr do you mean?

Some optional Zephyr subsystems (like DFU or file systems) require
rewriting nonvolatile storage to work properly, of course. But these
have to be enabled. The 'hello_world' sample doesn't write any flash
when it runs. So the answer you are looking for really depends on your
use case.

Martí

"abraddy via lists.zephyrproject.org"
<abraddy=slb.com@lists.zephyrproject.org> writes:

I'm currently considering Zephyr for some of our future projects, but have a  (hopefully) quick question. We have a requirement that FLASH memory is not erased (including bit-setting on overwrites) and was wondering if anyone can tell me off-the-cuff whether Zephyr requires the ability to re-write non-volatile memory at run-time.
Thanks in advance, Alan.



run-time non-volatile overwrite

abraddy@...
 

I'm currently considering Zephyr for some of our future projects, but have a  (hopefully) quick question. We have a requirement that FLASH memory is not erased (including bit-setting on overwrites) and was wondering if anyone can tell me off-the-cuff whether Zephyr requires the ability to re-write non-volatile memory at run-time.
Thanks in advance, Alan. 


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Marco Cavallini
 

On 07/10/20 08:52, Marco Cavallini wrote:
On 07/10/20 03:08, Boie, Andrew P wrote:

What CPU is on your Reel Board?
I had an issue with this, someone gave me a Reel Board at a LF event in Lyon, but when I tried to flash it, turned out to have a different SoC not supported by Zephyr.

Andrew
Hi Andrew,
You are right!
My board doesn't have mounted the Nordic nRF52840.
Let me request a response from the manufacturer.
Thank you
--
Marco

Hello,
I have the reel_board_v3 that has a separate CPU module.
Phytec forgot to ship it, so there is a part missing within the reelboard package - NOTM.2 Adapter for nRF52840.
It is on the way ;-)

Thank you Andrew for pointing it out.

--
Marco


West v0.8.0 released

Bolivar, Marti
 

Hello,

I'm announcing the release of west v0.8.0.

https://pypi.org/project/west/0.8.0/
https://github.com/zephyrproject-rtos/west/tree/v0.8.0

Release notes:

https://docs.zephyrproject.org/latest/guides/west/release-notes.html#v0-8-0

To upgrade:

Ubuntu: pip3 install --user west==0.8.0
Windows/macoS: pip3 install west==0.8.0

Thanks to everyone who contributed to this release!

Martí

---

Gerard Marull-Paretas (1):
west: initial support for type hints

Martí Bolívar (76):
Add MAINTAINERS.rst
project.py: delete dead code
update: make output more helpful
commands: add WestCommandSpec __repr__
manifest: filter duplicates when merging west-commands
MAINTAINERS.rst: some changes from going through this once
MAINTAINERS.rst: make copy pasting commands easier
version: 0.7.99
init: fix error message when init directory already exists
MAINTAINERS.rst: add note for starting next version
log: add use_color() API function
west diff: only print output for projects with nonempty diffs
west manifest: add --path action
lint: flake8 fixes
Revert "app: make main() in west.app.main module public API"
manifest: refactor the file
manifest: fix abstraction violation
manifest: make _flags_ok() always return bool
manifest: make Project.west_commands a list always
manifest: validate: fix error handling
manifest: re-work ManifestProject's fake attributes
manifest: fix Project.is_cloned() if abspath is None
manifest: remove some ManifestProject properties
manifest: clean up Project.posixpath logic
manifest: fix _ManifestImportDepth() call
manifest: type check 'import-context' kwarg
manifest: type annotate internal functions
manifest: type annotate public functions
manifest: type annotate exception types
manifest: type annotate Project and ManifestProject
manifest: type annotate Manifest
manifest: clarify validate() docstring
.gitignore: add htmlcov/
manifest: fix Project.git() cwd on windows / 3.6.0
manifest: use a crystal ball to aid the next commit
util: accept PathLike where relevant
test_config: don't use obsolete kwarg
configuration: remove deprecated read_config kwarg
configuration: don't use canon_path()
configuration: add type annotations
manifest: accept os.PathLike, produce str
app/project: add missing f for f-string
project.py: stop using canon_path()
commands: accept PathLike topdir
manifest: replace a realpath with an abspath in ManifestProject
commands: modify extension command internals
util: remove canon_path()
remove .shippable.yml
conftest: make it more os.PathLike friendly
app: fix import error followed by update
MAINTAINERS.rst: updates following 0.7.3
west list: fix manifest path
tests: add regression tests for 'west list manifest'
.gitignore: add .dir-locals.el
tests: minor cleanups
manifest: add missing return type
manifest: clean up some zephyr pylintrc complaints
manifest: debug log project paths
ManifestCommand: tweak manifest import error printline
manifest: adjust some implementation details
manifest: add 'path-prefix' key to import: map
tests: add test cases for import: path-prefix
manifest: update ImportFlag docstring
tests: clean up dependency handling
manifest: use typing.NamedTuple
add __main__.py
tox.ini: remove useless cruft
MAINTAINERS.rst: cleanups, clarifications
manifest: fix ImportFlag docstring for sphinx
manifest: bump schema version
West v0.8.0a1
init: fix 'west init -l .'
Improve west init -l docs
manifest: rework workspace escape checks
West v0.8.0a2
West v0.8.0

Michael Zimmermann (1):
add support for manifest filenames other than west.yml

Torsten Rasmussen (4):
zephyr base: Fixes issue with failing to discover Zephyr base
app: make main() in west.app.main module public API
manifest: adding manifest_path to kwargs when calling Manifest.__init__
tests: extended test case for Manifest.from_file()


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Andrei
 

Hi,

On Wed, Oct 07, 2020 at 08:52:00AM +0200, Marco Cavallini wrote:
On 07/10/20 03:08, Boie, Andrew P wrote:

What CPU is on your Reel Board?
I had an issue with this, someone gave me a Reel Board at a LF event in Lyon, but when I tried to flash it, turned out to have a different SoC not supported by Zephyr.

Andrew
Hi Andrew,
You are right!
My board doesn't have mounted the Nordic nRF52840.
Let me request a response from the manufacturer.
There is also reel_board_v2, have you tried it?

Best regards
Andrei Emeltchenko


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Marco Cavallini
 

On 07/10/20 03:08, Boie, Andrew P wrote:
What CPU is on your Reel Board?
I had an issue with this, someone gave me a Reel Board at a LF event in Lyon, but when I tried to flash it, turned out to have a different SoC not supported by Zephyr.
Andrew
Hi Andrew,
You are right!
My board doesn't have mounted the Nordic nRF52840.
Let me request a response from the manufacturer.

Thank you
--
Marco


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Boie, Andrew P
 

On 05/10/20 20:15, Henrik Brix Andersen wrote:
Hi,

On 4 Oct 2020, at 18.44, Marco Cavallini [KOAN]
<m.cavallini@koansoftware.com> wrote:

I have already done the udev settings and the board is not detected
when I plug the reel board “Debug USB” connector to my PC I fear my
board is defective.
I wonder what happens when a Reel board is plugged in.
Did you remember to turn the board on using the power switch? Are any of
the LEDs on the board lit?

Does anybody have one ?
Yes. I have a couple of those boards. I have no issue with flashing them.

Regards,
Brix
--
Henrik Brix Andersen
What CPU is on your Reel Board?
I had an issue with this, someone gave me a Reel Board at a LF event in Lyon, but when I tried to flash it, turned out to have a different SoC not supported by Zephyr.

Andrew


Re: API meeting: agenda

Carles Cufi
 

Hi all,

An additional item for today:

- Cleanup of work queue API doc
- PR: https://github.com/zephyrproject-rtos/zephyr/pull/28824

-----Original Message-----
From: Cufi, Carles
Sent: 06 October 2020 15:39
To: devel@lists.zephyrproject.org; users@lists.zephyrproject.org
Subject: API meeting: agenda

Hi all,

Agenda for today, sorry for the short notice.

- Pinmux and pinctrl API: Decide what the priorities for this are, and how
to get to LTS with it
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/22748

Since there are no other new items in the Triage column, I would propose
we go through the To Do and In Progress items and make sure they are still
applicable and they have a person assigned who is actively working on
them.

Teams link: https://teams.microsoft.com/l/meetup-
join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40threa
d.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-
b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-
5e334e88f6d8%22%7d

https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-
Working-Group-Meetings#zephyr-api-discussion
https://github.com/zephyrproject-rtos/zephyr/projects/18
https://docs.google.com/document/d/1lv-
8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles


API meeting: agenda

Carles Cufi
 

Hi all,

Agenda for today, sorry for the short notice.

- Pinmux and pinctrl API: Decide what the priorities for this are, and how to get to LTS with it
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/22748

Since there are no other new items in the Triage column, I would propose we go through the To Do and In Progress items and make sure they are still applicable and they have a person assigned who is actively working on them.

Teams link: https://teams.microsoft.com/l/meetup-join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40thread.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-5e334e88f6d8%22%7d

https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#zephyr-api-discussion
https://github.com/zephyrproject-rtos/zephyr/projects/18
https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Marco Cavallini
 

On 05/10/20 20:15, Henrik Brix Andersen wrote:
Hi,

On 4 Oct 2020, at 18.44, Marco Cavallini [KOAN] <m.cavallini@koansoftware.com> wrote:

I have already done the udev settings and the board is not detected when I plug the reel board “Debug USB” connector to my PC
I fear my board is defective.
I wonder what happens when a Reel board is plugged in.
Did you remember to turn the board on using the power switch? Are any of the LEDs on the board lit?

Does anybody have one ?
Yes. I have a couple of those boards. I have no issue with flashing them.
Regards,
Brix
--
Henrik Brix Andersen


Hi Brix,
yes of course.
I tried connecting to my PC the Reel Board on Debug-USB port (and then to nRF-USB port).

I see the red LED close to U13 and green LED close to Q3

--
Marco


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Marco Cavallini
 

On 05/10/20 20:44, Bolivar, Marti wrote:
"Henrik Brix Andersen via lists.zephyrproject.org"
<henrik=brixandersen.dk@lists.zephyrproject.org> writes:

Hi,

On 4 Oct 2020, at 18.44, Marco Cavallini [KOAN] <m.cavallini@koansoftware.com> wrote:

I have already done the udev settings and the board is not detected when I plug the reel board “Debug USB” connector to my PC
I fear my board is defective.
I wonder what happens when a Reel board is plugged in.
Did you remember to turn the board on using the power switch? Are any of the LEDs on the board lit?

Does anybody have one ?
Yes. I have a couple of those boards. I have no issue with flashing
them.
I have one and it's working for me also. Try plugging it in while
'udevadm monitor' is running. You should see a bunch of lines related to
device creation.
Martí

Hi Marti,
in fact I tested that as well.

I am running an Ubuntu 18.04 O.S.
I tried connecting to my PC the Reel Board on Debug-USB port and then to nRF-USB port. Both are no working. Which one is expected to be used?


I added the udev rule (it's also explained here [1])

$ cat /etc/udev/rules.d/90-daplink.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="0d28", ATTRS{idProduct}=="0204", MODE="664", GROUP="plugdev"

$ sudo udevadm control --reload-rules


Unfortunately 'lsusb' and 'dmesg' don't show any activity.
I tried also the udevadm monitor command, no events are detected.

$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
...nothing here...


Could you please send me the output on your side?
Perhaps my board is defective?


[1] https://docs.zephyrproject.org/latest/boards/arm/reel_board/doc/index.html#programming-and-debugging


Thanks
--
Marco


Re: STM32: Ethernet Driver not working on F7 and H7 with 2.4.0 #networking #driver #ethernet #stm32

David Leach
 

Andreas,

 

Can you bisect this to narrow down where things stopped working for you?

 

David

 

From: users@... <users@...> On Behalf Of andreas.eberhart via lists.zephyrproject.org
Sent: Friday, October 2, 2020 2:12 AM
To: users@...
Subject: [Zephyr-users] STM32: Ethernet Driver not working on F7 and H7 with 2.4.0 #driver #ethernet #stm32 #networking

 

Dear all,

We try to run the net/sockets/packet sample on both, the Nucleo F746ZG and the H747I Discovery Board an run into the following issue with version 2.4.0 (works fine with 2.3.0 on F7):

*** Booting Zephyr OS build zephyr-v2.4.0-41-gcc0244bdd7d6  ***

[00:00:03.736,000] <inf> net_pkt_sock_sample: Packet socket sample is running

[00:00:03.736,000] <inf> net_pkt_sock_sample: Waiting for packets ...

[00:00:03.737,000] <dbg> net_pkt_sock_sample.send_packet_socket: Sent 100 bytes

[00:00:03.737,000] <wrn> net_if: iface 0x20010b04 is down

[00:00:04.001,000] <err> eth_stm32_hal: Failed to enqueue frame into RX queue: -62

[00:00:04.196,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 62 bytes

[00:00:04.197,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 110 bytes

[00:00:04.232,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 91 bytes

[00:00:04.232,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 89 bytes

[00:00:04.232,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 95 bytes

[00:00:04.232,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 71 bytes

[00:00:04.233,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 75 bytes

[00:00:04.233,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 69 bytes

[00:00:04.697,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 60 bytes

[00:00:04.715,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 82 bytes

[00:00:04.715,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 102 bytes

[00:00:04.716,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 82 bytes

[00:00:04.716,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 102 bytes

[00:00:05.001,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 60 bytes

[00:00:05.696,000] <dbg> net_pkt_sock_sample.recv_packet_socket: Received 60 bytes

[00:00:08.112,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:08.112,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:08.112,000] <err> eth_stm32_hal: Failed to obtain RX buffer
.
.
.

[00:00:09.615,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:09.625,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:09.626,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:09.627,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:09.629,000] <err> eth_stm32_hal: Failed to obtain RX buffer

[00:00:09.737,000] <err> net_pkt_sock_sample: Failed to send, errno 55

[00:00:09.737,000] <inf> net_pkt_sock_sample: Stopping...

[00:00:09.737,000] <err> os: ***** USAGE FAULT *****

[00:00:09.737,000] <err> os:   Illegal use of the EPSR

[00:00:09.737,000] <err> os: r0/a1:  0x20011ce4  r1/a2:  0x20014a4c  r2/a3:  0x20011788

[00:00:09.737,000] <err> os: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x0800c293

[00:00:09.737,000] <err> os:  xpsr:  0x60000000

[00:00:09.737,000] <err> os: Faulting instruction address (r15/pc): 0x00000000

[00:00:09.737,000] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0

[00:00:09.737,000] <err> os: Current thread: 0x200110d8 (main)

[00:00:09.850,000] <err> os: Halting system

Has anyone encountered this behavior with the Ethernet driver on the STM32? It seems like the ethernet driver (eth_stm_32_hal.c) is not able to pass on the received packets to the buffer using net_pkt_rx_alloc_with_buffer().

Regards,

Andreas


Re: Help flashing Zephyr to a Reel bord #reel_board #flash

Bolivar, Marti
 

"Henrik Brix Andersen via lists.zephyrproject.org"
<henrik=brixandersen.dk@lists.zephyrproject.org> writes:

Hi,

On 4 Oct 2020, at 18.44, Marco Cavallini [KOAN] <m.cavallini@koansoftware.com> wrote:

I have already done the udev settings and the board is not detected when I plug the reel board “Debug USB” connector to my PC
I fear my board is defective.
I wonder what happens when a Reel board is plugged in.
Did you remember to turn the board on using the power switch? Are any of the LEDs on the board lit?

Does anybody have one ?
Yes. I have a couple of those boards. I have no issue with flashing
them.
I have one and it's working for me also. Try plugging it in while
'udevadm monitor' is running. You should see a bunch of lines related to
device creation.

Martí


Regards,
Brix
--
Henrik Brix Andersen



421 - 440 of 2694