-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sim3u167bgm SOC support #55287
Comments
About the license, this is the comment header from the source files: //------------------------------------------------------------------------------
// Copyright (c) 2012 by Silicon Laboratories.
// All rights reserved. This program and the accompanying materials
// are made available under the terms of the Silicon Laboratories End User
// License Agreement which accompanies this distribution, and is available at
// http://developer.silabs.com/legal/version/v10/License_Agreement_v10.htm
// Original content and implementation provided by Silicon Laboratories.
//------------------------------------------------------------------------------ This is the "Silicon Laboratories End User License Agreement which accompanies this distribution" (Documentation/Silabs_License_Agreement.txt): This is what you can find at http://developer.silabs.com/legal/version/v10/License_Agreement_v10.htm as of today (2023-02-03):
While the distributed license is proprietary since it says things like Unless an official Silicon Labs representative steps in and gives their green light I don't think we can merge this. Any comments on that? |
FYI: I notified GARDENAs SiLabs FAE on 2023-03-02 about this issue. SiLabs sent a question back about the HAL version used on 2023-04-28, which we answered the same day. Will post updates here once things progress. |
I am a Silicon Labs employee. I've checked with our legal team and it is their opinion that the newer license (linked in the header files) applies to the HAL files, and it is ok to port code with the Si32 HAL register definitions to the Zephyr OS project. Please let me know if you have any questions. Best regards, |
Thanks a lot. I've created the HAL-PR and linked it in this issues description. I've also added a link to the full code of the current port. |
@silabs-Joe Unfortunately the license is still not compatible: zephyrproject-rtos/hal_silabs#29 (comment) |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
@github-actions I'm still working on it. |
I did some work on top of @M1cha's efforts and created two up-to-date PRs which (hopefully) address all previous problems. Additionally, it is now based on the official SiLabs development kit. PRs: |
Introduction
GARDENA uses a sim3u167bgm module in their smart Gateway and I've ported zephyr to it. The work is already done in terms of what is needed for that product and we want to mainline this now so others can benefit from it as well.
Problem description
Support for the SOC, GARDENAs SOM and every driver it's currently using should be merged.
Proposed change
This issue serves as an overview of this port and will link to all related PRs.
Detailed RFC
In this section of the document the target audience is the dev team. Upon
reading this section each engineer should have a rather clear picture of what
needs to be done in order to implement the described feature.
HAL
The port used silab's SI32 HAL from the Precision32 IDE.
This is only used for the register definitions. The drivers are fully zephyr-native.
It might be worth taking a look at the license That's linked to in every file's copyright header.
Drivers
We currently only intend to add support for drivers that we need. See the task list for a list of which ones we wrote.
There won't be a pinctrl driver since the hardware is too limited for that(you can't change the config at runtime without temporarily disconnecting all pins), but my port allows using pinctrl devicetree nodes to define the initial configuration.
Board
The intention is to only add support for the GARDENA smart gateway. It's readily available and can be used by anyone to develop software because root access is provided by default via UART. SPI, USART0, a few GPIOs, the reset pin and SWD are connected to the Linux SoC.
If it's a hard requirement to support Silabs official development board as well we can do that but it's currently not planned.
Dependencies
None that aren't already mainline. The PRs will contain everything that's needed.
Concerns and Unresolved Questions
Task List
The text was updated successfully, but these errors were encountered: