-
Notifications
You must be signed in to change notification settings - Fork 57
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
modules: hal_silabs: Add Proprietary TRX example #49
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi! Unfortunately the HAL repo is not the right place to add examples. We should add them in main Zephyr repo instead.
This exemple only work with Silabs specific API. I don't think it makes sense to place it in Zephyr repo, do you? However, I believe it makes sense to publish it somewhere. Do you think it should be published on an external repository? Note Espressif already publish examples with their HAL: |
Hi! You're right indeed, and we should be fine with hosting these samples here in the SiLabs HAL then :) Thanks for pointing that out. |
examples/proprietary_trx/src/config/rail/brd2601b/radio_settings.radioconf
Outdated
Show resolved
Hide resolved
examples/proprietary_trx/src/config/rail/brd2602a/radio_settings.radioconf
Outdated
Show resolved
Hide resolved
f9876a9
to
527d38d
Compare
examples/proprietary_trx/src/main.c
Outdated
} | ||
if (s_obj.events & EVENT_RADIO_ERROR) { | ||
smf_set_state(SMF_CTX(&s_obj), &radio_states[ERROR]); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe if two events raise in the same iteration, one of them will be ignored. The occurrence of the bug will depends of the execution time of the functions declared in radio_states
.
BTW, if we miss the EVENT_RADIO_SENT event, we won't be able to send anything anymore.
5541cd5
to
576b290
Compare
7463b7b
to
ee150d9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @zohavas.
Usually I tried to give all my comments in the two first version of a PR. Unfortunately, some of my comments are still related to code existing since the first version. I am sorry about that, I know it is not convenient.
5cec2c7
to
34580b1
Compare
34580b1
to
cfced72
Compare
a0b3eaa
to
ac3b80a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am still dubious about the state machine, autogen files, etc... However, I don't see major issues we could fix without changing the whole design.
@fkokosinski we are almost ready, we need to validate some things with our legal department. Please wait with the merge until we are ready, thank you. |
Add Proprietary TRX example to show SiliconLabs radio board capabilities. Signed-off-by: Zoltan Havas <zoltan.havas@silabs.com>
ac3b80a
to
ebc2b4d
Compare
@fkokosinski thank you for waiting, we are ready with the requested legal validation, the merge can go, thank you for your help! |
Thanks for the ping. Please note that Zephyr is currently in a feature freeze, meaning we shouldn't be merging anything until it ends on February 23rd. I would also prefer to have 2 ACKs on the PR to Zephyr before moving with this to be sure that these changes will be pulled into Zephyr. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Samples should not be in hal repositories, this was never agreed with tsc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Samples should not be in hal repositories, this was never agreed with tsc
Indeed. I'm trying to find a suitable place where this could potentially land in the main tree, and the closest I've found so far would be under samples/boards
there.
|
||
.. code-block:: bash | ||
|
||
west build -p always -b efr32bg22_brd4184a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should IMO include two prior steps:
west update hal_silabs
west blobs fetch hal_silabs
This introduce an example of use of Rail library in Zephyr. This is a reboot of PR[1]. Compared to the original PR, this version: - remove some files imported from Simplicity Studio. Only radio_config.[ch] are kept. - drop the useless Finite State Machine For now only two boards (based xg22 and xg24) are supported. I hope to add support for all the Series-2 boards in the future. Note Zephyr does not allow to host samples application in HALs. Samples specific to one board and using non-standard APIs are not very welcomed in the main repo. So, the Silabs downstream is probably the best (the only) place to provide publish it. [1]: zephyrproject-rtos/hal_silabs#49
This introduce an example of use of Rail library in Zephyr. This is a reboot of PR[1]. Compared to the original PR, this version: - remove some files imported from Simplicity Studio. Only radio_config.[ch] are kept. - drop the useless Finite State Machine For now only two boards (based xg22 and xg24) are supported. I hope to add support for all the Series-2 boards in the future. Note Zephyr does not allow to host samples application in HALs. Samples specific to one board and using non-standard APIs are not very welcomed in the main repo. So, the Silabs downstream is probably the best (the only) place to provide publish it. [1]: zephyrproject-rtos/hal_silabs#49 Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
This introduce an example of use of Rail library in Zephyr. This is a reboot of PR[1]. Compared to the original PR, this version: - remove some files imported from Simplicity Studio. Only radio_config.[ch] are kept. - drop the useless Finite State Machine For now only two boards (based xg22 and xg24) are supported. I hope to add support for all the Series-2 boards in the future. Note Zephyr does not allow to host samples application in HALs. Samples specific to one board and using non-standard APIs are not very welcomed in the main repo. So, the Silabs downstream is probably the best (the only) place to provide publish it. [1]: zephyrproject-rtos/hal_silabs#49 Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
This introduce an example of use of Rail library in Zephyr. This is a reboot of PR[1]. Compared to the original PR, this version: - remove some files imported from Simplicity Studio. Only radio_config.[ch] are kept. - drop the useless Finite State Machine For now only two boards (based xg22 and xg24) are supported. I hope to add support for all the Series-2 boards in the future. Note Zephyr does not allow to host samples application in HALs. Samples specific to one board and using non-standard APIs are not very welcomed in the main repo. So, the Silabs downstream is probably the best (the only) place to provide publish it. [1]: zephyrproject-rtos/hal_silabs#49 Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
This introduce an example of use of Rail library in Zephyr. This is a reboot of PR[1]. Compared to the original PR, this version: - remove some files imported from Simplicity Studio. Only radio_config.[ch] are kept. - drop the useless Finite State Machine [1]: zephyrproject-rtos/hal_silabs#49 For now only two boards (based xg22 and xg24) are supported. I hope to add support for all the Series-2 boards in the future. Note Zephyr does not allow to host samples application in HALs. Samples specific to one board and using non-standard APIs are not very welcomed in the main repo. So, the Silabs downstream is probably the best (the only) place to provide publish it. Also note that files generated by Simplicity Studio (rail_config.*) ends lines with \r. To pass Zephyr compliance, this patch imports these files with \r removed: sed -i 's/\r//g' */rail_config.[hc] Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
This introduce an example of use of Rail library in Zephyr. This is a reboot of PR[1]. Compared to the original PR, this version: - remove some files imported from Simplicity Studio. Only radio_config.[ch] are kept. - drop the useless Finite State Machine [1]: zephyrproject-rtos/hal_silabs#49 For now only two boards (based xg22 and xg24) are supported. I hope to add support for all the Series-2 boards in the future. Note Zephyr does not allow to host samples application in HALs. Samples specific to one board and using non-standard APIs are not very welcomed in the main repo. So, the Silabs downstream is probably the best (the only) place to provide publish it. Also note that files generated by Simplicity Studio (rail_config.*) ends lines with \r. To pass Zephyr compliance, this patch imports these files with \r removed: sed -i 's/\r//g' */rail_config.[hc] Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
This introduce an example of use of Rail library in Zephyr. This is a reboot of PR[1]. Compared to the original PR, this version: - remove some files imported from Simplicity Studio. Only radio_config.[ch] are kept. - drop the useless Finite State Machine [1]: zephyrproject-rtos/hal_silabs#49 For now only two boards (based xg22 and xg24) are supported. I hope to add support for all the Series-2 boards in the future. Note Zephyr does not allow to host samples application in HALs. Samples specific to one board and using non-standard APIs are not very welcomed in the main repo. So, the Silabs downstream is probably the best (the only) place to provide publish it. Also note that files generated by Simplicity Studio (rail_config.*) ends lines with \r. To pass Zephyr compliance, this patch imports these files with \r removed: sed -i 's/\r//g' */rail_config.[hc] Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
This introduce an example of use of Rail library in Zephyr. This is a reboot of PR[1]. Compared to the original PR, this version: - remove some files imported from Simplicity Studio. Only radio_config.[ch] are kept. - drop the useless Finite State Machine [1]: zephyrproject-rtos/hal_silabs#49 For now only two boards (based xg22 and xg24) are supported. I hope to add support for all the Series-2 boards in the future. Note Zephyr does not allow to host samples application in HALs. Samples specific to one board and using non-standard APIs are not very welcomed in the main repo. So, the Silabs downstream is probably the best (the only) place to provide publish it. Also note that files generated by Simplicity Studio (rail_config.*) ends lines with \r. To pass Zephyr compliance, this patch imports these files with \r removed: sed -i 's/\r//g' */rail_config.[hc] Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
This introduce an example of use of Rail library in Zephyr. This is a reboot of PR[1]. Compared to the original PR, this version: - remove some files imported from Simplicity Studio. Only radio_config.[ch] are kept. - drop the useless Finite State Machine [1]: zephyrproject-rtos/hal_silabs#49 For now only two boards (based xg22 and xg24) are supported. I hope to add support for all the Series-2 boards in the future. Note Zephyr does not allow to host samples application in HALs. Samples specific to one board and using non-standard APIs are not very welcomed in the main repo. So, the Silabs downstream is probably the best (the only) place to provide publish it. Also note that files generated by Simplicity Studio (rail_config.*) ends lines with \r. To pass Zephyr compliance, this patch imports these files with \r removed: sed -i 's/\r//g' */rail_config.[hc] Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
Add Proprietary TRX example to show SiliconLabs radio board capabilities.