1. users@lists.zephyrproject.org
  2. Messages
   Date   
partition in board overlay file (for nrf52840-dk)

Nikos Karamolegkos
 

Hello,

I have create a board overlay file inside my zephyr sample where I create my partition in flash. However, if I use FLASH_AREA_ID(image_0) I can see that this ID exists which means that the partition exists too. How can I remove all these default partitions and keep only the desired ones set to my .overlay file in my project?

Thank you,

--
Nikos Karamolegkos
R & D engineer at ICS-FORTH
Telecommunications and Networks Lab (TNL)
Re: Set GPIO with SYS_INIT() #gpio #nrf52840 #sys_init

Bob Recny
 
Edited

Thanks Erik for the pointer. There was a race issue in initializing the pin before the driver was ready.

I changed from

SYS_INIT(board_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);

to

SYS_INIT(board_init, APPLICATION, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);

and the pins worked as expected.
Re: Problem with SWD after Flash on STM32L432 Nucleo Board

Chuck Link
 

I will raise a dedicated issue in GitHub.

On May 10, 2021, at 8:01 AM, Erwan Gouriou <erwan.gouriou@...> wrote:

Hi Chuck,

Thanks  for reporting this, this behavior seems indeed unusual.
Can you raise a dedicated issue in github ?

Cheers
Erwan

On Sun, 9 May 2021 at 19:00, <cml@...> wrote:

I am developing an application currently running on STM32L432 KC Nucleo reference board. I have created an STMCubeMX startup file and simple application that works flawlessly.  I can program and reprogram at 4000 kHz using the STM programmer tool.    I want to use Zephyr RTOS so I’ve built the Zephyr 2.5.0 L432KC project exactly as documented.  I can build either the “Blinky” or “HelloWorld” and load the image the first time flawlessly using The onboard ST-LINK at 4000 kHz.   However as soon as the Zephyr project is loaded, the SWD becomes troublesome.  West Flash loses complete control.  Moving back to STM tools I can sometimes connect.   I can not communicate at any speed other that 5 kHz. Sometimes not at all.   Usually it requires a power cycle and holding reset to erase (at 5 kHz) to reprogram.   Then I can use West Flash again.   


Most interesting, I can program the STMCubeMX image and reprogram multiple times at 4000 kHz.  If I move over to the Zephyr tools and image, I can use West Flash the first time at full speed and subsequently I can reprogram the Zephyr image at 480 kHz.  If I remove power from the target, I have to go back to the STM Programmer to erase the Zephyr image at 5 kHz and start the process again.  It appears at the Zephyr image is not initializing at least one register at startup.  Once the register is set using the STMCubeMX image, as long as power is not removed, the Zephyr image works OK (not great since programming speed is only 480 kHz.)

Has anyone else seen this or resolved this issue?  It appears that something is not being initialized completely.  I will continue the research, as well as try this on other STM boards.   

Thanks for the fantastic OS.  We are using it successfully on several other projects based on Nordic chips.   This is my first experience with STM chips.  


Thanks, Chuck
Re: Problem with SWD after Flash on STM32L432 Nucleo Board

Erwan Gouriou
 

Hi Chuck,

Thanks  for reporting this, this behavior seems indeed unusual.
Can you raise a dedicated issue in github ?

Cheers
Erwan

On Sun, 9 May 2021 at 19:00, <cml@...> wrote:

I am developing an application currently running on STM32L432 KC Nucleo reference board. I have created an STMCubeMX startup file and simple application that works flawlessly.  I can program and reprogram at 4000 kHz using the STM programmer tool.    I want to use Zephyr RTOS so I’ve built the Zephyr 2.5.0 L432KC project exactly as documented.  I can build either the “Blinky” or “HelloWorld” and load the image the first time flawlessly using The onboard ST-LINK at 4000 kHz.   However as soon as the Zephyr project is loaded, the SWD becomes troublesome.  West Flash loses complete control.  Moving back to STM tools I can sometimes connect.   I can not communicate at any speed other that 5 kHz. Sometimes not at all.   Usually it requires a power cycle and holding reset to erase (at 5 kHz) to reprogram.   Then I can use West Flash again.   


Most interesting, I can program the STMCubeMX image and reprogram multiple times at 4000 kHz.  If I move over to the Zephyr tools and image, I can use West Flash the first time at full speed and subsequently I can reprogram the Zephyr image at 480 kHz.  If I remove power from the target, I have to go back to the STM Programmer to erase the Zephyr image at 5 kHz and start the process again.  It appears at the Zephyr image is not initializing at least one register at startup.  Once the register is set using the STMCubeMX image, as long as power is not removed, the Zephyr image works OK (not great since programming speed is only 480 kHz.)

Has anyone else seen this or resolved this issue?  It appears that something is not being initialized completely.  I will continue the research, as well as try this on other STM boards.   

Thanks for the fantastic OS.  We are using it successfully on several other projects based on Nordic chips.   This is my first experience with STM chips.  


Thanks, Chuck
Zephyr 2.6.0-rc1 tagged

Kumar Gala
 

Hi all,

The first release candidate for Zephyr 2.6.0 has been tagged (v2.6.0-rc1).

The merge window for features and enhancements is now closed for this release, and it will remain closed until 2.6.0 is released; the stabilization period is now open. During the stabilization period only bug-fix, documentation, and stabilization-related patches may be merged to master. Additional features or enhancements for the 2.6.0 release require approval by the TSC.

We currently have the following bug counts:

* High - 5
* Medium - 41
* Low - 152

The goal for release is to be at:
* High - 0
* Medium < 20
* Low < 50

We have a long way to go on lows!

As we need to reduce bug counts for the release, you are all encouraged to submit PRs that close existing bug reports, and to help reviewing such PRs submitted by other contributors or maintainers. You can follow the bug numbers with the thresholds for each bug category here:

https://testing.zephyrproject.org/issues/zephyrproject-rtos/zephyr/index.html

Testing Zephyr master branch during the stabilization period is also requested; please test the code base and file bug reports so they can be addressed before the release deadline. Everyone is encouraged, especially hardware vendors, to test on hardware available to them. Use twister to run tests from the Zephyr tree on the boards you have using the device testing features.

The full release log can be found here:

https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.6.0-rc1

We plan to release weekly candidates (2.6.0-rcx) leading to the final release (2.6.0) which is tentatively scheduled for 28 May.

You may continue to submit pull requests for new features in order to gather feedback early or collaborate with others, but the release team would like to encourage everyone to focus on bugfixes and documentation improvements to the largest extent possible, so that we can release 2.6.0 on time and in the best shape possible.

A big Thank You to everyone that contributed to this release so far, be it with code, reviews, documentation or any other type of contribution!

Kumar
Problem with SWD after Flash on STM32L432 Nucleo Board

Chuck Link
 

I am developing an application currently running on STM32L432 KC Nucleo reference board. I have created an STMCubeMX startup file and simple application that works flawlessly.  I can program and reprogram at 4000 kHz using the STM programmer tool.    I want to use Zephyr RTOS so I’ve built the Zephyr 2.5.0 L432KC project exactly as documented.  I can build either the “Blinky” or “HelloWorld” and load the image the first time flawlessly using The onboard ST-LINK at 4000 kHz.   However as soon as the Zephyr project is loaded, the SWD becomes troublesome.  West Flash loses complete control.  Moving back to STM tools I can sometimes connect.   I can not communicate at any speed other that 5 kHz. Sometimes not at all.   Usually it requires a power cycle and holding reset to erase (at 5 kHz) to reprogram.   Then I can use West Flash again.   


Most interesting, I can program the STMCubeMX image and reprogram multiple times at 4000 kHz.  If I move over to the Zephyr tools and image, I can use West Flash the first time at full speed and subsequently I can reprogram the Zephyr image at 480 kHz.  If I remove power from the target, I have to go back to the STM Programmer to erase the Zephyr image at 5 kHz and start the process again.  It appears at the Zephyr image is not initializing at least one register at startup.  Once the register is set using the STMCubeMX image, as long as power is not removed, the Zephyr image works OK (not great since programming speed is only 480 kHz.)

Has anyone else seen this or resolved this issue?  It appears that something is not being initialized completely.  I will continue the research, as well as try this on other STM boards.   

Thanks for the fantastic OS.  We are using it successfully on several other projects based on Nordic chips.   This is my first experience with STM chips.  


Thanks, Chuck
Re: Set GPIO with SYS_INIT() #gpio #nrf52840 #sys_init

Bob Recny
 

I realize I mentioned the need to set the pin low and that code above is attempting to set the pin high. If I just start the board without this code, the pin is measured low on my oscilloscope even with it unconfigured. I'm first setting the pin high so I can observe the change, then make the adjustment to low.
Set GPIO with SYS_INIT() #gpio #nrf52840 #sys_init

Bob Recny
 

Greetings,

I'm working on adding a board to Zephyr. I'm attempting to use a board.c file to configure GPIO pins as output and initialize them low on start-up. I've attempted to follow existing boards, but am not being successful. device_get_binding() always returns NULL so the call to gpio_pin_configure() never occurs. I took the nrf52840dk_nrf52840 board and added CMakeLists.txt and board.c.

CMakeLists.txt:

zephyr_library()
zephyr_library_sources(board.c)

board.c:

#include <init.h>
#include <drivers/gpio.h>

#define TEST_PIN	31		/* P0.31 */

static int board_init(const struct device *dev)
{
	ARG_UNUSED(dev);

	int ret;
	const struct device *gpio_port;
	gpio_port = device_get_binding(DT_LABEL(DT_NODELABEL(gpio0)));

        if (!mode_asel_port_dev) {
                return -ENODEV;
        }

	ret = gpio_pin_configure(mode_asel_port_dev, TEST_PIN, GPIO_OUTPUT_HIGH);
	if (ret < 0) {
		return ret;
	}

	return 0;
}

SYS_INIT(board_init,  POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);

Any suggestions?

Thanks, Bob
Set zephyr EXACT version

Rodrigo Brochado
 

Hello,

How can I restrain zephyr to be at a specific version on my application CmakeLists.txt?

I've done this:
find_package(Zephyr 2.7.0 EXACT)

even on the hello_world sample and it compiled normally with 2.4.0 without complains. I've also unset ZEPHYR_BASE with no success. I've followed this guide:
https://docs.zephyrproject.org/latest/guides/zephyr_cmake_package.html#zephyr-cmake-package-version

Thanks!
SDK 0.13.0-alpha-1 Release

Kumar Gala
 

Hi all,

Just wanted to let people be aware few have an alpha release of the v0.13.0 SDK. The main focus of this alpha release is to enable ARC64 support in the toolchain.

Additionally we’ve updated gcc to be based on the GCC 10.3.0 release and pulled in QEMU 6.0.0.

I expect we will update OpenOCD to be based on a snapshot post the v0.11.0 release. Also, there’s expectation that ESP32 support will be added as well.

The SDK can be found here:

https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.13.0-alpha-1

general:
Added support for ARC64. NOTE: GDB isn't currently supported
for ARC64.

qemu:
Updated to QEMU 6.0.0
Added arc64 support. NOTE: this update ARC support replaces
the machine (-M simhs) with (-M virt). This change will require
updates to boards/arc/qemu_arc/board.cmake in Zephyr to match.

gcc:
Update to gcc 10.3 release
Added support for ARC64

binutils:
Updated to add support for ARC64

newlib:
Updated to add support for ARC64

crosstool-ng:
sync with upstream. Upstream now supports newlib-nano so we drop
our Zephyr specific updates. This also pulls in gcc-10.3 and
initial support for ARC64.

yocto:
Update to yocto 3.2.3 baseline. This is in prep to support building
qemu-6.0.0

Thanks to all that contributed fixes and enhancements to this version of the SDK.

- k
Re: [Zephyr-devel] Network forum agenda

Jukka Rissanen
 

One topic emerged:

- WiFi and wpa supplicant support in Zephyr


Cheers,
Jukka

On Mon, 2021-05-03 at 17:57 +0300, Jukka Rissanen wrote:
Hi all,

There is a network forum meeting tomorrow Tue 4 May at 8AM PST /
17.00
CEST.

Currently the agenda is empty, so if there is anything network
related
topics you want to discuss, please let me know, otherwise I will
cancel
the meeting.

Live Agenda/Minutes:
https://docs.google.com/document/d/1qFsOpvbyLzhflJbbv4Vl__497pKHDoUCy9hjAveyCX0/edit?usp=sharing

Shared Folder:
https://drive.google.com/drive/folders/1j6d0FLeOjiMil1Ellb59AsfHdzuWdAAc?usp=sharing

___________________________________________________________
Join Microsoft Teams Meeting (
https://teams.microsoft.com/l/meetup-join/19%3ameeting_NDU5ODRkNzktZDBmNC00MDg5LWI2OWEtNzM0MGZjMDU0Yjgw%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
)
+1 321-558-6518 ( tel:+1 321-558-6518,,458216365# ) United States,
Orlando (Toll)
Conference ID: 458 216 365#
Local numbers (
https://dialin.teams.microsoft.com/325d775d-c910-441e-90d0-353ebaa56cdd?id=458216365
) | Reset PIN ( https://mysettings.lync.com/pstnconferencing ) |
Learn
more about Teams ( https://aka.ms/JoinTeamsMeeting ) | Meeting
options
(
https://teams.microsoft.com/meetingOptions/?organizerId=841a7c92-7816-4faf-9887-5e334e88f6d8&tenantId=af0096d9-700c-411a-b795-b3dd7122bad2&threadId=19_meeting_NDU5ODRkNzktZDBmNC00MDg5LWI2OWEtNzM0MGZjMDU0Yjgw@thread.v2&messageId=0&language=en-US
)


Cheers,
Jukka
Network forum agenda

Jukka Rissanen
 

Hi all,

There is a network forum meeting tomorrow Tue 4 May at 8AM PST / 17.00
CEST.

Currently the agenda is empty, so if there is anything network related
topics you want to discuss, please let me know, otherwise I will cancel
the meeting.

Live Agenda/Minutes:
https://docs.google.com/document/d/1qFsOpvbyLzhflJbbv4Vl__497pKHDoUCy9hjAveyCX0/edit?usp=sharing

Shared Folder:
https://drive.google.com/drive/folders/1j6d0FLeOjiMil1Ellb59AsfHdzuWdAAc?usp=sharing

___________________________________________________________
Join Microsoft Teams Meeting (
https://teams.microsoft.com/l/meetup-join/19%3ameeting_NDU5ODRkNzktZDBmNC00MDg5LWI2OWEtNzM0MGZjMDU0Yjgw%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
)
+1 321-558-6518 ( tel:+1 321-558-6518,,458216365# ) United States,
Orlando (Toll)
Conference ID: 458 216 365#
Local numbers (
https://dialin.teams.microsoft.com/325d775d-c910-441e-90d0-353ebaa56cdd?id=458216365
) | Reset PIN ( https://mysettings.lync.com/pstnconferencing ) | Learn
more about Teams ( https://aka.ms/JoinTeamsMeeting ) | Meeting options
(
https://teams.microsoft.com/meetingOptions/?organizerId=841a7c92-7816-4faf-9887-5e334e88f6d8&tenantId=af0096d9-700c-411a-b795-b3dd7122bad2&threadId=19_meeting_NDU5ODRkNzktZDBmNC00MDg5LWI2OWEtNzM0MGZjMDU0Yjgw@thread.v2&messageId=0&language=en-US
)


Cheers,
Jukka
No binding for LIS3DH #dts

Kiril Zyapkov
 

I played with Zephyr back in 2018 -- I had a working setup with custom out-of-tree board for CJMCU8223 -- a Chinese thingy with NRF51. Some days ago, I decided to revive this setup and use it for a toy project.

It took some fiddling to adapt to the latest Zephyr and `west`, but I think I got most everything in place. One issue remains though -- I cannot get a binding for the LIS3DH sensor onboard. I think the issue comes from some mismatch in the "compatible" strings and related DT glue -- at some point LIS3DH has been merged with LIS2DH. It must be some obvious oversight, but I don't know the system well enough to trace it.

I think the issue is not with my custom board, because trying to build `zephyr/samples/sensor/lis2dh` for one of the in-tree boards with LIS3DH sensors results in the same error:

#warning "LIS2DH driver enabled without any devices"

or a linker error if using `DEVICE_DT_GET()`.

To reproduce:

Add the okay for the sensor node in, say, 96b_wistrio.overlay:
&i2c1 {
    lis3dh@32 {
        status = "okay";
    };
};

Change `st_lis2dh` to `st_lis3dh` in `zephyr/samples/sensor/lis2dh/src/main.c`

Run `west build -b 96b_wistrio zephyr/samples/sensor/lis2dh`

Also, my custom board, failing in the same way:

git clone https://github.com/kzyapkov/zephyr-cjmcu8223/
west build -b cjmcu8223 zephyr-cjmcu8223/sample_app/

I hope that's something trivial to fix.

Cheers!
-- Kiril
STM32: Clock control configuration moved from Kconfig to device tree

Erwan Gouriou
 

Hi,

We've started to transition STM32 clock system configuration from Kconfig to dts.

The main change (that introduces the whole mechanism) has been merged earlier this week,
making it available to L4/F4 and WB series:
It was followed by another change continuing the transition for remaining series 
(F0/F1/F2/F3/F7/G0/G4/L0/L1/L5/WL) and was merged earlier today.
The last change impacts H7 and is currently under review:

This series of changes allows to configure the whole stm32 clock system using
device tree, but for now, no extra modification is done in stm32 clock_control drivers. 

Kconfig style configuration is still functional but will be tagged as deprecated.
For now, only a couple of in tree boards have been converted to the new dts based
method.

I've raised an issue to track the mass conversion of the existing in tree boards
By the way, we're welcoming community contributions for this task!

Once all boards are converted, we'll be able to deprecate the Kconfig part,
which I hope could be done in DV2.6.0 timeframe.

During deprecation period, the stm32 clock_control developments involving 
device tree will be limited in order to keep backward compatibility with Kconfig.
This is done as a convenience for out of tree users. But for instance, code additions
like support of new series or PLLs will be implemented directly using device tree.

After the deprecation period, STM32 Kconfig clock_control part will be removed
and we'll be able to rework STM32 clock_control driver deeper and take advantage
of the benefits provided by device tree.

Don't hesitate to reach me on slack if you have questions.

Cheers
Erwan
Googletest as a Zephyr module for native_posix target #nrf52

tjones@...
 

I'm new to Zephyr and am trying to get a Linux VM hosted native_posix unit test build environment set up for our Zephyr nRF52 embedded project. 

I've set up the Zephyr SDK and west native_posix (& qemu_x86) build environment and can build and run the samples and a simple hello world test under my Ubuntu 20.04 Linux VM.

We'd like to use GoogleTest/Mock for our unit test environment within the Zephyr native_posix environment. Has anyone here got that working? I've got some way following this StackOverflow post unit-testing-c-code-into-zephyr-with-googletest , but unfortunately it does not provide details of the module.yml and Kconfig file contents. I don't yet know enough to fill them in myself and west / cmake reports that my googletest module is "not a valid zephyr module".

Any help or pointers would be appreciated!
Re: Zephyr HCI USB vs Bluez version

Piotr Barszczewski <piotr@...>
 

Furthermore the same thing happens using bluetoothctl which seems to be the prefered way of doing HCI on Linux over the gatttool and hcitool. 
I really can’t find a way to read/write with any bluez utils and nRF52840 DK with HCI_USB firmware. On the other hand a simple CSR dongle works ok. With nRF52840DK and HCI_USB it’s always the same story, it connects but doesn’t do anything and disconnects after ~10 seconds. Is there any way to make it work with a pretty normal BLE device? Never any had issues with connecting from phones or other HCI dongles, just one with Zephyr based HCI.

< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7                                                             #58 [hci2] 74.790926
        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                                                                            #59 [hci2] 74.792191
      LE Set Scan Parameters (0x08|0x000b) ncmd 1
        Status: Success (0x00)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2                                                                 #60 [hci2] 74.792206
        Scanning: Enabled (0x01)
        Filter duplicates: Enabled (0x01)
> HCI Event: Command Complete (0x0e) plen 4                                                                            #61 [hci2] 74.793190
      LE Set Scan Enable (0x08|0x000c) ncmd 1
        Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 42                                                                              #62 [hci2] 74.800193
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Connectable undirected - ADV_IND (0x00)
        Address type: Random (0x01)
        Address: EC:50:02:EA:E6:3E (Static)
        Data length: 30
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        Company: Apple, Inc. (76)
          Type: iBeacon (2)
          UUID: ...
          Version: 512.16102
          TX power: -59 dB
        RSSI: -39 dBm (0xd9)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2                                                                 #63 [hci2] 74.800213
        Scanning: Disabled (0x00)
        Filter duplicates: Disabled (0x00)
> HCI Event: Command Complete (0x0e) plen 4                                                                            #64 [hci2] 74.801190
      LE Set Scan Enable (0x08|0x000c) ncmd 1
        Status: Success (0x00)
< HCI Command: LE Create Connection (0x08|0x000d) plen 25                                                              #65 [hci2] 74.801203
        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: EC:50:02:EA:E6: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                                                                              #66 [hci2] 74.803190
      LE Create Connection (0x08|0x000d) ncmd 1
        Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 31                                                                              #67 [hci2] 74.904193
      LE Enhanced Connection Complete (0x0a)
        Status: Success (0x00)
        Handle: 0
        Role: Master (0x00)
        Peer address type: Random (0x01)
        Peer address: EC:50:02:EA:E6:3E (Static)
        Local resolvable private address: 00:00:00:00:00:00 (Non-Resolvable)
        Peer resolvable private address: 00:00:00:00:00:00 (Non-Resolvable)
        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                                                                   {0x0001} [hci2] 74.904214
        LE Address: EC:50:02:EA:E6:3E (Static)
        Flags: 0x00000000
        Data length: 30
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        Company: Apple, Inc. (76)
          Type: iBeacon (2)
          UUID: ...
          Version: 512.16102
          TX power: -59 dB
< HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2                                                       #68 [hci2] 74.904282
        Handle: 0
> HCI Event: LE Meta Event (0x3e) plen 4                                                                               #69 [hci2] 74.905193
      LE Channel Selection Algorithm (0x14)
        Handle: 0
        Algorithm: #2 (0x01)
> HCI Event: Command Status (0x0f) plen 4                                                                              #70 [hci2] 74.906191
      LE Read Remote Used Features (0x08|0x0016) ncmd 1
        Status: Success (0x00)
> ACL Data RX: Handle 0 flags 0x02 dlen 7                                                                              #71 [hci2] 74.906279
      ATT: Exchange MTU Request (0x02) len 2
        Client RX MTU: 247
> HCI Event: LE Meta Event (0x3e) plen 12                                                                              #72 [hci2] 75.056195
      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
= bluetoothd: src/device.c:load_gatt_db() No cache for EC:50:02:EA:E6:3E                                                          75.056414
< ACL Data TX: Handle 0 flags 0x00 dlen 7                                                                              #73 [hci2] 75.056493
      ATT: Exchange MTU Response (0x03) len 2
        Server RX MTU: 517
< ACL Data TX: Handle 0 flags 0x00 dlen 7                                                                              #74 [hci2] 75.056505
      ATT: Exchange MTU Request (0x02) len 2
        Client RX MTU: 517
> ACL Data RX: Handle 0 flags 0x02 dlen 16                                                                             #75 [hci2] 94.955356
      LE L2CAP: Connection Parameter Update Request (0x12) ident 3 len 8
        Min interval: 9
        Max interval: 24
        Slave latency: 0
        Timeout multiplier: 100
@ MGMT Event: New Connection Parameter (0x001c) plen 16                                                           {0x0001} [hci2] 94.955378
        Store hint: Reserved (0x3e)
        BR/EDR Address: 02:EC:50:02:EA:E6 (OUI 02-EC-50)
        Min connection interval: 9
        Max connection interval: 24
        Connection latency: 0 (0x0000)
        Supervision timeout: 100
< ACL Data TX: Handle 0 flags 0x00 dlen 10                                                                             #76 [hci2] 94.955387
      LE L2CAP: Connection Parameter Update Response (0x13) ident 3 len 2
        Result: Connection Parameters accepted (0x0000)
< HCI Command: LE Connection Update (0x08|0x0013) plen 14                                                              #77 [hci2] 94.955393
        Handle: 0
        Min connection interval: 11.25 msec (0x0009)
        Max connection interval: 30.00 msec (0x0018)
        Connection latency: 0 (0x0000)
        Supervision timeout: 1000 msec (0x0064)
        Min connection length: 0.000 msec (0x0000)
        Max connection length: 0.000 msec (0x0000)
> HCI Event: Command Status (0x0f) plen 4                                                                              #78 [hci2] 94.956383
      LE Connection Update (0x08|0x0013) ncmd 1
        Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 10                                                                              #79 [hci2] 95.353393
      LE Connection Update Complete (0x03)
        Status: Success (0x00)
        Handle: 0
        Connection interval: 30.00 msec (0x0018)
        Connection latency: 0 (0x0000)
        Supervision timeout: 1000 msec (0x0064)
> HCI Event: Disconnect Complete (0x05) plen 4                                                                        #80 [hci2] 104.956473
        Status: Success (0x00)
        Handle: 0
        Reason: Remote User Terminated Connection (0x13)
@ MGMT Event: Device Disconnected (0x000c) plen 8                                                                {0x0001} [hci2] 104.956490
        LE Address: EC:50:02:EA:E6:3E (Static)
        Reason: Connection terminated by remote host (0x03)


On 23 April 2021 at 20:12:16, Piotr Barszczewski (piotr@...) wrote:

Hello,

Is there some guide on which of the recent kernel/bluez/linux versions does the HCI_USB ( https://github.com/zephyrproject-rtos/zephyr/tree/master/samples/bluetooth/hci_usb ) work on nRF52840_pca100056 board? I’m having quite hard time figuring how to make it work beyond being able to scan, connect or disconnect.

As an example I usually try the following with any HCI device:
1. Connect to my test device with gatttool
2. Try to discover characteristics
3. Send a few bytes with char-write-cmd …
4. Observe on test device if it was received
5. Disconnect

The problem I’m observing on Ubuntu 20 with kernel 5.8.0-50 is that the nRF DK enumerating as port hci1 always has it’s address set to 00:00:00:00:00:00 and does not do anything beyond connecting. Tried with Bluez 5.55 and 5.58, my bluetoothd.service already has -E flag set. Usually I’m working with CSR dongles and never had issues with multiple HCI devices connected and thought that it would be a quick test do compare how nRF52840 performs with Zephyr. Yet here I am out of ideas on what to do next, asking the very basic question, bit puzzled on how yo make such a simple thing work. Would really appreciate if someone could point me to how to make Zephyr HCI work with any Bluez

Best regards
Zephyr HCI USB vs Bluez version

Piotr Barszczewski <piotr@...>
 

Hello,

Is there some guide on which of the recent kernel/bluez/linux versions does the HCI_USB ( https://github.com/zephyrproject-rtos/zephyr/tree/master/samples/bluetooth/hci_usb ) work on nRF52840_pca100056 board? I’m having quite hard time figuring how to make it work beyond being able to scan, connect or disconnect.

As an example I usually try the following with any HCI device:
1. Connect to my test device with gatttool
2. Try to discover characteristics
3. Send a few bytes with char-write-cmd …
4. Observe on test device if it was received
5. Disconnect

The problem I’m observing on Ubuntu 20 with kernel 5.8.0-50 is that the nRF DK enumerating as port hci1 always has it’s address set to 00:00:00:00:00:00 and does not do anything beyond connecting. Tried with Bluez 5.55 and 5.58, my bluetoothd.service already has -E flag set. Usually I’m working with CSR dongles and never had issues with multiple HCI devices connected and thought that it would be a quick test do compare how nRF52840 performs with Zephyr. Yet here I am out of ideas on what to do next, asking the very basic question, bit puzzled on how yo make such a simple thing work. Would really appreciate if someone could point me to how to make Zephyr HCI work with any Bluez

Best regards
HTTP client not connecting to Microsoft Azure Blob Storage #fota

petrus.vanderwalt@...
 

Hi everyone,

I want to create a FOTA solution for my project.  I am trying to use the HTTP client to download a file from Microsoft Blob storage.  My issue is that the HTTP client does not connect to my Blob storage host address "zephyriot.blob.core.windows.net" using MBed TLS and the Baltimore CyberTrust Root certificate.  I have checked that the URL copied from blob storage does work when using my internet browser.  The HTTP client does connect when I use my IoT hub host address "WCM.azure-devices.net".  I have included my source code for you to look at.  I am hoping that someone here has had success downloading files from Blob storage and can provide a solution to my issue.  Any help is much appreciated.

This is the output:
Preparing HTTP GET request for http://zephyriot.blob.core.windows.net:443/downloads/BlobDownloadTest_v_0.0.0.txt
uart:~$ getaddrinfo status: 0
addrinfo @0x20014dc0: ai_family=1, ai_socktype=1, ai_protocol=6, sa_family=1, sin_port=bb01
sock = 0
Error: connect(sock, res->ai_addr, res->ai_addrlen)
exit

?
digicert.cer
?
test_certs.h
?
blob_download.c

Re: STM32F107 clocks

Gunnar Bråding
 

Awesome! Worked like a charm. Thanks a bunch!

Cheers,
— Gunnar

On 16 Apr 2021, at 15:10, Attie Grande <attie.grande@...> wrote:

Hi Gunnar,

We got the PLL2 code into the STM32CubeF1 codebase a little while ago [1].
There are also some patches for adding this support into Zephyr, but I
need to revisit them / make a PR now that the PLL2 support was merged
into STM32CubeF1... [2][3][4].

I hope that helps!

Attie

[1]: https://github.com/STMicroelectronics/STM32CubeF1/commit/f5aaa9b45492d70585ade1dac4d1e33d5531c171
[2]: https://github.com/argentum-systems/zephyr/commit/6c167af50aeca2fc5f6e760de205807fda51c1c9
[3]: https://github.com/argentum-systems/zephyr/commit/cb65e6da942f907b63f0711b57318839561264b6
[4]: https://github.com/argentum-systems/zephyr/commit/da99de64bcf9cbb3dc8a2e1da2e0a4fb9f45258b


On Thu, 15 Apr 2021 at 14:29, Erwan Gouriou <erwan.gouriou@...> wrote:

Hi Gunnar,

Unfortunately, we miss code for PLL2 configuration as PLL input.
Though, I'm adding Attie who investigated that point and may have code to get it working.

BR
Erwan

On Thu, 15 Apr 2021 at 10:51, Gunnar Bråding <gunnar@...> wrote:

Hi!

I got a board with the crystal at 25MHz, and need to use the PLL2 as input to the system clock.
I just do not seem to understand the code enough to see how to set the prediv and multiplication for the PLL2
I can choose PLL2 as input to the PLL, and PLL as input to the system clock, but how do set the parameters for PLL2?

Any pointers would be very much appreciated.

Cheers,
— Gunnar
Final Reminder: CFP -- Zephyr Developer Summit 2021

Brett Preston
 

Members of the Zephyr Community,

A final reminder that the Call for Papers for the Zephyr Developer Summit closes tomorrow (Tuesday, April 20):

Look for schedule announcement and registration on May 5.

Thank you,


Brett


On Wed, Apr 14, 2021 at 10:00 AM Brett Preston <bpreston@...> wrote:
Members of the Zephyr Community,

A reminder of the Call for Papers that remains open until Tuesday, April 20:

The Zephyr Developer Summit has been scheduled for Tuesday, June 8 - Thursday, June 10, 2021

This free virtual event will feature two tracks:

Track A: Mini-conference (each will be 120 minutes in length)
  • This track is designed to let the organizer(s) focus on discussing an open topic with the other key participants.  A successful mini-conference outlines a problem and provides sufficient background so participants can engage in effective discussion.   Examples where this style is used:  Linux Plumbers, Conference Fishbowl Sessions, extended BOF etc.  Goal here is to have an effective discussion session and make progress on an outstanding problem.
  • Some possible topic areas could include:
    • Firmware
    • Modules
    • Networking Stack
    • Power Management
    • Toolchain
    • Topics identified in 2020 developer survey
Track B: Presentations. (choice of 30 or 60 minutes in length or lighting talks)
  • This is designed for sharing knowledge and providing context for other discussions.
  • Some possible topic ideas include:
    • How is Zephyr being used in products
    • Demos of tools working with Zephyr
    • Overview of proposed technologies for inclusion
    • Summary of what’s happening in subsystems
    • Updates on west, modules, runtimes, etc.
    • Security & Safety team updates
    • Test infrastructure Improvements
    • BOF topics
    • Lightning talk on something cool in Zephyr you want to share

Other Key Dates
  • May 5 - Schedule announcement
  • May 5 - Registration opens

Thank you!


Brett


On Wed, Apr 7, 2021 at 4:16 PM Brett Preston <bpreston@...> wrote:
Members of the Zephyr Community,

The inaugural Zephyr Developer Summit has been scheduled for Tuesday, June 8 - Thursday, June 10, 2021.

Furthermore, the Call for Papers is Now Open: https://forms.gle/i637wnnBp9ahrnc37 (closes April 20).

This free virtual event will feature two tracks:

Track A: Mini-conference (each will be 120 minutes in length)
  • This track is designed to let the organizer(s) focus on discussing an open topic with the other key participants.  A successful mini-conference outlines a problem and provides sufficient background so participants can engage in effective discussion.   Examples where this style is used:  Linux Plumbers, Conference Fishbowl Sessions, extended BOF etc.  Goal here is to have an effective discussion session and make progress on an outstanding problem.
  • Some possible topic areas could include:
    • Firmware
    • Modules
    • Networking Stack
    • Power Management
    • Toolchain
    • Topics identified in 2020 developer survey
Track B: Presentations. (choice of 30 or 60 minutes in length or lighting talks)
  • This is designed for sharing knowledge and providing context for other discussions.
  • Some possible topic ideas include:
    • How is Zephyr being used in products
    • Demos of tools working with Zephyr
    • Overview of proposed technologies for inclusion
    • Summary of what’s happening in subsystems
    • Updates on west, modules, runtimes, etc.
    • Security & Safety team updates
    • Test infrastructure Improvements
    • BOF topics
    • Lightning talk on something cool in Zephyr you want to share

Other Key Dates
  • May 5 - Schedule announcement
  • May 5 - Registration opens

Thank you,


Brett

--
Brett Preston
Sr. Program Manager
The Linux Foundation
+1 (971) 303-9030



--
Brett Preston
Sr. Program Manager
The Linux Foundation
+1 (971) 303-9030



--
Brett Preston
Sr. Program Manager
The Linux Foundation
+1 (971) 303-9030
401 - 420 of 2972