|
Re: Bluetooth: Starting dev for TI CC256x support
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
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
|
By
Arnaud Mouiche
·
#6716
·
|
|
RFC: API Change: clock_control
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
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
|
By
Chruściński, Krzysztof
·
#6715
·
|
|
Re: Bluetooth: Starting dev for TI CC256x support
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
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
|
By
Christopher Friedt
·
#6714
·
|
|
Re: Bluetooth: Starting dev for TI CC256x support
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
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
|
By
Peter A. Bigot
·
#6713
·
|
|
Bluetooth: Starting dev for TI CC256x support
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 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
|
By
Arnaud Mouiche
·
#6712
·
|
|
SDK 0.11.1 Release
Hi,
Some minor fixes that got missed for the v0.11.0 release. Mostly impacts OpenOCD and newlib usage.
The SDK can be found
Hi,
Some minor fixes that got missed for the v0.11.0 release. Mostly impacts OpenOCD and newlib usage.
The SDK can be found
|
By
Kumar Gala
·
#6711
·
|
|
Re: support for multi instance zephyr in same soc
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
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
|
By
Kumar Gala
·
#6710
·
|
|
Re: clang toolchain doesn't failing to compile properly
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
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
|
By
Sigvart Hovland
·
#6709
·
|
|
support for multi instance zephyr in same soc
Hello,
We are currently running zephyr on M7 and linux on A72.
The base M7 support has been upstreamed
Hello,
We are currently running zephyr on M7 and linux on A72.
The base M7 support has been upstreamed
|
By
Scott Branden
·
#6708
·
|
|
clang toolchain for zephyr doesn't failing to compile properly
#gettingstartedguide
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
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
|
By
Akira Kato <akira.kato@...>
·
#6706
·
|
|
Upcoming Event: Zephyr Project: Dev Meeting - Thu, 01/30/2020 8:00am-9:00am, Please RSVP
#cal-reminder
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
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
|
By
devel@lists.zephyrproject.org Calendar <devel@...>
·
#6704
·
|
|
Dev Rev Meeting - Jan 30 2020 Agenda
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
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
|
By
Kumar Gala
·
#6703
·
|
|
first steps / debug
#debug
#nrf52480
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
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
|
By
Rafael Dias
·
#6702
·
|
|
Re: Updated Event: Zephyr Project: Dev Meeting
#cal-invite
On Wed, Jan 29, 2020 at 7:08 AM devel@... Calendar <devel@...> wrote:
Zephyr Project: Dev Meeting
When:
Thursday, 2 May 2019
8:00am to 9:00am
(UTC-07:00) America/Los Angeles
Repeats: Weekly on
On Wed, Jan 29, 2020 at 7:08 AM devel@... Calendar <devel@...> wrote:
Zephyr Project: Dev Meeting
When:
Thursday, 2 May 2019
8:00am to 9:00am
(UTC-07:00) America/Los Angeles
Repeats: Weekly on
|
By
Justin
·
#6701
·
|
|
Updated Event: Zephyr Project: Dev Meeting
#cal-invite
Zephyr Project: Dev Meeting
When:
Thursday, 2 May 2019
8:00am to 9:00am
(UTC-07:00) America/Los Angeles
Repeats: Weekly on Thursday
Where:
https://zoom.us/j/993312203
Organizer:
Zephyr Project: Dev Meeting
When:
Thursday, 2 May 2019
8:00am to 9:00am
(UTC-07:00) America/Los Angeles
Repeats: Weekly on Thursday
Where:
https://zoom.us/j/993312203
Organizer:
|
By
devel@lists.zephyrproject.org Calendar <devel@...>
·
#6700
·
|
|
Upcoming Event: Zephyr Project: APIs - Tue, 01/28/2020 9:00am-10:00am, Please RSVP
#cal-reminder
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
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
|
By
devel@lists.zephyrproject.org Calendar <devel@...>
·
#6699
·
|
|
Re: ARM Cortex R intermittent MPU memory access check failures with CONFIG_USERSPACE
+ 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
+ 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
|
By
Glaropoulos, Ioannis
·
#6698
·
|
|
API meeting: Agenda
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.
-
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.
-
|
By
Carles Cufi
·
#6697
·
|
|
Re: GPIO porting status, 28th January
Hi all,
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
Hi all,
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
|
By
Carles Cufi
·
#6696
·
|
|
ARM Cortex R intermittent MPU memory access check failures with CONFIG_USERSPACE
I'm getting intermittent run-time failures such as:
syscall z_hdlr_k_uptime_get failed check: Memory region 0x0002ff70 (size 8) write access denied
***** Hardware exception *****
I'm getting intermittent run-time failures such as:
syscall z_hdlr_k_uptime_get failed check: Memory region 0x0002ff70 (size 8) write access denied
***** Hardware exception *****
|
By
Phil Erwin Jr
·
#6695
·
|