I cannot access my snickerdoodle via minicom or screen. I get a solid green light and a blinking white light. The white light never stops blinking. I tried booting both with and without a system.bit file (placed it in the BOOT partition and then deleted it). I am trying to upload an image showing my BOOT and ROOTFS partitions, my bootimage.bif (with which I built boot.bin, and my uEnv.txt), but it won’t let me.
How can I upload the image (I will email the image to you guys)? and what am I doing wrong?
If you are seeing a rapidly blinking white LED (not a “breathing white LED”) then there is likely an issue with initialization. Is the snickerdoodle not booting with the standard image or only with the boot.bin that you’ve built?
Addition: I do not have a pre-loaded SD-card with a standard snickerdoodle black image anymore. One of the ones I bought from Crowd Supply was corrupted and the one that came with the snickerdoodle allowed me to log in initially. Once I included a system.bit file that one stopped working, and was not able to recover the SD card. Could it have been semi-corrupted?
I used my own SD card for the situation specified above.
2nd Addition: (I do not want to edit the other comments for the progression of the conversation not to be lost) I checked again and the light is blinking fast. I apologize for the previous misinformation. How can I proceed if this happens?
Your boot image looks a bit strange. Is there a reason you’re including the devicetree, ramdisk, uImage and uboot script in the boot image? The way you’re boot image is specified the FSBL would be responsible for loading the bitstream and then loading U-Boot and continuing to boot. If you are able to boot using a fresh image from HERE and successfully boot then it would indicate an issue with your boot image. Are you using a snickerdoodle or snickerdoodle black? Can you share a bit about the project configuration that you’re using to generate you’re FSBL, etc.?
I am new to this entire process, so pardon my ignorance. I am using a snickerdoodle black. I was including the device tree, ramdisk, uImage and uboot because I thought by default those were necessary for the booting process. I actually don’t have a firm grasp as to what device tree, ramdisk, and uImage do yet or how to configure them properly. I also saw a uEnv.txt file that I’m not sure how to configure either.
I made a basic shift register program in Vivado, which I turned into a system.bit bitstream file and copied to the BOOT partition of the SD card.
Do I need to generate a new fsbl.elf file every time I create a new project in Vivado? I generated one given my shift register program, used it to generate the boot.bin file using bootgen and also moved the fsbl.elf file to the SD card. I am probably performing additional steps that are not needed (Let me know if this is the case). Also, what would constitute a parameter that I would want to modify in FSBL and where and how would I do it?
Also, what do you mean by using a fresh image? Do you mean mapping the downloaded ubuntu image to the ROOTFS directory created on the SD card? I would send you pictures of how things look, but the forum does not let me upload pictures. Is there a way to email those to you?
My end goal is simply to create a very basic test program in the PL and integrate it with a very basic C/C++ program in linux. I just want to be able to get something simple working and build something more complicated from there.
I believe what Bush is asking is if you’ve tried booting the board without modifying anything in the image provided at the link he provided. Based on your description, you shouldn’t need to alter the fundamental structure of the SD card image to implement your Vivado project/s (that’s a pretty advanced topic…).
Oh ok. I understand. Now, how would I get my SD card to that fundamental structure? I do not have my original SD card setup anymore. Do I still need a BOOT and ROOTFS partitions on my SD card? I have downloaded the image. Would it just be a matter of copying that image onto the BOOT partition with no other files? What do I do with the ROOTFS partition?
Also. Assuming I get that working, to run my vivado project would I just have to copy the system.bit file to the BOOT partition?
You can check out the tutorial videos here for instructions on how to format a snickerdoodle SD card (expand the “Prepare and Mount snickerdoodle Prebuilt Linux System on MicroSD Card & Boot” toggle).
I’d try that first to make sure you can get something booting.