No worries, I hope to understand the SPL boot properly though. I will go through some reading and in any case, I will wait when you can look into it. For now, *I managed to boot centOS* using the kernel made with petalinux/yocto, and yes I had problems with rights and properly copying all the files.
You have been a great help and thank you for that! Regards, Piyush D Jadhav
On Tue, May 14, 2019 at 10:28 PM Pablo Sebastián Greco < pablo@fliagreco.com.ar> wrote:
Hi, I've been trying to answer your mail all day, but hasn't been easy ;) El 13/5/19 a las 19:26, Piyush Jadhav escribió:
Hi Pablo,
Sorry for the late reply and thank you for pushing us for getting the serial port repaired, the port was not functioning. Now that we have it working, I have started to debug through the serial communication, but I want to raise some doubts in the process. In the blog, https://wiki.centos.org/SpecialInterestGroup/AltArch/armhfp, the last step is to *dd* the *u-boot-with-spl.bin* file as follows,
dd if=/usr/share/uboot/${boardmodel}/u-boot-sunxi-with-spl.bin of=${sdcard} bs=1024 seek=8 conv=fsync,notrunc
Yeah, that applies to sunxi devices
But is missing how to load the *u-boot-spl.bin *and* u-boot.img. *Could you please shine some light on this for us? I understand that the order has to be ROM code -> SPL -> u-boot -> kernel. Does it means that I have to also dd u-boot.img, like here,
dd if=u-boot-spl.bin of=/dev/sdX bs=1024 seek=8 dd if=u-boot.img of=/dev/sdX bs=1024 seek=*X (?)*
That is a good question, that I don't know the answer to. At the moment I have my hands full with the preparation for 8, and my simple google queries haven't yielded anything interesting.
On the other hand, I also tried to boot with another method using only the centOS Rootfs file (in the root ext4 partition), and the Boot.bin and image.ub files (in boot partitions) which I created using petalinux/yocto. The kernel boots up but falls into the kernel panic, with errors as *cant execute the /sbin/init - (error -8)* -> which refers as permission denied. Please let us know what you think of this too!
That is a good test, and you could try mixing things to see if it boots (maybe that permission denied is caused by a missing driver)
Thanks a ton in advance!
Regards, Piyush
On Thu, Apr 11, 2019 at 10:23 PM Pablo Sebastián Greco < pablo@fliagreco.com.ar> wrote:
El 10/4/19 a las 09:27, Piyush Jadhav escribió:
Hi Pablo,
Thank you very much for the help. Though I performed the same steps from the wiki link, ( https://wiki.centos.org/SpecialInterestGroup/AltArch/armhfp) for Zynq ZC706 using the uboot files you provided and the generic userland image (also the old version with kernel 4.14), but the device *does not* boot up. The DONE leds on the device does not light up at all.
Debugging these things without a serial console tend to be hard, because you're flying blind.
At this point I tried the generic userland image files on also the raspberry pi3b+, even the raspberry *does not* boot up. Although userland image provided for particularly raspberry works as expected and boot into the device.
Yeah, the rasbperrypi images are really specific for those rpi, it would be a miracle if those worked on other devices.
I also see that the userland generic image creates three partitions on the drive, two of which are for boot, which does some procedure to detect the board automatically. I was wondering, if it is possible for you to guide me how I can create single boot partition, using the files you provided.
There should be 4 partitions actually 1 vfat, for rpi boot with generic kernel 2 /boot 3 swap 4 /
There is high possibility that I am doing something wrong. Please let me know what you think,
As I said before, the first thing would be getting the serial console working, with any distribution, just to be able to see the device booting. Then, I'd try just to make uboot work, even without an OS image, just an SD card without any other data or partitions. Only after all that is working, it should be easier to start testing an OS.
Regards, Piyush D Jadhav
On Tue, Apr 9, 2019 at 2:49 AM Pablo Sebastián Greco < pablo@fliagreco.com.ar> wrote:
El 8/4/19 a las 12:28, Piyush Jadhav escribió:
I am a begineer in using the Zynq 7000 ZC706 SoC. I have already booted linux made with Yocto project with meta-xilinx and PREEMPT-RT layers. Everything is working as expected. Though we are not satisfied with the real time performance on Scheduler and Latency tests, however alternatively it could be interesting to compare with another OS like CentOS.
I have followed the procedure on described here to install CentOS using the rootfs files made with yocto and the files in /boot (boot.bin + UImage
- dtb).https://github.com/umiddelb/aarch64/wik ... ch64-board
But I am not able to successfully create the OS. I am not having a serial communication with the board, so I cant debug further. I will/can only have a SSH communication once the OS boots up.
Does anyone guide me how can I take this ahead?
I could not find anything aarch64 for that device, all I found was 32 bits. That said, it seems to have mainline uboot and kernel support (zynq-zc706.dts), so it could be installed using the steps here https://wiki.centos.org/SpecialInterestGroup/AltArch/armhfp Since we usually don't build uboot for that device, I made a version for you to test, and left it here https://people.centos.org/pgreco/zynq-zc706/ The normal images provided by CentOS use kernel 4.14, but if you need an image with a newer version, we have this test image here https://armv7.dev.centos.org/repos/images/CentOS-Userland-7-armv7hl-generic-... which uses 4.19
Please let us know how it went.
Thanks. Pablo.
HTH. Pablo.
Pablo.
-
Piyush Jadhav