Reminder: Zephyr Project: APIs When: Tuesday, 4 February 2020, 9:00am to 10:00am, (GMT-08:00) America/Los Angeles Where:https://zoom.us/j/177647878 An RSVP is requested. Click here to

Hi all, Today we will talk first about GPIO and the merge of the topic-gpio branch to master: - Cleanup the public and private API with typedefs - Testing status - Issues with master CI that

Hi Scott, Yes, the whole “board” concept needs an overhaul to become instead “instances” or “targets” as you say. In the nRF5340, which is a dual-core asymmetric Cortex-M33, we used

Interesting, some parts of the documentation gave me the (wrong?) impression that a BOARD allowed some level of variation and configuration at build

Thanks Kumar - we will go with this convention for naming the target. ie board_cpu. It will work out as long as there are not multiple cpu's on the same board that need different zephyr builds. At

Hi, Thanks Kumar. Please note that this version of the SDK is now required for development on master and is enabled in CI. Anas On 03/02/2020, 05:56, "users@... on behalf of

Hello Christopher, Yes, I will use the Bluetooth chipset with HCI over UART connection. I will check your advice. Thanks, Arnaud

Hello Peter, The chipset I expect to support first is the CC2564 which is not a SOC but a simple HCI adapter. Zephyr will run on another MCU. Regards, Arnaud Le

Hi all, I’ve created a RFC for clock control API update: https://github.com/zephyrproject-rtos/zephyr/issues/22424 Please review and comment on the GitHub issue. Regards, Krzysztof

I'm working on the split-LL BLE stack [1] implementation currently, but that is for the "Single Chip" configuration. From what you describe, it sounds as though you would like to use the SoC as a BLE

https://github.com/zephyrproject-rtos/zephyr/pull/22012 removed support for this SOC. If you're interested in maintaining this platform, it could be resurrected. Please comment on that issue to get

Hi all, I wish to develop the required driver to interface Zephyr with the TI Bluetooth CC256x chipset family. Here are the requirements: a) Need to upload an initialization script (what they call a

Hi, Some minor fixes that got missed for the v0.11.0 release. Mostly impacts OpenOCD and newlib usage. The SDK can be found

This has been a long standing issue. Since these are both ARM you can get away with doing something similar to how we handle building different images for SoCs that have 2 different M-class

What target are you trying to compile for? From the stack overflow thread I find Target: x86_64-pc-linux-gnu Then some references to the Nordic HAL. So I’m just going to assume you are trying to

Hello, We are currently running zephyr on M7 and linux on A72. The base M7 support has been upstreamed

Hi, I don't know if this is the proper place to ask technical question about zephyr but I have tried stackoverflow and started github issue with no help. I am new to zephyr so I followed the getting

Reminder: Zephyr Project: Dev Meeting When: Thursday, 30 January 2020, 8:00am to 9:00am, (GMT-08:00) America/Los Angeles Where:https://zoom.us/j/993312203 An RSVP is requested. Click here to

NOTE: The cal invite has gotten messed up and might show the meeting starting a hour earlier than normal. This is NOT correct, we are working on trying to correct the issue. The meeting time is the

Hi! This is my first message to the Zephyr forum. Well, I started to work with zephyr a few days ago. I followed the steps from the Getting Started Guide and I'd like to perform the debugging of the