![]() # Loading init Ramdisk from Legacy Image at 04000000. Image Type: ARM Linux Kernel Image (uncompressed) # Booting kernel from Legacy Image at 02080000. SF: Detected s25fl256s_64k with page size 256 Bytes, erase size 64 KiB, total 32 MiB In the meantime, I am building our application (based upon the example code) and I am able to successfully run this on the platform under the Kuiper Image.Īny pointers you can provide would be greatly appreciated I also modified the U-Boot configuration to DISABLE the FALCON mode (bypasses loading u-boot, goes straight to loading uImage, this will hang probing I2c, probably due to missing. (again, my goal here is to "duplicate" the stock setup, but with the buildroot setup with our additions). I modified the kernel configuration to point to the appropriate DTS file for the ZED+RFCOMM4 board in the Xilinx kernel. U-boot is 2018.01 (along with the SPL it builds) - this seems to be the default for this version of buildroot Kernel is Xilinx 2019_R2 - IIO and libiio are enabled. I've modified the (complicated) u-boot parameters to mount the RAMDisk. I removed the uEnv.txt, since it was setting bootargs to mount the RFS on mmcblk0p2, which my image does not. This would seem to indicate that maybe the driver can't find the AD9364 device? Line 4986 in the driver code is the message ( I believe) - Return from clk_set_rate() - called from the Driver PROBE call. The Error I see is: ad9361 spi0.0: Failed to set BB ref clock rate (-22) The system will boot to the login prompt. However, I am still getting driver load failures. This now seems to load successfully on the system. ![]() I then found on-line the Python script to convert this to a. I was able to unpack the boot_sysfiles.tgz file and obtain the. Also, I have not found in any documentation how to "add" this into the U-boot or final Buildroot build, would you have any pointers/references regarding this? bit file for these FMCOMMs boards? A "built" version would be best, but a pointer to source would be OK, as I can have the FPGA engineer then generate the file bitstream for me. what's missing? It seems to me maybe the bitstream is not loaded correctly, or there's some other mismatch. ![]() In the bootlog, I see that the ad9361 driver is successfully probed and loaded, however, when I check /dev/ I only see 2 iio: devices (vs. This time, this will boot to the login prompt. The Kuiper version is a very old (2014) U-Boot. I then replaced the BOOT.BIN file generated in the Buildroot Setup (which was ~ 90KB) with the BOOT.BIN from the Kuiper image for this FMCOMM board (which was ~ 2,7MB). dtb file being output as part of the overall buildroot images, only the devicetree.dtb for the kernel). (there seems to be a default zynq-zed dts file in the uboot tree but I don't see a separate. Spl_load_image_fat_os: error reading image system.dtb, err -2 because again don't have this DTB file. Spl_load_image_fat: Error reading image fpga.bin, err -2 I guess because I don't have this fpga.bin (bitstream) file? ![]() This could be to a mismatch in the DTS file, or missing PL logic. Testing with the ad9364 image, this updated image with the matching DTS file Hangs at the point of detecting (probing?) I2C devices (I believe). I then found in the Xilinx kernel sources the DTS files for these RFCOMM boards, and modified my defconfigs accordingly (I have 2 defconfigs, one for each RFCOMM Board) to build images for each development system. This image will boot on the target ZED board, sans the necessary logic for the RFCOMM boards. After resolving some conflicts regarding "unnecessary" ADI drivers that were being built, I have the requisite output sdcard.img/boot.vfat images. ![]() This image also includes the ad9361 driver and the IIO subsystem. The U-Boot per the Buildroot default is the 2018.1. I am using the Xilinx 2019_R2 Kernel from Github. I have built this using the ZED board defconfig, plus some additional packages (specifically, mysql). I have a Buildroot-2021-02.1 system upon which I am using to generate the overall system for our application (which will utilize the AD9364 device). Both of these setups are working with the Updated -ADI-Kuiper image on 16GB SD Cards. We are developing the Software ahead of the available Hardware design. One has FMCOMMS3 (AD9361), the other has FMCOMMS4 (AD9364). I have 2 development setups, both using ZED Board. This is a multi-faceted questions, if not the appropriate forum, please advise. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |