-
Notifications
You must be signed in to change notification settings - Fork 11
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
examples: dts: Update example dts for zcu102 and kv260 to work with zephyr rpmsg_multi_services demo #27
Comments
@wmamills are we still planning to run baremetal firmware as part of CI ? Or only zephyr firmware for zynqmp platforms? I would like to change IPI node that is used to communicate with Remote core in dts. After that current baremetal firmware binaries won't work, we will have to update it. Is that ok? |
I would like to run baremetal also but they can be new binaries. We don't need to run the old ones. If that is not possible we can start with just Zephyr. |
Ok, first we target zephyr. Once it's done we can update baremetal binaries.. |
@wmamills I can't bring-up ethernet port on kv260 board. I wanted to check with you if ethernet is working on your side? |
Just to provide information, the ethernet port should shows up, I can access my kv260 |
@uLipe what dts are you using? Also, anything special you need to mention on u-boot command line? |
so, I can see eth0 interface, but don't see IP address assigned to it: |
I got it, I think there was connection problem. |
zephyr dts for xilinx mailbox is here: https://github.com/zephyrproject-rtos/zephyr/blob/main/dts/arm/xilinx/zynqmp_rpu.dtsi#L35
Current example dts for zcu102 does not contain counter part of this node.
Currently lockstep mode is supported only for zephyr. So, lockstep mode dts need to be updated to make zephyr demo work on zcu102.
Also, kv260 device-tree needs to be pushed from latest petalinux.
The text was updated successfully, but these errors were encountered: