-
Notifications
You must be signed in to change notification settings - Fork 18
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
Issue with SD image generated following ROS 2 publisher example #73
Comments
KRS is a bit unstable right now, as the firmware extensions (e.g. The concepts WILL remain the same and the dev flow identical to the usual ROS one, but moving to Ubuntu will provide a more developer friendly environment. Also, instead of having to create your own SD card image, you'll only need to flash Ubuntu's official Kria images (see here). Another possibility is that you're not using the right resources. What confuses me a bit though is that you above report:
This relates to Vitis 2020.2, which corresponds with |
Btw, the issue above is that the kernel's not finding the rootfs while running You could probably boot successfully fixing this. If you're not familiar with these concepts though, I'd recommend checking out the Ubuntu path of KRS's release. See https://xilinx.github.io/KRS/sphinx/build/html/docs/install.html#ubuntu-22-04. |
That was what the example in the Documentation said I should get. What I actually get is "# /" as shown in the picture. I am using Vitis 2022.1 and Ubuntu 22.04 to develop my applications and trying to follow the flow of creating the SD image with colcon acceleration.
Does that mean that only the Native development will be supported in the future?
I followed these steps in my development platform and then tried to run this example https://xilinx.github.io/KRS/sphinx/build/html/docs/examples/0_ros2_publisher.html#building-creating-the-raw-image-and-running-in-hardware, but the image created using that approach results in my issue |
When you are upgrading to Vitis 2022.1 with Ubuntu 22.04, you might need to upgrade the firmware as well, Please go through the documentation below. On how to update firmware. https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1641152513/Kria+K26+SOM#Boot-Firmware-Updates |
@mvgianel then follow guidelines for Ubuntu, not for Yocto. See https://xilinx.github.io/KRS/sphinx/build/html/docs/install.html#ubuntu-22-04.
No, with Ubuntu you've got three avenues of development: |
@vmayoral I am following the guidelines for Ubuntu 22.04, and after following them, I ran this example: https://xilinx.github.io/KRS/sphinx/build/html/docs/examples/0_ros2_publisher.html#building-creating-the-raw-image-and-running-in-hardware However, when I connect through Putty to the board, instead of getting the expected prompt, I got what the image shows. |
I had upgraded the firmware but I just noticed there is a newer version. I will upgrade and report later if that solves the issue. |
@jasvinderkhurana after upgrading the firmware, I was able to use the official Kria Ubuntu 22.04, but I still have the same issue with the image created by following the tutorial. |
I have succeeded in booting KRS1.0 (petalinux) on KR260 from sdcard. Development Environment: Firstly I have finished the sdcard image creation by the following two instructions: (I have ignored the error while the whole build "$ colcon build --merge-install". And I have just built the KRS1.0 sdcard image partly by "$ colcon build --build-base=build-kv260 --install-base=install-kv260 --merge-install --mixin kv260 --packages-select ament_acceleration ament_vitis vadd_publisher") Then, I have done the two steps after burning the sdcard image:
Currently (KRS1.0) the system.dtb is for KV260. So I have copied the system-zynqmp-sck-kr-g-revB.dtb file as system.dtb into the boot partition. After replacing the system.dtb, device /dev/sda2 appears in the linux kernel message. The file was obtained from the petalinux2022.1 + KR260 BSP:
Then I could find system-zynqmp-sck-kr-g-revB.dtb in the pre-built/linux/images directory. I have used uEnv.txt written below:
The error suffering us was "/dev/mmcblk1p2 is not found". After replacing the system.dtb, /dev/sda2 can be accessed. Then the uEnv.txt file skips the two-staged boot and directly boot using root=/dev/sda2. Integrating this fix into firmware/acceleration_firmware_kr260 is another issue. |
@ohkawatks Thank you so much for helping! I am working with a KV260 and Ubuntu 22.04 but I followed the steps you delined using the petalinux kv260 image. I also had to use system-zynqmp-sck-kv-g-revB.dbt but y renamed it to system.dbt. However, after following the steps I get the same behavior as I previously mentioned |
Can you see /dev/sda, /dev/sda1, and /dev/sda2 after the error? |
This is still broken https://support.xilinx.com/s/question/0D54U00005zHNQHSA4/sd-card-image-from-krs-github-tutorial-does-not-boot?language=en_US&t=1670337200519 Proposed fix of using precompiled system.dtb and uEnv.txt files worked. |
I have encountered the same issue in KR260. |
@mvgianel Hi,
|
Hi @lanyangyang, Thank you for your reply! I was able to get everything working after following your instructions :) |
Hi @ohkawatks, Sorry, I misspelled the file extension here, but it was correct on the board. I was not able to see /dev/sda after adding the uEnv.txt and changing the system.dtb on the sd card. However, after following the instructions bellow I was able to log into petalinux: However, I cannot locate the ros files that I need to source to run my ros2 node: Do you know what could be causing this? |
Great to know for PetaLinux. Is there any way to set up FreeRTOS to boot from SD card? |
you need to modify the partition name to mmcblk0p2 in the uEnv.txt in order to locate the ros files.
|
I followed example 0 to create an SD and use it on the KV260 but instead of getting
xilinx-k26-starterkit-2020_2 login:
I got
/ #
After reseting the board while keeping it connected to my computer I got the following messages:
![image](https://user-images.githubusercontent.com/23347523/195706803-aa6d02f3-fc82-4f1e-8b6c-f1b60cbb2a88.png)
I used Balena Etcher and the linux method described here: https://www.xilinx.com/products/som/kria/kv260-vision-starter-kit/kv260-getting-started/setting-up-the-sd-card-image.html but got the same result.
Does anyone know what could be causing this?
The text was updated successfully, but these errors were encountered: