Forums » Software Development »
Building BSP for 5cse
Added by Sam Anderson almost 8 years ago
I am trying to follow your documentation for using Yocto to build an image for the 5CSE on the dev board carrier, and having nothing but trouble.
I have followed the exact instructions on your support page, and successfully compiled an image, but there seems to be conflicts.
When I untar that rootfs onto the sd card where the old rootfs used to be, then boot the card, I get flooded with the following error after the device boots.
eth0: Could not attach to PHY
stmmac_open: Cannot attach to PHY (error: -19)
libphy: PHY stmmac-0:ffffffff not found
My best guess is that this is due to a mismatch of the device tree used in the u-Boot on the original sd image, which leads to my next questions, of why in the world the u-boot and preloader generation are not being done in Yocto?
I have used the instructions from the support page to generate uboot and preloader with similar effects.
I guess my main question is, are there a complete set of instructions to build an complete image that actually works for this combination of hardware?
Replies (4)
RE: Building BSP for 5cse - Added by Alexander Block almost 8 years ago
Sam,
I believe that the issue you ran into if following the Yocto wiki steps is that you may have selected the "mitysom-5csx" machine type as shown in the instructions. In your specific case you would actually want to select the "mitysom-5cse" machine type as that corresponds to the 80-000708 dev kit.
We have updated the Yocto wiki page to cover the different module types during the filesystem build process (https://support.criticallink.com/redmine/projects/mityarm-5cs/wiki/Yocto_for_MitySOM-5CSX).
After performing a build with the correct machine type you should be able to untar the rootfs onto the SD card and boot properly.
Let us know if that doesn't resolve your problem and we'll continue looking into it further.
Thanks,
Alex
RE: Building BSP for 5cse - Added by Sam Anderson almost 8 years ago
Hi Alex,
I selected the 5cse for the build, not the 5csx. I have done this full build no fewer than 3 times with what I believe to be the correct settings, and had consistently non-functional results.
I will try the updated instructions, but if there is anything you can add as I do that, I would appreciate it.
RE: Building BSP for 5cse - Added by Daniel Vincelette almost 8 years ago
Hi Sam,
I'm currently re-running the yocto build here to see if I can recreate the issue you are seeing. I will update when I have a result.
Dan
RE: Building BSP for 5cse - Added by Daniel Vincelette almost 8 years ago
Hi Sam,
I've been able to recreate what you're seeing. It looks like the devicetree generated through yocto is named socfpga_mitysom5cse_devkit.dtb and what uboot is looking for on the SD image that ships with the 5CSE devkit is socfpga_mitysom5csx_devkit.dtb. The newer version of the 5CSE SD card uses the newer socfpga_mitysom5cse_devkit.dtb naming scheme and can be downloaded from: https://support.criticallink.com/redmine/attachments/download/9458/MitySOM_5CSE_L2_3Y8_Dev_Kit_Release_1.zip.
I'm currently working on cleaning up the documentation to make it more clear on how to take all the individual components and fully recreate an SD card image from scratch, there is a script in the link above called make_fs_image.sh that takes the preloader/uboot/uboot environment/rootfs/fpga image and creates the image to binary copy onto a SD card but it needs some clarification.
To answer your question of why yocto doesn't do the uboot/preloader build is because both require files generated from the quartus build of the FPGA, these handoff files change depending on what pin mux options are chosen through the qsys setup of the HPS.
