m3atwad

Members
  • Content Count

    23
  • Joined

  • Last visited

About m3atwad

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. ok cool! Glad you're up and running!
  2. This also could be of help. This was another member of the Digilent forums helping me with tftpboot
  3. Here are some of my useful project files. recover.dts is my uncompiled final device tree blob. I uncompile it with hte dtc tool so I can see what the final device tree looks like. My ultimate goal for this first step is to just get to the point where the kernel attempts to load the driver and initialize the MAC and fails. Oh and I also added the mdio and phy part by hand based on the following https://www.xilinx.com/support/answers/61117.html It isn't the same use case as I'm working in PL, but I think it was the right direction and I subbed in my PHY which is the marvell,88e1510. recover.dts design_1_wrapper.xsa system-user.dtsi
  4. Hello, I'm trying to get my temac ethernet mac up and running in the PL for the zedboard. I bought the quad eth board from ospero and the zedboard and the TEMAC MAC IP. When I instantiate the temac core petalinux only puts in a very small entry in my device tree and when linux boots it doesn't seem to try to load the driver. In working on this I've got a few general questions to help my understanding. I've read that Xilinx says you have to add the MDIO and PHY part of the device tree for the eth yourself manually - the tool (petalinux) doesn't do that. 1. Where in the petalinux-config -c kernel menu do you enable the temac core drivers? I can't find out where to enable the XILINX_LL_TEMAC #define 2. I will repost my device tree so far below. How do you figure out what gaps there are and how to fill them in? Should I be using the petalinux-config menus to tell petalinux how to create the correct device tree? For example, the device tree links between the DMA and the TEMAC MAC IP? 3. I think I have the 'compatibility' string set correctly so why isn't the kernel trying to probe this on boot? There is nothing in dmesg after boot that references this PL IP MAC. 4. Should I be using the axi ethernet subsystem driver when I'm using the stand alone Xilinx TEMAC MAC in my PL design or should I be using a TEMAC specific driver? I notice here: https://github.com/Xilinx/linux-xlnx/tree/master/drivers/net/ethernet/xilinx Xilinx has both the axi ethernet subsystem and the ll_temac driver. Since I'm using the TEMAC IP I figured I should use the ll_teamc driver? Right now I'm just trying to get linux to attempt to probe the TEMAC MAC on boot. It isn't doing that right now, it only loads the standard ethernet mac in the PS that is default to zedboard. I've attached a screenshot of my current PL device tree entries for the dma and temac core.
  5. Hi, The first step is to verify your tftp server is stable via another machine (laptop, desktop etc...). I setup that first independant of the zynq. From there you work through the tftp boot and I do the following flow. 1.Set hardware boot settings (jumper) to boot from jtag 2. run xsct and connect to your chip 3. run FSBL 4. download uboot to it 5. execute con to continue to run ARM #0 6. look at terminal and see boot. Make sure your tftp server has the files you need with the correct names. As an example, make sure your fpga bitstream is there with the right name or boot will hang. You can also verify this gets loaded by checking the prog done pin (usually has LED for most dev boards).
  6. Hi lonel, Thanks so much - this has been a huge help and I now have my zynq up and running! I'm going to play around with different boot options for a little while as well and test some of your recommendations out! Thanks again!
  7. I load FSBL (I think) via jtag using ps7_init.tcl My process is below: 1. Connect via jtag using xsct 2. Load ps7_init.tcl and run ps7_init 3. dow u-boot.elf 4. execute 'con' command 5 switch over to console and interact with u-boot. 6. Launch kernel boot process via tftpboot calls I'm trying to avoid the sd card while i'm developing the images and learning/researching and testing stuff with petalinux. The jtag approach seems more streamlined because I can do it all via ethernet from my build machine using tftp. I have also finally gotten the zynq to boot into linux following your advice! My problem was a missing PL bitstream that caused the boot process to hang. I am thinking that the gpio IP core in PL that has an axi interface wasn't there causing the bootprocess to hang.
  8. Ok - so would I add a new recipe to overwrite this? I've found the file in build/tmp/deploy/images/zedboard-zynq7/uEnv.txt. Also - can the tftpboot command pull down the uEnv.txt file from my tftp server even though it isn't an image like image.ub, uImage etc...?
  9. Hi lonel, Thanks so much for the help! That makes senese! Do you know how to modify uEnv.txt in petalinux? Since I'm using tftp boot I'd like to clean up my uEnv.txt as you've described. I think the correct way to do this is to have petalinux produce an accurate uEnv.txt file with all my build images. I see that petalinux does in fact produce a uEnv.txt after the build. Do you know how to apply modifications to uEnv.txt via petalinux so that the petalinux build produces a correct one for my application along with the output products?
  10. Hi lonel, Thanks for the help! I have found my uEnv.txt as shown in the screenshot in case anyone else is looking for the location in a petalinux project. See attached screenshot. lonel - I have environment variables defined in platform-top.h and in uEnv.txt and some are the same. Should I get rid of uEnv.txt and just use platform-top.h (attached) or should I switch to just using uEnv.txt? It seems like you could use either and I am getting confused with both of these two things being applied. One last thing - How did you choose the fpga bitstream address of 0x10000000? How does uboot know to get the image from that address and where does it send the bitstream data - what interface gets that bitstream into the PL section? platform-top.zip
  11. Hi Lonel, Thanks for the reply. Where can I find the location of uEnv.txt? Can I view and verify this from uboot? The only commands I run from uboot are 'run netboot'. Where is tftp_boot supposed to be run from?
  12. Hello, I have a basic zedboard design using the following steps. 1. Create vivado project for zedboard using the zedboard template (accessed by double clicking on zynq block in BD -> templates -> zed board. 2. I added a gpio for the LEDs 3. Validate design and build with no problems. 4. Export .bit and .xsa file to petalinux project. 5. Create petalinux project based on #4 vivado files. 6. Build petalinux project. I am trying to use tftp boot. I can verify the tftp server is working because I see uboot open image.ub, the kernel load and attempt to boot. My boot process hangs as shown in attached screenshot 22.jpg. I actually think my problem is that I'm not loading the FPGA bitstream and because there is an axi lite gpio block it is causing the boot process to hang. I know when I build images for the sd card I manually run a command that packages the fpga.bit file into the BOOT.bin. This is a very simple 'hello world' test project so I think I'm missing something obvious like this. I am using xsct command console to load the ps7_init.tcl, dow u-boot.elf and then I execute the 'run netboot' command. This downloads image.ub and extracts it but I think the fpga bitstream is left out. I can see the tftp / image.ub process working as shown in screenshot 23.jpg. So I'm thinking after I get to the uboot prompt I need to load the fpga bitstream so my question is the following. 1. How do I load the fpga bitstream - what command is it? I've found fpga loadb, but am confused as to how to use it. 2. How do I know where to put the fpga bitstream? 3. How do I read it from the tftp server I have?
  13. ok thats it. I kept seeing "ramdisk" online and didn't realize it was initramfs. Thanks!
  14. Hello, This is probably a general question, but I have a zed board and I've gotten it booted and I've also gotten it to boot off of a somewhat custom image. I noticed the sdcard/images that come with the zedboard are a few files on the card I believe is the typical ramdisk image files that are loaded and run out of ram. If you reset the board everything goes back to the fresh ramdisk image. The image I built myself seems to unpack the rootfs to another partition on the sdcard I'm using. I then screwed something up and it didn't unmount correctly and isn't booting smoothly. So long story short - where do I specify that I want the image unpacked into ram and run solely out of there? I'm a little new so I'm sure I'm missing something obvious here. I've looking in "petalinux-config -c rootfs" and don't see anything there. I also don't see anything in the kernel config GUI in petalinux. Thank you for any help!
  15. A little more info - I want to pair it with this FMC card from ADI. https://wiki.analog.com/resources/eval/user-guides/ad-fmcmotcon2-ebz/introduction Also - do I need the SoC voucher?