Post Go back to editing

Linux Boot Error: Failed to start ADI eval system

Category: Software
Product Number: AD4630-24
Software Version: ADI Kuiper Linux 2024-08-27

Hi! 

I was using the EVAL-AD4630-24FMCZ with ADI Kuiper Linux 2021-07-28 in the ACE environment with no problems so far. Last week, I updated the ACE Plugin of the AD4630IIO to version 1.2024.40200 - after connecting the board, the error message appeared that 

the Linux version on the Zedboard is not compatible with ACE anymore: 

I flashed the SD card with the newest ADI Kuiper Linux image (2024-08-27) and copied the boot files of the AD4630 design (BOOT.bin, devicetree.dtb and the zynq-common/uImage) into the root directory as described in the wiki. However, the ZedBoard is not booting correctly anymore:

  • No red LED is blinking, and the blue LD12/Done lights up immediately after the power LED (not after 20-30s as stated for the new versions of Kuiper Linux)
  • The boot log of the ZedBoard shows the error: [FAILED] Failed to start ADI eval system

What is going wrong here? 

Thanks a lot in advance for any help! 

Thread Notes

Parents
  • Hi,  .

    We'll look into this and get back to you. May we know what is the specific version before you update? On the other hand, I will be moving this thread to the Linux Software Drivers forum.

    Regards,
    Jo

  • Hi  

    Is there any news about it? We are blocked in work because since these updates we are not able to evaluate the AD4630 with ACE any further. It would be nice to know if this issue is due to a wrong procedure on our side, or if somebody at ADI is currently looking into the matter. 

    Thank you for a short update.

    Regards, 

    David

  • Hi  

    My apologies for the confusion and the delay in resolving your issue. 
    The issue appears to be caused by our Wiki not being up to date. 

    We had a recent major update to the AD4630 plug in to add Linux Runtime Configuration that allows us to push boot files to the users SD card. This is a feature we will be including in compatible ACE plug ins which enables ACE to reconfigure Linux configuration options (in this case clock mode, data mode, lane mode and data rate) and configure SD cards for the attached daughter board. 
    So when you flash the new SD card image, it comes without any product drivers and ACE will push the appropriate boot files when you open the plug in. 

    This update requires a new SD card image as you saw after updating the plug in and you correctly flashed to your SD card. 
    However the next step of flashing boot files into the root directory is not correct and is likely what is causing your issue. You mention a wiki where you found these instructions, can you link the wiki you were using? We have been updating our documentation and I want to make sure we have all the relevant pages updated. (It may have been updated since you last looked at it) 

    I recommend re-flashing your SD card with the new image, then connecting your hardware with the new SD card and opening ACE. It will still detect the daughter board and when you open the plug in you will get a message saying it needs to push a new kernel. Accept this and ACE will push the file and reboot your ZedBoard. After the reboot your SD card will be correctly configured to work with the ACE plug in. 

    If you are still facing issues after following these steps please let me know ASAP so I can help to solve the issue.

    Regards,
    Cathal 

  • Dear  

    Thank you very much for your answer. Your explanation solved the issue and the AD4630 runs again perfectly fine with ACE and ADI Kuiper Linux 2024-08-27.

    Regarding the wiki:

    I started on this page for downloading the SD card image: ADI Kuiper Linux for Evaluation [Analog Devices Wiki]. This led me to the wiki page on how to write the image to the SD card for Linux hosts: Linux Download and setting up the image [Analog Devices Wiki]. On both ends of paragraph "Writing SD Card GUI" and "Verify" it is written that "the SD card is still not bootable" like this, and one should follow the instructions on this page Analog Devices Kuiper Linux [Analog Devices Wiki] to obtain a bootable image. This is what caused the confusion and why I started copying boot files.

    Again, thank you very much for the clarification!

    Regards, 

    David

Reply Children
No Data