Re: Bluetooth: Starting dev for TI CC256x support
Arnaud Mouiche
Hello Peter,
toggle quoted messageShow quoted text
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 03/02/2020 à 13:35, Peter A. Bigot a
écrit :
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 started.
|
|
RFC: API Change: clock_control
Chruściński, Krzysztof
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 Chruściński
|
|
Re: Bluetooth: Starting dev for TI CC256x support
Christopher Friedt
On Mon., Feb. 3, 2020, 6:57 a.m. Arnaud Mouiche, <arnaud.mouiche@...> wrote: Questions: 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 coprocessor, either over UART or SPI or something. Is that correct? In that case there may be a way to add a vendor-specific HCI command [2] or simply call the command from within your application.
|
|
Re: Bluetooth: Starting dev for TI CC256x support
Peter A. Bigot
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 started.
Peter
|
|
Bluetooth: Starting dev for TI CC256x support
Arnaud Mouiche
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 'BTS' file), mainly a binary file which is sequence of action (HCI command, host baudrate change, delays...) It is a mix of device configuration, firmware patching (new features like BLE support are enabled through the init script). Each silicon version may require a different init script content. b) A basic protocol called HCILL to manage Host and/or adapter sleeping. b) is described here: https://processors.wiki.ti.com/index.php/CC256x_eHCILL_Low_Power_Protocol. The Linux driver is also a good reference: https://github.com/torvalds/linux/blob/master/drivers/bluetooth/hci_ll.c a) Init process is described in https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools/hciattach_ti.c Questions: - Is there already somebody working on the subject ? - I'm interesting by some advice to manage such "binary initialisation script" file integration. Here is what think to implement: + a python script to transform the initial binary BTS file into a C file where each action has been split in a array of strcut ready to be walk through by the driver. + the list of BTS files to embed in the firmware is managed in the cmake file of the board + the HCI driver performing init and power management can be implemented as a fresh copy of https://github.com/zephyrproject-rtos/zephyr/blob/master/drivers/bluetooth/hci/h4.c if I don't find easy way to manage a factorization. Regards, Arnaud
|
|
SDK 0.11.1 Release
Kumar Gala
Hi,
Some minor fixes that got missed for the v0.11.0 release. Mostly impacts OpenOCD and newlib usage. The SDK can be found here: https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.11.1 Please download and try things out and report any issues. OpenOCD: • Fixed missing commits from rebase - related to ARC and Zephyr RTOS awareness Newlib: • Removed setting -DMISSING_SYSCALL_NAMES on builds. Make syscall function names consistent and naming compatible with 3rd party GNU toolchains. Thanks to all that contributed fixes and enhancements to this version of the SDK. - k
|
|
Re: support for multi instance zephyr in same soc
Kumar Gala
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 cores.
toggle quoted messageShow quoted text
Look at boards/arm/lpcxpresso54114 for an example - k
On Jan 30, 2020, at 3:17 PM, Scott Branden <sbranden@gmail.com> wrote:
|
|
Re: clang toolchain doesn't failing to compile properly
Sigvart Hovland
What target are you trying to compile for?
From: devel@... <devel@...>
On Behalf Of Akira Kato via Lists.Zephyrproject.Org
Sent: Thursday, January 30, 2020 7:13 PM To: devel@... Cc: devel@... Subject: [Zephyr-devel] clang toolchain doesn't failing to compile properly
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 started guide. Here's the post I made: https://stackoverflow.com/questions/59976179/zephyr-error-using-llvm-works-fine-with-default-toolchain The problem is described there with the error logs. Thanks, Akira
|
|
support for multi instance zephyr in same soc
Scott Branden
Hello, We are currently running zephyr on M7 and linux on A72. The base M7 support has been upstreamed here: We are now looking at running Zephyr on A72 instead of linux. But it doesn't look like Zephyr build system will work if we name the board name the same for each CPU ? Any suggestions on how to name and add support for 2 different instances of Zephyr running on the same board? In our case: something that might easily achieve this is if upcoming arm64 support was not put under boards/arm but under boards/arm64 and ARCH=arm64 used instead of ARCH=arm.... Regards, Scott Branden
|
|
clang toolchain for zephyr doesn't failing to compile properly
#gettingstartedguide
Akira Kato <akira.kato@...>
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 started guide. Here's the post I made: https://stackoverflow.
The problem is described there with the error logs.
Thanks,
Akira
|
|
Upcoming Event: Zephyr Project: Dev Meeting - Thu, 01/30/2020 8:00am-9:00am, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
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 RSVP Organizer: devel@... Description: Join Zoom Meeting
|
|
Dev Rev Meeting - Jan 30 2020 Agenda
Kumar Gala
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 same as always.
https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#zephyr-dev-meeting —— Today’s agenda will focus on Device Tree, including pinmux. - k
|
|
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 application that I`m developing. Has anyone here had this same kind of problem? How do you go about debugging an application? Rafael Dias
|
|
Re: Updated Event: Zephyr Project: Dev Meeting
#cal-invite
Justin
|
|
Updated Event: Zephyr Project: Dev Meeting
#cal-invite
devel@lists.zephyrproject.org Calendar <devel@...>
Zephyr Project: Dev Meeting When: Where: Organizer: devel@... An RSVP is requested. Click here to RSVP Description:
|
|
Upcoming Event: Zephyr Project: APIs - Tue, 01/28/2020 9:00am-10:00am, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: APIs When: Tuesday, 28 January 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 RSVP Organizer: devel@... Description: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/177647878 Live meeting minutes: https://docs.google.com/
|
|
Re: ARM Cortex R intermittent MPU memory access check failures with CONFIG_USERSPACE
Glaropoulos, Ioannis
+ Andrew, Stephanos
Hi Phil, Thanks for reporting this. I need to do a more careful looking into it, but it is likely that you have spotted a bug in the Cortex-M implementation.
The implementation of mpu_buffer_validate() has not changed since its initial porting – it seems that it does not protect writing RNR and then accessing RBAR, RASR registers aferwards and that seems to have always been the case. So a thread context-switch interrupting this operation may modify the RNR register, making the read of RBAR, RASR or RLAR (v8m) inside the functions called by mpu_buffer_validate() invalid.
If mpu_buffer_validate() is called by thread supervisor mode, it needs to be protected by locking IRQs. In fact, only the PendSV needs to be lock because only that one does MPU reprogramming. Alternatively RNR could be saved and restored in PendSV handler (normal IRQs do not touch MPU).
I’d appreciate if you file a bug report for this for Cortex-M.
For Cortex-R, user mode is not assumed to be working (yet) so, strictkly speaking, it is not a bug, but if you work on Cortex-R user mode, this is one thing you need to consider!
Ioannis
From: devel@... [mailto:devel@...]
On Behalf Of phil.erwin via Lists.Zephyrproject.Org
Sent: Monday, January 27, 2020 9:38 PM To: devel@... Cc: devel@... Subject: [Zephyr-devel] ARM Cortex R intermittent MPU memory access check failures with CONFIG_USERSPACE
I'm getting intermittent run-time failures such as:
/**
|
|
API meeting: Agenda
Carles Cufi
Hi all,
I cannot attend today so Peter Bigot will kindly chair the meeting instead. The discussion will be centered exclusively around the completion of the GPIO transition into its new API. - Driver conversion check: - https://github.com/zephyrproject-rtos/zephyr/issues/18530 - Users conversion check: - https://github.com/zephyrproject-rtos/zephyr/issues/20017 - Walk-through of the proposed merge procedure by the topic-gpio branch active manager, Peter Bigot: - https://github.com/zephyrproject-rtos/zephyr/issues/21789#issuecomment-578810880 - Establish a timeline for completion of the full process Additional items in the "Triage" column in the GitHub project may be discussed if time permits. If you want an item included in the meeting, please add it to the GitHub project. 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: GPIO porting status, 28th January
Carles Cufi
Hi all,
toggle quoted messageShow quoted text
We are very close to finalizing the port of users to the new GPIO API. There are only 4 Pull Requests that need to be reviewed, reworked and merged in order to complete the process. If you know you are not going to have time to rework your PR in the next 2 days please let us know so that we can take over the Pull Request. This is the current status of GPIO user porting as of today (26th January): Remaining users with PR but requiring reviews: drivers/sensor/bma280: https://github.com/zephyrproject-rtos/zephyr/pull/22104: Peter Remaining users with PR but requiring rework of the PR: drivers/wifi/winc1500: https://github.com/zephyrproject-rtos/zephyr/pull/22156: Tomasz samples/drivers/espi: https://github.com/zephyrproject-rtos/zephyr/pull/22154: Alberto (needs rebase) drivers/ieee802154/ieee802154_cc*: https://github.com/zephyrproject-rtos/zephyr/pull/22241: Tomasz All reviews and rework of existing PRs are very welcome. See the full overview here: https://github.com/zephyrproject-rtos/zephyr/issues/20017 Regards, Carles
-----Original Message-----
|
|
ARM Cortex R intermittent MPU memory access check failures with CONFIG_USERSPACE
Phil Erwin Jr
I'm getting intermittent run-time failures such as: /**
|
|