-
Notifications
You must be signed in to change notification settings - Fork 28
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
boards: move board specific configurations #63
Conversation
@pablogs9 @Acuadros95 PTAL. |
Running CI, thanks a lot @uLipe |
@mergify backport foxy galactic main |
✅ Backports have been created
|
It seems to break the CI @uLipe : https://github.com/micro-ROS/micro_ros_zephyr_module/runs/7534484810?check_suite_focus=true#step:4:5888 |
@pablogs9 my bad, during rebase I dropped a piece of the dts I will change this to draft while I fix it |
It seems the problem is more complex, the ucd node was introduced from zephyr version 2.7 , which is on my env for now. For now I will make this compatible with 2.6 and figure later how to make the things to be compatible across the RTOS versions |
Thanks. Maybe we should investigate the working status of this module in 2.7 @Acuadros95 |
d06e442
to
f5c6986
Compare
@pablogs9 PTAL again, for now let's keep compatible with 2.6. Actually I have this running on Zephyr 3.1 but using the overlay + kconfig updates that broke the CI + this PR ros2/rcutils#368 |
f5c6986
to
45bfc52
Compare
@pablogs9 , @Acuadros95 , I just took the opportunity to modify the zephyr transport serial port to use the DT macros, label property in the devices are being removed from Zephyr and will not work in future kernel releases. Please take another review and ask me any questions you might to have. |
I'll take a look on Monday when I have some hardware in the office |
modules/libmicroros/microros_transports/serial-usb/microros_transports.c
Outdated
Show resolved
Hide resolved
modules/libmicroros/microros_transports/serial-usb/microros_transports.c
Show resolved
Hide resolved
Hello @uLipe:
|
Hi @pablogs9 my bad, I forgot to push the serial to usb commit to the PR will do it later and you will be able to test. |
45bfc52
to
f1b89c7
Compare
@pablogs9 PTAL again, you may able to build serial usb now |
Hi @pablogs9 any updates regarding your tests? About the Zephyr version I think it is safe to drop the 2.4 support, since most of V2 users would go to version 2.6 or 2.7, the last one is a LTS version. There is no Zephyr-API breaking changes across 2.4 to 2.7, the same is not true for the build system for example, depending on what changed in a particular subsystem. |
Hello @uLipe, I have been able to build the USB example but I have the following error:
Any idea? I'm working in the disco_l475_iot1 |
@pablogs9 sure, I will do that late here, and re-request your review. |
@pablogs9 btw the error you re receiving is a timeout that is coming from USB endopoint, code 5 is -EIO, which is generated by the CDC ACM class when starting endpoint sending and no notification about the write is read back, are the connections, cable ot host computer okay? Do you see the enumeration on your host? |
a26502f
to
ad2f02b
Compare
@pablogs9 rebase, please check one more time. |
Signed-off-by: Felipe <[email protected]>
port for serial transport. Signed-off-by: Felipe <[email protected]>
ad2f02b
to
af8165d
Compare
@pablogs9 fixed the changelog, please do a check again. |
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.
LGTM, @Acuadros95 merge if you are ok
@pablogs9 sorry for the delay, since we dropped the version 2.6 the CONFIG_USB symbol was also deprecated, I will remove it and update the PR |
replacing the CONFIG_USB symbol dropped in version 2.6 Signed-off-by: Felipe Neves <[email protected]>
15d8ae4
to
7266123
Compare
@pablogs9 @Acuadros95 I added the Zephyr UDC0 nodelabel, which replaces the CONFIG_USB from version 2.7 and above, please approve the workflow when you have time. |
@Acuadros95 PTAL and merger if you are ok |
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.
LGTM
* 4.0.0 * boards: move board specifc details to its own folder Signed-off-by: Felipe <[email protected]> * transports: use zephyr DT macros to set the serial port for serial transport. Signed-off-by: Felipe <[email protected]> * boards: disco_l475_iot1: add zephyr UDC0 nodelabel replacing the CONFIG_USB symbol dropped in version 2.6 Signed-off-by: Felipe Neves <[email protected]> * Update CHANGELOG.rst Signed-off-by: Felipe <[email protected]> Signed-off-by: Felipe Neves <[email protected]> Co-authored-by: Pablo Garrido <[email protected]> (cherry picked from commit 7e07006)
* 4.0.0 * boards: move board specifc details to its own folder Signed-off-by: Felipe <[email protected]> * transports: use zephyr DT macros to set the serial port for serial transport. Signed-off-by: Felipe <[email protected]> * boards: disco_l475_iot1: add zephyr UDC0 nodelabel replacing the CONFIG_USB symbol dropped in version 2.6 Signed-off-by: Felipe Neves <[email protected]> * Update CHANGELOG.rst Signed-off-by: Felipe <[email protected]> Signed-off-by: Felipe Neves <[email protected]> Co-authored-by: Pablo Garrido <[email protected]> (cherry picked from commit 7e07006)
* 4.0.0 * boards: move board specifc details to its own folder Signed-off-by: Felipe <[email protected]> * transports: use zephyr DT macros to set the serial port for serial transport. Signed-off-by: Felipe <[email protected]> * boards: disco_l475_iot1: add zephyr UDC0 nodelabel replacing the CONFIG_USB symbol dropped in version 2.6 Signed-off-by: Felipe Neves <[email protected]> * Update CHANGELOG.rst Signed-off-by: Felipe <[email protected]> Signed-off-by: Felipe Neves <[email protected]> Co-authored-by: Pablo Garrido <[email protected]> (cherry picked from commit 7e07006)
Te idea is to keep consistent with other zephyr modules and separate board specific details into their own overlays.
Also add the example l475 IoT discovery board as an example.
No changes in the environment or build.